Remitter Kyc

Log in to see full request history
SNoHttp Response CodeResponse CodeStatusDescription
12001trueKyc completed and OTP has been sent to remitter mobile number.
22002falseCustomer kyc is unsuccessful, Please try again. OR KYC related messages
32004falseInvalid Remitter details.
42003falseThese mobile number is not authorise to avail DMT transaction facility!
52008falseMerchant is not activate to use DMT services. Please try again after some time.
62009falseMERCHANT ID NOT FOUND..
720010falsevalidation_errors (dynamic message related to validations)
820011falseDMT service or preference is not active for this account.
920012falseUnable to process query remitter request.
1020013falseInvalid JWT token or token related errors (this is dynamic message could be change as per partner's input parameter)
1120014falseAuthentication failed.
1220015falseDMT Bank4 service is down.

📘

Note: Please use following wadh value for DMT Bank4 kyc. This wadh is applicable for both environment UAT as well Production.

TF/lfPuh1n4ZY1xizYpqikIBm+gv65r51MFNek4uwNw=

Encryption Logic for PID

<?php $ciphertext_raw = openssl_encrypt($piddata, "AES-128-CBC", $key, $options=OPENSSL_RAW_DATA, $iv); $enctoken = base64_encode($ciphertext_raw); echo $enctoken; ?>
Body Params
string
required

Remitter mobile number

string
required

Encrypted value of pid data. Please refer above section to get the encryption logic

string

Merchant shop latitude

string

Merchant Shop Longitude

string

Customer Email address

string

Customer Address

string
string
required

This value you will get in the query remitter api for response_code 2

string
required
Defaults to SITE | APP
string
required

Partner Merchant code

Headers
string
required
string

If authorisedkey is generated then you have to pass authorisedkey else no need to pass

Responses

Language
Click Try It! to start a request and see the response here! Or choose an example:
application/json