What is this demo?

This is a self-contained, sandboxed walkthrough of what it feels like for a customer to pay with — and get paid in — stablecoins through receivecoins.com on a merchant's site. "Good Casino" is a fictional brand built only to give the flow a realistic home — no real games, deposits, withdrawals, or gambling happen anywhere in this folder.

receivecoins.com supports both directions of money movement: merchants receive coins from customers (deposits) and send coins out to customers (withdrawals). This demo shows both.

The deposit journey (receive)

1. Merchant site — Good Casino's homepage, with a Deposit button like any real merchant would have.
2. Payment method — the customer chooses Pay by Card or Pay with Coins (Pay by Card is inert in this demo; the focus is Pay with Coins).
3. Amount — with Pay with Coins selected, they pick or type a deposit amount (defaults to $1,000).
4. receivecoins.com checkout — a separate, distinctly-branded checkout page opens: choose a coin and network, then send funds to a demo deposit address.
5. Confirmation — a "Simulate payment received" control (visible only in this demo) triggers the confirmed state and redirects back to Good Casino with the balance updated.

The withdrawal journey (send)

Deposits redirect to a hosted receivecoins.com checkout page because the customer is the one entering payment details there. A withdrawal is the opposite: Good Casino itself is sending funds out via receivecoins.com's Send capability, so there's no customer-facing page to hand off to — it's shown here as an embedded receivecoins.com panel inside Good Casino's own Withdraw flow, rather than a redirect.

1. Amount — from the balance chip, the customer clicks Withdraw and chooses how much of their balance to cash out (quick 25/50/75/Max chips or a custom amount).
2. Coin, network & address — an embedded receivecoins.com panel lets them pick a coin/network and enter their own wallet address to receive funds.
3. Review & confirm — a summary of the amount, coin, network, and destination address before sending.
4. Sent — a simulated broadcast sequence, then a confirmation with a demo transaction hash; the balance is deducted immediately.

What's real vs. simulated

The layout, copy, and interaction patterns reflect how a production receivecoins.com checkout behaves. The deposit addresses, QR codes, transaction hashes, and balances are all generated locally in your browser — nothing is sent to a server, a blockchain, or receivecoins.com's live systems.