Discussions

Hi everyone,

I’m currently integrating an older project that still relies on the legacy Sendwyre API, and I’ve hit a bit of a roadblock when it comes to handling webhook events—specifically failed transactions or transfer errors.

I’ve read through the legacy documentation, but I couldn’t find a clear breakdown of:

Which specific webhook events are triggered when a transfer fails, especially due to things like insufficient funds or KYC verification issues.

What the recommended retry logic is on the client side—should we always retry on certain error codes, or are some failures considered final?

Right now, I’m only reliably seeing transferProcessing and transferComplete, but I’m unsure how to cleanly detect issues without polling the API repeatedly (which I’m trying to avoid).

Has anyone successfully implemented robust webhook-based error handling with the legacy Sendwyre API? If so, I’d love to know:

Which events or status codes you listen for,

How you prevent duplicate retries,

And whether you’ve had to build in any manual overrides or admin tools to catch edge cases.

Appreciate any guidance, code snippets, or just your lessons learned!

Thanks in advance,
—Alex geometry dash lite