Get paid at the end of your own flow.
Drop a hosted checkout into the last step of your purchase or onboarding flow. The payer is screened before funds move, the payment settles into your Infinite Account, and it reconciles to the order that created it.
Draft — pending review
Checkout on Infinite (infinite.net) is a hosted, embeddable pay step a business places at the end of its own purchase or onboarding flow. The buyer pays on a supported rail, the payer is screened before funds move, and the payment settles into the business’s Infinite Account — reconciled to the order it came from, on one ledger.
- B2B software and marketplaces collecting a first payment inside their own signup or order flow
- Platforms whose customers check out into their own accounts on the network — third-party funds flow
- Businesses replacing “complete your order, then wire us” with one screened, reconciled step
The pay step, on the same network.
Payouts, Links, Invoicing, and Checkout are capabilities of the same Infinite Account — one compliance review, one integration, one ledger.
Hosted, in your flow
Create a checkout session for an order and hand the buyer to it — as the last step of your flow, not a separate page they have to find later.
Payer screened before funds move
The buyer is screened the same way a payout recipient is — sanctions, watchlists, and the network’s own counterparty record — with a hold for review rather than a silent landing.
Paid on the rail the buyer has
The buyer settles over a supported rail into your account; the checkout does not dictate their bank.
Reconciled to the order
The settled payment posts against the order reference that opened the session — cash applied on arrival, on the same ledger as everything you send.
Into a real account
Funds land in your Infinite Account — or, for platforms, in the customer’s own account on the network — not in a pooled float you allocate later.
From order to cash applied.
A B2B software company in London signs up a customer in Mexico and takes the first annual payment inside its own onboarding flow. On Infinite (infinite.net), the order and the reconciliation are one object.
Open a checkout session
Amount, currency, and your order reference — one API call at the last step of your flow.
Hand the buyer to the pay step
The buyer lands on the hosted checkout without leaving your flow. Nothing to retype, nothing to email back.
Buyer pays, screened before funds move
The buyer settles over a supported rail. The payer is screened before the payment lands; a flag holds it for a named analyst.
Settles and reconciles
The payment posts against the order in your Infinite Account, and a webhook tells your systems the order is paid.
Integrate once.
A checkout session is an object with an amount, a destination account, and your order reference. Creating it returns the hosted URL; settlement arrives as a webhook against the same object.
import { Infinite } from "@infinite/sdk"; const infinite = new Infinite({ apiKey }); const session = await infinite.checkout.create({ amount: "18000.00", currency: "USD", destination: "acct_ops_usd", reference: "ORD-20491", returnUrl: "https://app.example.com/welcome", }); redirect(session.url); // last step of your flow // checkout.completed arrives with the same id
Answers before you ask
Is the payer screened at checkout?
Yes — before funds move, the same way a payout recipient is: sanctions and watchlists, the network’s own counterparty record, and a hold for a named analyst when something trips. Checkout never lets an unscreened party settle into your account. The checks are the ones described on Stablecoin Compliance.
How does Checkout differ from a payment link?
Same receive side, different moment. A payment link is a request you send — the payer opens it whenever they get to it. Checkout is the pay step inside your own flow: you open a session for an order and the buyer pays before they leave. Both settle into the same Infinite Account and reconcile the same way.
Can Checkout settle into a customer’s own account?
Yes. Platforms operating third-party funds flow can open sessions whose destination is the customer’s own account on the network, so a buyer paying a platform customer settles straight to that customer rather than into a pooled balance you allocate later.
What if the buyer pays the wrong amount or is flagged?
A payment that does not match its session — or that trips screening — does not reconcile silently. It holds with the case assembled for your team, on the same ledger, so the exception is worked once rather than discovered at month-end. How stablecoin refunds and returns reconcile is covered in this essay.
Does Checkout need a separate integration?
No. Checkout shares the API, keys, and ledger of every other payments capability. A business already sending payouts or collecting by invoice adds Checkout as configuration on the same Infinite Account, not as a second project.
- PayoutsSend batch disbursements with one instruction
- LinksGet paid by link, reconciled on arrival
- InvoicingInvoice and settle in one flow
- SWIFT PaymentsSend global wires through one integration
- USD PaymentsMove dollars on every domestic rail
- Stablecoin PaymentsSettle in stablecoins on bank rails
- Foreign ExchangeConvert between currencies at settlement
- Transfer RoutesRoute money on the fastest compliant path
Finish the flow. Watch it reconcile.
Book a 30-minute demo and see a checkout go from order to settled, screened funds in your account.