Description:
Currently, the payment.succeeded webhook payload does not include a reference to the associated checkout_configuration object or its metadata.
While the documentation does not specify that this data should be included, having access to either the ch_ reference or the checkout_configuration.metadata would be highly beneficial for developers integrating Whop payments with external systems.
Impact:
Without a way to retrieve checkout_configuration metadata directly from the webhook, it’s difficult to correlate payment events with contextual data defined at checkout (e.g., internal order IDs, user identifiers, or campaign tracking data). This forces developers to maintain additional mapping logic in their own systems.
Expected Behavior:
The payment.succeeded webhook could optionally include:
• A checkout_configuration_id (ch_) reference, or
• The checkout_configuration.metadata field inline.
Description:
Currently, the payment.succeeded webhook payload does not include a reference to the associated checkout_configuration object or its metadata.
While the documentation does not specify that this data should be included, having access to either the ch_ reference or the checkout_configuration.metadata would be highly beneficial for developers integrating Whop payments with external systems.
Impact:
Without a way to retrieve checkout_configuration metadata directly from the webhook, it’s difficult to correlate payment events with contextual data defined at checkout (e.g., internal order IDs, user identifiers, or campaign tracking data). This forces developers to maintain additional mapping logic in their own systems.
Expected Behavior:
The payment.succeeded webhook could optionally include:
• A checkout_configuration_id (ch_) reference, or
• The checkout_configuration.metadata field inline.