First-party payouts, step by step.
A first-party payout moves your business’s own money — supplier invoices, payroll, treasury transfers. On Infinite (infinite.net), one KYB review on your business opens every rail: funds leave your own account over SWIFT, ACH, Fedwire, RTP, or stablecoins, and every counterparty is screened against sanctions and watchlists before funds move.
Where the money is at every step
Because no customer funds move, this is the simplest flow on the network — your business is the only funds owner from start to settlement. The full model lives at First-Party Funds Flow.
Your business is verified once
Standard KYB on your company — entity documents, ownership, and a compliance review. There is no customer-level onboarding, because no customer funds move. Nothing has moved yet; your funds still sit wherever they sit today.
Your account opens on the network
One account holds your operating funds across fiat and stablecoin balances, with every movement sub-ledgered and reconciled. Your business owns the balance throughout this flow — see First-Party Funds Flow for the onboarding detail.
You create the payout
One instruction with amount, currency, and destination, from the same API on every rail. By default Transfer Routes reads destination, urgency, and cost and picks the rail; when policy requires a specific rail, you pin one on the request.
The counterparty is screened
Before funds move, the counterparty is screened against sanctions and watchlists — on every rail. Flagged transfers stop for human review, and nothing releases while the review is open. A counterparty already vetted on the network starts pre-cleared.
Funds settle on the rail
Stablecoin transfers settle on-chain in minutes, 24/7; SWIFT wires settle same day to two business days by corridor; ACH, Fedwire, and RTP each keep their own timing. Where currencies differ, FX converts in flight at known rates.
The record closes the payout
Every transfer is sub-ledgered with its screening record attached — exportable for auditors and regulators. When compliance asks what happened, the answer is a record, not an investigation.
Frequently asked questions
What counts as a first-party payout?
Any payment made with your business’s own money: paying suppliers and vendors, running payroll, funding subsidiaries, or rebalancing treasury between your own accounts and currencies. If the funds belong to your customers, that’s a third-party flow — see third-party funds flow for the onboarding model that applies when customer money moves.
Do first-party payouts skip compliance checks?
No. KYB covers onboarding, and screening still runs on every payment: counterparties are screened against sanctions and watchlists before funds move, on every rail, and flagged transfers stop for human review. What first-party removes is customer-level onboarding, since no customer funds move — see First-Party Funds Flow for the full model.
Which rails can a first-party payout use?
SWIFT wires, ACH, Fedwire, RTP, stablecoin transfers, and FX conversions — all from the same account and the same API. By default Transfer Routes reads destination, urgency, and cost and picks the best rail per payment; when policy requires a specific rail, you can pin one on the request.
How fast do first-party payouts settle?
It depends on the rail. Stablecoin transfers settle on-chain in minutes, 24/7, weekends included; most SWIFT wires settle same day to two business days depending on corridor and cutoff; RTP delivers instantly around the clock; ACH is the cheap batch rail. Routing weighs speed against cost per payment.
Can we pay suppliers in other currencies?
Yes. GBP, EUR, MXN, and BRL convert in flight at firm, all-in rates, with local settlement over Faster Payments, SEPA, SPEI, and PIX — one instruction covers the transfer and the conversion. See Foreign Exchange for how quotes and execution work from the same account and API.
One KYB. Every rail.
Book a 30-minute demo and see your own money move — SWIFT, US rails, stablecoins, and FX from a single account.