Wallet Infrastructure
Wallet Infrastructure
Platform & Onboarding

Go-Live Checklist

What to confirm before moving to live.

Account

  • Your business is verified, and you have a live project and live API key. See Verification and Team.
  • Each API key has only the scopes it needs, and live keys are stored only on your server. See Authentication and API Keys.
  • Your team members have the right roles.

Wallets and payments

  • Passkeys register on your production domain, and rpId and origins match it.
  • Customers are credited only on deposit.confirmed.
  • Payments are marked paid only at confirmed (transaction.success).
  • Retries follow Reliability: no resubmitting after a timeout without reading the state first.
  • You handle every error on the pages you use, including insufficient_funds, wallet_not_found and idempotency_conflict.

Notifications

  • A live webhook endpoint is registered on each project, including your payment-links project.
  • Signatures are verified, old events are rejected and duplicates are skipped. See Setup and Verification.
  • Your endpoint responds 2xx quickly and processes events afterwards.

Recovery

  • Wallets are enrolled for recovery, and customers have a verified recovery contact. See How Recovery Works.

Operations

  • You reconcile your records against List transactions and balances regularly.
  • Your client backs off on 429. See Errors and Limits.
  • You log request_id from errors, to quote when you contact us.

On this page