How to Identify Zuddl Transactions on Stripe

Last updated: April 6, 2026

What This Does

When attendees make payments through Zuddl registration flows, Zuddl sends identifying metadata to Stripe with every transaction. This article explains the metadata fields attached to each Stripe PaymentIntent and Refund so you can locate and reconcile Zuddl transactions in your Stripe Dashboard.

Note: This applies only to events using Stripe as the payment gateway. If your event uses PayPal or CyberSource, the identification fields differ.

Metadata on Payments (PaymentIntents)

Every PaymentIntent created by Zuddl includes the following metadata fields:

Metadata Key	Description	Example
`source`	Always set to Zuddl. Use this to filter all Zuddl-originated payments.	`Zuddl`
`eventId`	The unique identifier (UUID) of the Zuddl event.	`a1b2c3d4-e5f6-...`
`eventName`	The name/title of the Zuddl event (up to 400 characters).	`Annual Tech Summit 2026`
`checkoutId`	The unique identifier of the Zuddl checkout session for this payment.	`f7g8h9i0-j1k2-...`
`flowContextId`	The identifier of the registration flow context that initiated this payment.	`m3n4o5p6-q7r8-...`
`modifyOrderId`	Present when the payment is for a modified order (e.g., ticket upgrade or add-on change). Empty for initial registrations.	`s9t0u1v2-w3x4-...`

Description Field

The Description field on each PaymentIntent is set to the event title (up to 900 characters). This makes Zuddl transactions easily identifiable when browsing your Stripe payments list, as the event name appears directly in the payment description column.

Metadata on Refunds

When a refund is issued through Zuddl, the following metadata is attached to the Stripe Refund object:

Metadata Key	Description
`source`	Always set to Zuddl.
`zuddlTransactionHistoryId`	The unique identifier of the transaction record in Zuddl. Use this to match a Stripe refund back to a specific Zuddl transaction.

Notes

The modifyOrderId field is only populated when a payment results from an order modification (such as a ticket upgrade). For initial registrations, this field is empty.
The eventName in metadata is trimmed to 400 characters, while the Description field supports up to 900 characters. For events with very long names, the metadata may be truncated.
Stripe metadata filters in the Dashboard are case-sensitive. Use Zuddl (capitalized) when filtering by the source field.
If you process refunds directly in Stripe (outside of Zuddl), those refunds will not carry Zuddl metadata.