Pre-Debit Notification API

status

Status defines acknowledgment from PayU. Possible values are :
· 1- This value indicates that pre-debit notification is triggered successfully for customer or deleted successfully in case of action delete.

· 0 – This value indicates pre-debit notification failed to get triggered and merchant should retry after some time to trigger the same or failed to get deleted in case of action delete.

action

Always returned as “MANDATE_PRE_DEBIT” to highlight the type of action.

message

Description of the pre-debit notification process

invoiceId
only for cards

This is an acknowledgment ID that a pre debit notification has been sent for processing.

invoiceStatus
only for cards

This is the status of the invoice whether it has been charged for recurring or not. Values can be:

• Paid
• Unpaid
• DeletedSince these statuses come from a third-party vendor, so these can vary if there is an addition of new status at the vendor end

approvedStatus
only for cards

This is for cases where the transaction is above 15000 as RBI guideline says approval is required through AFA (Additional Factor authentication). Values can be:

• Pending

• Approved
• Not_applicable
  Since these statuses come from third-party vendors, so these can vary if there is an addition of new status at the vendor end.

status

Status defines acknowledgment from PayU. Possible values are :
1- This value indicates that pre-debit notification is triggered successfully for customer or deleted successfully in case of action delete.
· 0 – This value indicates pre-debit notification failed to get triggered and merchant should retry after some time to trigger the same or failed to get deleted in case of action delete.

action

Always returned as “MANDATE_PRE_DEBIT” to highlight the type of action.

message

Description of the pre-debit notification process

invoiceId

This is an acknowledgment ID that a pre debit notification has been sent for processing.

invoiceStatus

This is the status of the invoice whether it has been charged for recurring or not. Values can be:

• Paid
• Unpaid
• Deleted
  Since these statuses come from a third-party vendor, so these can vary if there is an addition of new status at the vendor end

approvedStatus

This is for cases where the transaction is above 15000 as RBI guideline says approval is required through AFA (Additional Factor authentication) Values can be.:

• Pending

• Approved
• Not_applicable
  Since these statuses come from third-party vendors, so these can vary if there is an addition of new status at the vendor end.

authpayuid
mandatory

The value of mihpayid returned in the payment response of Registration transaction when transaction is successfully completed. As explained earlier in the document, you need to map this value against customer profile at his end so that correct authPayuid will be passed in the request.

requestId
mandatory

Unique request value generated at merchant’s end to distinguish independent request call.

debitDate
mandatory for cards and UPI

This parameter contains the date of debit when the recurring would be charged by merchant.
*In UPI:**

• For all frequencies (other than Daily and Adhoc), the merchant must send the notification 48 hours before the debit.
• For Daily and Adhoc frequency, the merchant must send the notification 24 hours before the debit. If the notification is sent after these durations, then the debit will fail.

invoiceDisplayNumber
mandatory only for cards

A unique display number by merchant for every subsequent invoice/recurring charge. This can be displayed on the merchant’s panel to the customer. This same value needs to be sent in the recurring api also.

amount
mandatory for cards and UPI

The transaction amount which will be deducted from the customer’s payment instrument.
For Cards:

• In case of Fixed billing plan, this amount should be same as
  billingAmount sent during Registration transaction.
• In case of Adhoc billing plan, this amount should be equal to or lesser than billingAmount sent during the Registration transaction.
  *Note: The amount mentioned in the Pre-Debit notification API for UPI should be same as the next execution amount. Else, the next recurring execution request will fail.

action
optional

Any of the following actions can be performed:
* Retrieve: Query the status of the pre-debit notification. Only authpayuid and invoice display numbers are mandatory for this action.
* Delete: Delete the already generated pre debit. Only authpayuid and invoice display numbers are mandatory for this action.