> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revolv3.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Certification & Go-Live Checklist

> Pre-launch requirements, mandatory test cases, production enablement process, and contact points for Revolv3 certification and go-live.

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 [Authentication](/docs/authentication-security/merchant-access-token) and [Production vs Sandbox](/docs/getting-started/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](/docs/core-concepts/merchants/merchant-setting).
* **Webhooks**: Webhook endpoints are configured, signature verification is implemented, and handlers respond with 2xx only after processing. See [Webhooks Guide](/docs/webhook-events/webhook) and [Creating a Webhook](/docs/webhook-events/creating-a-webhook).
* **Idempotency**: Payment and refund requests use idempotency keys or otherwise avoid duplicate charges on retries. See [Webhooks](/docs/webhook-events/webhook) and your integration flows.
* **TLS and security**: You use TLS 1.2+ and follow [Security Best Practices](/docs/authentication-security/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](/docs/getting-started/production-vs-sandbox) for endpoints and [Production Environment Limitations](/docs/getting-started/production-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](https://portal.revolv3.com) or [sandbox](https://portal-sandbox.revolv3.com)) 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](/docs/appendix/appendix-revolv3) 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.