Crypto payment gateway go-live checklist
Use this checklist before routing real buyers through a SwapSS Pay crypto checkout. It keeps the launch focused on the parts that usually break merchant payment flows: API credentials, invoice creation, webhook verification, status handling, support visibility, and finance records.
Launch checklist
| Area | Check | Doc |
|---|---|---|
| API access | Create scoped keys, store secrets server-side, and separate test from live usage. | Authentication |
| Test invoice | Create a sandbox invoice and confirm that your checkout stores order_id. | Test mode |
| Invoice creation | Use server-side invoice creation and redirect buyers to payment_url. | Invoices |
| Webhook intake | Verify signatures, dedupe events, and acknowledge quickly. | Webhooks |
| Fulfillment | Reload invoice state and fulfill only when the status is safe for delivery. | Statuses |
| Finance | Store invoice IDs, webhook event IDs, polling checks, and ledger export references. | Reconciliation |
| Security | Keep secrets out of browser code and rotate compromised keys immediately. | Security |
Support handoff
Before launch, make sure support can see the customer order ID, SwapSS invoice public ID, payment status, last webhook event, and last status poll. That is enough context to explain most payment questions without exposing private implementation details.
Related docs: quickstart, webhook verification, and idempotency.