Payment
Billie
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Billie GmbH · billie.io
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Billie at a glance
- Vendor
- Billie GmbH
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates Billie 1.5/5, the mean of 6 judges. Billie is a Berlin-based B2B buy-now-pay-later provider: the contracting entity is Billie GmbH, registered in Berlin Charlottenburg, with BaFin named as supervisory authority and claims assigned via Klarna Bank AB. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Billie is a Berlin-based B2B buy-now-pay-later provider: the contracting entity is Billie GmbH, registered in Berlin Charlottenburg, with BaFin named as supervisory authority and claims assigned via Klarna Bank AB. The strongest criterion is licence and account terms, scoring 4, then settlement and reconciliation at 3 to 4: the standard payout is a daily cumulative transfer less fees and deductions, with frequencies and splits chosen at contract setup, and dunning documented day by day — reminders on days 3, 10, 19 and 21, external collection on day 28, pausable from the merchant dashboard. Judges split on payment methods, scoring 2 to 4: the compliance officer credits a deliberately narrow, named set while others miss cards, wallets and per-country lists. Recurring billing splits the same way: the payments engineer and subscription owner find no subscription product, stored cards or token export. Checkout and SCA scores 1 to 2 — no payment reaches authorisation and we found no public information on 3-D Secure, SCA exemptions or PCI scope. No merchant rate is published; fees arrive netted into payouts.
Speaks for it
- Contracting entity fully named — Billie GmbH, Am Postbahnhof 15, 10243 Berlin, commercial register HRB 182428 B, VAT ID DE310295470, with BaFin named as supervisory authority.
- Claim chain disclosed in the terms — the receivable passes from the seller's payment service provider to Klarna Bank AB and then to Billie.
- Payout mechanics documented — a standard daily cumulative transfer 'less our fees and any deductions', with payout frequencies and splits chosen at contract setup.
- Dunning written out day by day, with reminders on days 3, 10, 19 and 21, handover to an external collection service on day 28, and a merchant-side pause from the dashboard.
- Installments are genuine scheduled charges — equal amounts, the first due 10 days after the order, collected by SEPA Direct Debit and interest-free for the buyer.
Held against it
- No payment is taken to authorisation at checkout, since the invoice settles later by bank transfer.
- We found no public information on card or wallet acceptance, or on a per-country method list with currencies.
- We found no public information on stored cards, subscription plan changes, proration, retries or exporting payment credentials to another provider.
- We found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, merchant termination terms or a merchant dispute process.
- We found no public information on where payment data is processed or stored, on subprocessors or on a data processing agreement; the credit-check flow shares personal, company and transaction data with Klarna, Billie and partner companies.
Best for
- You sell to business customers and want invoice purchase where the buyer chooses the payment term while you are paid in advance.
- You want buyer repayment handled for you — SEPA Direct Debit installments with an automated dunning ladder you can pause per order from the merchant dashboard.
- You want payout frequency and splits fixed at contract setup, choosing between the standard daily cumulative transfer and unbatched direct-debit models.
- You operate in the vendor's named segments — e-commerce, marketplaces or platforms — selling Europe-wide to business buyers.
Avoid if
- You need card or wallet acceptance — the documented method set is one BNPL family, invoice purchase plus installments, and the announced Billie cards are stated as not yet available.
- You run subscription billing — ask the vendor: the public pages we read do not show it
- You need payment authorisation at checkout — under invoice purchase the buyer pays later by bank transfer, so no payment is taken to authorisation at the order moment.
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 1 of 5 |
| Checkout, SCA & fraud | 1 of 5 |
| Subscriptions & recurring payments | 2 of 5 |
| Settlement, reconciliation & API | 2 of 5 |
| Licence, risk & account terms | 2 of 5 |
| European sovereignty | 2 of 5 |
Payment methods & local coverage
Show reasoningHide reasoning
How this is scored
Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.
0 — Not a payment acceptance product; customers cannot pay through it.
3 — Card payments with the major schemes, plus wallets such as Apple Pay or Google Pay.
5 — Cards and wallets plus SEPA Direct Debit and several European local methods (for example iDEAL or Wero, Bancontact, Klarna, EPS) listed by name.
8 — Broad EU coverage named per country with the countries and currencies each method serves — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.
10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.
The Finance Lead
Invoice purchase for business customers and interest-free installments are documented by name, with installment collection via SEPA Direct Debit and payment by bank transfer — a single BNPL family rather than card and wallet acceptance. We found no public information on cards, wallets, or which countries and currencies each method serves. 1 3 4
The E-Commerce Lead
Billie is a single-method acceptance product: business-customer invoice purchase, with interest-free installments on selected orders collected by SEPA Direct Debit, marketed Europe-wide to 1.3 million buyers. We found no public information on cards, wallets, or a named per-country method list with countries and currencies, so I cannot plan acceptance across my eight EU markets against it. 1 3 4
The SaaS Founder
Buyers can pay by invoice bank transfer, or on selected orders by interest-free installments collected through SEPA Direct Debit on each due date, with no registration required. I found no public information on card or wallet acceptance or a country-by-country list of local methods; a Billie buyer card is only announced, with no monthly fee. 1 3 4
The Payments Engineer
Billie accepts one method family: purchase on invoice, where the business customer pays by bank transfer with their chosen payment term, plus interest-free installments on selected orders that can be collected from the buyer by SEPA Direct Debit. That is a real acceptance product, but it is a single BNPL method — the captured pages give no information on cards, wallets, or other local methods a merchant could offer through Billie, and a buyer-side card product is only announced as coming. 1 3 4
The Compliance Officer
Billie accepts payments through invoice purchase for business customers — the buyer pays by bank transfer, no registration required — and through interest-free installments for selected orders, with SEPA Direct Debit named for collection, and the claim is assigned from the seller's payment service provider via Klarna Bank AB to Billie. We found no public information on card or wallet acceptance (announced Billie cards are stated as not yet available) or on a per-country method list with currencies. This is a deliberately narrow, named method set rather than broad local coverage, which I place just above the basic acceptance level. 1 3 4
The Skeptic
What a business customer can actually choose is narrow: pay the invoice by bank transfer, or split selected orders into interest-free installments collected by SEPA Direct Debit. We found no public information on cards or wallets — the Billie cards are announced as coming, without a monthly fee, and stated as not yet available — and no method is named per country despite buyers being described as Europe-wide. 1 3 4
Checkout, SCA & fraud
Show reasoningHide reasoning
How this is scored
The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.
0 — No checkout or payment form; the product does not take a payment to authorisation itself.
3 — A hosted payment page or payment links with 3-D Secure.
5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, and fraud screening with configurable rules.
8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, the PCI DSS scope of each integration type stated, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.
10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.
The Finance Lead
The buyer selects the payment method during ordering, after which Billie performs an address and credit check, and the homepage advertises multiple integration options without describing them. We found no public information on a hosted or embedded checkout, 3-D Secure, SCA exemption handling or fraud rules exposed to the merchant. 1 4
The E-Commerce Lead
The captured terms show the buyer selecting the method during the ordering process with an address and credit check performed by Billie at that moment, and the vendor claims multiple integration options without describing hosted or embedded forms. We found no public information on 3-D Secure or SCA exemption handling, PCI scope, or fraud screening exposed to the merchant, which is what I need to keep legitimate payments flowing. 1 4
The SaaS Founder
The captured pages show a buyer selecting the payment method during the ordering process, after which Billie performs an address and credit check, and the vendor advertises multiple integration options. I found no public information on 3-D Secure, SCA exemptions, merchant-facing fraud screening, or hosted versus embedded checkout. 1 4
The Payments Engineer
There is a checkout moment — the buyer selects the payment method in the order flow and Billie performs an address and credit check, with multiple integration options offered — but no payment is taken to authorisation, since the invoice settles by bank transfer. We found no public information on 3-D Secure, SCA exemptions, fraud screening rules, or the PCI scope of any integration, so none of the questions I ask before wiring up a checkout are answerable from these pages. 1 4
The Compliance Officer
Checkout is documented only as 'different integration options' with the payment method selected during the ordering process, where Billie performs an address and creditworthiness check on the buyer. We found no public information on hosted or embedded checkout forms, 3-D Secure or SCA exemption handling, PCI scope, or merchant-configurable fraud rules; under invoice purchase the buyer pays later by bank transfer, so the captured pages show no payment being taken to authorisation. 1 3 4
The Skeptic
The documented path is the buyer selecting the method during the ordering process and Billie then running an address and credit check, with 'different integration options' promised on the homepage. We found no public information on 3-D Secure, SCA exemptions, fraud screening rules or PCI scope — the only risk control shown is the credit check on the buyer, not payment authentication. 1 4
Subscriptions & recurring payments
Show reasoningHide reasoning
How this is scored
Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.
0 — One-off payments only; the product stores no payment method for a later charge.
3 — Saved cards (card-on-file) charged again for repeat or recurring payments.
5 — Stored cards and SEPA Direct Debit mandates for recurring charges, merchant-initiated transactions, and subscriptions or scheduled payments with notification of failed payments.
8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.
10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.
The Finance Lead
Installments are collected by SEPA Direct Debit on the due date, and the dunning ladder is written down in full — reminders on days 3, 10, 19 and 21, handover to external collection on day 28, and a merchant-side pause in the dashboard with automatic resume. This is buyer repayment rather than merchant subscription billing: we found no public information on card-on-file, merchant-initiated transactions, trials, proration or token export. 3 4 5
The E-Commerce Lead
Scheduled charges exist in one form: equal installments via SEPA Direct Debit with the first due 10 days after order, backed by a fully documented dunning cadence with reminders on days 3, 10, 19 and 21, handover to external collection on day 28, and a merchant dashboard control to pause the process. This is installment collection rather than a subscription product; we found no public information on stored cards, mandate pre-notification, smart retries, or a process for exporting payment tokens. 3 4 5
The SaaS Founder
Installments are split into equal amounts with the first due 10 days after the order, debited by SEPA Direct Debit on the due date, and the dunning is genuinely documented: automated reminders on days 3, 10, 19 and 21, handover to an external collection service on day 28, and a merchant can pause the process from the dashboard. But this is single-purchase buy-now-pay-later where the merchant is paid in advance and Billie chases the buyer; I found no public information on subscriptions, proration, card-on-file charging, or exporting payment tokens to another provider. 1 3 4 5
The Payments Engineer
Installments are genuine scheduled charges — equal amounts, the first due ten days after the order, debited by SEPA Direct Debit on the due date when the buyer opts in — and the dunning process is documented in detail: reminders on days three, ten, nineteen and twenty-one, handover to an external collector on day twenty-eight, and a pause the merchant can trigger from the Merchant Dashboard. There is no subscription product here, no stored cards, no retries or token export, so this sits just above one-off charging. 3 4 5
The Compliance Officer
Scheduled charges are real and documented: equal installments with the first due ten days after order, collected by SEPA Direct Debit, plus a dunning cadence written out day by day (reminders on days 3, 10, 19 and 21, handover to an external collection service on day 28) that the merchant can pause from the dashboard and that resumes automatically. We found no public information on card-on-file or merchant-initiated card charges, subscription logic such as trials or plan changes, mandate pre-notification, or any process for exporting stored payment credentials to another provider. 3 4 5
The Skeptic
The repeat-charging machinery that exists is one invoice split into equal installments: the first due ten days after the order, SEPA debits on each due date, default after fourteen days, and an automated dunning ladder — reminders on days three, ten, nineteen and twenty-one, handover to an external collection service on day twenty-eight — that merchants can pause from the dashboard. We found no public information on stored cards, subscription logic such as plan changes or proration, smart retries, or any way to take stored mandates to another provider. 3 4 5
Settlement, reconciliation & API
Show reasoningHide reasoning
How this is scored
Getting the money and knowing what it was: payout cadence and currencies, fee itemisation per transaction, reports that match a bank statement, and an API and webhooks a team can build finance processes on.
0 — No merchant reporting: the product is a payment button or link with no dashboard, report or API.
3 — A dashboard of transactions and payouts, a stated payout schedule, and CSV export.
5 — The payout schedule stated, reports or exports that link each payout to its transactions and fees, and a documented API with webhooks and a test mode.
8 — Configurable payout schedules and settlement currencies, reconciliation reports that match bank lines, accounting integrations or exports named, a versioned API with idempotency and published rate limits, and a public status page with incident history.
10 — Finance can close the month from the provider's data: interchange and scheme fees itemised per transaction, automated reconciliation to the ledger, a deprecation policy for the API, and full historical data exportable after the contract ends.
The Finance Lead
The standard payout is a daily cumulative transfer, in the provider's words, less its fees and any deductions, with payout frequencies and splits chosen at contract setup and net-batched versus gross-unbatched models explained — a stated cadence, but the fees arrive netted into the payout rather than itemised per transaction. We found no public information on reports tying each payout to its transactions, CSV or accounting exports, or webhooks; only a developer portal link is published. 1 2 5 6
The E-Commerce Lead
The standard payout is described as a daily cumulative transfer less fees and deductions, with alternative payout frequencies and splits chosen at contract setup, and a merchant dashboard and developer portal are named. We found no public information on reports linking each payout to its transactions and fees, or on webhooks and a test mode, so my finance team cannot yet plan month-end around it. 2 5 6
The SaaS Founder
Payout terms are documented: the standard is a daily cumulative transfer less fees and deductions, payout frequencies and splits are chosen at contract setup, and the unbatched options work as regular direct debits from the merchant's bank account, with a merchant dashboard in place. I found no public information on reports linking each payout to its transactions and fees, on API and webhook documentation beyond the mention of a developer portal, or on a test mode. 2 5 6
The Payments Engineer
The payout process is stated: the standard is a daily cumulative transfer less fees and any deductions, with payout frequencies and splits chosen at contract setup and unbatched modes settling by regular direct debits. A Merchant Dashboard and a developer portal exist and the help centre carries an article on which reports merchants receive, but we found no public information on the API's versioning, idempotency, webhooks, test mode, report formats, or a status page with incident history. 2 5 6 7
The Compliance Officer
The payout schedule is stated concretely: a standard daily cumulative transfer net of fees and deductions, with net and gross unbatched variants as regular direct debits, and payout frequencies and splits chosen when the contract is set up; a merchant dashboard exists for the dunning process and a developer portal is referenced. We found no public information on reports or exports linking payouts to their transactions and fees, on a documented API with webhooks and a test mode, or on accounting integrations, so this sits modestly above a basic payout-and-dashboard level. 2 5 6
The Skeptic
Payout handling is documented unusually concretely: a standard daily cumulative transfer 'less our fees and any deductions', net-unbatched and gross-unbatched alternatives involving regular direct debits from the merchant's bank account, and payout frequency and splits chosen at contract setup. A merchant dashboard and a developer portal exist and a help article on which reports merchants receive was captured, but no report contents, fee itemisation, webhooks or test mode are confirmed in the captured facts — and the fees deducted from payouts are never given a figure. 2 5 6 7
Licence, risk & account terms
Show reasoningHide reasoning
How this is scored
Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.
0 — The terms let the provider freeze funds or close the account at any time with no notice, reason or timeline.
3 — The regulated entity or the licensed partner behind the payments named, and a chargeback or dispute process described.
5 — The regulated entity named with its supervisor or licence type, the dispute process and chargeback fee published, and either safeguarding of merchant funds or a notice period for ordinary termination stated.
8 — Entity, supervisor, register number and passporting stated per country; safeguarding stated; reserve and rolling-hold conditions defined with limits and release timelines; freeze and termination terms with reasons and a route to appeal; PCI DSS level and attestation published.
10 — The bad day is written down: every regulated entity in the chain named with register links, reserve calculation disclosed, funds release timelines after termination committed, a documented complaint route to the supervisor, and exit terms that include handing back payment tokens and transaction history.
The Finance Lead
The contracting entity is fully named — Billie GmbH at a Berlin address, commercial register number and VAT ID published, BaFin stated as the competent supervisory authority — and the claim chain through the seller's payment service provider and Klarna Bank AB is disclosed in the terms. We found no public information on merchant-side reserves or rolling holds, freeze and termination conditions, safeguarding of merchant funds, or a dispute and chargeback process. 2 3 4 5
The E-Commerce Lead
The imprint names Billie GmbH at a Berlin address with commercial register number HRB 182428 B, German VAT ID DE310295470, and BaFin as the supervisory authority, and the terms document the claim flowing through the seller's PSP and Klarna Bank AB before Billie acquires it. We found no public information on a chargeback or dispute process and fee, safeguarding of merchant funds, reserve conditions, or termination notice periods. 2 3 4
The SaaS Founder
Billie GmbH is named with its Berlin address, commercial register number HRB 182428 B, a VAT ID, and BaFin as the competent supervisory authority, and claims pass through the seller's payment service provider and Klarna Bank AB before reaching Billie. I found no public information on a licence type or register number for the payment services, a merchant dispute or chargeback process, safeguarding of merchant funds, or reserve and termination conditions. 2 3 4
The Payments Engineer
The imprint names Billie GmbH at a Berlin address with a commercial register number and VAT ID and names BaFin as the supervisory authority, and the terms place Klarna Bank AB in the claim chain before Billie GmbH acquires the receivable, which answers who ends up holding the money. We found no public information on a dispute or chargeback process, safeguarding of merchant funds, reserve conditions, or merchant-side termination terms; buyer-side default costs are enumerated but no amounts are given. 2 3 4
The Compliance Officer
The regulated identification is unusually complete: Billie GmbH at Am Postbahnhof 15, 10243 Berlin, in commercial register Berlin Charlottenburg under HRB 182428 B, VAT ID DE310295470, with BaFin named as the competent supervisory authority at its Bonn address, and the claim chain runs through the seller's payment service provider and Klarna Bank AB before assignment to Billie. What we found no public information on is the merchant's bad day: safeguarding of merchant funds, reserve or rolling-hold conditions, freeze and ordinary-termination notice, and a merchant dispute or complaint route; the published default consequences (late payment flat fee, collection costs, default interest, external collection handover) all run against the buyer. 2 3 4
The Skeptic
The imprint identifies Billie GmbH with a Berlin address, commercial register number and VAT ID, names BaFin as the supervisory authority, and the payment chain through the seller's PSP and Klarna Bank AB to Billie is spelled out. But the captured terms govern the business customer who owes the invoice — complete with that customer's late-payment flat fee, collection costs and default interest — and we found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, freeze and termination terms for merchants, or a merchant dispute process. 2 3 4
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.
0 — Contracting entity and processing of payment data both shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; the processing location of payment data not stated or partly outside the EU.
5 — An EU contracting or regulated entity, with EU processing of core payment data stated or a subprocessor list published, and a data processing agreement offered.
8 — EU entity and EU licence, payment and cardholder data processed and stored in the EU on named infrastructure, subprocessor list published with locations, and a DPA covering the processing the provider does as processor versus as controller.
10 — Sovereign end to end and evidenced: European ownership, EU entity and licence, every processing location and subprocessor European, European rails (SEPA, Wero or national schemes) offered alongside cards, and certifications published.
The Finance Lead
The contracting entity is a German GmbH with a Berlin commercial register entry, the licensed bank in the payment chain is Klarna Bank AB, and privacy policies are published for both Billie and Klarna. The processing location of payment and cardholder data is not stated on the pages we captured, and we found no subprocessor list or data processing agreement. 2 3 4
The E-Commerce Lead
A German contracting entity is proven — Billie GmbH, registered in Berlin with BaFin named as supervisory authority — and privacy policies for both Billie and Klarna are published. We found no public information on where payment and cardholder data are processed and stored, on a data processing agreement, or on a subprocessor list. 2 3 4
The SaaS Founder
The contracting entity is Billie GmbH at a Berlin address with a German commercial register entry and BaFin as supervisor, and privacy policies are published for both Billie and Klarna. I found no public information on where payment and cardholder data are processed and stored, on a subprocessor list, or on a data processing agreement. 2 3 4
The Payments Engineer
The contracting entity is verifiably European: Billie GmbH, registered in Berlin with a German VAT number, BaFin named as supervisory authority, and privacy policies published for both Billie and Klarna. The captured pages state nothing about where transaction data is processed and stored, and we found no subprocessor list or data processing agreement; the credit-check data is described as transmitted to Klarna, Billie and partner companies. 2 3 4
The Compliance Officer
The contracting entity is demonstrably German: Billie GmbH registered in commercial register Berlin Charlottenburg under HRB 182428 B with VAT ID DE310295470, and privacy policies are published for both Billie and Klarna. The credit-check flow shares personal, company and transaction data with Klarna, Billie and unnamed partner companies, which is the only subprocessor information on the captured pages. We found no public information on where payment data is processed or stored, on a data processing agreement, or on Billie's role as controller versus processor for the credit-check data, so this sits just above the named-entity-and-privacy-policy level. 2 3 4
The Skeptic
The captured pages place the contracting entity squarely in Europe: Billie GmbH in Berlin, entered in the commercial register of Berlin Charlottenburg, with BaFin named as supervisory authority and privacy policies published for both Billie and Klarna. Beyond that it goes dark — we found no public information on where payment data is processed or stored, on subprocessors, on hosting, or on a data processing agreement — while the ordering flow shares personal, company and transaction data with Klarna and unnamed partner companies for credit checks. 2 3 4
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.
0 — No public prices at all; every rate is a sales conversation.
3 — A headline rate published for one method or card type, or a "from" percentage.
5 — Rates published per main method with domestic and international cards distinguished, and any monthly or plan fee stated with its billing period; ancillary fees (currency conversion, chargeback, payout) may still be missing or "on request".
8 — Every method priced publicly, cross-border and currency conversion markups stated, chargeback, refund and payout fees listed, minimum monthly fees and contract term given, and whether the model is blended or interchange++ said plainly.
10 — Complete fee computability: the effective rate derivable for a given volume, card mix and country mix — interchange++ with the markup published or a blended rate with every exception listed — plus volume tiers, reserves and every ancillary fee on a public page.
The Finance Lead
No merchant rate, per-transaction fee, monthly fee or contract price appears on the captured pages; the only pricing statements are buyer-side late-payment charges and default interest, a no-monthly-fee announcement for the upcoming Billie cards, and payouts described as net of unspecified fees and deductions. From these pages a merchant cannot compute an effective cost for their own mix. 3 4 6
The E-Commerce Lead
The only published fee terms I found are buyer-side default charges — a late payment flat fee, dunning and collection costs, default interest — alongside an "up to 25 %" processing-cost reduction claim, while payouts are described as net of "fees and any deductions" without amounts. We found no public merchant rates for the invoice or installment method, so I cannot compute an effective fee for my own volume. 1 3 4 6
The SaaS Founder
The only published figures are a claim of up to 25 % lower payment processing costs and buyer-side terms: installments that are interest- and fee-free, plus unnamed late-payment flat fees, collection costs and default interest charged to the buyer. I found no published merchant rate on the captured pages — only that payouts arrive 'less our fees and any deductions' — so I cannot compute an effective fee from public information. 1 3 6
The Payments Engineer
The only figures we found are buyer-side — interest-free, fee-free installments and no monthly fee for the announced Billie cards — plus a merchant-facing claim of cutting payment processing costs by up to 25 %, which is not a rate. The fee Billie charges the merchant appears only as unspecified fees and deductions netted from the daily payout, so a merchant cannot compute an effective fee for their own mix from these pages. 1 3 4 6
The Compliance Officer
We found no public information on merchant fees — no headline rate, per-transaction percentage or monthly fee appears on the captured pages, and the payout option is chosen at contract setup, so an effective cost cannot be derived from public material. The published price statements are buyer-side only: installments described as interest-free and free of charge, and enumerated default costs (a late payment flat fee, dunning and collection costs, default interest) given without amounts; the 'up to 25 %' processing-cost reduction is a marketing claim, not a rate. 1 3 4 6
The Skeptic
No merchant rate appears on any captured page: the payout process deducts 'our fees and any deductions' without a figure, and the closest thing to pricing is a marketing claim of cutting payment processing costs by up to 25 percent. The only fee items published are the defaulting buyer's — a late-payment flat fee, dunning and collection costs, default interest — and even those carry no amounts. For a merchant, every rate here is a sales conversation. 1 3 4 6
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Billie
Is Billie European?
Not determined: the vendor’s pages as captured do not say where Billie is based.
Where does Billie store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Billie have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to Billie?
As of 3 Nov 2026, the panel rates Adyen (3/5), Mollie (3/5) and Novalnet (3/5) highest among the other 35 Payment products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Adyen (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Billie alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (billie.io, billie.io/impressum, billie.io/agb/billie-klarna, billie.io/en/terms/billie-klarna, help.billie.io/merchant/s/article/How-does-the-dunning-process-work-merchant?language=en_US, help.billie.io/merchant/s/article/What-are-the-payout-options-for-the-merchants-merchant?language=en_US and 1 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page billie.io Checked 3 Nov 2026 Details →
- 2 Imprint — found from the homepage www.billie.io Checked 3 Nov 2026 Details →
- 3 Payment methods & local coverage — found from sitemap www.billie.io Checked 3 Nov 2026 Details →
- 4 Payment methods & local coverage — found from sitemap www.billie.io Checked 3 Nov 2026 Details →
- 5 Subscriptions & recurring payments — found from sitemap help.billie.io Checked 3 Nov 2026 Details →
- 6 Settlement, reconciliation & API — found from sitemap help.billie.io Checked 3 Nov 2026 Details →
- 7 Settlement, reconciliation & API — found from sitemap help.billie.io Checked 3 Nov 2026 Details →