Accept Faster Payments from UK customers on one API.
BazPay accepts Faster Payments — Faster Payment, BACS Direct Debit and Faster Payments Instant Credit Transfer — from any customer with a participating local settlement account. Mandate capture, settlement timing and R-transaction events all run through the same platform that handles your card acceptance.
Built for merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms and professional-services businesses. One direct regional acquirer, one EUR settlement balance, one signed webhook stream across every rail.
Why accept Faster Payments through BazPay
Faster Payments acceptance is worth doing right — it reaches every UK current account on one scheme, avoids card interchange for higher-ticket transactions and shortens the reconciliation trail for finance teams. Four properties make that easier here.
-
Accept Faster Payments across the UK
Faster Payments reaches every UK current account, 24 hours a day, every day of the year. A single BazPay integration lets you accept Faster Payments from any customer with a participating local settlement account, without opening a bank relationship per country.
-
Mandate management built in
BACS Direct Debit mandates are captured, stored and versioned inside the platform. You get a stable mandate reference on the charge object; renewals and reversals ride on the same reference.
-
Predictable settlement timing
Faster Payments settles within seconds where both banks participate; BACS credit settles same or next business day; BACS Direct Debit follows the three-working-day BACS cycle. Every charge carries the expected settlement date on the response.
-
Cards and Faster Payments on one contract
Faster Payments acceptance sits alongside card, wallet and local payment method acceptance on the same platform. You reconcile all rails against the same GBP balance and the same signed event stream.
The Faster Payments rails you can accept
Three Faster Payments scheme variants plus cross-rail alignment. Each is a dashboard toggle away once boarding completes — no re-integration per rail.
-
Faster Payments
Faster Payment
Shopper-initiated bank-to-bank credit transfers into your merchant settlement account. Useful for higher-ticket B2B invoices and for shoppers who prefer bank rails to card entry. Settlement lands same or next business day depending on cut-off.
- Push
- Same/next day
-
BACS Direct Debit
BACS Direct Debit
Merchant-initiated pulls under a stored mandate. B2C and B2B rulebook variants supported. Ideal for recurring invoices, subscriptions and any charge where the shopper has authorised repeated collection.
- B2C
- B2B
- Recurring
-
Faster Payments
Instant Faster Payment
Faster-rails version of a BACS credit: funds credited within seconds where both banks participate. Automatic fallback to standard BACS credit for corridors where one bank is not enrolled.
- Sub-10 seconds
- Fallback Faster Payment
-
Cross-rail
Faster Payments alongside cards and wallets
The same charge object accepts Faster Payments, card or wallet payments. Offer bank-transfer, card and Apple Pay on the same checkout without stitching three vendors — a dashboard toggle per rail.
- Cards
- Wallets
- LPM
Deeper coverage on Faster Payments reference; broader processing context on Single Euro Payments Area processing; bank-side authentication on open banking.
From mandate to settled dollar
Six stages describe the path a Faster Payments payment takes from the shopper's authorisation to settlement into your settlement account. Every stage change fires a signed webhook keyed to the charge ID.
-
Collect authorisation
For BACS Direct Debit, the shopper signs a scheme-compliant mandate. For a Faster Payment, the shopper initiates the transfer from their bank.
-
Create the charge
One REST call creates the charge with the mandate reference or the transfer reference. Idempotency keys make the request safe to retry.
-
Submit to rail
The platform submits the Faster Payments message inside the current settlement cycle. The response returns the expected settlement date and the mandate reference.
-
Wait for the cycle
Faster Payments confirms within seconds. A BACS credit confirms same or next business day. BACS Direct Debit confirms per B2C or B2B cycle — every stage change fires a signed webhook.
-
Settle to your settlement account
Funds credit your merchant settlement account. Interchange++ statements break out the Faster Payments lines per mandate for reconciliation into your ledger.
-
Handle exceptions
Returns, R-transactions and dispute events fire signed events on the same webhook stream. The mandate reference stays stable across the whole life of the customer relationship.
Faster Payments acceptance on a payment platform vs bank-only setup
Traditional Faster Payments acceptance goes through a bank relationship. That works — until you want to reconcile Faster Payments and card in one ledger, or fire a signed webhook on an R-transaction. Below is where a payment-platform approach earns its keep.
| Dimension | BazPay (platform) | Bank-only setup |
|---|---|---|
| Contract | Bank rails + card acceptance on one contract | Separate bank + acquirer relationships |
| Mandate storage | Gateway-side, versioned, portable | Stored per bank system, not portable |
| Reporting | Interchange++ lines per mandate | Bank statement, aggregated |
| Rail fallback | Automatic fallback to a BACS credit | Manual re-submission |
| R-transaction events | Signed webhook per return | Batch file per cycle |
| Cross-rail visibility | Faster Payments + card + APM in one dashboard | Portal per rail |
Rate structure on the pricing page. Outbound side of the flow on payouts.
Features engineered into Faster Payments acceptance
Every capability below ships on the standard integration. No premium tier gates Faster Payments Instant, mandate management or R-transaction webhooks.
-
Faster Payment
Bank-to-bank push transfers into your merchant account — useful for B2B invoices and higher-ticket shopper-initiated payments.
-
BACS Direct Debit
Merchant-initiated pulls under B2C or B2B mandates stored gateway-side and portable between rails.
-
Confirmation of Payee
The beneficiary name is checked against the account before the debit is shown, so a mistyped payee is caught before money moves.
-
Mandate management
Scheme-compliant mandate capture, versioned storage and stable reference across renewals. Cancellations and updates fire signed events.
-
R-transaction handling
Returns and refusals arrive as signed webhooks so your dunning stack reacts on the same signature scheme as card retries.
-
Rail reconciliation
Every Faster Payments line breaks out on the settlement report with the mandate reference. Finance teams reconcile per customer without joining three vendor exports.
-
Cross-rail on one contract
Faster Payments sits behind the same charge object as card and APM. Add or remove a rail from a dashboard toggle.
-
Signed webhooks
HMAC-signed, replay-protected events for every Faster Payments state change on the same envelope as card, wallet and LPM events.
A Faster Payments charge in the same shape as a card charge
One versioned REST endpoint creates the charge. The payment_method field
picks the rail; the response object stays canonical. For BACS Direct Debit, the
mandate reference binds to the charge and to every downstream event.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 12900,
"currency": "EUR",
"payment_method": "faster-payments_debit",
"customer": "cus_5F9k",
"mandate": "mnd_02H9",
"metadata": { "invoice_id": "INV-10842" }
}The response returns the canonical charge object with the mandate reference bound and the expected settlement date. Read the full schema in the API reference and handler samples in the developer docs.
Where merchants accept Faster Payments alongside cards
The four profiles below already rely on BazPay for Faster Payments acceptance in production. Each uses the same charge object and the same webhook envelope; the emphasis on BACS Direct Debit vs BACS credit vs Faster Payments differs by business model.
-
B2B invoicing
Professional-services firms sending higher-ticket invoices where the buyer's finance team prefers a bank transfer over a card. Faster Payment clears same day on cut-off.
-
SaaS enterprise subscriptions
Enterprise plans billed by BACS Direct Debit under a B2B mandate, alongside card-on-file renewals for smaller tiers on the same subscription reference.
-
Multi-country e-commerce
Storefronts offering Faster Payments-based checkout alongside cards for shoppers in markets where bank transfer is a preferred rail — one integration reaches both.
-
Utility-style recurring billing
Recurring collections where a BACS mandate authorises repeated pulls under a stable reference over multiple years.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a merchant of record and not a marketplace of third-party PSPs.
Security, mandate compliance and rulebook adherence
Faster Payments processing adheres to the Pay.UK Mobile Money rulebooks (Credit Transfer, Direct Debit and Instant Credit Transfer). Mandate capture follows the scheme B2C and B2B format requirements and stores the mandate versioned so amendments are traceable. Where Faster Payments runs alongside card acceptance, PCI DSS Level 1 covers the card leg and authentication runs through 3-D Secure 2.2.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment (relevant when Faster Payments runs alongside card acceptance)
- Faster Payments rulebooks
- Adherence to the SEPA, Faster Payments and BACS scheme rulebooks
- Mandate compliance
- Scheme-compliant mandate capture and storage; B2C and B2B variants supported
- GDPR
- In-region data residency; DPA on request
- Authentication
- 3-D Secure 2.2 with automatic exemption logic on the card leg where BazPay accepts card + Faster Payments together
Questions merchants ask about accepting Faster Payments
How do I accept Faster Payments as a regional merchant?
Sign up for a BazPay merchant account, receive sandbox credentials and integrate against the REST API or install a maintained storefront plugin. Once merchant underwriting is complete, live keys are enabled and you can accept Faster Payments — Faster Payment, BACS Direct Debit and Faster Payments — from any regional customer with a participating settlement account. Funds settle to your own local settlement account.
What is the typical Faster Payments time from initiation to settlement?
Faster Payments typically completes within ten seconds where both banks are participants. Standard Faster Payment settles the same business day if the transfer is submitted before the day's cut-off, otherwise the next business day. BACS Direct Debit follows the three-working-day BACS cycle. Every BazPay charge response returns the expected settlement date, and signed webhooks fire on each state change.
Which banks that accept Faster Payments can shoppers use?
Every bank inside the Faster Payments scheme's participating countries can send and receive Faster Payments transfers and process BACS Direct Debits. The current geographic scope covers the United Kingdom, Ireland, Belgium, Canada, Greece and Slovakia — each wallet operator publishes its own reachability list. For Faster Payments, participation is opt-in per bank; the wallet operator also publishes the register of participants. BazPay does not itself publish a bank list because that list changes as banks join and leave the schemes.
How does BACS Direct Debit differ from a card charge?
BACS Direct Debit is a merchant-initiated bank-to-bank pull under a mandate the shopper has authorised. There is no interchange fee (Faster Payments carries its own scheme fees), no 3-D Secure step and no card issuer in the flow. The trade-off is a longer settlement cycle and the possibility of an R-transaction (a return or refusal) within the scheme window. BazPay handles the mandate lifecycle and surfaces R-transactions as signed webhooks so your dunning stack reacts on the same signature scheme as card retries.
Can I refund Faster Payments?
Yes. Refunds are issued from the API or the dashboard and return to the original settlement account. For Faster Payment, a refund is a new outbound transfer; for BACS Direct Debit, refunds go through the return path defined in the scheme rulebook. Every refund fires a signed webhook keyed to the original charge ID.
Do I need a separate acquiring bank on top of BazPay for Faster Payments?
No. BazPay is a direct regional acquirer and payment gateway. Faster Payments acceptance runs inside the platform and settles into your regular business settlement account. You do not open a separate acquiring or clearing relationship to accept Faster Payments through the platform.
Are Faster Payments suitable for recurring billing?
Yes. BACS Direct Debit is a natural fit for recurring subscriptions, memberships and utility-style billing under a stored mandate. BazPay's recurring billing surface treats Faster Payments and card-on-file as first-class alternatives on the same subscription reference — the reporting surface tracks retention across both.
Which merchant profiles can accept Faster Payments through BazPay?
Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and does not act as a merchant of record.
Start accepting Faster Payments alongside cards
Share your business model, your mix of BACS Direct Debit vs BACS credit vs Faster Payments, and the customer corridors you need. A named engineer will confirm boarding fit and map the wiring inside one working day.