Discussions

Hey everyone,

Hope you're all doing well!

We've been integrating with Wyre's APIs and are starting to scale up our webhook usage for transaction status updates and other events. While the webhooks generally work great, we're trying to solidify our best practices around their reliability and how to handle potential edge cases. golf hit

Specifically, I'm wondering:

How does Wyre ensure webhook delivery reliability? Is there a retry mechanism in place if our endpoint is temporarily unavailable, and if so, what's the retry schedule/duration?
What are the recommendations for handling duplicate webhook events on our end? We're designing our system to be idempotent, but it would be helpful to know if duplicate deliveries are a common occurrence to design for.
Are there any specific headers or unique identifiers in the webhook payload that can help in detecting and de-duplicating events more effectively?
For critical events, do you recommend relying solely on webhooks, or should we also implement a polling mechanism as a fallback for reconciliation? If so, what's a reasonable polling frequency?
Any insights or guidance from the Wy Wyre team or other developers using the webhooks extensively would be hugely appreciated! We want to make sure our integration is as robust as possible.

Thanks in advance for your help!