One structure
Many merchants, many gateways, a single integration and a single ledger — with failover when a provider degrades.
OrchestrationOne structure connecting many merchants to many gateways. A white-label checkout, local methods from Pix to Bizum, identity checks and merchant-of-record settlement — behind a single integration.
Wherever they buy
Payment approved
Risk 12/100 · low
Most teams assemble this from four vendors and a spreadsheet: a gateway, a fraud tool, a billing service and someone reconciling it all by hand. CheckoutWeb runs it as one system, with one place to look when something breaks.
Many merchants, many gateways, a single integration and a single ledger — with failover when a provider degrades.
OrchestrationYour brand, your domain, your rules. Hosted or embedded, and mobile-first either way.
CheckoutWe are the legal seller, so tax registration, invoicing and compliance in each market are ours, not yours.
WorldwideSub-merchant onboarding with the same identity checks, split payments and per-seller settlement terms.
PlatformsPlans, seats, proration, invoices, upgrades and usage-based billing on the cycle you set.
BillingAbandoned checkouts, failed renewals and declined authorisations, each chased on its own schedule.
RecoveryRisk scoring, facial verification, liveness and document checks, recorded next to the payment.
ProtectionStablecoins and major assets, swapped to the asset you hold at the confirmed rate.
NativeCheckoutWeb sits between the businesses you serve and the providers that move the money. Connect once and give every merchant on your platform the same rails, rules and reporting.
Plans, seats, trials, upgrades and metered usage, billed on a schedule you do not maintain.
Onboard sub-merchants, split a payment across sellers and settle each one on its own terms.
A checkout tuned for the market the buyer is in, with recovery on everything that slips.
Embed payments in your own product and keep the relationship, the branding and the data.
Your customers should never wonder who is taking their money. The checkout on the right is live — switch brands and watch the whole page follow.
Payment methods
Pro Plan
$29.00
Secure payment
Try a brand
Going international should be a settings change, not a second provider and a second set of tax registrations. We are the merchant of record, so the obligations a new market creates land with us.
R$ 149,90
Pix · Cards
$29.00
Cards · Crypto
€24,90
Cards · Crypto
¥4,200
Cards
The same checkout, priced and paid the way each market expects.
Five things happen between your customer pressing pay and the money being yours. Every one of them is ours.
01
Any channel, any market, any method — on a checkout wearing your brand.
Pro Plan
€24,90
02
Device, location and behaviour are scored before the payment is ever sent for authorisation.
03
CheckoutWeb is the merchant of record, so the tax line and the compliant invoice are our obligation.
Pro Plan
04
The currency they paid with becomes the asset you chose to hold, priced at confirmation.
Paid
€24,90
Converted
29,00 USDT
05
One settlement, in your currency or your wallet, with one line in your reporting.
29,00 USDT
payout · your wallet
A buyer will abandon a checkout that only offers a method they do not use. Money should be able to reach you the way each market actually pays, and leave in whatever form you want to hold.
Ways money comes in
Ways money goes out
Methods are shown to describe how each market pays. What is enabled on your account depends on your markets and your contract — talk to sales for the list that is live today.
Most gateways treat crypto as something you bolt on later. Here it is a payment method — one more button on the checkout you already run.
The currency your customer pays with and the asset you want to hold are two different decisions. Set them independently and we handle the conversion at confirmation.
Customer pays
€24.90
You receive
29.00 USDT
Your customer pays on-chain from wherever they are. You get paid in the currency your bank speaks — no exchange, no wallet, no volatility spreadsheet.
Customer paid
0.0412 ETH
Your balance
$29.00
Settle in
We settle natively where we are strongest, and orchestrate the rest. Keep the acquirer relationships you already have, and put one integration in front of all of them.
Native
Pix, cards and crypto settled by CheckoutWeb, with us as merchant of record.
Routed
Bring your existing providers and keep their rates, contracts and reserves.
Provider names are shown for interoperability. Availability differs per account.
Adding a sales channel should not mean adding a payment provider, a second set of fraud rules and another report nobody trusts. The channel changes. Everything behind it does not.
One customer, not five records
The person who bought on your store last month and paid a link today is the same customer, with one history, one saved method and one lifetime value.
The same rules everywhere
Fraud scoring, retries and recovery run identically whether the sale came from a storefront, an in-app purchase or a WhatsApp thread.
A channel is a setting
Turning on payment links or social selling is a switch in the dashboard, not a project with its own integration and its own reconciliation.
One number at the end of the month
Every channel settles into the same balance and the same report, so finance stops stitching exports together to find out what you sold.
Most lost revenue is not lost demand. It is a checkout left open on a phone, a renewal that failed while nobody was looking, or a good customer a bank declined for the wrong reason. All three are recoverable, and none of them recover themselves.
Abandoned checkouts
Follow-up by email and messaging starts on its own when a checkout goes cold, and returns the customer to the same link with the cart intact — no export, no manual list, no new cart to rebuild.
Failed renewals
Declined cards are retried on a schedule tuned per issuer and market, using refreshed credentials rather than the number that just failed, with dunning that stops the moment the payment clears.
Declined authorisations
A soft decline gets a second chance instead of becoming a lost sale: retried across providers, with network tokens and updated card credentials, and routed to the acquirer most likely to approve it.
Checkout abandoned
Pro Plan · $29.00
Reminder sent
Email · your order is still waiting
Follow-up sent
Messaging · one tap back to checkout
Sale recovered
$29.00 paid with a card
Churn from a declined card is still churn, and most of it is involuntary — an expired card, a bank that said no for a reason nobody read. We run the invoices, the retries and the reminders so your MRR reflects your product, not your billing stack.
Pro Plan
$29.00 / month
A blunt filter costs more than it saves. Every transaction is scored, the obvious ones are decided instantly, and the grey area goes to a human instead of a rejection.
Fraud rules only go so far when you cannot tell whether a person is real. The verification stack runs inside the same platform as the payment.
Every transaction weighed on device, location, velocity and history before authorisation.
Match the person paying against the document they present.
Confirm a real person is present, not a photograph, a replay or a generated face.
Validate identity documents and the data on them against the account being opened.
Run the same checks on the sellers joining your platform, not only on their buyers.
Scores, checks and outcomes recorded next to the payment they belong to.
Verification products vary by market and by regulatory regime. Talk to sales for what applies to yours.
Your store, your CRM, your finance stack and your reports stay where they are. CheckoutWeb plugs into them and keeps the payment data in sync.
Take the checkout your store already sends people to.
Keep plans and entitlements in sync with billing.
Customers, payments and status where your team works.
Trigger campaigns from real payment events.
Reconciliation that matches what accounting expects.
Export or stream the numbers into your own reports.
Everything else
If your team can call an endpoint, CheckoutWeb fits your stack without waiting on a roadmap.
Approval rate, recovered carts, active subscriptions and every payment across every channel — on one screen your whole team can read.
Revenue · 30d
$248,400.20
Approval rate
94.2%
Recovered
$18,240.00
Subscriptions
1,284
Recent payments
Figures shown are sample data for this preview.
Every payment event you take is already structured data. Connect the sources that sit outside it — your store, your CRM, your warehouse — and ask in your own words. The report is written for you, and every figure in it links back to the rows it came from.
Asked in your own words
“Why did approval drop in Spain last week?” returns a written answer with the cohort, the issuer and the decline codes behind it — not a blank chart builder waiting for you to know the schema.
Payment events, already modelled
Authorisations, captures, refunds, disputes, retries, renewals and on-chain confirmations arrive structured, so the numbers are right without anyone maintaining a pipeline.
Your other sources, joined in
Connect a store, a CRM, a warehouse or a spreadsheet and the report reads across all of it — ad spend next to approval rate, plan next to churn, cohort next to lifetime value.
Auditable, not approximate
Every figure traces to the transactions that produced it. Open the number and you get the rows, not a summary you have to trust.
Reports are generated from your own data. Accuracy depends on the sources you connect.
Ask anything about your payments
Why did approval drop in Spain last week?
Commercial teams get the dashboard. Engineering gets a REST API, SDKs and webhooks — so the platform fits your product instead of the other way round.
bun add @checkoutweb/sdkimport { CheckoutWeb } from "@checkoutweb/sdk";
const checkoutweb = new CheckoutWeb({
apiKey: process.env.CHECKOUTWEB_API_KEY,
});
const checkout = await checkoutweb.checkouts.create({
amount: 14990,
currency: "BRL",
methods: ["pix", "card"],
});
return checkout.url;{
"id": "chk_8Kd2Pq4Vn1",
"status": "pending",
"amount": 14990,
"currency": "BRL",
"methods": ["pix", "card"],
"checkout_url": "https://pay.checkoutweb.com/8Kd2Pq"
}Illustrative example of the API shape. The published SDKs and full reference ship with the docs.
Rates published in full, with the whole platform included. Nothing to negotiate before you can see how it works.
Yes. Logo, colours and domain are yours, on the hosted page or embedded in your own flow. Nothing on the payment screen points back to us.
Both, and you choose per account. Processing natively with us makes CheckoutWeb the legal seller, so the tax registration, the invoice and the compliance obligations are ours. Routing through your own acquirer keeps you as the seller and uses us as the orchestration layer in front of it.
The checkout prices in the buyer's currency and offers the methods their market expects, while settlement lands in the currency you keep books in. What is enabled for your account depends on your markets and contract, so talk to sales for the current list.
Yes. Bring your existing acquirers and keep their rates, contracts and reserves. You get one integration and one reconciliation in front of all of them, plus failover when one degrades.
Card data is entered into fields served by CheckoutWeb, so it does not touch your servers. That keeps you on the lighter self-assessment path rather than the full audit that handling raw card numbers requires.
You do not have to. The customer pays on-chain, the payment confirms, and it settles to you in your own currency at the confirmed rate — so the volatility never reaches your books. The reverse also works: take euros and hold stablecoins.
When a checkout is abandoned, CheckoutWeb starts a follow-up sequence by email and messaging. The customer returns to the original link with the cart intact and pays there — no new cart, nothing to retype.
Every transaction is scored on device, location and behaviour signals. Clear cases are decided instantly, and the borderline ones go to a review queue instead of a flat decline. You write the rules rather than inheriting someone else's defaults.
They are raised, tracked and answered in the dashboard, next to the payment they belong to, with the evidence and the deadline attached. Where we are the merchant of record, the dispute is filed against us.
Strong customer authentication is applied where the rules require it and exemptions are requested where they apply, so a payment is not challenged more than it has to be.
A hosted checkout is a redirect and a webhook, which is an afternoon. Embedding it in your own flow takes longer. Sandbox keys, API logs and test methods are available from the first day, before any commercial conversation.
No. CheckoutWeb connects to your store, CRM, finance and reporting stack, and anything not covered by a connector can be wired up through the API and webhooks.
Yes. Customers, payments, subscriptions and payouts are exportable, and the same records stream over the API and webhooks, so your history is not stranded here.
Launch the checkout, connect your channels, and let the platform chase the payments that would otherwise slip away.