Skip to main content
POST
Create Pre-Debit Notification
Before each UPI Autopay recurring debit, NPCI requires notifying the customer in advance. This endpoint sends that notice through the payment provider and returns an id you must reference on the debit. The flow has three steps:
  1. Notify: call this endpoint with the mandate’s vaulted_token, the upcoming amount, and the billing_date. Provider routing comes from origin_payment_id (the mandate-creation payment) or an explicit provider_data.
  2. Check the status: SENT means the provider delivered the notification and returned its reference in provider_data.provider_notification_id.
  3. Debit: create the recurring payment with payment_method.detail.bank_transfer.pre_debit_notification_id set to the returned id. Yuno resolves the provider reference and forwards it automatically — see Create payment.
This request requires an X-Idempotency-Key. Reusing a merchant_reference returns the existing notification for your account.

Authorizations

public-api-key
string
header
default:<Your public-api-key>
required
private-secret-key
string
header
default:<Your private-secret-key>
required

Headers

X-Idempotency-Key
string
required

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

application/json
account_id
string<uuid>
required

Your Yuno account ID.

merchant_reference
string
required

Your unique reference for this notification. Reusing a reference returns the existing notification (idempotent per account).

amount
object
required
billing_date
string<date>
required

Date of the upcoming debit (YYYY-MM-DD). Per NPCI, notify the customer at least 24 hours before the debit.

description
string

Text shown to the customer in the notification (for example, the subscription name and renewal notice).

billing_sequence_number
string

Sequence number of the debit within the mandate (for example, 2 for the second charge).

origin_payment_id
string<uuid>

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.

customer_payer
object
payment_method
object
provider_data
object

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.

id
string<uuid>

Unique identifier of the pre-debit notification. Reference it on the recurring debit as payment_method.detail.bank_transfer.pre_debit_notification_id.

account_id
string<uuid>

Your Yuno account ID.

status
enum<string>

SENT: the provider accepted and delivered the notification. REJECTED: the provider refused it. ERROR: the notification could not be relayed.

Available options:
SENT,
REJECTED,
ERROR
merchant_reference
string

Your unique reference for this notification (idempotent per account).

description
string

Text shown to the customer in the notification.

amount
object
billing_date
string<date>

Date of the upcoming debit (YYYY-MM-DD).

origin_payment_id
string<uuid>

The mandate-creation payment used to derive provider and connection, when provided.

provider_data
object
created_at
string<date-time>
updated_at
string<date-time>