Gateway agnostic recurring payments
Break free from processor lock-in. Use Network Transaction IDs to route MIT payments across multiple gateways for better success rates, cost optimisation, and resilience.
Gateway agnostic MITs
Enable gateway-agnostic MIT routing and Orchestration handles the technical details. Your saved payment methods work across any supported processor - you just use the payment_method_id and Orchestrator routes to the best available gateway.
Simple integration
Enable the feature, save cards normally, charge with payment_method_id. Orchestration does the rest.
Multi-gateway routing
Route each MIT payment to any supported processor based on cost, success rate, or region.
Automatic retry
If one processor declines, automatically retry through another without customer action.
How it works
Enable the feature
Enable connector-agnostic MIT on your business profile. This allows Orchestration to route MIT payments across multiple processors.
POST /account/{merchant_id}/business_profile/{profile_id}/toggle_connector_agnostic_mit
Content-Type: application/json
{
"enabled": true
}Save card (customer present)
Create a payment with setup_future_usage: "off_session". After 3DS authentication, the card is saved and ready for cross-processor MIT charges.
POST /payments
{
"amount": 6500,
"currency": "ZAR",
"setup_future_usage": "off_session",
"customer": { "id": "cus_subscription_user" }
}MIT payment (customer not present)
Charge the customer using the saved payment_method_id. Orchestration routes to the best available processor automatically.
POST /payments
{
"amount": 6500,
"currency": "ZAR",
"off_session": true,
"confirm": true,
"recurring_details": {
"type": "payment_method_id",
"data": "pm_xxx"
}
}Smart retry across gateways
Configure routing rules to automatically retry failed MIT payments through alternate processors. Orchestration maintains authorisation context across all retry attempts.
Routing configuration
Configure routing rules in the Peach Payments Dashboard to optimise MIT payment success:
- Primary processor based on cost or success rate
- Fallback processors for automatic retry on soft declines
- Region-specific routing for international customers
Supported processors
Gateway-agnostic MIT routing is supported on the following processors:
How Orchestration handles it
You don't need to manage the technical details. Orchestration automatically:
During initial payment
- ✓Captures authorisation chain data from card networks
- ✓Stores payment method securely in PCI-compliant Vault
- ✓Returns payment_method_id for future charges
During MIT payment
- ✓Routes to best available processor based on your rules
- ✓Includes authorisation chain data automatically
- ✓Retries across gateways on soft declines
Ready to get started?
Try the interactive Gateway Agnostic MIT flow to see how cross-processor recurring payments work.
Try Gateway Agnostic MIT Flow