Client call
One integration is the contract with the game client. The wallet calls the cashier and reads a credit result and a separate payout result. Familiar rails in the next market should not mean starting the client over.
The wallet and the cashier need a shared id
The join stores one id for the player and another result for money leaving. A shop plugin that only returns success does not keep those records apart.
In India the question to write down first is the rail, the name, and the state, before the wallet moves. This page does not say a rail is already switched on.
Bank transfers
A repeat top-up should stay on the brand's own checkout. Saved details can make the next purchase shorter, including a one-click return, only for a player the game already knows. The rail, the name, and the amount still have to match that player. If they do not, nothing is credited, even if the phone already shows the transfer as done.
The bank can already hold the funds while this title still shows an open credit. The name match can still be unfinished, or the rail can be shop-only and silent about this title. An open credit cannot be spent. Anything over the cap is neither a bonus nor a fresh credit under a new id. Leave support one transfer, one figure, and one decision. Paying straight from a bank, with no card in the middle, is a separate rail and still needs the same id.
Prize payouts
Payouts can be asked for when the player asks, not only on a weekly batch. Prize money and partner earnings should not mean a clerk typing one transfer at a time. The return is not handing back a purchase that never became play. A refund gives the unused credit back. A payout pays the win only to the wallet's owner. Each event keeps a separate ceiling, a separate review, and a separate status word.
The receiving account must already sit on that player's record. An account first used that day, or one standing in another person's name, still blocks that prize after the play was valid. The player can read why. The note cites the mismatch, the open item, or the absent review. A single yes across both directions is how the wallet drifts from the cash the studio holds.
Rails named in the written offer
Players already pay with cards, wallets, and bank rails where they live. The join should offer those, not a foreign list. A rail is on only when the written offer names this studio, this title, and this state.
UPI
A shop rail. It can fund a wallet only after this studio is named by both the provider and the bank. A logo does not say that.
RuPay and cards
Debit is one offer and credit is another. A card that works in a shop can stop on this title. Disputes return on the card. The packet is the transfer, the identity, and the purchase.
Netbanking
Useful when a card is refused or the amount is above a wallet cap. The name printed on the transfer is what gets matched. It takes longer to match than a card authorisation.
IMPS and NEFT
Bank rails with a delay of their own. Paying a winner this way does not undo a card. Money can travel from the player's bank to the studio with no middle hop, and that path still needs its own ceiling.
Wallets
Some players will not put a bank card on the title. The game must already know the player who holds that wallet or voucher. A top-up with no name does not become balance the player can spend. Digital assets, if the contract names them, are their own rail and not a way past a bank that has already refused the studio.
State if settlement stays in INR or moves currency, and name the side that moves. No rate is printed here. A buried conversion is not a quote the studio can sign. Each rail still needs a ceiling of its own before go-live, and the studio writes that ceiling into the file before launch.
Credit, purchase, then the prize
1
Marking the credit
The wallet changes only after the cashier marks the credit final and stores the shared id.
2
The purchase leaves
The purchase can leave the wallet only after that credit exists.
3
The title settles
The game closes the result. Winnings wait until review. A changed result means the payout pack is written again. It is not an unseen second credit.
4
The prize
The prize is sent, or the player can read the refusal.
Each row keeps its own id. A signable day splits cleared credits, refused credits, payouts, and fees into rows. No row list means there is no statement.
Permission is its own file
The person funding the wallet is identified first. The studio still needs a permission of its own wherever the statute asks for one. A firm that only carries the message can pass a result and can stop a payout. Carrying a message is not the studio's permission. This is not legal advice.
State permission and the moving firm's policy are different answers. The title on the client is a third answer. If a partner says one join covers every state, ask which permission they are quoting. Clearing ordinary shop takings does not clear this title.
Clearance in one state does not follow the player across the border. The cashier should be able to block a market without relabeling the studio as retail.
One contract, two results
Pay page
The player completes payment on the provider's page, then comes back. The studio still matches the name before the wallet moves.
Notices
A changed status, a decline, or a held payout each return on their own. The earliest yes is not the finished record.
Only a bank that has already named this studio and this title should see the earlier refusal. Pushing a declined purchase at a retail acquirer so it will say yes is not routing. Before the client is public, rehearse a decline, a wrong name, and a status that updates. Always-yes replies from a sandbox prove nothing. The wallet records the purchase. The cashier records the money. They need the shared id on both sides.
Studio file and client
Company
Studio papers, plus whoever owns and directs the studio, not only whoever fills the form. A title operated for another party still names that party.
Website
The live client, a plain account of what the player can buy or play, and the Indian state that offer is for. Writing gaming on a slide does not describe the title.
Flows
State whether credits, payouts, or both are required, and name the rails for each.
History
Processing statements if you have them, including chargebacks. If you have none, say so. A made-up history is worse than a thin file.
Questions on the join
Can this join in India take UPI?
Only if both the provider and the bank accept the studio. UPI is a shop rail, not a standing yes for the title. Request a written yes for this title on the account offered.
Do top-ups and payouts share one arrangement?
No. Each direction has a status of its own and failure words of its own. Paying a winner is not a refund. A bank payout and a reversal down the first rail are different paths.
Which papers does a studio file start with?
Studio papers, the client, who controls the studio, the title, the state, and any processing history. A first title is not the pack used when card disputes already exist.
How is a card dispute unlike bonus abuse?
A chargeback is the cardholder opening a dispute on that charge. Bonus abuse breaks the rules of the title. The transfer record can show the money. The studio has to show the purchase and the promotion.
Do prizes need a path of their own?
Yes. The path is chosen before the title is public, not when the first large prize appears. Give every path a ceiling and a review. If a question is still open after this list, it belongs in the file, not in a guessed answer.
Book the studio review
Send the client, the state the studio sits in, and whether credits, payouts, or both are in scope. Write down the inbound rails and the outbound rails. This preview saves nothing and does not mail the file.
Send the join