PayNext acts as an abstraction layer between your application and payment processors. Connect multiple processors, enable various payment methods, and manage everything from a single Dashboard—while your code interacts with one consistent API.
Always configure and test processors in sandbox first. Each processor page includes sandbox resources and test credentials. Processor Details
Every processor page includes a details table showing capabilities:
| Field | Description |
|---|
| Payment Methods | Which payment methods the processor supports |
| Supported Currencies | Link to the processor’s currency documentation |
| Metadata Mapping | Whether custom fields can be forwarded to the processor |
| Network Tokens | Whether PayNext can use network tokens with this processor |
| Fraud Support | Processor’s fraud prevention tools (e.g., Stripe Radar, Braintree Fraud Tools) |
| 3DS Support | Whether the processor accepts 3D Secure authentication data |
| 3RI Support | Whether the processor supports 3RI for recurring payments |
| Status | Meaning |
|---|
| ✓ | Fully supported — All metadata fields can be mapped to processor fields |
| ✓ (Limited) | Limited support — Only specific fields are available due to API constraints |
| ✗ | Not supported — Processor does not accept custom metadata |
Need additional metadata mappings for a processor with limited support? Contact our support team—we can add new variables quickly.
Network Tokens
Network tokens replace raw card numbers with tokens that update automatically when cards expire or are reissued. PayNext creates and manages network tokens—they work across any processor that supports them. This reduces declines and improves authorization rates for recurring payments.
Enable network tokens for all processors that support card payments. Contact your processor representative to activate this feature, then enable it in Dashboard → Integrations → [Processor].
3DS
To enable 3D Secure authentication, you need the merchant CAID (Card Acceptor ID) and BIN (Bank Identification Number) for each card scheme (Visa, Mastercard, etc.). Request these from your processor representative and configure them in Dashboard → Integrations → [Processor] → 3DS.
See the 3D Secure guide for authentication flows and configuration details.
How PayNext Works
When you process a payment through PayNext:
- Your application calls the PayNext API with payment details
- PayNext routes the request to the appropriate processor based on your workflow rules
- The processor (Stripe, Braintree, PayPal, Unlimit) authorizes and settles the payment
- PayNext normalizes the response and stores it in a unified format
This architecture means you write integration code once. Adding a new processor or payment method requires only Dashboard configuration—no code changes.
Unified Data Model
Each processor returns data in its own format. PayNext normalizes everything into a standard schema:
| What PayNext unifies | Benefit |
|---|
| Payment statuses | Unified statuses work the same across all processors |
| Payment methods | Cards, wallets, and alternative methods share a consistent structure |
| Customer records | Single customer profile links payment methods from any processor |
| Transaction history | One ledger for all payments regardless of processor |
| Webhook events | Standardized event types (payment.created, payment.settled) for all processors |
Processors and Payment Methods
PayNext separates two configuration layers:
| Processor | Payment Method |
|---|
| Role | Authorizes payments, processes refunds, settles funds | Collects payment details from customers |
| Examples | Stripe, Braintree, PayPal, Unlimit | Cards, Apple Pay, Google Pay, Venmo |
| Configuration | API credentials in Dashboard → Integrations | Enable/disable in Dashboard → Checkout |
