Payments on a gaming platform look different from a typical store. The amounts are small, the same player buys again and again, and they're waiting in the middle of a session for credits to show up. A top-up that takes an hour to land, or lands short and nobody notices, becomes a support ticket.
This post covers how to sell top-ups, credits, and passes with 402pay: one payment per purchase, credits applied when the payment confirms, the fees that matter on small amounts, and how to handle a player who sends a little less than they owe.
A payment for every top-up
Each top-up is its own payment. When a player picks a bundle, your server creates a payment for its price with the top-up's id as the reference and the player's id in metadata, then sends the player to the payment's hosted checkout. Prices can be set in USD, EUR, GBP, CAD, or AUD, starting at $1.00 or its equivalent.
The reference does two jobs. It ties the payment back to the top-up when the webhook arrives, and it makes creating the payment safe to repeat: the same reference returns the payment that already exists rather than a second one, so a player double-tapping the buy button doesn't end up with two open payments. Our post on idempotency keys and safe retries covers the rest of that pattern.
If your bundles are fixed and you sell them outside the game, on a community page or in a chat, a payment link per bundle works too. Every player who opens it gets a payment of their own.
Players pay the way they already do
Checkout offers cards, Apple Pay, and Google Pay beside every coin and network you accept. A player holding USDT on Tron pays with that; a player who has never owned crypto pays by card. Either way the payment reaches your wallet as crypto, and your server hears about it the same way.
Crypto quotes hold their rate for 15 minutes by default, long enough to switch to a wallet app and send. Card availability is set for each business, and cards cost 4% + 30¢ per transaction.
Credit on confirmation, exactly once
Credit the player when the payment.succeeded webhook arrives, not when they return from checkout. It's signed, so your server can verify it came from 402pay, and it means the transfer has confirmed on its network and can't be undone. On Solana that takes seconds and on Tron about a minute; on Bitcoin it takes minutes, which is worth telling players before they choose it.
A delivery your server doesn't answer is retried, so the same event can arrive more than once. Mark each top-up credited in the same transaction that adds the credits, and skip it the second time. That one rule removes the most common way game economies leak money through payments.
async function onPaymentSucceeded(payment) { const topUp = await db.topUps.find(payment.reference); if (!topUp || topUp.credited) return; // already handled const due = Number(payment.amount) + Number(payment.customer_fee); const received = Number(payment.amount_received); // Paid in full (or more): credit the bundle that was ordered. // Accepted short: credit in proportion to what arrived. const credits = received >= due ? topUp.credits : Math.floor((topUp.credits * received) / due); await db.topUps.credit(topUp.id, credits);}The handler reads amount_received rather than assuming the bundle was paid in full. On a normal payment the two match. The difference shows up only when you've chosen to accept a short payment, which is the next section.
Credit what was paid, once, when it's final.
Short payments
Short payments are more common on small amounts. A player withdrawing from an exchange may not notice the exchange took its fee out of the transfer, and on a $5 top-up a fixed withdrawal fee is a large share. 402pay handles these in three tiers:
| Within your tolerance | Short by up to your underpayment tolerance (0.5% by default, adjustable to 0%, 0.5%, 1%, 2%, or 5%), it counts as paid in full and succeeds. |
|---|---|
| Further short | The payment becomes underpaid. Checkout tells the player how much is left, to the same address at the same rate, and payment.succeeded follows when the rest arrives. |
| Never completed | You can accept what arrived as the full payment, or once the quote expires, send the player a new checkout for exactly what's left. |
Because every checkout has its own address, a short transfer is never ambiguous: it belongs to one top-up and one player. Accepting it fires payment.succeeded, and the handler above credits in proportion to what arrived, so accepting a short payment never hands out the full bundle. The guide to underpayments and overpayments covers each option in more detail.


Overpayments
A player who sends too much gets the bundle, and the whole amount lands in your wallet. You get payment.overpaid alongside payment.succeeded, and can send the extra back from your wallet or credit it, as your policy says.
Fees on small payments
A successful stablecoin payment costs 1% + 10¢, billed on your fee statement and never taken out of the deposit. On a large order the fixed part disappears; on a small top-up it doesn't:
| $2.00 top-up | $0.12 fee, 6% of the price. |
|---|---|
| $5.00 top-up | $0.15 fee, 3% of the price. |
| $10.00 top-up | $0.20 fee, 2% of the price. |
| $25.00 top-up | $0.35 fee, 1.4% of the price. |
| $50.00 top-up | $0.60 fee, 1.2% of the price. |
Two settings help. You can have customers pay 402pay's fee, which adds it to their total at checkout, and you can set bundle sizes so the smallest one still makes sense. The network fee is separate: the player's wallet pays it on top of what they send, and checkout shows an estimate beside the total. On Ethereum it can be a real share of a few dollars, so many platforms offer stablecoins on Solana or Tron for their smallest bundles. See pricing for every fee.
Late transfers and players you need to stop
- A transfer that arrives after the quote expired is still matched to its top-up, by its address, and marked as needing review. Hold the credits until you accept it or send it back.
- A transfer on the wrong network lands at the same address and is held for review the same way.
- If a player abuses your links, you can block them as a customer, and checkout stops taking their payments on your links. See block a customer.
Whatever happens, the money sits in your own wallet the whole time. 402pay can't hold a player's payment back or reverse it, and refunds are a send from your wallet. The gaming solution page summarizes the product for gaming platforms, and the accept a payment guide walks through the API from the first request.
Common questions
- When the payment.succeeded webhook arrives, which means the transfer has confirmed on its network. Credit once per top-up, since webhooks can be delivered more than once.
- A shortfall within the business's tolerance, 0.5% by default, counts as paid. A larger one marks the payment underpaid, and checkout asks the player for the rest at the same rate. The business can also accept what arrived.
- A successful stablecoin payment costs 1% + 10¢, so $0.15 on a $5.00 top-up, and the business can pass it on to the customer. The network fee is paid by the player's wallet on top of what they send.
- Yes, where cards are available for the business. Card payments cost 4% + 30¢, and reach the business's wallet as crypto like any other payment.
See what 402pay can do for you.
Discover how 402pay helps your business accept any card and get paid in crypto, straight to a wallet you control.







