Transaction status (ValidateStatus and TrxStatus)
As stated in the response XML/JSON payload string of Do_Transfer (SOAP), Perform Transfer (REST), Do_BillPayment (SOAP), Bill Payment (REST), Get_TrxStatus (SOAP) , Get Transaction Status (REST) and Call back methods.
| Value | Type | Status | HTTP Status Code (REST API) | Remark |
| 000 | Approved | Transaction is Successful. | 200 (OK) | - |
| 101 | Declined | Blacklisted Sender. | 403 (Forbidden) | Sender name is found to be full match in UN or OFAC or other official sanction list. |
| 102 | Declined | Insufficient GSVA fund. | 403 (Forbidden) | Contact sales_remittance@tranglo.com to topup RSP GSVA wallet. |
| 103 | Declined | Blacklisted Beneficiary. | 403 (Forbidden) | Beneficiary name is found to be full match in UN or OFAC or other official sanction list. |
| 104 | Declined | Beneficiary name mismatched or empty. | 403 (Forbidden) | For Get_Validation only. Name mismatch means account is valid but the name provided by RSP is does not match exactly with the bank’s records.RSP may ignore or update RSP records with updated Beneficiary name prior to sending Do_Transfer. |
| 105 | Declined | Sender name mismatched. | 403 (Forbidden) | Applicable to Get_Validation & Get_Watchlist method only. |
| 106 | Declined | RSP Account Inactive. | 403 (Forbidden) | Contact support_remittance@tranglo.com to reactivate account. |
| 107 | Declined | Blacklisted Sender/Beneficiary. | 403 (Forbidden) | Blacklisted Sender/ Beneficiary Sender or Beneficiary name is found to be full match in UN or OFAC or other official sanction list. |
| 108 | Declined | Invalid Sender ID Expiry Date. | 403 (Forbidden) | Refer to Do_Transfer ‘sIdExpiry’ parameter. (Format: MM/dd/YYYY) |
| 302 | Error | Internal Server Error. | 500 (Internal Server Error) | RSP can retry the transaction until successful. In addition to that, RSP can also use Get_TrxStatus SOAP or Get Transaction Status REST API (Section “2.4 Transfer: Get Transaction Status”) method to check for transaction status if there is no response coming back due to network timeout or other errors. |
| 900 | Error | Invalid Username or Password / Invalid Signature. | 401 (Unauthorized) | - |
| 901 | Error | Invalid Sender Currency. | 400 (Bad Request) | RSP Currency Code as per RSP GSVA Wallet. Do not send as Sender currency. |
| 902 | Error | Invalid Beneficiary Currency. | 400 (Bad Request) | Please ensure correct currency as per target country. |
| 903 | Error | Invalid Sender ID. | 400 (Bad Request) | Please ensure Sender ID is 8 digits or more. |
| 904 | Error | Sender First or Last Name exceeded characters limit. | 400 (Bad Request) | Please ensure not exceed 50 characters. |
| 905 | Error | Invalid Sender Amount. | 400 (Bad Request) | - |
| 906 | Error | Invalid Bank or Issuer code. | 400 (Bad Request) | - |
| 907 | Error | Invalid Beneficiary ID. | 400 (Bad Request) | - |
| 908 | Error | Invalid Beneficiary Amount. | 400 (Bad Request) | - |
| 909 | Error | Beneficiary account limit exceeded. | 400 (Bad Request) | Please refer to Service Spec. |
| 910 | Error | Transaction not found in GloRemit system. | 404 (Not Found) | - |
| 911 | Error | Transaction expired. | 400 (Bad Request) | - |
| 912 | Error | Invalid Branch ID or Bank Branch Code. | 400 (Bad Request) | - |
| 913 | Error | Invalid/Duplicate Transaction ID. | 400 (Bad Request) | - |
| 914 | Error | Invalid Sender/Beneficiary Identification Type. | 400 (Bad Request) | - |
| 915 | Error | Invalid Beneficiary Account Type. | 400 (Bad Request) | - |
| 916 | Error | Invalid Birthdate. | 400 (Bad Request) | - |
| 917 | Error | Beneficiary Country / Nationality. | 400 (Bad Request) | - |
| 918 | Error | Invalid Beneficiary Account Number. | - | - |
| 919 | Error | Invalid Relationship Code. | - | - |
| 920 | Error | Invalid Sender Contact Number. | - | - |
| 921 | Error | Invalid Source of fund Code. | - | - |
| 922 | Error | Invalid Purpose Code. | - | - |
| 930 | Error | Transaction Rejected by Issuer. | 400 (Bad Request) | RSP should NOT retry the transaction as it is rejected internally by Beneficiary Issuer systems. |
| 931 | Error | Transaction Rejected – Issuer system busy. | 400 (Bad Request) | RSP can retry the transaction until successful. In addition to that, RSP can also use Get_TrxStatus SOAP method to check for transaction status if there is no response coming back due to network timeout or other errors. |
| 932 | Declined | Validation Not Supported. | 403 (Forbidden) | Error based on Beneficiary country and transaction type combination. |
| 933 | Declined | Transaction Rejected due Name Mismatch. | - | - |
| 934 | Declined | Transaction Rejected due invalid account number / account dormant. | - | - |
| 935 | Error | Account Validation is not available. Applicable for Get Validation only. | 400 (Bad Request) | - |
| 945 | Pending | Cancellation / Change Name request is in Progress. | 200 (OK) | - |
| 946 | Declined | Duplicate Cancellation / Change Name Request. | 403 (Forbidden) | - |
| 947 | Error | Cancellation / Change Name Transaction Not Found. | 404 (Not Found) | - |
| 948 | Declined | Cancellation / Change Name Not Possible. | 403 (Forbidden) | - |
| 949 | Declined | No Code Found for Cancellation / Change Name. | 404 (Not Found) | - |
| 966 | Pending | Transaction Under Compliance Review | 200 (OK) | The transaction is currently on-hold under Tranglo's Compliance and will reach out to RSP via email for RFI purposes. |
| 967 | Suspected | Transaction is suspected. | 200 (OK) | RSP should NOT retry the transaction. This normally happens when GloRemit system is unable to confirm whether the Beneficiary bank has accepted or rejected the transaction. Please email to support@tranglo.com for follow-up. |
| 968 | Pending | Transaction is pending. | 200 (OK) | RSP can also use Get_TrxStatus SOAP method to check for transaction status. |
| 969 | Pending | Transaction under process. | 200 (OK) | RSP can also use Get_TrxStatus SOAP method to check for transaction status. |
| 981 | Declined | Exceed Daily Transfer Amount Limit. | 403 (Forbidden) | Please refer to Service Spec. |
| 982 | Declined | Exceed Per Transaction Amount Limit. | 403 (Forbidden) | Please refer to Service Spec. |
| 999 | Error | General or Network Error. | 500 (Internal Server Error) | RSP can retry the transaction till success. |
Only Applicable for Cash Pickup Transaction
| Payout Status | Type | Description |
| In Process | Pending | Transaction is pending to be claimed. |
| Claimed | Approved | Beneficiary has claimed the money. |
| Cancelled | Declined | Transaction has been cancelled / expired. |
Only Approved and Pending type of transaction is considered as accepted in GloRemit systems. RSP Partner should reconcile the Approved and Pending transaction before attempt to retry or discard in RSP systems.
Error and Declined transaction type is considered failed and RSP systems can freely retry transactions.
Suspected transaction type is considered as Pending. RSP system MUST NOT retry transactions with Suspected status. Tranglo support team will be investigating such transactions and will update the transaction status once we have confirmation. RSP may email Tranglo Support for check for status of the investigation.
Reference
Currency code ISO 4217
https://www.iso.org/iso-4217-currency-codes.html
Country code ISO 3166
http://www.iso.org/iso/english_country_names_and_code_elements