Base URLs
Sandbox
Production
Authentication
All API requests require RSA-SHA256 signature authentication. Every request must include these headers:Signature Construction
The signature is computed over a signing string built from:For detailed signing implementation with code examples in Node.js, Python, and Java, see Authentication & Environments or the Authentication Deep Dive.
Request Format
All requests use JSON with the following conventions:- Amounts are strings holding a positive integer in minor units (cents). Example:
"1250"= €12.50 - Timestamps use ISO 8601 format in UTC (with
Zsuffix) - IDs must be unique per transaction. The idempotency key is
paymentRequestIdfor Retail Pay andorder.merchantTransIdfor Create QR Order and Link Pay Create (see Idempotency)
Example Request Body
Response Format
All responses include aresult object indicating the outcome:
Success Response
Result Status Codes
Available Endpoints
Payments
Webhooks
Error Handling
When a request fails, the response includes error details:Error Response
Common Error Codes
For complete error reference, see Error Handling & Result Codes.
Rate Limits
Testing in Sandbox
The sandbox environment simulates the full payment flow:- Create payments using test credentials
- Simulate user actions - payments auto-complete after creation
- Receive webhooks to your configured endpoint
- Query status using the Inquiry API
SDK & Code Examples
Complete signing and API client implementations are available in the Authentication Deep Dive:- Node.js -
RebellClientclass with full signing - Python -
RebellClientclass with cryptography library - Java - Signing utilities and HTTP client examples
Related Documentation
Quick Integration Guide
Step-by-step integration walkthrough
Authentication Deep Dive
Detailed signing implementation
Webhooks
Webhook setup and signature verification
Error Handling
Complete error codes reference