Direct-to-V2 Onboarding
This guide is for merchants adopting Convenient Checkout V2 for the first time — you do not have an existing V1 integration.
Already have a V1 integration?
If you already process payments through Convenient Checkout V1, use the V1 to V2 Migration Guide instead. That guide covers compatibility, coexistence, and cutover — none of which apply if you're starting fresh.
Complete the steps below to go from a net-new merchant to a production-ready Convenient Checkout V2 integration.
Before You Begin
Prerequisite
Complete Merchant Onboarding first — you'll need a merchantId from CCG before any of the steps below.
Your Path
| Step | Page | Purpose |
|---|---|---|
| 1 | Merchant Onboarding | Register your merchant and complete required configuration |
| 2 | Integration Steps | Integrate the V2 API and/or widget |
| 3 | Go-Live Checklist | Validate readiness before processing live payments |
What's Different for a Net-New Merchant
Because you have no existing V1 data, two settings that matter for a migrating merchant don't apply to you:
- Cross-version compatibility — this is a migration-only mechanism CCG uses to route requests for payments/refunds that originated in V1. It has no effect for you, since none of your transactions will have V1 origin.
- Split tender — an optional capability (default off), not a required setup step. Ask your CCG onboarding contact to enable it only if you intend to support customers splitting one payment across two cards. See Why Adopt V2 for the business case.
Related Documentation
- Merchant Onboarding
- Why Adopt V2
- V1 to V2 Migration Guide — if you have an existing V1 integration
- Getting Started with CCG