One integration reaches cards, bank rails, local payment methods and crypto — and sends every transaction to the acquirer that performs best for it.
Most platforms treat acceptance and payout as two different products, built by two different teams, reconciled by nobody. We built one rail for all of it.
Cards, bank rails, local methods and crypto, routed to the acquirer best placed to authorize.
02Every transaction scored and sent down the path built to clear it — routing, never retries.
03Mass payouts to sellers, creators, partners and talent — any method, any market, on your schedule.
04Fiat to crypto and back, stablecoin settlement, on-chain payouts.
05Issue cards to customers, staff or partners, on the same rail you already collect and pay out on.
06Dedicated IBANs for collections, subject to business profile and jurisdiction.
Cards work almost everywhere. Where they don't, you need the rail your customer actually reaches for — Open Banking across Europe, PIX in Brazil, Fawry in Egypt, local wallets across Asia-Pacific. We've already built those in.
Use the Hosted Cashier and stay out of scope entirely. Or integrate the Direct API and keep the checkout your own — pay-ins, payouts, refunds and transaction queries, all on the same integration. Build against the sandbox first; the base URL is the only thing that changes when you go live.
Create a session, redirect the customer. Fastest route to live.
Server-to-server pay-ins and payouts when you own the checkout.
Refund and reconcile from the same integration.
Build against the sandbox, then switch the base URL.
Tell us what you sell and where your customers are. We'll walk you through the methods that apply, the markets you're missing, and what onboarding actually involves.