🟦
By implementing Billie through Stripe you get seamless B2B payments with 30-day repayment terms, making the B2B payment process simple for both you and your customer.

Background

Stripe introduced new capabilities that allow merchants to send additional data to connected partners like Billie via the Payment Intent object. These enhancements enable Billie to process richer transaction data, resulting in:

Better risk assessments
Higher buyer Acceptance Rates
Fewer false declines
More transparency for your support and operations teams

Your existing integration (Merchant → Stripe → Billie) will continue to work as is. However, we highly recommend adopting these enhancements to unlock better performance without any disruption to your current setup

Getting access to the new attributes

Some of these attributes are new to the Payment Intent Request and they are temporarily gated. Each merchant will have to request access to them but Billie can help to accelerate the process. In that case, contact your Key Account Manager or email merchants@billie.io

Billie Payment Method Options, is not yet in Stripe’s public documentation. A temporary PDF guide is available. [For Merchants] Billie - Payment Method Options.pdf (If you are sharing a PDF version of this document, please download and send the PDF)

Merchant Integration Update

To take advantage of these improvements, you can update your Payment Intent requests to include the following additional data. These updates are optional but strongly encouraged.

Data Element	Required by API?	Primary Benefit	If Missing
Customer Information	Optional	Higher conversions, skip identity form	Extra form on HPP
Order Line Items	Optional	Better risk scoring, more approvals	Less certainty in risk decision
Buyer Organization	Optional	Full B2B context, smoother checkout	Extra form on HPP
Internal Order Reference	Optional	Faster support resolution	Slower support workflows

Customer Information

Why

By collecting and sharing customer data up front — which you likely already have — you eliminate an extra data collection step from Billie’s side. This results in a smoother checkout experience and better conversion rates for your buyers.

What happens if not updated

If this information is missing or incomplete, Billie will display a data collection form on the order confirmation Hosted Payment Page (HPP). Our analytics show that buyers are often frustrated by having to re-enter information they already provided to you, which can negatively impact conversion.

How to implement it

Create a Customer object in Stripe Create a customer | Stripe API Reference
1. Required: name, email
2. Optional but recommended: phone, address
Stripe will return a customer_id (e.g. cus_xxxxx).
Pass the customer_id in the Payment Intent using the customer field Create a PaymentIntent | Stripe API Reference

Order Line Items

Why

By providing Billie with detailed context about the order — not just the total amount — we can make a more informed risk decision based on the actual articles your buyers are selecting. This typically leads to higher buyer Acceptance Rates while also helping to reduce operational risk.

What happens if not updated

Billie will assess the transaction using other available data. However, certainty in risk assessment may be reduced, which can impact approval rates.

How to implement it

Create a PaymentIntent | Stripe API Reference

When creating a Payment Intent, populate the amount_details object. Include: discount_amount, shipping, tax
Add a line_items array with item details: amount, description, quantity, product
For more detail, refer to Stripe’s documentation Payments line items

Buyer Organization

Why

Billie is a B2B payment method, and transactions are created by your customer on behalf of an organization. Sharing this information upfront removes an additional step from Billie’s process, improves conversion rates, and helps reduce operational risk.

What happens if not updated

Billie will show a form on the HPP to collect organization data. This can create friction for buyers and reduce conversion.

How to implement it

Create a PaymentIntent | Stripe API Reference

Populate payment_method_options.billie.company_details with the following attributes: registered_name, registration_number, registered_address (line1, line2, city, postal_code, country), vat (if known)

Example:

"payment_method_options": {
  "billie": {
    "company_details": {
      "registered_name": "Zeta Electronics Gold GmbH",
      "registration_number": "HRB 934855",
      "registered_address": {
        "line1": "Tannenweg 4",
        "line2": "",
        "city": "Haslach im Kinzigtal",
        "postal_code": "77716",
        "country": "DE"
      },
      "vat": "DE812345678"
    }
  }
}

Internal Order Reference (Merchant Order ID)

Why

Billie sends post-purchase communications in parallel to yours. Sharing the same internal order reference improves customer support response time and buyer satisfaction.

What happens if not updated

Buyers and Billie may need additional time to identify the correct order during support interactions, which can slow resolution.

How to implement it

Create a PaymentIntent | Stripe API Reference

Populate payment_method_options.billie.reference with your internal order ID:

Example:

"payment_method_options": {
  "billie": {
    "reference": "ORDER-12345-ABC"
  }
}

In total the payload of the payment method options for billie will look like this:

"payment_method_options": {
  "billie": {
    "company_details": {
      "registered_name": "Zeta Electronics Gold GmbH",
      "registration_number": "HRB 934855",
      "registered_address": {
        "line1": "Tannenweg 4",
        "line2": "",
        "city": "Haslach im Kinzigtal",
        "postal_code": "77716",
        "country": "DE"
      },
      "vat": "DE812345678"
    },
    "reference": "ORDER-12345-ABC",
    "capture_method": "manual"
  }
}