Payout rails

What happens after the gate opens

Everything that decides whether a payout may happen sits upstream of this page: the balance a player must reach, any hold that applies, the identity check before a first payout, and the per-state settings that may close redemption in a jurisdiction that is open to play. All of that is documented in the redemption engine, and it is where the policy work is.

This page starts one step later, at the moment a payout has been approved and something physical has to happen. From here the questions are mechanical: which rail, what does the recipient have to get right, what does it cost, and what do you do when it comes back.

The rails, and what each trades off

Four ways money reaches a person. One of them is ours, and only on the managed platform; the rest you arrange yourself on either route. They are described here anyway, because choosing between them is a decision you will make regardless of who supplies them and the trade-offs are not obvious until you have run a queue.

• Push to card

  Yours, on both routes

  What sets the speed

  The receiving issuer, not the sender. Two payouts sent at the same moment to two cards can arrive days apart.

  Who bears the cost

  The operator, per payout, unless it is passed on to the recipient — which is a policy decision with a support cost attached.

  How it fails

  The card has been closed, reissued or does not accept pushed funds. The payout comes back and has to be reissued down another rail.

  What the recipient needs

  A card in the recipient's own name that accepts credits.

• Bank transfer

  Yours, on both routes

  What sets the speed

  The rail's own clearing cycle and the receiving bank. Nothing the sender does makes it faster.

  Who bears the cost

  The operator, per payout, typically less than a card push.

  How it fails

  Details typed wrongly, an account that has been closed, or a name that does not match the one you verified. Returns can arrive days after the payout looked successful.

  What the recipient needs

  Account and routing details, entered correctly, in a name that matches their verified identity.

• Pay by bank

  Yours, on both routes

  What sets the speed

  The recipient's own bank, once they have authorised it there.

  Who bears the cost

  The operator. Pricing is per payout and depends on the provider.

  How it fails

  Their bank is not supported, or they abandon the authorisation part-way. The mistyped-details failure disappears, because nothing is typed.

  What the recipient needs

  An account at a supported bank, and to complete an authorisation in their own banking app.

• Crypto

  Ours on the managed platform

  What sets the speed

  The network, and what the sender is willing to pay in fees at that moment.

  Who bears the cost

  The operator pays the network fee. It varies with congestion rather than with the size of the payout.

  How it fails

  Differently from everything above it, and this is the one to understand: an address typed wrongly or a transfer sent on the wrong network is gone. There is no return, no reversal and nobody to ask. Every other rail on this table has a path back.

  What the recipient needs

  A wallet address, on the right network, exactly right.

Notice what is missing from that comparison: how long each one takes, and what each one costs. Both are real questions and neither has an answer that would survive being written down here — they are set per provider, per merchant and per country, and they move. What is stable is who bears the cost and what determines the speed, so that is what the cards carry. Ask each provider for their own figures, in writing, and date them.

Where payouts fail

• The bounce after the balance is goneA payout is approved, the Sweeps Coins balance is deducted, the transfer is sent — and days later it comes back. The player's balance now says zero and no money has arrived, which is the worst place a player can be left standing: their money is neither in the account nor in their hand. It is also entirely foreseeable, which is why it has a callout of its own below.
• The name mismatchVerification was passed under one name and the receiving account is in another — a spouse, a maiden name, a nickname on the bank record. The rail rejects it or the bank holds it, and there is no way to resolve it that does not involve asking a person for documents at the worst possible moment.
• Details entered wronglyThe most common and the most boring. Everything downstream of it is expensive: a support contact, a manual reissue, and a player who has been told twice that money is on its way.
• The one you cannot undoA crypto transfer to the wrong address. There is no reissue path that does not come out of the operator's own money, so the decision to be made in advance is whether you will cover it, and under what circumstances.

Queue discipline

A payout queue is a promise with a clock on it. What damages a brand is rarely the size of a payout and almost always the silence around a slow one — a player who has been approved and not paid tells other players, and the telling outlives the delay.

Three habits are worth having before volume arrives. Know your oldest pending item at any moment, not your average age, because the average hides exactly the item that will be screenshotted. Separate the queue that is waiting on you from the queue that is waiting on a bank, so nobody spends the morning chasing something no human can accelerate. And make sure that whoever can see the queue is also allowed to act on it, because a queue watched by someone without authority to release anything is a dashboard, not a process.

Who runs this on each route

Read the first two rows together, because they are the whole arrangement on the managed platform: the decision is ours to enforce against your policy, and the transfer is yours to execute. On an API integration both are yours, and we never see the redemption at all.

If you are a player