Your customer wants to pay in stablecoins. Your accountant wants a numbered invoice with the right VAT on it. Today that is two systems and a spreadsheet holding them together.
Pago402 is one: send a payment link, let them settle by card or in USDC, and the compliant document comes out the other end without anyone re-typing it.
Reverse charge — VAT to be accounted for by the recipient (Art. 196 Directive 2006/112/EC)
The money is easy to receive. Proving what you received, to whom, in which country, and at what tax treatment is the part that costs a person a week a month.
Customers in a dozen countries, some businesses, some not. Every one of them changes what you're supposed to charge — and you find out at quarter-end.
You take a cut and pass the rest on. That makes you responsible for money that was never yours, and for telling everyone what happened to it.
Wires take days, cost a percentage and arrive short. Your client offered to pay in stablecoins, and your accountant said absolutely not.
Software is buying from you now. It can't complete a signup form, hold a card, or wait for a human to approve a €0.03 charge.
“A customer in Dublin wants to pay by card, one in Lisbon wants to pay in USDC, and one in Zurich hasn't decided. I need all three to end up in the same books.”
Finance lead · B2B software, 40 peopleYou send one link. The payer opens it and sees the methods that actually work for them — card, or a stablecoin on the chain they use. They pick; you don't have to guess in advance, and you don't maintain three checkout flows.
The payment lands and the invoice closes itself. Partial payment leaves the balance visible instead of failing the whole thing — the customer tops it up to the same address.
VAT is decided from the facts, not from a default. Irish customer, Portuguese business with a valid VAT number, Swiss company: three different treatments, worked out per invoice.
Documents come out numbered and in sequence, as PDFs, grouped on your cadence and in your timezone. Nobody exports a CSV and fixes it by hand.
“Sellers on our marketplace want paying quickly. We take 8%. I don't want to write custody code, and I really don't want to be holding their money on a spreadsheet.”
CTO · vertical marketplaceEach seller is a separate account with its own keys, its own branding on the payment page, and its own onboarding — hosted, so you never see a document you'd have to store. Your fee is separated the moment funds arrive, not reconstructed later from a report.
The split happens once, at the source. Your commission and the seller's proceeds go to different places immediately, so no balance is ever ambiguous.
Your systems hear about it directly. Signed notifications, retried until they land, so your own dashboard never disagrees with ours.
Sellers get their own documents, issued in their name with their numbering, not a line item on yours.
“My client in Singapore pays a €14,000 invoice by wire. It arrives four days later, €80 short, and the reference field is empty. Every single time.”
Founder · design agencyPrice the work in euros; let them settle in a stablecoin. The amount is fixed at the rate when the payment opens, so nobody is arguing about a market move afterwards, and the conversion happens on your side — you don't have to hold anything you didn't want to hold.
Money arrives while the client is still in the thread, not on Thursday.
The expected amount is exact, and what arrives is checked against it before anything is marked paid.
The invoice is issued with reverse charge stated on it, so the accountant gets a document they recognise rather than a screenshot of a wallet.
“Half our API traffic is now agents acting for someone else. They can't sign up, and metering them after the fact means chasing invoices for eleven euros.”
Head of platform · market data APICharge at the door instead. A request without payment gets back a machine-readable price. The agent pays it and repeats the request, and the whole exchange finishes inside the same call — no account, no card on file, no invoice to chase. It works down to fractions of a cent, which is where per-call pricing usually falls apart.
Pricing is quoted, not assumed. An agent can ask what something costs without committing to buy it.
The buyer needs no relationship with you, which is the only way a one-off machine purchase is worth transacting at all.
Those payments arrive in the same ledger as the card and stablecoin ones, and appear on the same documents.
Card via Stripe, stablecoins on Polygon, BSC or Base, or a direct machine payment. The payer sees what's available to them and nothing that isn't.
Invoice in euros or dollars and let people settle in USDC, USDT, esEUR or esUSD. The conversion is yours to keep, not theirs to argue about.
Place of supply, domestic rates, intra-EU reverse charge with the legal wording on the document, exports out of scope. Customer VAT numbers checked against the EU register.
Numbered without gaps, issued on your billing cadence, rendered to PDF and kept. Corrections are credit notes, the way an auditor expects.
Balances sit in accounts the platform controls through a hardware-backed key service. Nobody on your team has a seed phrase to lose.
Proceeds settle to your destination, fees separate at source, overpayments are tracked and returned rather than quietly absorbed.
Everything the interface shows is available programmatically, so your own tools can read the same truth.
Signed, retried notifications when an invoice is paid, plus emails to payers with the link and the receipt.
From the dashboard or from your own software, priced in the currency you sell in. You get a link to send.
Card, stablecoin, or machine payment. The exact amount and a deadline are shown up front, so there is nothing to interpret.
Money is only credited once it's been verified independently of whoever reported it. Nothing is marked paid on a promise.
Your fee split, the payout, the notification to your systems, and the tax document — in that order, without anybody starting it.
The notification that money moved has to be provably from the provider, and the transfer has to be confirmed against the network itself. Either one alone can be wrong or forged, so neither is trusted alone.
What an invoice has received is always recomputed from the underlying payments. A message delivered four times produces the same answer four times.
A regular sweep compares what we recorded against what actually happened and reports any disagreement to a human. It never silently corrects a balance — an automatic fix would hide the very problem it found.
Once a fiscal document is issued the database itself refuses to modify or delete it. The only correction is a credit note, which is what the law expects anyway.
Signing keys live in a managed key service and are never present in the application. There is no export, and no file to steal.
When the facts don't determine the treatment, issuance halts and asks. A draft you fix in an afternoon is a much smaller problem than an issued document that misstates a liability.
Thirty minutes, your own numbers. We raise it in the system, pay it in a stablecoin while you watch, and show you the document that comes out — including which VAT treatment it picked and why.
No account, no integration work, nothing to install beforehand.
HTTP has had a code reserved for “you owe me money” since 1997, and almost nothing ever used it. It turns out to be the right name for a platform built on the assumption that a payer might be a person with a card, a company with a treasury, or a piece of software that needs to settle a bill and get on with its work — and that all three should end up on the same invoice.