Pre-Deposit Check callback

This callback allows clients to validate a transaction before the actual fund movement happens in the virtual account. The client can accept or reject incoming funds via this callback.

🙌

Important note

Please use only Staging Credentials on each API Reference page to test the APIs directly from our Documentation.

API Endpoint

EnvironmentAPI endpoint
staging/sandboxhttps://your.custom.endpoint.com
productionhttps://your.custom.endpoint.com

The client can use this callback to accept or reject any incoming transaction for their virtual account.

The incoming transactions will be accepted under the following scenarios:

  • If the remitter account details is whitelisted via remitter whitelisting API
  • If the client response in pre-deposit check callback is to accept the funds.
  • If the remitter whitelisting flag is disabled and the pre-deposit check callback response is either inappropriate/no response.
  • If the remitter whitelisting flag is disabled and the pre-deposit check callback is not subscribed by the client.

The incoming transaction will be rejected under the following scenarios:

  • If the client response in pre-deposit check callback is to reject the funds.
  • If the remitter account details are not whitelisted, the remitter whitelisting flag is enabled, and the pre-deposit check callback is not subscribed.
  • If the remitter account details are not whitelisted, the remitter whitelisting flag is enabled, and the pre-deposit check callback response is inappropriate/no response

Please note the PDC callback need to be subscribed during onboarding. The whitelisting flag may be enabled/disabled on the basis of client use case during on boarding.

Body Params
string
required

The transaction amount that will be collected in the virtual account.

string
required

The unique transaction reference number from the bank partner

string
required

A unique identifier assigned to each merchant by Decentro during Onboarding.

string
required

The unique transaction identifier of Decentro, passed against each payment transaction.

string
required

The virtual account of Merchant at Decentro's end where the funds will be stored, if accepted.

string
required

Account number of the payer/remitter.

string

Account ifsc of the payer/remitter.

string

Name of the payer if propagated by the partner bank.

string
required

The transafer type of the E collect transaction. Possible values: IMPS, NEFT, RTGS

Headers
string

The header token shared by you should not contain any unsanitized values like @ # $ % ^ & * ! ; : ' " ~ ` ? = + ) (

string

The header token shared by you should not contain any unsanitized values like @ # $ % ^ & * ! ; : ' " ~ ` ? = + ) (

Response

Response body
Language