Flow Advisory | Autopay PDNs | Version 1.1.3

Advisory : Allowing Merchant to send the PDN for debit date upto T+3 Day and to keep multiple PDN active in the system.

Deployment Date : 19th November 2026

We are enhancing how Pre-Debit Notifications (PDNs) work for UPI AutoPay. These changes let the merchants notify users further in advance and keep more than one Pre-Debit Notification (PDN) active on a mandate, so scheduled debits, especially on Daily mandates, are not skipped because a new Pre-Debit Notification (PDN) had to wait for the previous debit to finish.

1. What is changing ?

   1. Pre-Debit Notification (PDN) debit date can now be up to T+3 Day.

      You can now send a PDN on T-Day with a debit_date of up to T+3 Day (earlier limit: T+2 Day)
      Eg : For a mandate with frequency as Daily or Aspresented, on 3rd November 2026, you can send the Pre-Debit Notification (PDN) for the debit_date of 4th November 2026 or 5th November 2026 or 6th November 2026 or for all the debit_dates mentioned above (all 3 days in advance and all at once).
      • A debit_date beyond T+3 will be rejected with error_invalid_debit_date.
      • The minimum 24-hour gap between PDN and debit (NPCI rule) and the 23:50–00:00 cutoff for T+1 PDNs remain unchanged.
      • The debit_date must fall within the mandate's start and end dates.

   2. Multiple active Pre-Debit Notifications (PDNs) per mandate.

      Today, sending a new PDN cancels any earlier PDN on the same mandate that has not yet been presented. After this change, the behaviour depends on the mandate frequency:

      
      

      Frequency	Active PDNs allowed	Does a new PDN cancel earlier ones?
      As Presented	Up to 7 per debit date, i.e. up to 21 across T+1, T+2 and T+3	No. Earlier PDNs stay active.
      Daily	1 per debit date, i.e. up to 3 across T+1, T+2 and T+3	No. A second PDN for the same debit date is rejected.
      Weekly, Fortnightly, Monthly and others	1 at a time (one debit per frequency cycle)	No change to current behaviour

      1. For Aspresented mandates, active PDNs can be presented in any order for a same debit date, a later PDN can be presented before an earlier one for the same debit date.
      2. For Daily Frequency mandate: On 10th Nov'26 you can send PDNs for 11th Nov, 12th Nov and 13th Nov. Each can be presented once on its own debit date.
      3. Note:
         1. PDN should be presented on their respective debit dates. No carry forward.
         2. If PDN is not presented on the debit date, then it'll be marked as Expired.

   3. Addition of new field : debit_date_end_timein the callbacks and the Get Transaction Status (GTS) response

      Pre-Debit Notification (PDN) callbacks and the Get Transaction Status (GTS) response will include a new field:

      "debit_date_end_time": "2026-11-13 23:59:59"
      

      1. For all frequencies, a Pre-Debit Notification (PDN) that has not been presented by 23:59:59 IST on its debit date will move to Expired and can no longer be presented. Each PDN expires independently which means, if the T+1 PDN expires, the T+2 and T+3 PDNs are unaffected.

   4. Presentation rules :

      The Presentation API will accept any active notification_sequence_id on the mandate. A presentation will be accepted only if:

      1. The Pre-Debit Notification (PDN) is in success status and has not already been presented.
      2. The presentation is made within the Pre-Debit Notification's (PDN's) window (from debit_date to debit_date_end_time).
      3. The presentation amount exactly matches the Pre-Debit Notification (PDN) amount.
      4. Re-presentations after an eligible failure are still allowed while remaining_presentation_attempts is above zero, but they must also complete before the PDN's debit_date_end_time.
      5. If a presentation failed for example, at 11:30 PM and if it had a representable error code, the next re-presentation attempt would fall after 23:59:59, the presentation will be marked Failed and the Pre-Debit Notification (PDN) completed.

   5. Pause and revoke :

      1. If a mandate is paused or revoked, all of its active Pre-Debit Notifications (PDNs) will be moved to cancelled.

2. New error responses

   
   

   Scenario	response_key
   debit_date is more than T+3 Day	error_invalid_debit_date
   As Presented: an 8th active PDN for the same debit date	error_active_pdn_limit_exceeded
   Daily and other frequencies (except aspresented frequency) : a second active PDN for the same debit date	error_active_pdn_exists_for_debit_date

3. Action required from you

   1. Handle the new response_key listed above in your PDN integration.
   2. Accept the new debit_date_end_time field in callbacks and GTS responses. If your parser rejects unknown fields, update it before go-live.
   3. For As Presented and Daily mandates, a new PDN will no longer cancel the previous one. If you currently re-send a PDN to correct an amount or date, the earlier PDN will remain active, make sure you present only the Pre-Debit Notification (PDN) you intend to debit.
   4. Always use the notification_sequence_id returned in the PDN callback when calling the Presentation API. For Daily mandates, sequence numbers are derived from the debit date and may not be consecutive; do not compute them on your side.
   5. Schedule presentations early in the debit day so that any re-presentations can complete before 23:59:59 IST.
   6. Daily mandates: to avoid missed debits, send Pre-Debit Notifications (PDNs) for upcoming dates (T+2 or T+3 day) in advance rather than waiting for the previous debit to complete.

4. What is not changing

   1. Multiple debits on the same day are possible only for As Presented mandates. All other frequencies still allow one debit per debit date / cycle.
   2. The 24-hour minimum notice and the T+1 cutoff window.
   3. Pre-Debit Notification (PDN) statuses (Pending, Success, Failed, Completed, Cancelled, Expired) remain the same. No new status is introduced.

For any further queries you may reach out to us.