Transaction Status (ValidateStatus and TrxStatus)
As stated in the response XML string of Method 2.2 and Method 2.4
| Code | Status Type | Description |
| 000 | Approved | Transaction is Successful |
| 101 | Failed | Blacklisted Sender. Sender name is found to be full match in UN or OFAC or other official sanction list |
| 102 | Failed | Insufficient GSVA fund. Contact sales_remittance@tranglo.com to topup RSP GSVA wallet. |
| 103 | Failed | Blacklisted Beneficiary. Beneficiary name is found to be full match in UN or OFAC or other official sanction list |
| 104 | Failed | Beneficiary name mismatched or empty. 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 | Failed | Sender name mismatched Applicable to Get_Validation & Get_Watchlist method only |
| 106 | Failed | RSP Account Inactive. Contact support@tranglo.com to reactivate account. |
| 107 | Failed | Blacklisted Sender/Beneficiary Sender or Beneficiary name is found to be full match in UN or OFAC or other official sanction list |
| 108 | Failed | Invalid Sender ID Expiry Date (Refer to Do_Transfer ‘sIdExpiry’ parameter) (Format: MM/dd/YYYY) |
| 302 | Failed | Internal Server Error (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) |
| 900 | Failed | Invalid Username or Password / Invalid Signature |
| 901 | Failed | Invalid Sender Currency. RSP Currency Code as per RSP GSVA Wallet. Do not send as Sender currency. |
| 902 | Failed | Invalid Beneficiary Currency. Please ensure correct currency as per target country. |
| 903 | Failed | Invalid Sender ID. Please ensure Sender ID is 8 digits or more |
| 904 | Failed | Sender First or Last Name exceeded 50 characters |
| 905 | Failed | Invalid Sender Amount |
| 906 | Failed | Invalid Bank or Issuer code |
| 907 | Failed | Invalid Beneficiary ID |
| 908 | Failed | Invalid Beneficiary Amount |
| 909 | Failed | Beneficiary account limit exceeded Please refer to Section 2.7 |
| 910 | Failed | Transaction not found in Tranglo system |
| 911 | Failed | Transaction expired |
| 912 | Rejected / Failed (Subject by receiving country) | Invalid Branch ID or Bank Branch Code |
| 913 | Failed | Invalid/Duplicate Transaction ID |
| 914 | Failed | Invalid Sender/Beneficiary Identification Type |
| 915 | Failed | Invalid Beneficiary Account Type |
| 916 | Failed | Invalid Birthdate |
| 917 | Failed | Invalid Beneficiary Country |
| 930 | Rejected / Failed (Subject by receiving country) | Transaction Rejected by Issuer (RSP should NOT retry the transaction as it is rejected internally by Beneficiary Issuer systems) |
| 931 | Failed | Transaction Rejected – Issuer system busy (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 | Failed | Validation Not Supported Error based on Beneficiary country and transaction type combination |
| 933 | Rejected / Failed (Subject by receiving country) | Transaction Rejected due Name Mismatch |
| 934 | Rejected / Failed (Subject by receiving country) | Transaction Rejected due invalid account number / account dormant |
| 945 | Pending | Cancellation / Change Name request is in Progress. |
| 946 | Failed | Duplicate Cancellation / Change Name Request |
| 947 | Failed | Cancellation / Change Name Transaction Not Found |
| 948 | Failed | Cancellation / Change Name Not Possible |
| 949 | Failed | No Code Found for Cancellation / Change Name |
| 966 | Pending | Transaction under compliance review |
| 967 | Suspected | Transaction is suspected. Do NOT retry. This normally happens when Tranglo 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. RSP can also use Get_TrxStatus SOAP method to check for transaction status. |
| 969 | Pending | Transaction under process. RSP can also use Get_TrxStatus SOAP method to check for transaction status |
| 981 | Failed | Exceed Daily Transfer Amount Limit Please refer to Section 2.7 |
| 982 | Failed | Exceed Per Transaction Amount Limit Please refer to Section 2.7 |
| 999 | Failed | General or Network Error (RSP can retry the transaction till success) |
Status Type:
- Failed: Transaction fee will be refunded
- Rejected: Transaction fee will NOT be refunded
- Approved: Transaction credited successfully
- Suspected and Pending: Transaction in processing
Only Approved and Pending type of transaction is considered as accepted in BizPay systems. Customer Partner should reconcile the Approved and Pending transaction before attempt to retry or discard in Customer systems.
Error and Declined transaction type is considered failed and Customer systems can freely retry transactions
Suspected transaction type is considered as Pending. Customer 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. Customer may email Tranglo Support for check for status of the investigation.
Reference
Currency code ISO 4217 – http://www.iso.org/iso/support/currency_codes_list-1.htm
Country code ISO 3166 – http://www.iso.org/iso/english_country_names_and_code_elements