Every partner wins on something.
One is cheaper, one is faster, one needs no prefunding. The trade-off changes per payment.
Your policy decides, and the reasons are kept.
Every stablecoin payment touches several partners, each with its own quote, status, and reference. Open Passage sits on top of the partners you already use, from pay-in to payout. For each payment it picks the route that fits your rules, then gives your team one view from quote to settlement. Your partners move the money; we never hold it.
Works across the stack you already run
Each new partner opens a corridor or trims a cost. It also brings another integration, another dashboard, and another place a payment can stall.
One is cheaper, one is faster, one needs no prefunding. The trade-off changes per payment.
Your policy decides, and the reasons are kept.
IDs, fees, and statuses come back in different shapes for the same payment.
One view across every partner.
One partner waits on funding or compliance, and your customer notices first.
Live status from every partner, and a needs-attention queue.
Amounts and references across partners are matched by hand.
A ledger export with every reference and event.
You approve. Your partners move the money. We track every step.
Connect the pay-in, FX, and payout partners you already work with. Your contracts stay yours.
Set up once in the console. Partner credentials never pass through the API.
When a partner degrades, it drops out of routing and payments move to routes that still pass your policy.
See what each partner in a route costs, not one blended number.
Policy changes, approvals, and route decisions on one audit trail, with roles for who can do what.
Open Passage picks the route and tracks every step alongside your partners, never between you and your money.
Routes are ranked by your policy, not by partner deals.
Partner relationships and terms stay yours.
Money moves between you and your partners.
Roles, an audit trail, signed webhooks, tenant API keys, and no partner credentials through the API.
Request a route, record the payment, and receive signed status events from every partner.
{
"status": "recommended",
"selected": {
"routeId": "route_2",
"legs": [
{ "role": "fx", "partner": "Partner C" },
{ "role": "payout", "partner": "Partner D" }
],
"totalFee": "USD 0.51",
"settlement": "same_day"
},
"excluded": [
{ "routeId": "route_1", "reason": "Requires prefunding." },
{ "routeId": "route_3", "reason": "Settlement exceeds same day." }
],
"rationale": "Only route 2 settles same day without prefunding."
}Still deciding whether this belongs in your stack? These are the questions that usually come up on the first call.
Book a call →No. Money moves between you and your partners. Open Passage picks the route that fits your rules and tracks the payment from quote to settlement.
No. You keep your partner contracts and terms. Open Passage works across the pay-in, FX, and payout partners you already run.
Through a REST API and signed webhooks. Your system requests a route, saves the payment, and receives status updates from every partner. Partner connections are set up with you for the rails you use.
Thirty minutes. We walk one of your payments end to end: the partners it touches, where it stalls, and how it is reconciled today. Then we tell you plainly whether a routing layer helps.
Pricing is agreed with each early team. It is never tied to which partner or route your policy picks.
Your team, under the roles you set. Policy changes, approvals, and route decisions are kept on one audit trail.