Outgoing Update Mandate From Customer
Server sends a callback to the customer (PAYER/PAYEE) to the url configured when the final status of mandate updation is received from NPCI. It is sent to the same entity whoever has initiated the mandate request.
Event ID
Example:- evt_V2_03c6ec0681124450b55cf92fa35df241
Server sends a callback to the customer (PAYER/PAYEE) to the url configured when the mandate is updated.
Example:- MERCHANT_CUSTOMER_OUTGOING_MANDATE_UPDATED
timestamp when webhook was created
Example:- 2021-12-07T13:46:40Z
Details of the event
Example:- YES_BIZ
Example:- customer1@abc
Example:- ABC
Example:- customer@xyz
Example:- Customer Name
Example:- 4121
Example:- DEMOUAT01
Example:- BANK
Example:- https://www.abcxyz.com/
Example:- uniqueMandateNumber@bank
Example:- 00
Example:- 806115044725
Example:- SUCCESS
Example:- This is remarks
Example:- UPI
Example:- UPI
Example:- Mandate is successfully updated
Example:- DEMO-CUST-1234
Example:- 2020/06/04
Example:- 2020/06/05
Example:- UPI_MANDATE
Example:- true
Example:- PAYER
Example:- 5
Example:- ON
Example:- MONTHLY
Example:- true
Example:- BJJMsleiuryufhuhsoisdjfadb48003sdaa0
Example:- 2020-06-01T10:10:42Z
Example:- merchant mandate
Example:- PAYER
Example:- BJJ71f7d43bdf64d72d9saddfded
Example:- true
Example:- 2016-11-24T19:00:00Z
Example:- 100.00
Merchant can get multiple callbacks for the same event type till the transaction status reaches a terminal state. Terminal states for a transaction are SUCCESS, FAILURE, EXPIRED, DECLINED.
|
Optional Fields
|
Constrains
|
|---|---|
recurrenceRule
| It is not present if recurrencePattern is ONETIME, DAILY or ASPRESENTED.
|
recurrencValue
| It is not present if recurrencePattern is ONETIME, DAILY or ASPRESENTED.
|
expiry
| It will be present only when the payee has initiated the mandate.
|
payeeName
| It will be present if role is PAYER
|
payerName
| It will be present if role is PAYEE
|