---
title: add_payment_info event on Guesty Pay checkouts
description: "If your site uses a Guesty Pay checkout, you may notice that the **add_payment_info** analytics event does not fire. **Why this happens.** In HomeRunner…"
url: "https://homerunner.io/docs/why-does-the-add-payment-info-analytics-event-not-fire-on-a-guesty-pay-checkout/"
updated: "2026-10-26"
category: Booking engine and checkout
---

# add_payment_info event on Guesty Pay checkouts

If your site uses a Guesty Pay checkout, you may notice that the **add_payment_info** analytics event does not fire.

**Why this happens.** In HomeRunner Toolkit versions before 3.322.7, the **Conversion Tracking** module only detects payment details on Stripe checkouts, so the event cannot fire on a Guesty Pay checkout.

**What to do.** Update the HomeRunner Toolkit plugin to version 3.322.7 or later in **Dashboard > Updates**.

**How the event behaves after the update.** On a Guesty Pay checkout, the event fires once, at the moment your guest submits the form and Guesty accepts the card. This is just before the **purchase** event and before any 3-D Secure redirect. The event carries **payment_type: credit_card**, the same as on Stripe sites. When a pixel ID is configured, the Meta Pixel **AddPaymentInfo** event fires alongside it.

Stripe checkouts are unchanged: the event still fires when your guest completes the last card field.

**To verify.** Run a GTM preview through a test checkout and confirm that **add_payment_info** appears ahead of **purchase**.

Still stuck? [Contact the HomeRunner team](https://homerunner.io/contact/) with your site address and what you tried, and we take it from there.