Wallet Verify Callback 1: Wallet Verify Result
Where should I integrate
Case 1: Success
If Unhosted Wallet Owner successfully completed message signing, you can expect to receive below callback from GTR with callbackType:18 and verifyStatus:100000.
Once you receive this callback from GTR, you can continue the transfer.
{
"requestId": "[REQUEST-ID]",
"invokeVaspCode": "YOUR_VASP_CODE",
"originatorVasp": "ORIGINATOR_VASP_CODE",
"beneficiaryVasp": "BENEFICIARY_VASP_CODE",
"callbackType": 18,
"callbackData": {
"notifyResult": {
"verifyMessage": "Verify Success",
"verifyStage": "WALLET_OWNER_VERIFICATION",
"verifyStatus": 100000
}
}
}
Case 2: Fail
If Unhosted Wallet Owner never scanned the QR Code with the right wallet or never completed message signing, you can expect to receive below callback from GTR with callbackType:18 and verifyStatus:100001.
Once you receive this callback from GTR, you should stop the process or ask your user to retry.
{
"requestId": "[REQUEST-ID]",
"invokeVaspCode": "YOUR_VASP_CODE",
"originatorVasp": "ORIGINATOR_VASP_CODE",
"beneficiaryVasp": "BENEFICIARY_VASP_CODE",
"callbackType": 18,
"callbackData": {
"notifyResult": {
"verifyMessage": "Verify Failed",
"verifyStage": "WALLET_OWNER_VERIFICATION",
"verifyStatus": 100001
}
}
}
Case 3: Expired
If Unhosted Wallet Owner never performed any operations, this request will be auto expired. After GTR mark this request as expired, you can expect to receive below callback from GTR with callbackType:18 and verifyStatus:100031.
Once you receive this callback from GTR, you should cancel the process from your end.
{
"requestId": "[REQUEST-ID]",
"invokeVaspCode": "YOUR_VASP_CODE",
"originatorVasp": "ORIGINATOR_VASP_CODE",
"beneficiaryVasp": "BENEFICIARY_VASP_CODE",
"callbackType": 18,
"callbackData": {
"notifyResult": {
"verifyMessage": "Verification Timeout",
"verifyStage": "WALLET_OWNER_VERIFICATION",
"verifyStatus": 100031
}
}
}