Skip to main content
Search

Wallet Verify API 1: Create Verify

Where should I integrate

Wallet Verify - Unhosted Wallet Verification

Please submit the following payload to this endpoint:

curl --silent --location --request POST "/api/verify/wallet/verify" \
--cert-type P12 --cert ./certificate.p12:'[MY_PASSWORD_OF_CERT]' \
--header 'Content-Type: application/json' \
--header "Authorization: Bearer [YOUR LOGIN TOKEN]" \
--header "Connection: keep-alive" \
--data-raw "{
\"requestId\": \"[GENERATE YOUR REQUEST ID]\",
\"beneficiaryAddress\": {
\"address\": \"[TARGET ADDRESS]\",
\"tag\":\"[TARGET TAG: LEAVE EMPTY IF NO NEED]\"
},
\"originatorAddress\": {
\"address\": \"[TARGET ADDRESS]\",
\"tag\":\"[TARGET TAG: LEAVE EMPTY IF NO NEED]\"
},
\"blockchainInfo\": {
\"network\": \"[NETWORK SYMBOL]\",
\"ticker\": \"[TICKER SYMBOL]\",
\"txId\": \"[IF ITS DEPOSIT, PLEASE FILL TXID, OR LEAVE IT EMPTY STRING OR UNSET]\"
},
\"complianceInfo\": {
\"amount\": \"[AMOUNT OF CRYPTO CURRENCY TICKER]\",
\"fiatPrice\": \"[FIAT PRICE]\",
\"fiatName\": \"[FIAT NAME]\"
},
\"sourceVaspCode\": \"[ONLY TRSP VENDOR NEED TO FILL THIS, IGNORE IF YOU'RE VASP/EXCHANGE]\"
}"

You can expect to get following response. Please render the qrCodeContent as an image to your VASP user.

Your service will be awaiting the Unhosted Wallet Owner to sign a message after they scan the QR Code and connect the wallet.

GTR will notify you of the result or the expiration.

You are supposed to hold this transfer before your service receives the callback from GTR.

{
"verifyStatus": 100000,
"verifyMessage": "Success",
"data": {
"qrCodeContent": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"expireTime": [Timestamp of this QR Code to be expired, e.g 192848184313]
}
}

About address screening

This API does not return screeningResult in its synchronous response.

If the wallet owner later completes the signing flow successfully, GTR may perform address screening on the verified address and include that result in the callback to your service.

That means:

  • The create-verify API response is only for QR code session creation.
  • The screening result, if available, should be consumed from the Wallet Verify callback flow.