Collecting via FPX B2C or B2B1 in CHIP Collect may result in situations where a customer’s account has been deducted but the payment has failed.
Additionally, you may wonder why a particular customer keeps attempting to purchase but fails to complete payments.
These situations can be frustrating for both you and your customers. However, understanding FPX response codes can help you verify failed payments and take appropriate action.
FPX response codes provide important information on the status of a transaction, indicating whether it was successful, declined, or requires further action.
In the case of failed payments, FPX response codes can help you identify the cause of the failure. Based on this information, you can determine whether the payment should be refunded or a new payment request should be initiated.
Identifying FPX response codes via the CHIP Merchant Portal
As a CHIP merchant, you can view the FPX response code for each transaction in the CHIP Merchant Portal. This can help you quickly identify and address any failed payments that may have occurred.
To view the codes, you can follow the steps below:
FPX response codes
To help you understand these response codes, we’ve put together a guide that explains the most common FPX response codes related to failed payments and their meanings:
Note: You can use 'CTRL + F' or 'Command + F' to find the matching code.
|Invalid Seller Or Acquiring Bank Code
|Invalid Buyer Account
|No Credit Account
|Duplicate Seller Order Number
|Invalid Seller Exchange Or Seller
|Maximum Transaction Limit Exceeded
|Merchant Specific Limit Exceeded
|Invalid Seller for Merchant Specific Limit
|No Buyer Account Number
|Transaction Not Permitted
|Transaction To Merchant Not Permitted
|Invalid Serial Number
|Transaction Not Found
|Invalid Buyer Name Or Buyer ID
|Host Decline When Down
|Buyer Cancel Transaction
|Invalid Transaction Model
|Invalid Transaction Type
|Internal Error At Bank System
|Debit Failed Exception Handling
|Credit Failed Exception Handling
|Transaction Not Received Exception Handling
|Bank Internet Banking Unavailable
|Invalid Buyer Bank
|Pending Authorization (Applicable for B2B model)
|Transaction Cancelled By Customer
|Invalid Application Type
|Invalid Email Format
|Invalid Maximum Frequency
|Invalid Frequency Mode
|Invalid Expiry Date
|Invalid e-Mandate Buyer Bank ID
|Transaction Rejected As Not In FPX Operating Hours
|Invalid Acquiring Bank Code
|Invalid Source IP Address (Applicable for B2B2 model)
|Invalid Seller Exchange IP
|Seller Exchange Encryption Error
|Invalid Number Of Orders
|Invalid Seller Exchange
|Invalid FPX Transaction Model
|Transaction Rejected Due To Duplicate Seller Exchange Order Number
|Duplicate Exchange Order Number
|Seller Does Not Belong To Exchange
|Invalid Transaction Type
|Seller Exchange Date Difference Exceeded
|Buyer Session Timeout At Internet Banking Login Page
|Buyer Failed To Provide The Necessary Info To Login To Internet
Banking Login Page
|Buyer Choose Cancel At Login Page
|Buyer Session Timeout At Account Selection Page
|Buyer Failed To Provide The Necessary Info At Account Selection Page
|Buyer Choose Cancel At Account Selection Page
|Buyer Session Timeout At TAC Request Page
|Buyer Failed To Provide The Necessary Info At TAC Request Page
|Buyer Choose Cancel At TAC Request Page
|Buyer Session Timeout At Confirmation Page
|Buyer Failed To Provide The Necessary Info At Confirmation Page
|Buyer Choose Cancel At Confirmation Page
|Internet Banking Session Timeout
|Transaction Amount Is Lower Than Minimum Limit
|Transaction Is Canceled By Merchant
* Merchant should not take transaction with response code ‘09’ as final. This transaction status will be changed once FPX receives an updated status from the Bank.
We’re always open to content contributions from our community. Join our Facebook Group and share your work or topic ideas to potentially be featured on our blog.
Moreover, if you have suggestions for our upcoming features, we’d love to hear them! Share your Wishlist with us.