Skip to main content
Use this checklist before requesting production access. Completing certification (when required) and these steps helps ensure a smooth go-live.

​
Pre-Launch Requirements

Before you request production enablement, confirm:
  • Credentials: Sandbox integration is working with your sandbox API key and you understand how to switch to production credentials. See How to Obtain API Keys and Production vs Sandbox.
  • Merchant and processor setup: Merchant settings, processor credentials, and any feature toggles (e.g. network tokenization) are configured as needed for production. See Merchant Settings.
  • Webhooks: Webhook endpoints are configured, signature verification is implemented, and handlers respond with 2xx only after processing. See Webhooks Guide and Creating a Webhook.
  • Idempotency: Payment and refund requests use idempotency keys or otherwise avoid duplicate charges on retries. See Webhooks and your integration flows.
  • TLS and security: You use TLS 1.2+ and follow Security Best Practices.

​
Mandatory Test Cases

When certification is required, Revolv3 sends test cases to the merchant based on their implementation and specific use cases. Your onboarding manager will provide the exact test cases and instructions when you are ready for certification—Revolv3 does not publish a single fixed list, since requirements vary by integration.

​
Production Enablement Process

  1. Complete sandbox testing: Test the flows you need for go-live. When certification is required, your onboarding manager will provide the specific test cases for your implementation.
  2. Complete certification (if required): Run through the test cases and any readiness review your onboarding manager provides. Use the contact points below to request or schedule certification.
  3. Request production access: Contact Revolv3 (see below) to request production enablement. Include correlation IDs and sample payloads when asking for certification or go-live support.
  4. Receive production credentials: Production API key, portal access, and any processor-specific credentials. Keep these separate from sandbox.
  5. Switch endpoints and keys: Update your integration to use production base URL and API key. See Production vs Sandbox for endpoints and Production Environment Limitations for rate limits.

​
Contact Points for Certification and Go-Live

For certification questions, production enablement, and go-live support:
  • Support: Log into the Revolv3 portal (production or sandbox) and use the help icon to submit a support ticket. Include timestamps, request IDs, correlation IDs, and sample request/response payloads when reporting issues or requesting certification support.
  • Appendix and escalation: Revolv3 Appendix lists contacts, glossary, and quick operational notes.
Your onboarding manager will share the certification playbook and any readiness or go-live appointment details when you are ready.