Go-Live Requirements

Use this page to understand what Verto requires before your integration can move from sandbox testing to live production traffic.

1. Complete the production prerequisites

Before you request production access, make sure you can do all of the following:

1. Authenticate successfully in sandbox.
2. Test your core receive, exchange, payout, or sub-account flows end to end.
3. Process webhook events and handle duplicate deliveries safely.
4. Use idempotency keys on write operations that can create financial side effects.
5. Prepare your KYB, compliance, and commercial documentation.
6. Complete the required Country Exposure Attestation before you process live transactions.
7. Complete the Dual-Use Goods Compliance Declaration for applicable trade and payment flows.
8. Plan your production validation, including test data submission and a low-value penny test where required.
9. Build an RFI and compliance-exception workflow before you process live payouts or onboarding cases.

🚦 The Two-Stage Approval Process

🕐

Stage 1 (Baseline): 1-3 weeks after primary KYB and commercial setup.
Stage 2 (Advanced Atlas): additional review for higher-risk and nested account flows.

Your approval path depends on whether you are integrating as a direct fintech or as a platform operating on behalf of downstream users.

1️⃣ Stage 1: Baseline Capabilities

Complete standard KYB, commercial, and compliance setup to unlock baseline production access for your master corporate account.

Baseline setup includes:

• Business verification (KYB): Company registration, business model, proof of operations, and ultimate beneficial owner (UBO) information.
• Standard Customer Due Diligence (CDD): Company verification, UBO identification, PEP and sanctions screening, and risk assessment.
• Commercial agreement: Service terms, SLAs, and approved pricing blocks.
• Country Exposure Attestation: Confirmation that you will not use Verto to transact with prohibited sanctioned persons, entities, sectors, regions, or out-of-risk-appetite jurisdictions.
• Dual-Use Goods Compliance Declaration: Confirmation that Verto transactions will not facilitate military, defence, weapons-proliferation, or prohibited dual-use activity.

If your integration only uses first-party flows, Stage 1 may be enough to start operating in production.

2️⃣ Stage 2: Atlas Advanced Capabilities

Any integration that touches third-party cash networks, regulated downstream users, or higher-risk activity requires enhanced approval by the Compliance Team.

For nested, third-party, POBO, COBO, or reliance-based flows, your Account Manager will guide you through the formal compliance assessment process. This can include document submission, AML policy review, a compliance review interview, RFI responses, approval sign-off, contractual addenda, and implementation sign-off before production access is granted.

Approvals for Stage 2 typically take 4-8 weeks due to enhanced compliance and regulatory review.

3. Validate your operational readiness

Before launch, confirm that your production environment is operationally ready:

1. Store production secrets separately from sandbox values.
2. Confirm production IP allowlisting where required.
3. Enforce MFA for production users and configure approval workflows for sensitive payment actions where required.
4. Deploy webhook endpoints over HTTPS and monitor delivery failures.
5. Log correlation IDs, payment references, and transaction state changes.
6. Confirm the corridors, currencies, jurisdictions, and payout models you plan to support are approved for your account.
7. Submit production test data where required, using non-settled production transactions if your implementation plan requires data validation.
8. Complete a low-value penny test where required to validate data integrity, not only connectivity.
9. Obtain implementation and compliance sign-off before enabling live transaction settlement.
10. Confirm your team can detect, assign, and escalate Requests for Information (RFIs) using Handle RFIs and Compliance Exceptions.

4. Understand post-launch obligations

After go-live, your production activity remains subject to ongoing controls:

• Transaction monitoring: Inbound and outbound transactions may be screened in real time. Transactions can be paused for compliance review if screening or monitoring rules require investigation.
• KYC refresh: Customer information may need to be refreshed periodically based on risk rating. Typical review cycles are every 3 years for low-risk customers, every 2 years for medium-risk customers, and annually for high-risk customers.
• Material change notification: Notify Verto if your group structure, client base, product activity, or country exposure changes materially after approval.
• RFI response SLAs: Respond to RFIs within the agreed timelines. Delayed or repeated non-response can suspend affected transactions and may trigger account review.

🛑 Common Blockers

Address these early to ensure your Go-Live hits the scheduled launch date:

🎯 Next Steps