Receiving Payments

Payments arrive directly in your own Monero wallet. This processor is non-custodial: it never holds your funds, and it never holds a spend key. You give it view-only access so it can watch for incoming payments and generate a unique receiving address per charge — that's all.

Never share your spend key or seed.

We only ever ask for your secret view key. A view key lets us see incoming payments; it can never move your money. If anything claiming to be us asks for your spend key, mnemonic, or 25-word seed — it is not us. Walk away.

What you provide

  • Primary address — your wallet's standard address (starts with 4).
  • Secret view key — 64 hex characters. Watch-only; cannot spend.

We validate offline that the view key matches the address before saving it. The view key is stored encrypted at rest; the address is public.

Finding your secret view key

  • Cake Wallet: menu → Wallet keys / seed → copy the view key (secret).
  • Monero GUI: Settings → Wallet → Show seed & keys → Secret view key.
  • Feather: Wallet → View Keys → Secret view key.
  • monero-wallet-cli: run viewkey and copy the secret value.

Then go to Dashboard → Settings → Receiving, paste both values, choose your confirmation threshold, and save.

How a payment flows

  1. For each charge, we derive a unique subaddress under your own wallet from your view key.
  2. The customer pays that subaddress. The funds land directly in your wallet — they never pass through us.
  3. We watch the blockchain (view-only) and mark the charge confirmed once it reaches your confirmation threshold.
  4. You receive a charge.confirmed webhook. There is no payout step — the money is already yours.

Important: keep your wallet able to see new addresses

Every charge uses a new subaddress under your wallet. Your wallet only detects subaddresses inside its lookahead window (Monero wallets scan a bounded range of subaddress indices ahead of the last one used). If you issue charges faster than your wallet scans, a payment can be on-chain and confirmed by us, yet not show in your wallet until it catches up. The funds are never lost — they are at the subaddress — but to avoid confusion:

  • Open / sync your wallet regularly so it keeps pace with the subaddresses we issue.
  • Dedicate this wallet (or a fresh account within it) to your store, so our issuance doesn't collide with subaddresses you create by hand.
  • High volume? Raise your wallet's subaddress lookahead, and expect to keep the wallet open.
  • If a payment "didn't arrive," rescan / fully sync your wallet before assuming anything is wrong — check the charge's address on a block explorer.

Confirmations

Choose how many blockchain confirmations a payment needs before we mark a charge confirmed (3 ≈ 6 min, 5 ≈ 10 min, 10 ≈ 20 min — recommended). Fewer confirmations are faster but carry a small reorg risk; use 3 only for low-value payments where speed matters.

Privacy note

A view key reveals all incoming payments to your address to whoever holds it. Only configure hosts you trust, and prefer a wallet/account dedicated to this store rather than your personal savings wallet.