The add_payment_info event
add_payment_info is a GA4 recommended e-commerce event that fires when a visitor submits payment information during checkout. It carries the order items, currency, value, and a payment_type label (such as the card brand or wallet). It is a late-funnel step, just before purchase, and one where privacy discipline matters most: it must record that payment was entered, never the payment details themselves.
What this means
add_payment_info is a GA4 recommended retail event fired when a visitor adds payment information in checkout. It includes the `items`, `currency`, `value`, and a `payment_type` such as 'Credit Card' or a wallet name. GA4 treats it as a defined late-funnel step between begin_checkout and purchase.
It marks one of the deepest commitments before purchase — the visitor has supplied the means to pay.
Late-funnel drop-off and privacy
Drop-off after add_payment_info is a red flag: people rarely enter payment details and then abandon unless something breaks — a declined card, a validation error, or a surprise total. Investigate this step closely. Equally important: the only payment data this event should carry is a generic method category. Card numbers, expiry, CVV, and billing identifiers must never enter analytics.
- Fires when payment info is submitted in checkout
- Carries items, value, and a generic payment_type
- Drop-off here usually signals payment errors
How it appears in analytics and logs
An add_payment_info event means a visitor supplied payment details. Drop-off after this step is unusual and may signal payment errors, declined cards, or last-second cost surprises.
Diagnostic use case
Measure how many shoppers reach the payment step, isolating drop-off between adding payment info and completing the purchase.
What WebmasterID can help detect
WebmasterID can record a payment-step event first-party using only a generic method label, so the late funnel is measurable without ingesting payment data.
Common mistakes
- Putting real payment details into the event.
- Using a payment_type that identifies the customer.
- Ignoring drop-off after this high-commitment step.
Privacy and accuracy notes
Never put card numbers, CVVs, or account details in this event. The payment_type label is a generic method category, not a payment instrument. This is educational, not legal advice.
Related pages
- The begin_checkout event
begin_checkout is a GA4 recommended e-commerce event that fires when a visitor starts checkout. It carries the items in the order plus currency, value, and an optional coupon. It marks the transition from cart to purchase flow and is the entry point for measuring checkout abandonment — the gap between starting checkout and completing a purchase.
- The add_shipping_info event
add_shipping_info is a GA4 recommended e-commerce event that fires when a visitor provides shipping information during checkout. It carries the order items, currency, value, and a shipping_tier label such as 'Ground' or 'Express'. It is a mid-to-late checkout step, often where unexpected shipping costs cause abandonment, and like all checkout events it must avoid recording the address itself.
- The purchase event and e-commerce
The purchase event records a completed transaction and anchors all e-commerce reporting: revenue, items, and conversion value. It carries a transaction id, a value and currency, and an items array describing what was bought. The discipline is to record the order, not the customer — product and revenue data belong in the event, personal identity does not.
- Privacy-first analytics
Measure checkout without sensitive data.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.