Third-party cross-border payments, step by step.
A third-party cross-border payment moves money that belongs to your customers across a border — a marketplace paying sellers abroad, a platform disbursing for clients. On Infinite (infinite.net), every customer whose funds move gets a real account through chartered, FDIC-insured partner banks, and onboarding, screening, and monitoring run on the network.
Who holds the funds, and what clears them
When customer money moves, regulators expect diligence on the customer — not just on your platform. That expectation shapes every hop below; the full model lives at Third-Party Funds Flow.
Your platform completes KYB
Your own business is verified first — entity documents, ownership, and a compliance review, the same KYB that opens a first-party account. At this point no customer funds have touched the network.
Each customer is onboarded
KYC and KYB run on each customer whose funds move, through compliant, whitelabel flows in your brand provided by Hosted Flows — your customer sees your product while verification runs to network standard behind it.
Each customer gets a real account
A managed DDA, a yield-bearing DDA, or a bank-owned wallet — issued through Infinite’s chartered, FDIC-insured partner banks, not a row in your ledger. The customer’s funds sit in the customer’s own account, not pooled on your platform’s books.
The payment is created and routed
One instruction covers the transfer and any conversion. Each payment takes the best rail for its corridor — stablecoins on the long leg, SWIFT or local rails where they win — with FX converted in flight where the destination currency differs. Routing is Transfer Routes.
Both sides are screened before funds move
Sanctions and watchlist screening runs on both sides of every payment — before funds move, on every rail. Flagged transfers stop for human review, with every case assembled and documented by Infinite Agents before an analyst opens it, and every decision made by a human.
Settled, monitored, documented
Funds land the same day, and transaction monitoring runs continuously across the network behind them. Every onboarding, screen, and decision is documented and exportable for auditors and regulators — see Global Compliance for the program end to end.
Frequently asked questions
What makes a payment a third-party flow?
The funds belong to your customers rather than your business — payouts, disbursements, customer balances. Regulators expect customer-level diligence on every one of them, which is why each customer is onboarded and gets their own account. See Third-Party Funds Flow for the full model, and first-party for moving your own money.
Who holds our customers’ funds?
Each customer’s funds sit in their own account — a managed DDA, a yield-bearing DDA, or a bank-owned wallet — issued through Infinite’s chartered, FDIC-insured partner banks, not pooled balances on your platform’s books. See the Managed Account page for how per-customer accounts work.
How do our customers get onboarded?
Through compliant, whitelabel onboarding flows in your brand, provided by Hosted Flows — your customer sees your product while KYC and KYB run to network standard behind it. A customer vetted once is vetted for the whole network, so first-time review closes in 1–2 days instead of ~30.
What screening runs on a cross-border payout?
Sanctions and watchlist screening runs on both sides of every payment — before funds move, on every rail — and transaction monitoring runs continuously behind it. Flagged transfers stop for review, with every case assembled and documented before an analyst opens it and every decision made by a human. See Global Compliance.
Do we need our own banking or money transmitter licenses?
Accounts are established under Infinite’s regulated banking partners and operated under Infinite’s compliance program. What that means for your own licensing posture depends on your flow of funds — see third-party funds flow for how platforms move money for their customers compliantly, and talk to sales about your specific setup.
How fast do cross-border payouts settle?
Same day, once the counterparty is vetted. Each payment takes the fastest compliant path across stablecoin, SWIFT, or local rails, with FX converted in flight where the destination currency differs — Transfer Routes chooses per corridor. Traditional correspondent wires spend 3–5 days in flight.
Compliance review in days, not months.
Talk to sales and see how customer onboarding, screening, and monitoring run on the network — with an account for every customer.