Create Pre-Debit Notification
Send the NPCI-required pre-debit notification to the customer before a UPI Autopay recurring debit.
id you must reference on the debit.
The flow has three steps:
- Notify: call this endpoint with the mandate’s
vaulted_token, the upcomingamount, and thebilling_date. Provider routing comes fromorigin_payment_id(the mandate-creation payment) or an explicitprovider_data. - Check the status:
SENTmeans the provider delivered the notification and returned its reference inprovider_data.provider_notification_id. - Debit: create the recurring payment with
payment_method.detail.bank_transfer.pre_debit_notification_idset to the returnedid. Yuno resolves the provider reference and forwards it automatically — see Create payment.
X-Idempotency-Key. Reusing a merchant_reference returns the existing notification for your account.Authorizations
Headers
Unique identifier used in HTTP headers to ensure that a request is processed only once, even if it is retried due to network issues or timeouts.
Body
Your Yuno account ID.
Your unique reference for this notification. Reusing a reference returns the existing notification (idempotent per account).
Date of the upcoming debit (YYYY-MM-DD). Per NPCI, notify the customer at least 24 hours before the debit.
Text shown to the customer in the notification (for example, the subscription name and renewal notice).
Sequence number of the debit within the mandate (for example, 2 for the second charge).
ID of the mandate-creation payment. When provided, Yuno derives the provider and connection from its successful charge. Either origin_payment_id or provider_data is required.
Explicit provider routing. Either origin_payment_id or provider_data (id + connection_id) is required.
Response
Notification created. Check status: SENT means the provider delivered it.
Unique identifier of the pre-debit notification. Reference it on the recurring debit as payment_method.detail.bank_transfer.pre_debit_notification_id.
Your Yuno account ID.
SENT: the provider accepted and delivered the notification. REJECTED: the provider refused it. ERROR: the notification could not be relayed.
SENT, REJECTED, ERROR Your unique reference for this notification (idempotent per account).
Text shown to the customer in the notification.
Date of the upcoming debit (YYYY-MM-DD).
The mandate-creation payment used to derive provider and connection, when provided.