jalalmanafi

3 ms·

1. 1.▲
   by jalalmanafi 8mo ago

   Makes sense — idempotence testing is a great use case. We've hit bugs where retries created duplicate charges. If this existed as a hosted tool with a UI to configure scenarios (instead of encoding in txids), would that have saved y
2. 2.▲
   by jalalmanafi 8mo ago

   Clever approach — encoding the behavior in the txid itself. Did you have a UI to configure scenarios, or was it all code-based? And did you simulate webhook failures/retries too, or just delays?
3. 3.▲
   Ask HN: How do you test payment webhook edge cases?

   1 points by jalalmanafi 8mo ago|5 comments