Transaction status (ValidateStatus and TrxStatus)
As stated in the response XML/JSON payload string of Do_Transfer and Get_TrxStatus methods.
| Value | Type | Status | Remark |
| 000 | Approved | Transaction is Successful. | - |
| 102 | Declined | Insufficient GSVA fund. | Contact [email protected] to topup Customer wallet |
| 103 | Declined | Blacklisted Beneficiary. | Beneficiary name is found to be full match in UN or OFAC or other official sanction list |
| 104 | Declined | Beneficiary name mismatched or empty. | For Get_Validation only. Name mismatch means account is valid but the name provided by Customer is does not match exactly with the bank’s records. Customer may ignore or update Customer records with updated Beneficiary name prior to sending Do_Transfer |
| 106 | Declined | Customer Account Inactive. | Contact [email protected] to reactivate account. |
| 107 | Declined | Blacklisted Beneficiary. | Blacklisted Beneficiary or Beneficiary name is found to be full match in UN or OFAC or other official sanction list |
| 302 | Error | Internal Server Error. | Customer can retry the transaction until successful. In addition to that, Customer 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 | Error | Invalid Username or Password / Invalid Signature. | - |
| 902 | Error | Invalid Beneficiary Currency. | Please ensure correct currency as per target country. |
| 905 | Error | Invalid Customer Amount. | - |
| 906 | Error | Invalid Bank or Issuer code. | - |
| 907 | Error | Invalid Beneficiary ID. | - |
| 908 | Error | Invalid Beneficiary Amount. | - |
| 909 | Error | Beneficiary account limit exceeded. | Please refer to Service Specification transaction limit session of each corridor. |
| 910 | Error | Transaction not found in TB system. | - |
| 911 | Error | Transaction expired. | - |
| 912 | Error | Invalid Branch ID or Bank Branch Code. | - |
| 913 | Error | Invalid/Duplicate Transaction ID. | - |
| 914 | Error | Invalid Beneficiary Identification Type. | - |
| 915 | Error | Invalid Beneficiary Account Type. | - |
| 916 | Error | Invalid Birthdate. | - |
| 917 | Error | Beneficiary Country / Nationality. | - |
| 918 | Error | Invalid Beneficiary Account Number. | - |
| 919 | Error | Invalid Relationship Code. | - |
| 921 | Error | Invalid Source of fund Code. | - |
| 922 | Error | Invalid Purpose Code. | - |
| 930 | Error | Transaction Rejected by Issuer. | Customer should NOT retry the transaction as it is rejected internally by Beneficiary Issuer systems. |
| 931 | Error | Transaction Rejected – Issuer system busy. | Customer can retry the transaction until successful. In addition to that, Customer 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. | 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. | - |
| 945 | Pending | Cancellation / Change Name request is in Progress. | - |
| 946 | Declined | Duplicate Cancellation / Change Name Request. | - |
| 947 | Error | Cancellation / Change Name Transaction Not Found. | - |
| 948 | Declined | Cancellation / Change Name Not Possible. | - |
| 949 | Declined | No Code Found for Cancellation / Change Name. | - |
| 967 | Suspected | Transaction is suspected. | Customer should NOT retry the transaction. This normally happens when Tranglo Business system is unable to confirm whether the Beneficiary bank has accepted or rejected the transaction. Please email to [email protected] for follow-up. |
| 968 | Pending | Transaction is pending. | Customer can also use Get_TrxStatus SOAP method to check for transaction status. |
| 969 | Pending | Transaction under process. | Customer can also use Get_TrxStatus SOAP method to check for transaction status. |
| 981 | Declined | Exceed Daily Transfer Amount Limit. | Please refer to Service Specification transaction limit session of each corridor. |
| 982 | Declined | Exceed Per Transaction Amount Limit. | Please refer to Service Specification transaction limit session of each corridor. |
| 999 | Error | General or Network Error. | Customer 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 Tranglo Business systems. Customer 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