Remitter whitelisting Callback

post

https://your.custom.endpoint.com/client/custom/endpoint

This callback is to inform the clients about the final status of the account whitelisting request to Decentro.

API Endpoints

Environment	Endpoint
Staging / Sandbox	https://your.custom.endpoint.com
Production	https://your.custom.endpoint.com

via this callback, clients will receive the final status of whitelisting request of a remitter's account.

Flow

Below is the remitter whitelisting flow for clients:

The client must ensure that the remitter whitelisting configuration flag is enabled for their consumer.
Clients can trigger the remitter whitelisting API by sending a request with the necessary account details.
A notification will be sent to the Decentro admin for review of your whitelisting request.
The admin will respond with either an accept or reject decision for your whitelisting request.
After the admin's decision, you will receive a remitter whitelisting callback indicating the final status of your whitelisting request.

Body Params

callback_attempt

string

Number of times the callback has been attempted.

callback_timestamp

string

Timestamp of the callback. Not the timestamp of the transaction.

callback_txn_id

string

Unique identifier mapped to the callback attempt.

original_callback_txn_id

string

Unique identifier mapped to the first callback attempt.

decentro_txn_id

string

The unique transaction identifier generated by Decentro for each request.

request_status

string

The request status after the admin action on the remitter details. Possible values: ACCEPTED/REJECTED

whitelisting_status

string

The whitelisting status of the remitter account details. Possible values: ACTIVE/INACTIVE

message

string

The description of the whitelisting status of the remitter account.

mapped_to_virtual_account_list

object

List of virtual details against which the remitter account is whitelisted.

Headers

your_custom_header_1

string

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

your_custom_header_2

string

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

Responses

API Endpoints

Flow

200200

400400