Four statuses. One audit proof.
Zero spreadsheets.
Incoming withdrawals move through RECEIVED → CONFIRMED → PROCESSING → COMPLETED. Every row carries a SHA-256 proof, every export is fit for Art. 20 GDPR, every user gets their own public MerkleBatch page. No appointment with the agency, no ticket with support — you can do it yourself. Mandatory across the EU from 19 June 2026.
One account, multiple shops
Create as many shops as your plan allows — each gets its own WidgetKey cuid and its own CORS whitelist. Domains are checked against the origin headers of incoming widget requests, not against hearsay.
Status flow with four stages
RECEIVED → CONFIRMED → PROCESSING → COMPLETED. Filterable, sortable, paginated. Every row has a proof badge that jumps to the public verification page — so you’re not hunting for the spreadsheet in a dispute.
Live configuration, no deploy
Colour, position, language, optional fields. Changes go live instantly — on the next pageview the widget loader pulls the new config from our edge cache. No re-deploy, no theme update.
CSV export. Art. 20 GDPR.
Every withdrawal table can be exported as CSV — RFC-4180-compliant, UTF-8 with BOM, so Excel doesn’t mangle accented characters. Satisfies the right to data portability under Art. 20 GDPR without a support ticket.
A MerkleBatch page per user
Every user has their own public verification page. We publish the Merkle root over all incoming withdrawals daily. Your lawyer can confirm without logging in that a given withdrawal was in the system at a given time.
Magic-link login. No password.
NextAuth v5 with email magic links. No password to forget, no Google OAuth (we removed it deliberately), no tracking. Sessions run on a JWT signed with a server secret that never reaches your inbox.