---
title: "Comment by Paul Hartness on \"Implementing UPI AutoPay Subscriptions in India: Mandates, Webhooks and Retry Logic\" | Hashnode"
description: "Good point on learning the provider's retry schedule before writing your own. Cards on Stripe have the same trap: if you add retries on top of the built-in ones"
url: "https://hashnode.com/posts/implementing-upi-autopay-subscriptions-in-india-mandates-webhooks-and-retry-logic/6ad88202cbbe0c18bdb59dcf/comment/6ad89c49560553a1da4abe2b"
---

[Discussion](https://hashnode.com/posts/implementing-upi-autopay-subscriptions-in-india-mandates-webhooks-and-retry-logic/6ad88202cbbe0c18bdb59dcf)

Comment [Implementing UPI AutoPay Subscriptions in India: Mandates, Webhooks and Retry Logic](https://hashnode.com/posts/implementing-upi-autopay-subscriptions-in-india-mandates-webhooks-and-retry-logic/6ad88202cbbe0c18bdb59dcf)

[Paul Hartness](https://hashnode.com/@retryfix)

[Oct 21](https://hashnode.com/posts/implementing-upi-autopay-subscriptions-in-india-mandates-webhooks-and-retry-logic/6ad88202cbbe0c18bdb59dcf/comment/6ad89c49560553a1da4abe2b)

Good point on learning the provider's retry schedule before writing your own. Cards on Stripe have the same trap: if you add retries on top of the built-in ones, you can end up hitting the customer twice in a day. The "pending" message advice applies everywhere too. Telling the customer before the next attempt saves a lot of surprised support emails.
