Form-Encoded Proxy Requests
Forward form-encoded requests to payment processors like Elavon.Request Format
Alternative: Headers
Pass all metadata via headers:| Header | Required | Description |
|---|---|---|
Content-Type | Yes | application/x-www-form-urlencoded |
X-Token | Yes | Token to use |
X-Proxy-URL | Yes | Target endpoint |
X-CVC-Session-ID | No | CVC session for CVV |
Placeholders
Placeholders work in form data:Examples
Elavon/Converge
Authorize.Net (AIM)
NMI
Response
Form responses vary by gateway:Delimited Response
Name-Value Pair Response
Parsing Responses
Delimited
Name-Value Pairs
URL Encoding
Special characters in values are automatically URL-encoded:| Character | Encoded |
|---|---|
| Space | %20 or + |
& | %26 |
= | %3D |
+ | %2B |
Date Format Variations
Different gateways expect different expiration formats:| Format | Example | Placeholder Combination |
|---|---|---|
| MMYY | 1225 | ${expirationMonth}${expirationYear} |
| MM/YY | 12/25 | ${expirationMonth}/${expirationYear} |
| MMYYYY | 122025 | ${expirationMonth}${expirationYear} (4-digit year) |
| YYYY-MM | 2025-12 | ${expirationYear}-${expirationMonth} |
Best Practices
1. URL-Encode Properly
Ensure special characters in non-card fields are encoded:2. Check Response Format
Gateways return different formats:- Delimited (pipe, comma)
- Name-value pairs
- XML
- JSON
3. Handle Gateway-Specific Errors
Next Steps
- JSON Requests - Modern API format
- XML Requests - SOAP/XML format
- CVC Sessions - CVV handling