Supported events and event parameters

Checkout sends GA4 events to track the payment lifecycle and user interactions with the Checkout page. The Events are grouped into categories using the event_category parameter.

Events overview

Event category: `checkout_global`

Checkout lifecycle

The following events track the main Checkout flow. They are retained for backward compatibility.

Event	Description
`checkout_view`	Triggered when the Checkout page is displayed to the user.
`checkout_method_selected`	Triggered when the user selects a Payment method at Checkout.
`checkout_form_valid`	Triggered when the Checkout form becomes valid and is ready for submission.
`checkout_submit`	Triggered when the user clicks the Pay or Continue button to submit the Checkout form.
`checkout_pending`	Triggered when payment processing starts and Checkout enters a pending or loading state.
`purchase`	Triggered when the payment is successfully completed.
`checkout_failed`	Triggered when the Checkout process fails and the payment is not completed.
`checkout_error`	Triggered when an unexpected or unknown error occurs during the Checkout process.
`checkout_view_expired`	Triggered when the user opens a Checkout page with an expired payment session.
`checkout_abandoned`	Triggered when the user leaves Checkout before completing the payment.

Event category: `checkout_form`

Form interaction

These Events track the validation state of individual Checkout form fields. An Event is sent when a field changes its validation state. Repeated Events for an unchanged state are not sent.

Event	Description
`valid_card / invalid_card`	The card number becomes valid or invalid.
`valid_expiry_date / invalid_expiry_date`	The expiry date becomes valid or invalid.
`valid_expiry_month / invalid_expiry_month`	The expiry month becomes valid or invalid, when applicable.
`valid_expiry_year / invalid_expiry_year`	The expiry year becomes valid or invalid, when applicable.
`valid_cvv / invalid_cvv`	The CVV becomes valid or invalid.
`valid_cardholder / invalid_cardholder`	The cardholder name becomes valid or invalid.
`valid_email / invalid_email`	The email address becomes valid or invalid.
`valid_country / invalid_country`	The country value becomes valid or invalid.
`valid_region / invalid_region`	The region value becomes valid or invalid.
`valid_city / invalid_city`	The city value becomes valid or invalid.
`valid_street / invalid_street`	The street value becomes valid or invalid.
`valid_full_address / invalid_full_address`	The full address becomes valid or invalid.
`valid_post_code / invalid_post_code`	The postal code becomes valid or invalid.
`valid_pin / invalid_pin`	The PIN becomes valid or invalid, when applicable.

Form state events

Event	Description
`checkout_form_valid`	Entire Checkout form becomes valid and ready to submit.
`checkout_submit`	User submitted the form.

Event category: `checkout_saved_card`

Saved card interactions

These Events track how users interact with saved cards.

Event	Description
`select_saved_card`	Triggered when the user selects a saved card.
`select_another_card`	Triggered when the user chooses another card or starts entering new card details.
`remember_me`	Triggered when the user selects or clears the Remember me checkbox.
`forget_card`	Triggered when the user removes a saved card.

Event category: `applepay`

Apple Pay

These Events track the Apple Pay payment flow.

Event	Description
`Begin`	Triggered when the user clicks the Apple Pay button and the payment flow starts.
`Submit`	Triggered when the user confirms the Apple Pay payment sheet.
`Cancel`	Triggered when the user cancels the Apple Pay payment sheet.
`Result`	Triggered when the Apple Pay flow finishes. The label parameter indicates success or fail.

Event category: `googlepay`

Google Pay

These Events track the Google Pay payment flow.

Event	Description
`Begin`	Triggered when the user clicks the Google Pay button and the payment flow starts.
`Submit`	Triggered when the user confirms the Google Pay payment sheet.
`Cancel`	Triggered when the user cancels the Google Pay payment sheet.
`Result`	Triggered when the Google Pay flow finishes. The label parameter indicates success or fail.

Event category: `checkout_authentication`

Authentication and return flow

These Events track 3DS authentication, OTP interactions, and the return-to-merchant flow.

Event	Description
`redirect_to_acs`	Triggered when the user is redirected to the Access Control Server (ACS) for 3DS authentication.
`otp_rendered`	Triggered when the OTP form is displayed to the user.
`otp_submitted`	Triggered when the user submits the OTP form.
`return_to_merchant`	Triggered when the user manually returns to the merchant.

Event parameters

Parameters for all Events

The following parameters are sent with Checkout events where available:

checkout_id
merchant_account_id
payment_request_id
currency
amount
reference_id
origin_reference_id
event_category

Parameters for Result events

The following parameters are sent with purchase, checkout_failed, checkout_error, and checkout_view_expired events:

payment_commit_id
payment_commit_status
payment_commit_resolution

Additional parameters

The following parameters provide additional context for specific Events, where available:

Parameter	Applies to	Description
`payment_method`	checkout_method_selected, Apple Pay, Google Pay	The selected Payment method.
`field_name`	Field validation events	The name of the field whose validation state changed.
`error_code`	checkout_error and invalid field events	The error code, if available.
`error_message`	checkout_error	A user-facing or normalised error message.
`label`	Apple Pay and Google Pay Result events	The result of the payment flow: success or fail.