Checking access…

Skip to main content
Version: v2

πŸš€ Convenient Checkout v2 API

Date: June 30, 2026
Audience: Merchants & Developers
Status: V2 available in production; rollout remains operation-specific.

Merchant-safe availability statement

Last validated: 2026-08-26
Accountable owners: CCG Product and API owners

V2 is available in production. Availability is operation-specific. Before migration, confirm that every operation in scope is production-ready and enabled for the merchant. Deferred or stubbed operations must not be used.


Summary

Convenient Checkout v2 is available in production, and its documentation and migration guidance are published. Availability still depends on operation readiness and merchant enablement. Start with the v1-to-v2 migration guide, then use comparison and reference docs for implementation details.


What's in v2?​

The v2 API brings meaningful improvements to the checkout integration experience:

AreaWhat Changed
Checkout SessionsRetrieve, update, cancel, and child-session creation are available when enabled for the merchant
Payment MethodsExpanded support β€” cards, bank accounts, and more
WebhooksRicher event payloads with full resource snapshots
Error ResponsesStructured error codes with machine-readable categories
API VersioningExplicit versioning via URL path (/v2/) for predictable compatibility

Migration Entry Point​

Use one canonical page for migration execution:

Then use these references for contract and behavior validation:

This announcement is intentionally concise to avoid duplicating migration instructions that are maintained in the migration guide.


API References​

VersionReferenceStatus
v2API Reference v2βœ… Current
v1API Reference v1⚠️ Legacy

πŸ“š Resources​

ResourceLink
V1 to V2 MigrationV1 to V2 Migration Guide
Customer and Payment Method Data MigrationMigrate to CCG
V1 and V2 API ComparisonV1 vs V2 API Comparison
V2 ChangelogV2 Changelog
API Reference v2/api-reference-v2/
API Diff (v1 vs v2)/api-diff/
Webhooks v2/webhooks-v2/
Getting StartedGetting Started

🏁 Bottom Line​

Use v2 only where the current merchant-safe availability statement says it is ready for your environment and endpoint set. If you are on v1, follow the V1 to V2 Migration Guide as the canonical implementation path.


Questions about migration? Contact your Convenient Checkout integration representative.