"How long will it take?" is the question every payout team hears daily. The answer depends on the rail, the amount, the currency, and a few things that have nothing to do with the rail at all.
The rails at a glance
Timings are for payments sent from Xace accounts on business days. They are the current published timescales and can change.
- UK Faster Payments (GBP) - up to £100,000: immediate. Above: one business day.
- SEPA (EUR) - up to the equivalent of £100,000: immediate. Above: one to two business days. SEPA Instant is available for near-real-time euro payouts.
- SWIFT (any currency, international) - one to five business days, depending on the route.
- TARGET2 (high-value EUR) - zero to two hours.
- CHAPS (high-value GBP) - zero to two hours.
Inbound SEPA settles same day. Inbound SEPA Instant and Faster Payments are near-real-time.
Which one to use
- Domestic GBP: Faster Payments up to £100,000. CHAPS when a larger amount has to land the same day.
- EUR in Europe: SEPA, or SEPA Instant when seconds matter, which is most player withdrawals. TARGET2 for large treasury moves that need same-day finality.
- Everywhere else: SWIFT. The route decides the speed. For USD, get the intermediary bank details from the beneficiary up front; wrong or missing ones are the difference between one day and five.
For player payouts, the rail is rarely the bottleneck. A withdrawal sits in your own approval and compliance queue far longer than it sits on SEPA Instant. Fix the queue first.
Batch payments
Paying hundreds of affiliates one at a time is the wrong tool. Upload a .csv, .xls or .xlsx of up to 1,000 payments and send them as one batch.
- Pick one validation format for the file, for example IBAN + BIC. It applies to every line, so different formats mean different files.
- Fill in the template from Templates and Guides in your account.
- Upload. Every line is checked automatically.
- Fix any invalid lines. Nothing is sent until the whole file passes.
- Submit. All payments go together.
Batch payments are switched on by the Xace operations team on request. A Per Batch Payment approval policy lets you require sign-off on the whole batch. Note that file uploads skip Verification of Payee, so control where the file comes from.
Recurring payments can be scheduled too, and history and receipts export per account.
Where the time really goes
When the rail is fast and the payment is slow, it is almost always one of these:
- Waiting for approval. Check the policy has an alternative approver and a sensible expiry.
- A Close Match or No Match on the payee. Someone has correctly stopped to check. Fix the payee, not the payment.
- Compliance review. New payees, unusual amounts and some corridors get a look. Payees that were approved on creation clear faster.
- Intermediary banks. Missing SWIFT details send the payment on a tour.
- Cut-offs. A one-day rail submitted late on Friday lands Monday.
The short version
Use SEPA Instant and Faster Payments for player withdrawals and keep the internal queue short. Batch affiliate and supplier runs weekly. Save TARGET2 and CHAPS for treasury moves where the fee does not matter. Collect full SWIFT details when you onboard a payee, not when the first payment is late. Send runs in the morning, mid-week.
