How a hosted crypto checkout knows you paid

Older ways of buying things with crypto asked you to send coins to an address and then prove it: paste the transaction hash, upload a screenshot, wait for someone to look it up. Our checkout does not work that way. You pay on a hosted checkout page, and it tells us by itself when the payment is complete. This guide explains what happens behind that page, step by step, and why it is both faster and safer than pasting hashes.

Step 1: the order fixes the price

When you press "Continue to payment", we create your order first. It records the card balance you chose, the top-up charge (15% of that balance), the $5.00 issue fee and the total. That total is locked in. Nothing that happens later, including a change to our rates, alters it.

We then ask our payment partner, PayerURL, to open a payment session for that order. The request carries the order reference, the total in US dollars and the address it should report back to once the money arrives. The partner answers with a link to a payment page made for this one order, and your browser is sent there.

Step 2: the checkout turns dollars into coins

On the hosted page you pick how to pay: USDT on TRC20, BEP20 or ERC20, or USDC, BTC, ETH, or Binance Pay. For each choice, the checkout converts the dollar total into an exact amount of that asset and generates the details to pay to: an address on the chosen network, or a Binance Pay request. A timer shows how long that quote stays valid, because crypto prices move. Why quotes expire covers that timer.

Importantly, the address on this page belongs to this payment session. That is how the checkout knows the money that lands there is yours and is for this order.

Step 3: your payment travels

You send from your wallet or exchange. For on-chain payments, the transaction goes out to the network and waits to be included in a block, then gathers confirmations. Each network has its own pace: stablecoins on cheap networks often confirm within a minute or two, bitcoin can take much longer. Binance Pay settles between accounts and is usually quick.

While this happens, your order in our dashboard still reads "Awaiting payment". That is expected; nothing has been confirmed yet.

Step 4: the checkout watches and decides

The payment partner watches the session address. When the transaction has enough confirmations, it compares what arrived with what the quote asked for and marks the payment as complete. If less arrived, it records the actual amount, so an underpayment is visible rather than hidden.

Step 5: a signed message reaches us

The partner then sends our server a message saying, in effect, "order such-and-such is paid; this much arrived; here is the payment reference". That message is signed with a secret shared only between our server and the partner. Before trusting it, our server recalculates the signature and checks it matches. A message with a missing or wrong signature is rejected and logged, so nobody can mark an order as paid by sending a fake notice.

A genuine notice moves the order from "Awaiting payment" to "Pending review" and stores the amount received, the currency and the reference. You get an email and a dashboard notification at the same moment. If the same notice arrives twice, which can happen with networks, the second one changes nothing.

Step 6: a person takes it from there

The automatic part ends here. A member of our team now reviews the paid order, compares the received amount with the total and issues the card. Paid orders are usually checked and issued within a few hours. The order page shows the payment reference and the time of payment, so you can see exactly what the checkout reported.

Why no transaction hash is needed

• No typos. A hash copied by hand can be wrong or belong to someone else's payment. The checkout matches payments by the session address, which cannot be mistyped.
• No reuse. With hash-based systems, one payment could be claimed for two orders. A payment to a session address can only belong to that session.
• Less to share. You never send us wallet screenshots that reveal balances or other transactions.
• Faster review. The reviewer starts with a confirmed amount instead of hunting for a transaction on an explorer.

When the automation needs help

A few situations still need a human conversation:

• A payment sent after the quote expired, which may no longer match the session.
• A payment on a different network than the one chosen on the checkout.
• A payment that arrived short because a fee was deducted from it.

In each case, open a support ticket with the order reference. Fixing an underpaid order covers the most common one, and keeping proof of a crypto payment explains what to have ready.

What you see versus what happens

The how it works page puts these stages in the context of the whole service, and the pricing page shows what an order costs.

Quick answers

Can I pay the checkout from someone else's wallet?

Technically yes, because the checkout matches the payment by address. Keep in mind that refunds of eligible balances go to the address entered in the refund form.

Does the checkout see my wallet balance?

No. It only sees the incoming payment, which is public on the blockchain anyway.