Skip to main content
Use this checklist before sending production traffic. Complete the steps in order so credentials, customer verification, webhooks, and failure handling are tested before you enable live mode.
Create a business from the Swervpay dashboard and complete business KYC. Production access is enabled for verified businesses.
Store the business ID and secret key in server-side environment variables or a secrets manager. Do not commit them to source control or expose them in frontend or mobile-app code.
In the Swervpay dashboard, open the Developer page and select IP Addresses. Add the static outbound IP address or addresses used by your production servers. Make sure all services that call the production API use an approved IP, and update the allowlist before changing hosting providers or network infrastructure.
Use https://sandbox.swervpay.co/api/v1 to test authentication, customer creation, KYC, collections, cards, payouts, and error handling. Keep production credentials and data separate from sandbox data.
Create the customer and submit the required KYC information before requesting a DEFAULT USD collection account. USD account issuance can be asynchronous, so handle both collection.created and collection.created.failed events.
Create a webhook from the dashboard or with the create webhook API. Subscribe only to the events you need, verify the X-SWERV-SECRET header, return a 2xx response promptly, and make handlers idempotent. Send a test event before going live.
Monitor delivery logs with the webhook logs API and retry failed deliveries with the retry API. Record transaction references and reconcile terminal states instead of treating an accepted request as a completed payment.
After sandbox testing and IP allowlisting are complete, enable live mode in the developer section of the dashboard. Switch to https://api.swervpay.co/api/v1, use production credentials, and verify the first production request and webhook delivery before increasing traffic.