We are looking to start using Automatic Retry but as I understand it, once we enable this feature we can not revert (i.e. disable it).
Therefore, we were hoping to test our application with Automatic Retry on our development server with our sandbox account.
Specifically, we want to test a failed subscription transaction changing the status to suspended. Since the first transaction of a subscription is handled differently (it changes the account to suspended, even without Automatic Retry being enabled), we would like the subscription to fail on the second transaction.
Looking at the available values to trigger behavior in the Testing Guide, I see we could use a zip code of 46282 to trigger a declined transaction. We could update the zip code after the first transaction to 46282 to cause the declined transaction but currently (without Automatic Retry) the first transaction after an edit is treated as a first transaction, so again this wouldn't really be testing Automatic Retry.
Is there a way to test Automatic Retry in a sandbox account?