Skip to main content
Walk this list before you flip a service to Mainnet mode. Each item is a single check; do all of them.

Service configuration

  • Mode is set to Mainnet.
  • Base URL points at the production origin (https://api.myproceeds.xyz).
  • Auth method matches the production upstream (production secrets, not test secrets).
  • Networks include only the chains you intend to accept on.

Paywall configuration

  • Pricing is final. Update any client-side caches that store the challenge.
  • Allowed HTTP methods match the production endpoint.
  • Target URL points at the production upstream path.
  • Custom headers and query parameters are correct.
  • Paywall passes Test in the dashboard.

Agent guidance

  • Service categories, contact email, and docs links are filled in via the per-service overflow drawer.
  • Homepage or API reference is set so the generated OpenAPI includes externalDocs.url.
  • Agent guidance is accurate for agents. Write it as instructions, not marketing.
Do not treat registry listing (x402scan, MPPScan) as a launch requirement. Share the charge URL. See Help agents call your API.

End-to-end behavior

  • x402 URL returns 402 with no payment, and 200 with valid payment.
  • MPP URL works for any Tempo-enabled paywalls.
  • Transactions show Completed for a real test payment (nanopayments: PendingCompleted after Gateway batch settlement).
  • Events show REQUEST → SUCCESS.

Settlement and operations

  • Wallet balances appear correctly for the chains you enabled.
  • You know how to withdraw to a wallet you control.
  • If you need USD, connect a US bank in Settings and complete Bridge KYC/KYB for ACH bank off-ramp.
  • Webhooks are configured and signature verification is tested (if you consume events on your server).
  • You can reach the dashboard if a paid request fails.
When every box is checked, you’re ready.

Monitor payments

How to watch transactions, events, and wallet balances in production.