Errors
In the Travel Rule system we have two error types:
- System Errors: Possible errors when requesting GTR
- Travel Rule Errors: Business exceptions in the interaction between VASP and VASP
The following are descriptions and handling methods for error types:
System Errors
| Error Name | HTTP Status Code | Verify Status Code | Solving method |
|---|---|---|---|
| No Login Session | 401 | 100021 | Re-login |
| Session Expired | 401 | 100014 | Re-login |
| No Auth | 401 | 100020 | Re-login |
| Limitation Exceeded | 402 | 100003 | Please go to GTR website and process with new subscription |
| GTR Server Fail | 500 | 100006 | Retry *Please contact to GTR team |
| Initiator Server Fail | 500 | 100007 | Initiator Server error, please check the error message. |
| Receiver Server Fail | 500 | 100008 | Receiver Server Error, please check the error message. |
| Client Bad Parameters | 400 | 100004 | Please double check your parameters |
| Client Invalid Parameters | 400 | 100023 | Please double check your parameters |
| Request ID Duplicated | 400 | 100005 | Please swap your ID generator, it seems possible to cause conflict |
| VASP Public Key Not Found | 400 | 100016 | Please fetch VASP List to get the correct VASP Public key |
| Business Fail (Common) | 200 | 100001 | The business error, please check the error message. |
Travel Rule Errors
| Error Name | Verify Status Code | Scenario | Reason | Take Action |
|---|---|---|---|---|
| Address not found | 200001 | The address cannot be found, or multiple sets of matches are found for one address. | Let customers double-check the wallet address, network, ticker, tag or the type of wallet address is not a hot-wallet. | |
| PII Decrypt Fail | 200002 | Exception when algorithm cannot decrypt ciphertext. | Please check if your encryption key or encryption method is the same as spec. | |
| PII Verify Fail (Common Fail) | 200003 | Verification does not meet the Required PII compliance requirements for receiving VASP and contains mismatched or missing PII information. | PII information verification failed due to a mismatch or related reasons. * Check the verified fields and contact the VASP, or ask the customer to double-check the KYC information between the two systems. | |
| Initiator Server Fail | 100007 | Initiator Server error, please check the error message. | Retry *Please contact the GTR team. | |
| Receiver Server Fail | 100008 | Receiver Server Error, please check the error message. | Retry *Please contact the GTR team. | |
| GTR Server Fail | 100006 | GTR Server Error, Please check the error message. | Retry *Please contact the GTR team. | |
| Business Fail (Common) | 100001 | Common failed, please check the error message. | Please contact VASP. | |
| TX ID Not found | 200007 | TX ID Not found | Let the customer double-check the TX-ID or network beneficiary address is correct. | |
| Wrong invoke procedure | 100027 | Wrong invoke procedure | Wrong invoke procedure | |
| Expired | 100031 | This record has expired | Please initiate another request with new requestId | |
| User NO KYC Fail | 200008 | Only TRSP clients may return this error, GTR users should directly use 200003. The user does not have KYC data, please let the user complete first. | Let users do KYC. | |
| IVMS Name Identifier Mismatch Fail | 200009 | Only TRSP clients may return this error, GTR users should directly use 200003. The user name does not match. | Let the user double-check the KYC name. | |
| User in the sanction list Fail | 200010 | The user in the sanction list. | Popup warning to users. |
Functional Status Code
| Name | HTTP Status Code | Verify Status Code | Scenario | Description |
|---|---|---|---|---|
| Success | 200 | 100000 | Success | Success or verify success |
| Pending | 200 | 100002 | Pending | Results are still incomplete, try again this API for a few seconds or minutes. |
| Cancel | 200 | 100028 | Cancel (End State) | Initiator cancel |