Take a bet from the player your card form just declined
The bettor watching the match already holds a wallet — they fund in USDT or USDC from wherever they are, the deposit credits your Paymos balance, and a confirmed top-up can't be clawed back. When you settle the bracket and clear the withdrawal, the winner's wallet credits in seconds. Licensing in each market stays with you.
Where the esports money leaks before it reaches your book
Why do card rails lose an esports audience at the deposit?
The bettor who follows a Twitch bracket from Manila or São Paulo is the one your card form is built to refuse — and the rails that do take the bet skim the rest.
Your best bettor holds a wallet, not a usable card
Esports betting lives in Southeast Asia, LatAm, and the CIS, on a young audience that already moves money in USDT. The card a 22-year-old in Jakarta tries is exactly what issuers decline most — prepaid, thin file, a geography flagged high-risk. They want the bet and the form says no, while the same player would sign one wallet transaction without a second thought.
The category is refused before your odds load
An issuer reads betting as high-risk and blocks a cross-border deposit on the code alone — your licence never enters the decision. The few acquirers that underwrite an esports book price that appetite hard: stack reserves and platform fees and you commonly land at 5–15% all-in, on a book whose margins are already thin.
The "0.5%" crypto gateway bills you twice
A rival processor leads with a headline near 0.5%, then a swap markup, a per-transfer fee, and merchant-paid gas land on the deposit — and the same stack lands again when you push the winnings out. Counted across both legs the real take usually reaches 1.5–2% or more. You priced your odds against the headline, not the bill.
The winnings wire crawls while your stream moves on
Esports settles in real time — a final ends and the chat wants paying. A cross-border wire to a winner adds a fee and a banking-day wait, and a "didn't authorise that bet" reversal costs the stake plus a per-dispute fee while the ratio creeps toward a surcharge. Meanwhile a processor parks a reserve on cash you've already earned.
What a wallet-funded book gets back
What does an esports book gain by taking the bet on-chain?
Four things turn in your favour the moment the deposit stops going through an issuer that was never going to approve it.
The geography that declined the card now pays
A wallet deposit answers to no issuer and no border. The player in Jakarta or Buenos Aires funds the same dollar stablecoin a player in Berlin does, from the wallet they already keep their balance in. You bank the global, crypto-native demand esports actually has, instead of leaking it to a card-decline screen.
A confirmed top-up is yours to keep
No bank sits between the bettor and your book to refuse the category, and once a deposit confirms on-chain it is final — no "didn't authorise that bet" reversal weeks later, no per-dispute fee, no chargeback ratio inching toward a fine. The balance credits your Paymos balance as the deposit clears, with nothing held back in a reserve.
The rate you price your odds on is the rate you settle on
Paymos is one flat 1.0% on a settled deposit, and that figure already absorbs acceptance gas, the sweep, and same-token settlement — no swap markup, no separate transfer line. The payout side adds no second processing fee: Paymos takes nothing on a withdrawal, you cover only a reduced network fee, less than the chain bills direct. Numbers laid out in Pricing.
The winner is paid before the lobby empties
You settle the bracket, your rules clear the withdrawal, and the payout broadcasts to the player's wallet — landing in seconds whether they sit one timezone away or twelve, with no banking-day wait. A contested map, a forfeit, a replay: how you read the result is yours alone. Paymos only moves the money once you release it.
Three ways to plug the cashier in
Which integration suits how your book runs?
Whether you run your own odds engine or push deposits through Discord and stream overlays, there is a route that fits.
Host-to-Host API — for your own odds and settlement engine
Run your own pricing and bracket settlement? The REST API gives create-invoice, watch-confirmations, and signed-payout calls, all delivered over HMAC-SHA256 webhooks keyed to your own order id. A confirmed deposit credits the player; a settled bracket fires one signed outbound transfer once your rules pass. Sandbox runs the same code as production.
See details
Embedded Checkout — a deposit panel on the bet slip
For the everyday top-up, an embedded panel sits right on the betting page. The bettor taps "pay in stablecoin," signs, and the cashier credits in seconds — no jump to another domain, no bet slip lost on the way. It runs beside whatever card and transfer options your card-native players still reach for.
See details
Payment Links — for stream and Discord promotions
Promoting a tournament special through a Twitch overlay, a Telegram channel, or a Discord server? Generate a payment link in the dashboard and drop it where the audience already is. The player pays from any wallet, your balance credits in seconds, and the cashier reflects it — no integration to ship for an off-platform push.
See detailsHow the cashier plays out in practice
What does a wallet cashier look like across a tournament?
Four moments from a live esports book — the pre-match top-up, the region cards refuse, the payout after the grand final, and the season-long regular.
Pre-match top-up — Embedded Checkout
A bettor catches the bracket reveal and wants in before the first map. They open the panel on the bet slip, sign one stablecoin transaction, and the cashier credits the balance in seconds — bet placed with time to spare. No prepaid or cross-border card decline to kill the deposit at the worst moment.
The region a card would refuse — Embedded Checkout
A player in a market issuers flag high-risk pays a dollar stablecoin from the wallet they already hold. The deposit credits in full in seconds — no cross-border interchange, no exchange-rate surcharge, no issuer rejecting the card on geography. A bettor a card form would have turned away is now placing bets.
Grand-final payout — Host-to-Host API
The final ends, your engine resolves the bracket, and your rules clear the withdrawal. One call to the payout API sends one transfer, and the winner's wallet credits in seconds — as quick to a player twelve timezones away as one next door, with no wire fee and no multi-day hold while the chat waits.
The season regular — renewal invoice
A bettor who plays every week of the split funds the book on a fresh invoice each cycle, paid from their wallet in one tap. Nothing is stored to expire and nothing is auto-pulled — the player approves each period, a renewal never fails on a lapsed card, and a player who's done simply leaves the next invoice unpaid.
Running an esports book on a wallet rail
Frequently asked questions
A map gets replayed and the result is contested — does Paymos decide the payout?
How fast does a deposit confirm so a bettor doesn't miss the match?
How is the winner's payout actually signed and sent?
Who runs player KYC and age checks — Paymos or the operator?
Does Paymos flag match-fixing or arbitrage on bet patterns?
Can we trust the sandbox numbers before we go live?
Honest disqualifier
When an esports book should pass on this rail
Four cases where a wallet cashier is the wrong tool — said plainly, so you find out now and not after integration.
Your age and identity stack isn't carrying its own weight yet
An esports audience runs young, and on cards the issuer quietly does a slice of the age filtering for you. A wallet deposit arrives with no name, no birthdate, no issuer — your own KYC layer decides, alone, who is old enough to bet. If that layer isn't ready to be the only gate, harden it before you add a rail that strips the card's hints.
Wallet-funded wagering is barred where you hold your licence
A handful of regimes that license esports betting still single out crypto deposits as the part they won't permit — sometimes only for certain licence classes. Whether yours is one of them is a question for your counsel, not your PSP. Paymos doesn't rule on it and no integration detail changes the answer, so get the reading first.
Your bonus-abuse defence is built on card and device data
A stream drop pulls a wave of sign-ups, and the multi-account farming that rides in is usually caught with shared card fingerprints and device telemetry from the card stack. Wallet deposits don't carry those tells, and a fresh address costs nothing to spin up. Make sure your abuse rules can read on-chain signals before you aim a promo at this rail.
You settle the books in fiat, on a bank's calendar
Paymos pays you in stablecoins, to your own wallet — there is no conversion leg and no wire into an operating account. A book that reports in EUR or GBP and pays staff, data feeds, and tax from a bank will need its own exchange step between wallet and bank. If you'd rather not own that step, this rail will pull against your back office.
Related flows
Other iGaming & Betting sub-niches on Paymos
Pricing
1.0% on a settled deposit. Acceptance gas covered, nothing skimmed on the payout
The flat 1.0% on a deposit already takes in acceptance gas, the sweep, and same-token settlement — no swap markup, no currency conversion, no reserve held against your float. On the payout Paymos takes nothing; you cover only a reduced network fee, below what the chain bills direct. High-volume books qualify for a lower rate on request, down to 0.3%. For scale: card-rail betting acquirers commonly land at 5–15% all-in once reserves are counted, and rival crypto gateways advertise from 0.5% yet settle nearer 1.5–2% once swap, transfer, and network costs hit deposit and payout both.
See pricing