We would like to request access to a public API endpoint and/or Zapier trigger that exposes failed payment events, including error details and failure reasons.
Use case / problem: Currently, failed payments and payment errors are only visible manually inside the platform. For teams operating at scale, this creates delays in response time and increases the risk of missed follow-ups, unresolved bookings, and revenue leakage. We need programmatic access to this data to automate alerts, remediation workflows, and reporting.
Requested data fields (at minimum):
-Booking / transaction ID
-Payment status (failed, declined, error, retrying)
-Failure timestamp
-Failure reason / error code
-Error message (gateway or processor-level)
-Payment method (card, VCC, etc.)
-Amount and currency
-Guest or payer identifier (if available)
Preferred implementation options (either is acceptable):
-API endpoint that returns real-time or near-real-time failed payment events
-Zapier trigger (e.g., “Payment Failed” or “Payment Error Occurred”) that fires instantly when a failure happens
Business impact:
-Enables immediate outreach to guests to resolve payment issues
-Reduces booking cancellations and revenue loss
-Allows accurate internal reporting and reconciliation
-Supports scalable operations without manual monitoring
We are a long-term customer actively scaling our operations, and having this capability would significantly improve reliability, automation, and financial controls. This feature would also be valuable to other high-volume users managing payments across multiple properties.
Thank you for considering this request.
Please authenticate to join the conversation.
Completed
💡 Feature Requests
3 months ago

Hazel Laxamana
Get notified by email when there are changes.
Completed
💡 Feature Requests
3 months ago

Hazel Laxamana
Get notified by email when there are changes.