GuidesAPI ReferenceChangelogSygna Bridge API StatusSygna Hub GitHubHome
Discussions

Discussions

Ask a Question
Back to all

Best practice for handling TRANSACTION_PENDING with no subsequent TRANSACTION_COMPLETED message?

15 days ago by Rosa Alford

Hello all,

I'm working on integrating our VASP platform with the Sygna Bridge and have a question about a specific transaction state.

In a few of our test cases, we've had a transaction from an Originator VASP send a TRANSACTION_PENDING message, but our system never received a subsequent TRANSACTION_COMPLETED message from their side. The transaction seems to be 'stuck' in this pending state indefinitely.

What is the recommended best practice for handling this scenario? Is there a specific timeout period we should be implementing after which we should assume the transaction has failed? Should we be attempting to re-query the transaction status, and if so, what is the correct API endpoint for this? Any guidance on how to programmatically handle this edge case would be extremely helpful.

Thanks for your help.

ragdoll hit