Gateway agnostic MITs
Route MIT (Merchant-Initiated Transaction) payments across multiple processors for better success rates and resilience. Enable this feature and Orchestration handles the technical details - your saved cards work across PeachPayments, ACI, and Cybersource.
Why gateway agnostic?
Traditional recurring payments lock you to a single processor. Gateway-agnostic MITs let you route charges to any supported processor for better success rates and redundancy.
Why gateway agnostic?
Traditional recurring payments lock you to a single processor. Gateway-agnostic MITs let you route charges to any supported processor for better success rates and redundancy.
Processor flexibility
Route MIT payments to any supported processor (PeachPayments, ACI, Cybersource) instead of being locked to the original gateway.
Higher approval rates
Orchestration maintains authorisation chain data that issuers recognise as legitimate recurring charges, improving approval rates.
Automatic retry
If one processor declines, automatically retry through another without re-authenticating the customer. Critical for subscription businesses.
No connector lock-in
Optimise routing based on cost, success rates, or geography. Switch processors without asking customers to re-enter cards.
Built-in redundancy
If your primary processor has downtime, MIT payments automatically route to backup processors. No single point of failure.
How it works
Supported Processors
Currently supported on PeachPayments, ACI, and Cybersource. Orchestration handles the technical details of cross-processor routing.
Automatic Token Management
Orchestration captures and stores network transaction identifiers during the initial payment. You just use payment_method_id - the rest is automatic.
Enabling the Feature
Enable via API: POST /account/:merchant_id/business_profile/:profile_id/toggle_connector_agnostic_mit with {"enabled": true}
Routing Configuration
Use metadata fields to configure different routing rules for CIT vs MIT payments, enabling smart processor selection.
Without Mandates
Without gateway-agnostic MITs, you're locked to a single processor. If that processor has downtime or high decline rates, you have no fallback.
Best Practices
- Enable connector_agnostic_mit on your business profile before saving payment methods
- Configure routing rules to try multiple processors for MIT payments
- Use metadata to differentiate CIT vs MIT for smart routing
- Monitor decline rates per processor and adjust routing accordingly
- Set up fallback processors for automatic retry on soft declines
This step doesn't require an API request.