Skip to content

4 min read

Payments for SMM panels: balance top-ups by card or crypto

How a social media marketing panel can accept top-ups by card or crypto, credit balances on confirmation, handle short payments, and keep fees low on small amounts.

A panel window with a balance bar filling, small order rows drawing from it, the top-up in greenA panel window with a balance bar filling, small order rows drawing from it, the top-up in green
On this page

A social media marketing panel doesn't sell one thing at checkout. Its customers, often agencies and resellers, keep a balance on the panel and spend it across dozens of small orders a day. The payment that matters is the top-up: how a customer adds funds, how fast the balance shows it, and what happens when a transfer lands a little short.

This post covers how an SMM panel can take balance top-ups with 402pay: a payment for each top-up, the balance credited when it confirms, the fees that matter on small amounts, and the rules on what a panel can sell.

Why a panel runs on a balance

Panel orders are small and frequent, and many are placed through the panel's own API by a reseller's software rather than by a person at a checkout. Paying for each order would mean a checkout, a confirmation wait, and a fixed fee every time. A balance turns that into one payment now and then, and lets orders draw from it instantly.

It also means the panel holds money its customers haven't spent yet. Track it as a ledger, not a number you overwrite. Our post on crediting a prepaid balance from webhooks covers that design, and prepaid balance or pay per order weighs the two models side by side.

A row of five steps: the customer adds funds, checkout confirms the payment, a signed webhook reaches the panel, the panel credits the balance, and orders spend from it.A row of five steps: the customer adds funds, checkout confirms the payment, a signed webhook reaches the panel, the panel credits the balance, and orders spend from it.
A top-up is the only payment. Orders spend from the balance it credits, with no checkout of their own.

A payment for every top-up

When a customer picks an amount on your Add funds page, your server records the top-up, creates a payment for it with the top-up's id as the reference and the customer's id in metadata, and sends them to the payment's hosted checkout. Amounts can be set in USD, EUR, GBP, CAD, or AUD, starting at $1.00 or its equivalent.

Create a top-up's paymentNode.js
app.post("/add-funds", requireUser, async (req, res) => {  const amount = Number(req.body.amount);  const topUp = await db.topUps.create({ userId: req.user.id, amount });   const response = await fetch("https://dash.402pay.co/api/v1/payments", {    method: "POST",    headers: {      Authorization: `Bearer ${process.env.PAY402_SECRET_KEY}`,      "Content-Type": "application/json",    },    body: JSON.stringify({      amount: amount.toFixed(2),      currency: "USD",      reference: topUp.id,      description: "Panel balance top-up",      metadata: { user_id: req.user.id },      success_url: "https://example.com/add-funds",    }),  });  const { data } = await response.json();  res.redirect(303, data.url); // the payment's hosted checkout});

The reference does two jobs. It ties the payment back to the top-up when the webhook arrives, and it makes the request safe to retry: if the call times out and your server sends it again with the same reference, it gets the payment that already exists rather than a second one. Our post on idempotency keys and safe retries covers the rest of that pattern.

A payment link per top-up size works for a first test, but a link doesn't carry your own customer id. For a balance the API is the better fit: the reference and metadata tell your panel exactly whose balance to credit.

Customers pay the way they already do

Checkout offers cards, Apple Pay, and Google Pay beside every coin and network you accept. An agency holding USDT on Tron pays with that; a first-time customer with no crypto pays by card. Either way the top-up reaches your wallet as crypto, and your panel 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 the balance on confirmation, exactly once

Credit the customer when the payment.succeeded webhook arrives, not when they come back from checkout. It's signed, so your panel 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 saying beside the coin on your Add funds page.

A delivery your server doesn't answer is retried, so the same event can arrive more than once. Write the credit as a ledger entry keyed by the payment's id, in the same transaction that marks the top-up done, and a repeat delivery finds it already there.

Credit what was paid, once, when it's final.

Short top-ups

Short payments are more common on small amounts. A customer withdrawing from an exchange may not notice the exchange took its fee out of the transfer. 402pay handles these in three tiers:

Within your toleranceShort 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 shortThe payment becomes underpaid. Checkout tells the customer how much is left, to the same address at the same rate, and payment.succeeded follows when the rest arrives.
Never completedYou can accept what arrived as the full payment, or once the quote expires, send the customer a new checkout for exactly what's left.

A balance makes the third tier simple: credit what arrived, and the customer's next order spends exactly that. Every checkout has its own address, so a short transfer is never ambiguous about whose balance it belongs to. The guide to underpayments and overpayments covers each option in more detail.

Fees on small top-ups

A successful stablecoin payment costs 1% + 10¢, billed on your fee statement and never taken out of the deposit. On a large top-up the fixed part disappears; on a small one it doesn't:

$5.00 top-up$0.15 fee, 3% of the amount.
$10.00 top-up$0.20 fee, 2% of the amount.
$25.00 top-up$0.35 fee, 1.4% of the amount.
$50.00 top-up$0.60 fee, 1.2% of the amount.
$100.00 top-up$1.10 fee, 1.1% of the amount.

Two settings help. You can have customers pay 402pay's fee, which adds it to their total at checkout, and you can set a minimum top-up so the smallest one still makes sense. The network fee is separate: the customer's wallet pays it on top of what they send. On Ethereum it can be a real share of a few dollars, so many panels steer small top-ups to stablecoins on Solana or Tron. See pricing for every fee.

Refunds, overpayments, and customers you need to stop

  • An order that fails or delivers only partly is usually refunded to the customer's balance. That's a ledger entry on your side; no money moves, and the funds stay in your wallet.
  • A refund out of the panel is a send from your wallet, in the coin and amount you choose. See refunds and disputes.
  • A customer who sends too much gets payment.overpaid beside payment.succeeded, and the whole amount lands in your wallet. Most panels credit the extra to the balance.
  • If a customer abuses your checkout, you can block them, and checkout stops accepting 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 top-up back or reverse it. The social media panels page summarizes the product for panels, and the accept a payment guide walks through the API from the first request.

Common questions

  • Yes, for services our Unacceptable Risk Policy allows. Customers add funds through a hosted checkout by card, Apple Pay, Google Pay, or crypto, and every top-up lands in the panel's own wallet. Card availability is set for each business.
  • When the payment.succeeded webhook arrives, which means the transfer has confirmed on its network. Credit once per payment, since webhooks can be delivered more than once.
  • A shortfall within the panel's tolerance, 0.5% by default, counts as paid. A larger one marks the payment underpaid, and checkout asks for the rest at the same rate. The panel can also accept what arrived and credit that.
  • A successful stablecoin payment costs 1% + 10¢, so $0.20 on a $10.00 top-up, and the panel can pass it on to the customer. The network fee is paid by the customer's wallet on top of what they send.

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.