Skip to main content
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:

​
Metadata Mapping

Metadata mapping lets you forward custom fields (device fingerprints, risk signals, customer attributes) to your processor. Support varies:
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:
  1. Your application calls the PayNext API with payment details
  2. PayNext routes the request to the appropriate processor based on your workflow rules
  3. The processor (Stripe, Braintree, PayPal, Unlimit) authorizes and settles the payment
  4. 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: Your reporting, analytics, and business logic work against this unified model—not processor-specific data structures.

​
Processors and Payment Methods

PayNext separates two configuration layers: Each processor supports specific payment methods. The processor pages document which methods are available and how to configure them.