Skip to main content

API & Zapier Trigger for Failed Payments and Payment Error Events

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.

Status: Completed5 comments

Log in to comment and vote

Comments5

  • Ankur Jain

    Team•

    Feb 6

    Hi Hazel,

    Thank You for your patience. We have deployed the Payment Failed trigger with latest Zapier version. Please update to the latest Zapier v1.1.2 and start using the Payment Failed trigger. Do let us know incase you face any issues.

    • Hazel Laxamana

      •

      Feb 6

      Thank you so much!

  • Ankur Jain

    Team•

    Jan 5

    Hi Hazel,

    New Year greetings!

    Thank you for reaching out and sharing your detailed requirement. We’ve reviewed your request, and we do have an API endpoint that can support this use case.

    You can use our List Charges API (https://nomod.com/docs/api-reference/fetch-charges) to fetch failed payment attempts by filtering on the Link ID and status fields. This will also provide other required details.

    Please review the API documentation and let us know if this approach works for you, or if you need any additional details.

    Best regards,
    Team Nomod

    • Hazel Laxamana

      •

      Jan 9

      Hi Ankur, thanks for the info but this approach is not suitable for us. We need an instant notification to catch even with webhook for any failed payments and reason for the failed payment.

      • Ankur Jain

        Team•

        Jan 20

        Hi Hazel,

        Thank You for your patience. We’ve prioritised the development of a Zapier trigger for payment failed events and will keep you informed as soon as it goes live in production.

        Thank you.