Duty27 is a calculation layer, not a Merchant of Record. It plugs into checkout you already control — Stripe, Mollie, Klarna, or your own — no revenue cut, no new payment processor, no giving up the customer relationship.
No credit card required.
Sourced directly from the European Commission's TEDB. Every response carries its rate source and effective date — built to hold up under audit, not just at checkout.
Rates change. Refunds and credit notes issued against a past sale need the rate that applied then — not the rate that applies today. Duty27 is built around effective-dated windows from the start, so a correction six months later resolves to the same rate the original sale used.
One call, correct rate — for digital goods and services, across every EU member state.
Reverse-charge is determined automatically for validated business buyers — no separate B2B code path to maintain.
On accounts with transaction tracking enabled, applies your home-country rate or the buyer's destination rate correctly, based on cumulative EU-wide sales — you don't track the threshold yourself. Opt-out available, per Article 59c(3).
Country-specific exceptions for e-books, newspapers, and periodicals — instead of a blanket standard-rate assumption that's wrong for them.
You state which one you're sending. No silent assumption either direction.
Not a bolted-on separate step, and not a bare yes/no. If the validation service is down, that's returned as its own explicit outcome — so checkout can hold and retry instead of guessing wrong in either direction.
Every response carries the rate's source and effective date, sourced directly from the European Commission's TEDB — not a resold or aggregated feed.
They become the legal seller of your product. Checkout routes through them — replacing your existing Stripe setup — and they take a cut, commonly 3.5–7%+ per transaction, in exchange for handling tax, invoicing, payment processing, and remittance end to end.
Real, valuable, human-assisted work. But it's not a developer tool, and it's not something a checkout flow can call in real time — you onboard over weeks, not an afternoon.
Calculates tax within Stripe Checkout or Billing. Costs 0.5% of transaction value (no-code) or €0.50/transaction via API — on top of Stripe's normal processing fees. You still configure registrations, product tax codes, and tax-ID collection yourself.
Plugs into a checkout you already control. No revenue cut, no new payment processor — keep your existing Stripe account — and no giving up the direct customer relationship. Integrate in an afternoon. Native support for the EU's Article 98(3) digital-publication exception (Annex III, point 6) — e-books, newspapers, and periodicals — beyond Stripe Tax's generic tax-code mapping. And when a sale needs to be provable months later, the record's already there — evidence type, OSS scheme, exchange rate, captured at the time, not reconstructed under time pressure.
Metered by calculation volume, never by revenue.
Your bill moves with usage, not with your product price or your margins.