Bacs
The UK batch payment rail for direct debits and bulk credits.
Bacs is a t+2 payment rail routed by KeyBS Pay. The UK batch payment rail for direct debits and bulk credits.
Payouts routed through Bacs settle to beneficiary accounts in GB. Where Bacs is available for the destination country, it is the default rail for eligible payouts.
Every Bacs payout is subject to KYB, KYC and sanctions screening. Pricing is disclosed in full before approval; failed payouts return a signed webhook event with a machine-readable reason code and remain refundable per program policy.
Corridor mechanics at a glance
Every KeyBS Pay payout follows the same operational contract; only the rail changes.
How a Bacs payout moves through KeyBS Pay
Bacs settles in t+2 on eligible GBP destinations.
Popular Bacs searches
Auto-generated from real query patterns across the KeyBS Pay hub.
Ask AI about the Bacs rail
Tap any question to open a KeyBS AI conversation prefilled with your query.
Countries reachable via Bacs
Bacs by industry
Bacs developer resources
Frequently asked questions
What is Bacs?
The UK batch payment rail for direct debits and bulk credits.
How fast is Bacs?
T+2. Actual settlement time is disclosed pre-approval and confirmed by signed webhook once the beneficiary bank acknowledges the credit.
Which countries can I reach through Bacs?
GB. Availability is beneficiary-bank-dependent; the router falls back to wire if the beneficiary bank is not on Bacs.
What currencies are supported on Bacs?
GBP is the primary settlement currency for Bacs. Multi-currency corridors are supported where the rail permits.
What limits apply on Bacs?
Rail-specific ceilings apply; the platform surfaces them pre-approval. Higher-value transactions are automatically routed to wire.
Is Bacs available 24/7?
Real-time rails (others) operate around the clock. Batch and wire rails follow the local banking window.
How do I integrate Bacs?
You don’t. KeyBS Pay abstracts rail selection: submit a payout to POST /v1/payouts and the router picks the fastest eligible rail. Use "method": "auto" (default) or force a specific method where policy requires.
Is Bacs regulated?
Yes. KeyBS Pay routes Bacs payouts only through partners licensed for the destination corridor.
Can I get a Bacs settlement report?
Yes. Per-rail, per-corridor reconciliation reports are available in the dashboard and via API export.
What happens if a Bacs payout fails?
Failed payouts return a signed webhook event with a machine-readable reason code. Funds remain in the source ledger and can be re-routed or refunded.
How is pricing set for Bacs?
Quote-based, disclosed in full pre-approval. No undisclosed intermediary-bank deductions on eligible local rails.
Can I use Bacs for consumer payouts?
Yes, where the beneficiary and route policy permit consumer flows. Stablecoin routes are business-only.
Are there cutoffs on Bacs?
Real-time rails have no cutoffs. Batch and wire rails follow local banking-day windows; cutoffs are shown at quote time.
Does Bacs support idempotent retries?
Yes. Every KeyBS Pay payout carries an Idempotency-Key so retries after transient errors are safe.
Which industries use Bacs most?
Marketplaces, cross-border trade, workforce and NGO programs are the largest users of Bacs on the KeyBS Pay platform.
Route your first Bacs payout
Rail selection is automatic — you never have to pick one manually unless program policy requires it.