Intelligent Routing
Route payments across your processor relationships to improve approval rates, instead of depending on one provider's decisions.
Payment orchestration is a layer between your checkout and your payment processors. Instead of sending every payment to a single provider, it chooses where each payment should go and keeps you processing when a provider has an outage. Soap gives you that layer through one integration, with 15+ processor relationships, fraud controls, and reporting built in.
Intelligent routing across 15+ processor relationships
Multi-processor redundancy with automatic failover
One integration for cards, wallets, bank payments, and payouts
Route payments across your processor relationships to improve approval rates, instead of depending on one provider's decisions.
Move traffic away from a processor that slows down or goes offline, without changing your checkout.
3D Secure, device signals, and real-time risk scoring run before a payment reaches any processor, so every route gets the same protection.
See approvals, declines, disputes, and payouts from every processor in one dashboard, instead of reconciling separate reports.
The compliance and risk surface processors actually ask about — wired into one integration.
Soap is a fit for teams managing high-frequency payments, more complex settlement paths, or tighter operational and compliance requirements than standard checkout stacks can handle.
Growing e-commerce and subscription businesses that have outgrown a single processor
Platforms and marketplaces that collect payments and pay out to sellers or providers
Businesses selling internationally that need higher approval rates for foreign cards
Teams that want a backup processor ready before an outage or account review, not after
Payment orchestration is software that sits between your checkout and the companies that actually process your payments. A business without it connects to one processor, and every payment depends on that processor's approval decisions, uptime, and pricing. With an orchestration layer, the business connects once, and the layer connects to many processors. For each payment it decides which processor to use, what to do if the payment is declined, and where to send traffic if a processor has problems. The checkout looks the same to your customers. What changes is how many payments get approved and how exposed you are to any one provider.
One processor is usually enough at the start. Orchestration starts to pay for itself when payments become a large part of revenue and small changes in approval rate are worth real money. Common signs: approval rates that drop for certain card types or countries, customers abroad whose cards are declined more often, a processor outage or account review that stopped sales for hours or days, or the need to add a second processor without rebuilding checkout. If any of these sound familiar, a single integration that can reach several processors removes the risk of depending on one.
Soap connects to 15+ processor relationships and chooses a route for every payment, with the goal of approving as many good payments as possible. When a processor slows down or goes offline, traffic moves to healthy routes automatically. Your team sets the rules in one place, and every route keeps the same fraud checks and reporting.
Sending payments to several processors should not mean managing several fraud setups. Soap runs 3D Secure, device signals, and real-time risk scoring before a payment is routed, so every processor receives the same screened traffic. Merchant onboarding uses AI-assisted KYC and KYB review, and onboarding takes days, not weeks, for approved merchants.
Soap's orchestration covers the major card networks, digital wallets such as Apple Pay and Google Pay, and bank payments, plus payouts to cards and bank accounts. Adding a payment method or a processor is a configuration change on Soap's side, not a new integration project for your developers.
A payment orchestration platform connects your business to many payment processors through one integration. It routes each payment to the best processor, retries declined payments, fails over when a processor has an outage, and gives you one view of all payment activity.
No. A payment gateway passes payments to one processor. A payment orchestration layer works above gateways and processors, deciding which one each payment should go to and handling retries and failover between them.
Processors approve different payments at different rates, depending on the card, country, and amount. An orchestration layer can send each payment where it is most likely to be approved, instead of relying on one processor for every card and country.
You integrate with Soap once, through its API or hosted checkout. After that, adding processors, payment methods, or routing rules does not require changes to your checkout.
Soap detects processors that are failing or slow and moves traffic to healthy routes automatically, so you keep accepting payments during an outage.
Onboarding takes days, not weeks, for approved merchants. AI-assisted review checks your documents as you submit them, and Soap's team handles anything that needs a closer look.
Soap brings routing, onboarding, fraud controls, and compliance operations into one stack so teams can scale without duct-taping more infrastructure together.