Skip to main content

Cart, checkout, and order lifecycle

Generated from COPE public event contracts. Do not edit this page by hand.
Cart, checkout, and order events describe the buyer journey before and after payment. Schema-backed events appear in the generated event schema reference.

Cart States

StateMeaningEventSchema-backed page
createdA cart was opened for a buyer or checkout flow.Managed by the Checkout SDK.Not published
activeThe cart can still change through line item, buyer identity, or currency updates.Managed by the Checkout SDK.Not published
abandonedThe cart did not convert in the configured window.Contact COPE support for current integration guidance.Not published
checkout_createdThe cart moved into a checkout attempt.Managed by the Checkout SDK.Not published

Checkout States

StateMeaningEventSchema-backed page
createdA checkout session was created and payment collection can begin.Managed by the Checkout SDK.Not published
cancelledThe checkout attempt was explicitly cancelled before completion.Managed by the Checkout SDK.Not published
expiredThe checkout attempt expired before completion.Managed by the Checkout SDK.Not published
completedCheckout produced a completed order.cart.order.completedSchema

Order States

StateMeaningEventSchema-backed page
createdThe order record exists but has not reached a terminal payment outcome.Internal transition before terminal webhook delivery.Not published
completedThe order completed and can be fulfilled, granted, or reconciled by consumers.cart.order.completedSchema
failedThe order could not complete successfully.Contact COPE support for current integration guidance.Not published
refundedFunds were returned after order completion.payment.refund.createdSchema
refund_reversedA prior refund was reversed.payment.refund.reversedSchema
chargebackedThe payment was disputed as a chargeback.payment.chargeback.createdSchema
chargeback_reversedThe chargeback was reversed.payment.chargeback.reversedSchema

Consumption Notes

  • Treat cart.order.completed as the primary fulfillment signal.
  • Use payment events when your integration needs payment-state reconciliation rather than order fulfillment.