Checking access…

Skip to main content
Version: v2

Direct-to-V2 Go-Live Checklist

Use this checklist to confirm production readiness for a net-new Convenient Checkout V2 integration. It extends the general UI Integration Checklist with the backend, payment, and split-tender gates that checklist doesn't cover.

UI Readiness (widget integration only)​

If you chose the widget integration path, complete all items in the UI Integration Checklist. Direct API integration merchants can skip to Environment & Merchant Enablement.

One V2-specific gate for widget integration:

  • Backend session creation confirmed to use V2 POST /sessions (merchant scope) β€” the v1 sessions path referenced in the Embedded Experience guide's setup examples must not be used

Environment & Merchant Enablement​

Before testing in any environment, confirm:

  • Every V2 operation in scope is available and enabled for your merchant β€” see V2 Environment Availability
  • Stage readiness confirmed per operation (do not infer it from production availability)
  • Production merchant enablement confirmed with your CCG onboarding contact

Backend & Payment Readiness​

  • Sessions, Payments, and Refunds API integration tested end-to-end in staging (merchant scope)
  • Webhook endpoint configured, validates idempotent processing for retry scenarios, and returns 2XX promptly β€” see Webhook Configuration
  • Reporting configured β€” see Reporting

Checkout Sessions Readiness​

Checkout Sessions (/v2/checkout-sessions/*) use user scope and are customer-facing β€” typically driven by the widget, not your merchant backend directly.

  • Checkout Session flows validated end-to-end in staging (widget integration) or your equivalent customer-facing flow tested (direct API integration)
  • Checkout Session cancellation and error paths tested

Split Tender (if enabled)​

  • Split tender flows tested against sandbox test cards β€” see the Split Tender Payments API guide for request/response handling
  • Rollback/partial-failure behavior validated in staging (split tender is all-or-nothing: both cards succeed or neither is charged)

Sandbox Validation​

Use the existing test data rather than inventing your own:

Troubleshooting & Support​

If you encounter issues before or after go-live:

  • Troubleshooting Guide β€” common integration problems and resolutions; start here before escalating
  • Split Tender 3DS Troubleshooting β€” specific to split tender + 3D Secure failures
  • For issues that cannot be resolved via the documentation, contact your CCG onboarding contact to initiate support handoff to the Convenient Checkout operations team.

Sign-Off​

  • Go-live readiness reviewed and approved by: confirm the accountable sign-off role with your CCG onboarding contact before going live