Skip to main content

Form-Encoded Proxy Requests

Forward form-encoded requests to payment processors like Elavon.

Request Format

Alternative: Headers

Pass all metadata via headers:

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: Card numbers don’t contain these, but other fields might.

Date Format Variations

Different gateways expect different expiration formats: Check your gateway’s documentation for the expected format.

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