JSON Proxy Requests
Forward JSON requests to payment processors.Basic Request
Request Fields
| Field | Type | Required | Description |
|---|---|---|---|
token | string | Yes | The token to use |
cvc_session_id | string | No | CVC session for CVV |
proxy_url | string | Yes | Target PSP endpoint |
request_data | object | Yes | Request body with placeholders |
http_headers | object | No | Headers to include |
http_method | string | No | HTTP method (default: POST) |
Placeholders
Placeholders are replaced with actual card data:Available Placeholders
For Cards:| Placeholder | Description |
|---|---|
${cardNumber} | Full card number |
${expirationMonth} | 2-digit month (01-12) |
${expirationYear} | Year (2 or 4 digit) |
${cvv} | Security code |
${cvc} | Alias for cvv |
| Placeholder | Description |
|---|---|
${accountNumber} | Account number |
${routingNumber} | Routing number |
Examples
Stripe
Adyen
Braintree
Response
The proxy returns the PSP’s response:Response Fields
| Field | Description |
|---|---|
success | Whether proxy succeeded |
proxy_response.status_code | HTTP status from PSP |
proxy_response.headers | Response headers from PSP |
proxy_response.body | Response body from PSP |
Error Handling
PSP Returns Error
success: true means the proxy worked. Check status_code for PSP errors.
Proxy Error
Best Practices
1. Always Include CVC Session
Most PSPs require CVV for card-not-present transactions:2. Set Appropriate Headers
Match the PSP’s expected format:3. Handle PSP Errors
Next Steps
- XML Requests - SOAP/XML proxying
- Form-Encoded Requests - Form data proxying
- CVC Sessions - CVV handling