How to Accept Billie Payments: A Guide to B2B BNPL at Checkout

September 4, 2026 at 07:00 AM

How to Accept Billie Payments: A Guide to B2B BNPL at Checkout

Billie is one of the few buy now pay later providers built specifically for business buyers rather than consumers, and that difference changes what the integration looks like. A consumer BNPL flow needs a name and an email. A B2B flow needs to identify a company, check its creditworthiness in real time, and then behave like a trade credit arrangement rather than a card payment. This guide covers what accepting Billie actually involves, the four routes to getting it live, and the operational details that catch merchants out after go-live.

What Billie does, and who carries the risk

Billie lets a business buyer complete a purchase and pay on invoice terms, while the merchant gets paid up front. Billie runs an instant credit decision on the buying company at checkout, and Billie assumes the credit and default risk from there. For the merchant, that turns what would otherwise be an accounts receivable problem into a normal settled payment.

Billie reports more than 1.3 million business buyers, over 9,000 active merchants, and more than 3 billion euro in processed volume across Europe. Its product line splits into three shapes: Pay Later (the merchant is paid up front, the buyer chooses terms), Pay in X (instalments), and Pay on Account (a trade credit arrangement).

The practical case for offering it is average order value and conversion on B2B carts. Business buyers routinely expect to pay on account, and a checkout that only takes cards forces a purchasing decision into a personal payment instrument. That is the same pattern we looked at in our guide to choosing a B2B payment mix: the constraint is rarely the card rail, it is whether the buyer can pay the way their finance function actually works.

Where Billie is available, and in which currencies

Availability depends on which route you use, so check the specific list for your provider rather than assuming a single European footprint.

Through Adyen, Billie covers twelve markets: Germany, Austria, Switzerland, France, Spain, Italy, the Netherlands, the United Kingdom, Denmark, Finland, Norway and Sweden. Supported processing and settlement currencies are EUR, GBP, NOK, SEK and CHF, with a two day settlement delay on payouts.

Through Briqpay, the Billie payment method page currently lists Austria, France, Germany, the Netherlands, Norway, Sweden, Switzerland and the United Kingdom, with support for B2B flows, hosted payment pages, captures, partial captures, refunds and partial refunds.

The four routes to accepting Billie

Direct with Billie. A REST API, SDKs, or a supported shop plugin, contracted directly with Billie. Most control, most work, and a separate integration to maintain alongside whatever else your checkout runs.

Through a PSP you already use. Billie is available through Adyen, Stripe, Klarna, Mollie and Kustom. If you already run one of these, this is usually the shortest path to live: activate the method on your existing account rather than building anything new.

One wrinkle worth knowing if you go the Adyen route: Billie is served over Adyen's Klarna connection rather than as a standalone Adyen method, so it appears in the API and in your reporting as a Klarna family payment method. That surprises people who go looking for a billie action type and do not find one. If you are setting up Adyen from scratch at the same time, our step by step Adyen integration guide covers the surrounding work.

Through a payment orchestration layer. Rather than integrating Billie once per provider, you integrate once and switch providers behind it. More on that below.

What the checkout has to send

B2B BNPL needs company identity, not just shopper identity, and this is the part that most often fails on a first integration attempt. Through Adyen, the required company object includes:

• Company name (required)
• Registration number (required, except in Germany and Austria)
• Registry location as an ISO country code (required)
• Tax ID, company type and homepage (optional)

You also send a shopperName object for the individual placing the order, plus the usual billing and delivery addresses and line items. Billie's credit decision is made against the company, so a missing or mistyped registration number is the difference between an instant approval and a decline that looks like a bug.

Two presentation options exist. A redirect flow sends the buyer to Klarna to authorise, or an inline widget keeps them in your checkout, which on Adyen means setting paymentMethod.subtype to sdk. Recurring payments are not supported for Billie.

The operational part most integration guides skip

Billie's own go live checklist is mostly about what happens after authorisation, and it is where the B2B nature of the product really shows:

• Turn automatic capture off. Capture manually, after the goods ship, not at order placement. Multiple partial captures are supported, which matters for split shipments.
• Submit the invoice and tracking information at capture. This is not optional housekeeping. Billie is buying a receivable, and the invoice is the instrument.
• Take your own bank details off the invoice and state Billie clearly as the payment method. If the buyer pays you directly because your IBAN was printed on the invoice, you have created a reconciliation problem for both sides.
• Display the Billie checkout badge and payment description correctly, per Billie's checkout design guide.

Refunds support full and multiple partial refunds, so post purchase adjustments behave the way you would expect.

Accepting Billie through Briqpay instead

If Billie is the only alternative method you will ever add, a direct or single PSP integration is fine. The reason merchants end up at an orchestration layer is that Billie is rarely the only one. A realistic European B2B checkout wants Billie in the DACH markets, invoice or leasing options in the Nordics, cards everywhere, and local wallets in specific markets, and each of those is another contract and another integration if you build them one at a time.

With Briqpay, Billie is configured as one method in a single API integration. That means:

• One integration, provider flexibility retained. Billie can run through Adyen, Klarna, Mollie or Stripe underneath, and you can change which without rebuilding your checkout.
• B2B specific logic, applied selectively. Show Billie only for company purchases, only in the markets where it is enabled, or only above an order value threshold, without shipping new checkout code each time.
• Combined with the rest of the mix. Billie sits alongside cards, invoicing and local methods in the same payment method catalogue rather than as a separate flow.

The cost side matters too. Every method you add through a separate integration adds engineering and operational overhead that has nothing to do with the payment itself, which is a large part of what actually drives checkout costs.

FAQ

Does Billie run a credit check on my buyer, and what happens if it fails? Yes, an instant credit decision on the buying company at checkout. A decline is a credit decision on that company, not an error in your integration, though a missing or incorrect company registration number will also produce a decline, so check that first.

When do I get paid? Billie pays the merchant up front and takes on the credit and default risk. Through Adyen, payouts carry a two day settlement delay.

Can I offer Billie only to business customers? Yes, and you should. Billie is built for B2B purchases and its credit decision is made against a company. Through Briqpay you can gate it to B2B sessions and to specific markets rather than showing it to every shopper.

Do I need a direct contract with Billie? Not if you access it through a PSP you already have. Activating Billie on an existing Adyen, Stripe, Klarna or Mollie account is generally faster than a direct integration, and through Briqpay the underlying provider stays yours.

Why does Billie show up as Klarna in my Adyen integration? Because Adyen serves Billie over its Klarna connection. It is the expected behaviour, not a misconfiguration.