Cross-border settlement benchmark — aggregate
Corridex-orchestrated cross-border payments settle in a median of ~2.4 min (P95 ~5.0 min) at 99.1% end-to-end success across ~320K tx/mo, versus an industry average of ~14.8 min median at 97.3% success (Jan–Mar 2025). Illustrative benchmark data.
Settlement time by corridor
- USD to EUR: median ~2.4 min on modern rails, ~35 min over SWIFT, 99.2% success.
- USD to GBP: median ~2 min on modern rails, ~40 min over SWIFT, 99.4% success.
- USD to INR: median ~1.6 min on modern rails, ~1.0 hr over SWIFT, 98.9% success.
- USD to MXN: median ~1.8 min on modern rails, 99.1% success.
- USD to SGD: median ~2.3 min on modern rails, ~37.5 min over SWIFT, 99.3% success.
- EUR to GBP: median ~1.5 min on modern rails, ~32.5 min over SWIFT, 99.5% success.
- GBP to USD: median ~1.8 min on modern rails, ~39.2 min over SWIFT, 99.4% success.
- GBP to EUR: median 85 sec on modern rails, 99.6% success.
- SGD to USD: median ~2.1 min on modern rails, 99.2% success.
- SGD to INR: median ~2.3 min on modern rails, 98.3% success.
- AUD to USD: median ~2.6 min on modern rails, 99.1% success.
- CAD to USD: median ~1.6 min on modern rails, 99.3% success.
- USD to BRL: median ~3.3 min on modern rails, 97.9% success.
- USD to CNY: median ~53.3 min on modern rails, ~53.3 min over SWIFT, 96.8% success.
- EUR to USD: median ~1.9 min on modern rails, 99.4% success.
- JPY to USD: median ~2.9 min on modern rails, 98.7% success.
- USD to AED: median ~2.7 min on modern rails, 98.4% success.
Key Findings from Latest Benchmarks
Partner networks outperform traditional rails by 2.3x in settlement speed while maintaining 99%+ success rates
Median settlement times range from 85s (EUR→GBP) to 3600s (USD→CNY) depending on corridor and connector type
Corridex orchestrated routing achieves 99.1% success rate with 142s median settlement across all corridors
Industry average success rate of 97.3% shows significant room for optimization through intelligent routing
What These Benchmarks Measure
Transparent performance metrics across six critical dimensions of cross-border payment orchestration
Success Rates
Track payment success across all corridors and connectors
Settlement Speed
Measure median, P95, and P99 settlement times
Uptime SLAs
Platform availability and reliability commitments
Corridor Coverage
Global payment routes with transparent performance data
Data Transparency
Monthly updates with documented methodology
Methodology
Real production transactions with statistical validation
Methodology & Data Sources
How Benchmarks Are Collected
All benchmark data is collected from live production transactions processed through Corridex's orchestration platform. We measure end-to-end timing from the moment a payment is accepted through our API to confirmed settlement at the destination.
- Success Rate: Percentage of payments reaching final settlement without manual intervention
- Median Time: 50th percentile settlement time (typical case)
- P95/P99: 95th and 99th percentile times (worst-case scenarios for SLA planning)
Data Quality & Validation
To ensure statistical validity and reliability, we apply rigorous validation criteria to all published benchmarks:
- Minimum volume: 1,000+ transactions per corridor per month for statistical significance
- Outlier filtering: Remove anomalies from system downtime or exceptional events
- Consistent methodology: Same measurement approach across all connectors and time periods
- Monthly updates: Rolling 30-day windows with documented data coverage periods
How to Interpret These Benchmarks
Understanding what these numbers mean for your payment operations:
- Compare corridors: Identify fastest routes for your specific currency pairs
- Evaluate connectors: Partner networks typically faster than traditional rails (SWIFT)
- Plan SLAs: Use P95/P99 times to set realistic customer expectations
- Anonymization: Connector names (Partner A, PSP 1) maintain neutrality while preserving type clarity
Need Custom Benchmark Analysis?
Request detailed performance reports for specific corridors, volume bands, or use cases not shown in public benchmarks