B2B invoicing
Every invoice leaves your ERP with its own IBAN. Paid means paid, the moment the money lands.
Unique virtual IBANs. Instant reconciliation. One webhook.
Paybyrd Pay by bank gives every customer, invoice or order its own virtual IBAN. When the transfer lands, in seconds over SEPA Instant or on the usual timeline over standard SEPA, it is matched automatically and a payment.received webhook fires exactly like a card payment.
Give every customer, invoice, or order its own IBAN. When the transfer lands, it matches itself, and your systems hear about it exactly the way they hear about a card payment. At a flat fee per transfer, not a percentage.
Illustrative simulation. Figures, names and events on this panel are generated to demonstrate the flow — they are not live production data.
One shared IBAN, a free-text reference, and a customer who types whatever they like. Finance spends the afternoon matching. Nobody knows an invoice is paid until someone looks. A virtual IBAN removes the guesswork: the account itself says who paid.
One API call creates an IBAN for a customer, an invoice, or an order. Thousands, if you need them.
Print it on the invoice from your ERP, show "Pay by bank" in your checkout, or push it into your CRM. Any reference text works, or none.
The transfer arrives over SEPA Instant, matches the invoice automatically, and payment.received hits your webhook, identical to a card.
Anywhere card fees sting and a bank transfer already makes sense. Now without the reconciliation tax.
Every invoice leaves your ERP with its own IBAN. Paid means paid, the moment the money lands.
Offer "Pay by bank" next to cards on €2,000 baskets, travel, furniture, tuition, and keep the margin.
Deposits and balances for hotels and travel agencies, matched to the booking without a single email.
Close the day, every day. One ledger for cards and bank, no unallocated cash to explain.
If you already take cards with Paybyrd, you already have the integration. Virtual IBANs are a resource, not a project.
{
"reference": "INV-2026-0418",
"amount": 4200.00,
"currency": "EUR",
"customer": "cus_8kLm2P"
} { "iban": "PT50 0035 0418 0000 2026 0418 7", "status": "awaiting_funds" } A small fee per bank payment rather than a percentage of the basket: the bigger the ticket, the more you keep. Your rate is agreed with the sales team alongside your card pricing.
Already integrated? Ask your account manager to enable virtual IBANs.
Yes. Our accounts fully support SEPA Instant, so transfers from banks on the instant scheme arrive in seconds. Standard SEPA credit transfers to the same IBAN land too, on the usual timeline.
Each virtual IBAN belongs to exactly one invoice, order, or customer. Whatever the payer types in the reference field, the money arriving on that IBAN is the match. No rules engine, no manual allocation.
Either. Per invoice gives you exact matching; per customer gives repeat payers one number to save. Mix both if it suits your flow.
No. Virtual IBANs are created through the same REST API you already use, and payments arrive on the same webhook endpoint as your card events. Cards and bank share one ledger.
A low per-transfer fee rather than a percentage, agreed with the sales team alongside your card pricing. Creating IBANs, reconciliation, and webhooks are included.
The payment is still matched to its invoice or customer, and the event carries the amount received, so your system decides what happens with a partial or over-payment, exactly as with a card.
Tell us where the money comes from today: checkout, invoices, or both. We'll agree your rate and switch on virtual IBANs on your existing integration.