The dunning in Appstle is very basic. So many apps have better dunning features. One thing that would be really helpful would be silent retries that don't count against your dunning settings for soft failures.

Here's just one example: I had a customer's payment method fail with the reason "There was a problem with Shop Pay". Something like this should not trigger a notification to the customer and should be retried maybe 2-3 times in the same day a few hours apart. This error resolved itself with no action by the customer. All it did was create confusion for them.

Like what are we expecting the CUSTOMER to do if there's a problem with SHOP PAY? There's no reason to involve them.

I have my dunning set up as 4 tries 1 day apart. But even with these settings it should allow for 2-3 silent retries per day for soft failures.

Other soft failures might include issuer/network issues, insufficient funds, activity limit exceeded, etc. None of these should involve the customer and none of them should count toward my dunning limit. Only hard failures should count toward the limit.