Orchestrate the stablecoin payments.
Keep the stack you have.

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.

Payment100 USD → NGN bank account
Your policySame-day settlementNo prefunding
Your fundsOpen Passage ranks your partner routesRecipient
100 USDYour operating account
  1. 1
    APay-in, FX, payout$99.52 delivered · Same day · Prefunding
    Excluded · needs prefunding
  2. 2
    BPay-inCFXDPayout$99.49 delivered · Same day · No prefunding
    Recommended by Open Passage
  3. 3
    BPay-inEFX + payout$99.50 delivered · 2 days · No prefunding
    Excluded · misses same day
NGN bank accountReceives ₦150,727 same day
Returned to your system with the reasons and alternatives

Works across the stack you already run

More partners. More hand‑offs.

Each new partner opens a corridor or trims a cost. It also brings another integration, another dashboard, and another place a payment can stall.

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 partner speaks its own format.

IDs, fees, and statuses come back in different shapes for the same payment.

One view across every partner.

Where did it stall?

One partner waits on funding or compliance, and your customer notices first.

Live status from every partner, and a needs-attention queue.

Month-end matching.

Amounts and references across partners are matched by hand.

A ledger export with every reference and event.

One decision layer for your payment stack.

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.

  • APay-in, FX, payoutConnected
  • BPay-inConnected
  • CFXConnected
  • DPayoutConnected
  • EFX + payoutConnected

Set up once in the console. Partner credentials never pass through the API.

Built for teams that run payments at scale.

Resilience

When a partner degrades, it drops out of routing and payments move to routes that still pass your policy.

Cost clarity

See what each partner in a route costs, not one blended number.

Governance

Policy changes, approvals, and route decisions on one audit trail, with roles for who can do what.

Your policy picks the route. Your partners move the money.

Open Passage picks the route and tracks every step alongside your partners, never between you and your money.

  • Neutral routing

    Routes are ranked by your policy, not by partner deals.

  • Your contracts

    Partner relationships and terms stay yours.

  • We never hold funds

    Money moves between you and your partners.

  • Secure by default

    Roles, an audit trail, signed webhooks, tenant API keys, and no partner credentials through the API.

One API from route to settlement.

Request a route, record the payment, and receive signed status events from every partner.

  • REST and JSON
  • Idempotent requests
  • Signed webhooks
Explore the API →
Illustrative data
{
  "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."
}

Questions teams ask first.

Still deciding whether this belongs in your stack? These are the questions that usually come up on the first call.

Book a call →
Do you hold or move our funds?

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.

Do we need to change partners?

No. You keep your partner contracts and terms. Open Passage works across the pay-in, FX, and payout partners you already run.

How do our systems connect?

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.

What happens on the first call?

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.

How is pricing decided?

Pricing is agreed with each early team. It is never tied to which partner or route your policy picks.

Who can see our payment data?

Your team, under the roles you set. Policy changes, approvals, and route decisions are kept on one audit trail.

If this is the layer you were going to build,
let’s walk one payment.