Proposal to Include Payment UID in BOOKING_PAYMENT_INITIATED Webhook Event

[fabriziospadaro]

Is your proposal related to a problem?

I’m always frustrated when I cannot access the payment UID from the BOOKING_PAYMENT_INITIATED webhook event. This makes it challenging to send a custom email to recover abandoned carts because constructing the recovery link requires the UID.

Describe the solution you'd like

I would like the BOOKING_PAYMENT_INITIATED webhook event to include the payment UID. This would allow me to construct a link such as https://cal.com/payment/uid and send custom emails to recover abandoned carts effectively.

Describe alternatives you've considered

I have attempted to work with the /payments API, but it returns zod errors. The same issues occur when trying to use /payments/[id]. These alternatives do not provide a reliable way to access the payment UID necessary for constructing the recovery link.

Additional context

Including the payment UID directly in the BOOKING_PAYMENT_INITIATED webhook event would streamline the process and reduce reliance on potentially faulty API calls.

Requirement/Document

Any documentation that supports adding additional data to webhook events or dealing with zod errors in API responses would be helpful.

---

House rules

• If this issue has a 🚨 needs approval label, don't start coding yet. Wait until a core member approves the feature request by removing this label, then you can start coding.
  • For clarity: Non-core member issues automatically get the 🚨 needs approval label.
  • Your feature ideas are invaluable to us! However, they undergo review to ensure alignment with the product's direction.