Money in and out, one balance.
Collect and pay out through one API, every payment screened, routed and reconciled.
Who it’s for
- Finance teams collecting from customers and paying suppliers in several countries
- Marketplaces and platforms collecting from buyers and paying sellers or partners
- Businesses replacing a provider per rail and country
Building on stitched vendors costs you time.
Why one stackYou need to move fast
So you stitch
And you wait
And it breaks
One flow, both directions.
CapabilitiesOne balance
Collections land in and payouts draw on the same Infinite Account.Screened before funds move
Payers and recipients are screened alike. Flags hold for a named analyst.A rail per payment
Transfer Routes picks the rail for each payment; FX converts where needed.Any rail the payer has
SWIFT, ACH, RTP, stablecoins, or another currency, all into one account.One reconciled report
Incoming payments match on arrival; outgoing payments close with a status each.
One account. The right rail for each payment.
Illustrative example- Your Infinite AccountOne balance behind every rail
- One instruction340 recipients · 6 currencies · no rail specified
- Recipients screenedCleared once, cleared for the networkCleared
- ACH or RTPUS contractors · by cutoff
- FX to EUR and GBPConverted in flight
- Stablecoins or SWIFTBy destination
Accounts, payments and requests in one console.
Console- Payments
- Transfers
- RFI inbox
- Balances and accounts
- Payees
- Verification
- Agents
- Developer
Payments
Pay pages, invoices and payment links in one list.
- Invoice INV-2042Hosted pay pageAwaiting deposit
- Payment linkUSDC on BasePaid
- Invoice INV-2039ACHCompleted
From instruction to reconciled funds.
DevelopersIllustrative workflow. Integration details are scoped to your account and enabled products.
1. Assign payment instructions or prepare the recipients. 2. Screen each payer and recipient; hold flags for review. 3. Route each payment on a supported rail. 4. Reconcile every payment to its account and reference.
Answers before you ask
FAQWhat does Orchestration cover?
Which rails are supported?
SWIFT wires, US rails (ACH, Fedwire, RTP), stablecoins, and other currencies converted by FX, all on the same account. Transfer Routes picks the rail per payment.
What happens if a payer or recipient is flagged?
That payment holds while the rest settle. A judgment call routes to a named analyst, with the case assembled by Compliance AI.
How does a payment get matched to the right customer?
Give each payer an account number through Virtual Accounts. A payment into it identifies the customer and reconciles to the open Link or Invoice.
How do we track each payment?
A webhook fires on every transition; returns reconcile to the original payment. See the documentation.
Can a platform collect and pay on behalf of customers?
Yes, through third-party funds flow: each customer holds their own account, and counterparties are verified through Embedded Compliance.
Walk one payment through.
Bring your rails and counterparties; an engineer walks a payment in and out.
Ask an AI about OrchestrationChatGPTClaudePerplexityGemini