Balance before the slip
Do not accept a stake against a deposit that is still Pending or Failed.
Sportsbooks · India
The search that matters here is betting payment methods, not a renamed casino page. Eligible sportsbooks need a deposit that can complete before a market moves, and a payout after the bet settles.
What players can use
UPI, UPI QR, UPI links, PhonePe, Paytm and IMPS, each with its own open or closed flag and its own amount band. Bank-transfer deposits use IMPS. Wallet deposits use PhonePe or Paytm only when that route is on.
Timing
A sportsbook deposit that is still Pending cannot fund a live bet. Credit the wallet from the signed Success notification. If the player abandons UPI, leave the bet unplaced and let them start a new payment.
Do not accept a stake against a deposit that is still Pending or Failed.
The status check does not change because the event has started. Success is still the only credit.
Minimum and maximum sit on the payment route. Your trading limits stay in the sportsbook.
After settlement
The gateway does not settle bets. Your platform grades the slip, then calls the payout API for the winnings. That call has its own notification. Reconciliation matches the payout reference in the CSV, separate from the original deposit.
Build steps live on the integration page. A casino cashier, including poker, is the casino payment gateway. The wider map is iGaming payment solutions.
The winnings call has its own signed result. Do not read the original deposit status to explain a missing payout.
Store the payout reference beside the graded slip. The deposit reference only explains how the wallet was funded.
Before the stake
A sportsbook cannot treat “the player came back from UPI” as a funded wallet. The status that matters is the signed notification: Pending, Success, Failed or Rejected. Only Success may increase the balance the slip is drawn against. That rule is the same before the event and after it has started. In-play gives you less time. It does not give you a softer status.
Keep the merchant reference from the moment the deposit is created. If the notification is delivered again, apply it once. A double credit is a trading problem as well as a ledger problem, because the extra balance can be staked before anyone notices.
The market can move while the payment is open. The stake waits until Success, or it is not placed.
Credit from the server notification. The return URL is a page the player sees, not proof the book can use.
Idempotency on the merchant reference stops a second notice from funding a second stake.
When it does not clear
Failed and Rejected close that payment. The player may start another deposit on a route that is still open. They may not reuse the closed reference, and they may not place the bet they were trying to fund. Pending stays unfunded until a later notification changes it. Do not expire the bet slip in a way that also throws away the payment reference. Support will need that reference if the player writes in an hour later.
Each betting payment method has its own minimum and maximum. Those bands sit on the route, not on the sport. A UPI link can be closed while IMPS stays open, or the reverse. PhonePe and Paytm appear only when the partner has approved them for this book. Read the live list on a schedule so a closed method is not still painted on the cashier.
A retry is a fresh deposit. The old one stays Failed in both ledgers.
If the player leaves the method, do not invent a Success. Leave the stake unplaced.
The gateway enforces the payment band. Your trading limits stay inside the sportsbook.
Two references
A winning bet produces a second payment, not a comment on the first. The deposit reference funded the wallet. The payout reference, created after your platform grades the slip, is what finance matches when the winnings leave. Daily CSV reports should show those as separate lines. Mixing them makes a settled bet look like a missing deposit, or a deposit look like an unpaid winner.
When a player says the deposit never arrived, use the lost-payment search and poll the result. Do not stake the market, and do not pay the bet, on a screenshot. Pending in the search result is still not Success. The webhook, the search and the CSV are all proven on a test project before production keys. Those build steps are on the integration page.
Match it to the cashier credit. It does not tell you whether any bet won.
Match it to the winnings you decided to release. The gateway does not know the odds.
Poll until there is a state you can book. Then update the wallet, not before.
Out of scope
Odds, voids, pushes and the sportsbook’s own cash-out rules stay in the book. This page moves money after those decisions. If you void a bet, your ledger returns the stake. The original deposit is not reopened, and the gateway is not asked to “undo the match”. If you pay a winner, you call the payout API for the amount you calculated.
Player eligibility, age, geo and which markets you offer are also yours. Unlawful wagering is not onboarded. A casino session, including poker buy-ins, is the casino payment gateway, because that cashier is not waiting on a market. The wider operator map is iGaming payment solutions.
Those are sportsbook rules. This page only moves the money after you decide the result.
The route opens after verification and partner approval. A method list is not a licence, and no settlement clock is published here.
The service is gateway technology. It is not a payment aggregator and it does not grade or hold the stake.
Frequently asked
