[jalalmanafi]

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?

[kay_o]

it was code base. first chunk would be git revision-sha . failure, retry, delay, multiple replay due to retry timeout (idempotence test)

[jalalmanafi]

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 you time? Or was code-based actually preferred?