diff --git a/content/data/bav/reverse-penny-drop/api-integration.mdx b/content/data/bav/reverse-penny-drop/api-integration.mdx index c2dc9095..76d55bd7 100644 --- a/content/data/bav/reverse-penny-drop/api-integration.mdx +++ b/content/data/bav/reverse-penny-drop/api-integration.mdx @@ -339,8 +339,6 @@ This API lets you test the end to end flow without an actual payment. This will Below are the summary of the notifications which need to be processed on your server by exposing an endpoint for Setu to send an HTTP POST request. -These notifications/webhooks are sent by Setu when the end user makes a payment and when banking partners send bank account details of the end user. - Please send back HTTP 200 status code if the request sent was processed correctly to avoid receiving multiple notifications for the same payment @@ -349,7 +347,11 @@ These notifications/webhooks are sent by Setu when the end user makes a payment
-_Please note that `accountType` can be `BANK_ACCOUNT`, `PPI` or `UNKNOWN`_ +##### 1. RPD_VERIFICATION_UPDATE Webhook + +This webhook is sent when the end user makes a payments. + +_`accountType` can be `BANK_ACCOUNT`, `PPI` or `UNKNOWN`_ - `PPI`, if the payment happened from a PPI (Pre Paid Instrument) account and not a valid bank account - `BANK_ACCOUNT`, if the payment happened from a valid bank account and the IFSC is in the RBI database @@ -363,14 +365,12 @@ _Please note that `accountType` can be `BANK_ACCOUNT`, `PPI` or `UNKNOWN`_ `UNKNOWN`, please notify us at support@setu.co.
-
_`bankAccountType` is an optional data field, you may not receive the value always. (Please contact with Setu team to know more about this feature.)_ _The value can be `SAVINGS`, `CURRENT`, `NRO`, `NRE`_ -
-##### Examples of webhook payload: +###### Examples Example 1 @@ -465,6 +465,124 @@ _The value can be `SAVINGS`, `CURRENT`, `NRO`, `NRE`_ +##### 2. RPD_DEBIT_ATTEMPT_FAILED Webhook +This webhook is sent when the end user tries to make a payments but the debit fails due to some reason. + + + +
+ + statusCode of this event can be one of the following: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
statusCodestatusDescription
R01The customer's debit attempt failed.
R02Payment authorization took too long.
R03The customer's bank is taking too long to respond.
R04The debit process took too long.
R05Connection timed out during the credit request process.
R06The transaction exceeds the risk threshold.
R07The customer's bank is unavailable.
R08This transaction isn't permitted for the beneficiary.
R09Connection timed out during the debit request process.
R12Beneficiary bank response time is too high.
R13The total debit amount exceeded the set limit.
R14Transaction details mismatch.
R16The requested function is not supported for the beneficiary.
R20Receiver/beneficiary is not available, causing a timeout.
R22The debit acknowledgement was not received.
R25Duplicate transaction request.
R100Any other upstream server error.
+
+
+ + + +###### Examples + + + Example 1 + + + +
+ + In case of customer's debit attempt failed + +
+ {` +{ + "data": { + "rpd": { + "id": "178ce32b-bf43-4797-9423-027d3722df08", + "additionalData": null, // customer's own data if they provided + "statusCode": "R01", + "statusDescription": "The customer's debit attempt failed." + } + }, + "event": "RPD_DEBIT_ATTEMPT_FAILED", + "timeStamp": "2023-08-24T12:59:11.427233" +} + `} + +
+
+
#### Get Details API