This is distributed transaction problem, and there are multiple ways to solve it with the simple one being callback (webhook) with timeout. Put debit in a pending state, wait for response from API call, if successful complete transaction else fail and log it.
On the Calbank app, a transaction can fail and when you try again you realize the failed one went through resulting in multiple transactions. I'm curious how they are not catching that. Backend guys, there should be a way to prevent this right? How do you handle such cases?
United States Trends
- 1. Lakers 71.2K posts
- 2. Luka 65.7K posts
- 3. Wemby 25.5K posts
- 4. Marcus Smart 5,653 posts
- 5. #Talus_Labs N/A
- 6. #LakeShow 5,479 posts
- 7. Blazers 8,043 posts
- 8. Russ 10.1K posts
- 9. Ayton 15.1K posts
- 10. Richard 44.6K posts
- 11. Horford 1,893 posts
- 12. #AmphoreusStamp 6,069 posts
- 13. #RipCity N/A
- 14. Podz 2,363 posts
- 15. #dispatch 61.5K posts
- 16. Champagnie 1,203 posts
- 17. Kuminga 3,310 posts
- 18. Thunder 33.7K posts
- 19. Godzilla 32.5K posts
- 20. Nico Harrison 1,681 posts
Loading...
Something went wrong.
Something went wrong.