一键重装系统工具 | U盘启动盘制作工具 | 误删文件恢复软件 | 硬盘数据抢救专家 | 电脑蓝屏修复助手 | C盘空间清理神器 | 电脑驱动离线安装工具 | 微信聊天记录恢复工具 | 照片误格式化恢复 | 电脑密码破解清除工具 | 系统崩溃紧急救援盘 | 电脑加速优化大师 | 电脑开不了机怎么重装系统 | 回收站清空了怎么恢复 | 硬盘分区丢失数据恢复 | 电脑卡顿重装系统有用吗 | U盘插入提示格式化数据恢复 | 电脑中毒文件被隐藏恢复 | 忘记电脑开机密码怎么办 | 新硬盘分区对齐工具 | 旧电脑装Win10流畅工具 | SD卡照片删除恢复免费版 | 移动硬盘打不开提示损坏修复 | 电脑无故重启系统修复工具 | 电脑小白一键重装神器 | 程序员电脑环境配置助手 | 设计师电脑字体/素材恢复工具 | 网吧网管系统维护工具箱 | 财务人员电脑发票备份恢复 | 学生党免费电脑系统安装包 | 电脑维修师傅必备工具盘 | 游戏玩家电脑性能优化助手 | 办公白领误删文档恢复软件 | 自媒体视频素材恢复工具 | 网课录制视频损坏修复工具 | 最好的U盘PE系统排名 | 数据恢复软件哪个最强 | 免费电脑助手与收费版区别 | 国产装机工具哪款无广告 | 离线版驱动助手推荐 | 轻量级电脑优化工具对比 | 支持NVMe驱动的PE工具 | 带网络功能的应急启动盘 | 2026最新版万能装机工具 | 支持Win11 24H2的PE工具 | 最新免激活系统重装工具 | 2026数据恢复软件破解版合集 | 纯净无捆绑装机助手V3.0 | 支持苹果M芯片的电脑助手 | 秋季更新版系统维护工具箱 | 电脑系统崩了怎么用U盘把重要资料拷贝出来 | 重装系统前哪些文件夹必须备份 | 固态硬盘误格式化还能恢复数据吗 | 如何制作一个既带PE又能存数据的双分区U盘 | 电脑总是弹窗广告用什么助手彻底拦截 后台管理
📢 欢迎访问系统之家!所有资源均经过安全检测。

Transaction response codes

发布时间:2026-09-19 | 浏览:1
📥 下载地址(文章开头)
装机神器,可以安装一切系统。
Transaction response codes It is highly unlikely that you will receive many of these response codes; as a general rule you should use the provided summary response code to determine whether a transaction is approved or declined. Valid response codes are of a two digit alphanumeric format. If an unknown response code is returned please contact Westpac with the appropriate transaction details. Please note that there are no response codes specific to card verification number mismatches. This is because no financial institutions within Australia currently return any such information if declining a transaction for security reasons. Response Codes are generally returned from the customer's issuing bank. Credit card transaction response codes Successful card transactions will generally have a response code of 00 - Approved or completed successfully or 08 - Honour with Identification. Other statuses indicate a problem processing the transaction. If you receive a status code starting with 'Q' that you do not understand, you should contact your Client Enquiry Manager with the transaction details. For non-approved transaction statuses that do not start with 'Q' the cardholder will likely need to contact their issuing financial institution for more information about the rejected transaction. When doing so you can recommend they: provide the date and amount of the transaction. request specific information regarding the transaction rejection. This indicates that the transaction has been authorised. What authorisation DOES mean:- The card number is valid The card has not been reported lost or stolen (although it may in fact be lost, stolen or compromised [card details improperly obtained or copied] and the card owner is unaware) There are sufficient funds available to cover the transaction. What authorisation DOES NOT mean:- An authorisation does NOT confirm that the person providing the card number is the legitimate cardholder. The risk remains that the person providing the card number has either stolen or improperly obtained the card. 01 - Refer to card issuer This indicates an error or problem from the card issuer. The problem may be related to the cardholder's account. This response code is often a result of one of the following:- Suspected Fraud Any other rule imposed by the card issuer that causes a decline (e.g. daily limit exceeded, minimum monthly payment not made, duplicate transaction suspected, etc.) 03 - Invalid merchant This can indicate a problem with merchant configuration. This can also be returned for AMEX transactions when there is a problem with the setup at American Express. This code can be returned from an issuing bank if they don't like the acquiring bank. An example of this would be someone trying to pay their speeding fine with an overseas card. The overseas issuing bank would return a 03, indicating that they wouldn't allow the transaction over the internet for an Australian bank. 04 - Pickup Card. This can mean the card has been reported as lost or stolen. The cardholder should contact their issuing bank. 05 - Do not honour This indicates an error or problem from the card issuer. The problem may be related to the cardholder's account. In general, the reason for this response code may be any of the following: Suspected Fraud Insufficient Funds Any other rule imposed by the card issuer that causes a decline. For example, daily limit exceeded, minimum monthly payment not made, duplicate transaction suspected, etc. You should not retry the transaction. If you want to attempt to charge the cardholder again then you must consider the following: Check that the cardholder's details are correct. It is likely you will need to change some of their details. Check for suspected fraudulent activity and re-attempt using authentication, such as 3-D Secure. 08 - Honor with identification This indicates that the transaction has been authorised. What authorisation DOES mean:- The card number is valid The card has not been reported lost or stolen (although it may in fact be lost, stolen or compromised card details improperly obtained or copied and the card owner is unaware) There are sufficient funds available to cover the transaction. What authorisation DOES NOT mean:- An authorisation does NOT confirm that the person providing the card number is the legitimate cardholder. The risk remains that the person providing the card number has either stolen or improperly obtained the card. 12 - Invalid transaction This code is often returned from the issuer when they do not accept the transaction. This can possibly be when a transaction for the same amount and merchant is attempted multiple times quickly for the same card. The cardholder should contact their issuing bank. 14 - Invalid card number (no such number) This code indicates that the card number does not exist. Also returned code if an AMEX card is used, but the merchant is not setup for AMEX cards. 17 - Customer cancellation This code will be returned if a user "voids" a transaction through the QuickStream interface or REST API (or "refunds" a transaction the same day it was created before the settlement cut-off ). In essence a reversal is performed. 22 - Suspected Malfunction This code normally indicates that the card number was invalid. 42 - No Universal Account This error is returned from some issuers when the credit account does not exist at the issuing bank. This situation is similar to the 14 response code. 54 - Expired Card This error is returned when the card has expired. Check that the expiry date is correct, and attempt the transaction again. If the transaction still does not work, check with the cardholder to see if they have a new card with a new expiry date. 61 - Exceeds withdrawal amount limits This error is returned when the cardholder does not have enough credit to pay the specified amount. Ask the cardholder if they have another card to use for the payment. 79 - Reserved for private use Applies for Mastercard only. The customer's bank (Card Issuer) has declined the transaction due to invalid card data. The customer should check the card information entered and try again, or use an alternate credit card. 82 - Reserved for private use Applies for Mastercard only. The customer's bank (Card Issuer) has declined the transaction due to a policy reason. The customer should check the card information entered and try again, or use an alternate credit card. 83 - Reserved for private use Applies for Mastercard only. The customer's bank (Card Issuer) has declined the transaction due to a security reason. The customer should check the card information entered and try again, or use an alternate credit card. 91 - Issuer or switch is inoperative This code is used to indicate that the next party in a card transaction timed out and the transaction has been reversed. This may happen between QuickStream and Westpac, or further down the chain. This response may also be returned for: pre-authorisation transactions that are manually reversed, eftpos transactions that are attempted and may be manually retried. 92 - Financial institution or intermediate network facility cannot be found for routing The card number is incorrect. The first 6 digits of the card number indicate which bank issued the card. These are used for routing card requests through the card network to the issuing bank. This error indicates that there is no bank that corresponds to the first 6 digits of the card number. The QuickVault account token used for the transaction was not found or is not enabled. Please check that the QuickVault account exists and is enabled. You can do this in via the REST API, QuickGateway or by signing into QuickStream. Payment response files with a 2-character response code field may report this as No rather than No account . Q0 - Scheme Tokenisation Error The Q0 status code indicates a scheme tokenisation error. This usually means that the scheme token is suspended. Q3 - Payment Gateway Unavailable The downstream card gateway was unavailable. The card transaction was not attempted and the transaction record will not exist. When you receive this response code, the transaction will not exist in QuickStream. QI - Transaction incomplete This status code indicates that a request message was sent to the QuickStream server but no response was received within the timeout period. QQ - Invalid Card The QQ error code indicates that the card details (card number, expiry date or CVN) are invalid. This could be because the card number does not meet check digit validation, an invalid expiry date was entered, or an invalid CVN was entered. QY - Card Type not accepted The QY error code indicates that the merchant is not enabled for the particular card scheme. This error code is normally returned for American Express cards, or when a UnionPay debit card is used. Only UnionPay cards are supported. Bank account transaction response codes (aka Direct Entry Transaction Response Codes) In all cases where the response code requires the account holder to contact their bank, it will help if they can provide a date and amount of the failed attempted transaction and specifically ask the bank why they returned that status for the attempted transaction. Otherwise, the issuing bank staff may just check the available funds in the account. Successful Direct Entry transactions will generally have a response code of G - WBC Exception Processing released successfully. 2 - Payment Stopped The account holder has requested that their bank stop any direct debit transactions. Contact the customer to determine an alternate payment mechanism, or if they wish to stop their service. 3 - Account Closed The account holder has closed their account. Contact your customer to ask for new account details. 5 - No Account/Incorrect Account# Contact your customer to determine if the BSB and account number you have is correct. It may be useful for them to fax you the first page of their bank account statement so that you can check you have the correct BSB and account number. 6 - Refer to Customer Contact your customer to determine if they have sufficient funds in their account, if the BSB and account number you have is correct, and if their account allows direct debit transactions. The banks use this response code as they see fit. If you receive this response code for a customer, and you have never had a successful debit for that customer, first check the BSB and account number. This could indicate one of the following: Account does not allow Direct Debit Incorrect Account Number Insufficient Funds Suspected Fraud Any other rule imposed by the account holder's bank that causes a decline (e.g. daily limit exceeded, duplicate transaction suspected, etc) G - WBC Exception Processing released successfully The transaction is being processed by Westpac. If the debit is from another bank, Westpac has sent the transaction to that bank. When a direct entry transaction is successful, it remains in this response code. When a transaction is declined and returned, the response will be set to a different response code. CANCELLED - Customer cancellation This code will be returned if a user "voids" a transaction through the QuickStream interface or REST API. In essence a reversal is performed. PayID transaction response codes PayID payments you receive will always be ACSC. Refunded/returned PayID payments may transition between Pending response codes before reaching an Approved or Declined status. It is highly unlikely that you will receive many of the Pending codes. PayTo transaction response codes A PayTo transaction may transition between Pending response codes before reaching an Approved or Declined status. It is highly unlikely that you will receive many of the Declined codes. RCVD - Received Payment instruction has been received, API specification validation is successful. This is an intermediate state in PayTo payment processing. No action required . PATC - Partially Accepted Technical Correct Payment initiation needs multiple authentications, some but not all have been performed. This is an intermediate state in PayTo payment processing. No action required . ACTC - Accepted Technical Validation Technical validations are successful. This is an intermediate state in PayTo payment processing. No action required . ACCP - Accepted Customer Profile Following technical validations, customer profile is validated and is successful. This is an intermediate state in PayTo payment processing. No action required . ACSP - Accepted Settlement In Process All preceding checks such as technical validations and customer profile check are successful, payment instruction is accepted for execution. This is an intermediate state in PayTo payment processing. No action required . ACCC - Accepted Settlement Completed Creditor Account Settlement in the payee's account has been completed. This is an intermediate state in PayTo payment processing. No action required . Payment instruction is pending. Further checks are being performed. No action required . ACFC - Accepted Funds Checked The funds reservation check of the debtor has been completed. This is an intermediate state in PayTo payment processing. No action required . ACPD - Accepted Clearing Processed Payment transaction is accepted for clearing process. This is an intermediate state in PayTo payment processing. No action required . ACSC - Accepted Settlement Completed Debtor Account The processing of the debit payment instruction is successful. This is a terminal state in PayTo payment processing. No action required . RJCT - Rejected Payment instruction has been rejected. This is a terminal state in PayTo payment processing. This status normally accompanies a reason code, view reason code for action . Payment transaction has been accepted, but been blocked from being posted to the credit account. This is a terminal state in PayTo payment processing. This status may accompany a reason code, view reason code for action . CANC - Cancelled Payment initiation has been cancelled. This is a terminal state in PayTo payment processing. This status may accompany a reason code, view reason code for action . AB01 - Aborted Clearing Timeout Clearing process is aborted due to timeout. Retry payment . AB02 - Aborted Clearing Fatal Error
📥 下载地址(文章中间)
装机神器,可以安装一切系统。
Clearing process is aborted due to a fatal error. Retry payment . AB03 - Aborted Settlement Timeout Settlement process is aborted due to timeout. Retry payment . AB04 - Aborted Settlement Fatal Error Settlement process is aborted due to a fatal error. Retry payment . AB08 - Offline Creditor Agent Payee Participant is unavailable, Flooded or Under Stress or Recovering. Retry payment . AC02 - Invalid Debtor Account Number Payer account number is invalid or missing. Contact payer . AC03 - Invalid Creditor Account Number Payee account number is invalid or missing. Check payee account . AC05 - Closed Debtor Account Number Payer account is closed. Contact payer . AC06 - Blocked Account Payee account is blocked and cannot accept credits. Check payee account . AC07 - Closed Creditor Account Type Payee account is closed. Check payee account . AC13 - Invalid Debtor Account Type Payer account product does not allow NPP payments. Contact payer to provide alternate account . AC14 - Invalid Creditor Account Type Payee account product does not allow NPP payments. Contact payee to provide alternate account . AC15 - Account Details Changed Payer Account Alias is not resolved or does not belong to Payer participant. Contact payer to provide alternate account . AG01 - Transaction Forbidden Account exists, but it does not accept credits due to unsupported transaction type. Check payee account . AG03 - Transaction Not Supported The credit account is open, but cannot accept NPP payments. Check payee account . AG07 - Unsuccessful Direct Debit There are insufficient funds to perform the debit transaction associated with the payment instruction. Contact payer or retry payment . AGNT - Incorrect Agent The resolved payer account bank does not match the PayTo agreement details. Contact payer to provide alternate account . AM01 - Zero Amount The payment amount is zero. Payment amount must be greater than zero . AM02 - Not Allowed Amount The payment amount is greater than the maximum allowed, the maximum limit for NPP payments is $99,999,999,999. Check payment amount submitted . AM03 - Not Allowed Currency The currency of the payment is not AUD. Payments must be made in AUD . AM04 - Insufficient Funds Debit account has insufficient funds for the payment. Contact payer or retry payment . AM05 - Duplication A repeat payment by the customer. Do not re-submit payment . AM06 - Too Low Amount Specified payment amount is less than the agreed minimum. Check payment amount submitted . AM09 - Wrong Amount Amount received is not the amount agreed or expected. Check payment amount submitted . AM12 - Invalid Amount The Amount in the Clearing or Settlement Request is missing, invalid or the amount in the Settlement Request does not match to the amount in the Clearing Request. Seek support from Qvalent helpdesk . AM18 - Invalid Number of Transactions The number of transactions in the payment instruction is Invalid. Seek support from Qvalent helpdesk . AM19 - Invalid Group Number of Transactions The number of transactions in the payment instruction does not equal '1'. Seek support from Qvalent helpdesk . AM21 - Limit Exceeded The payment amount exceeds the agreed limit between the responding participant and the payer customer. Contact payer or retry payment . AM22 - Zero Amount Not Applied Unable to apply zero amount to designated account. Check payment amount submitted, payment amount must be greater than zero . AV04 - Insufficient Funds The debtor account has insufficient funds for the payment. Retry payment . BE05 - Unrecognised Initiating Party Party who initiated the payment instruction is not recognised by the end customer. Contact payer . BE06 - Unknown End Customer End customer specified in the payment instruction is not known at the associated bank. Seek support from Qvalent helpdesk . BE08 - Missing Debtor Name Payer name is missing in the payment instruction. Check payer details . BE18 - Invalid Contact Details Contact details are missing or invalid in the payment instruction. Check contact details . BE22 - Missing Creditor Name The information regarding the Payee Name is required but not provided in the payment instruction. Check payee details . CH17 - Element Not Admitted Element in payment instruction is not allowed. Seek support from Qvalent helpdesk . CH20 - Decimal Points Not Compatible with Currency Number of decimal places is not compatible with the currency. Payment amount must be in AUD and have up to 2 decimal places . CH21 - Required Compulsory Element Missing Mandatory element in payment instruction is missing. Seek support from Qvalent helpdesk . CURR - Incorrect Currency Currency of the payment is incorrect. Payment must be made in AUD . DT01 - Invalid Date Settlement date and time is invalid in the payment instruction. Seek support from Qvalent helpdesk . DT02 - Invalid Creation Date Invalid creation date and time in Group Header (e.g. historic date). Seek support from Qvalent helpdesk . DT04 - Future date not supported Future payment date is not supported. Check payment date . ED06 - Settlement System Not Available Payment instruction is rejected due to Fast Settlement Service being unavailable. Retry payment . FF01 - Invalid File Format Payment instruction format is incomplete or invalid. Seek support from Qvalent helpdesk . FF04 - Invalid Service Level Code The Service Level code is not as per the specified format or is invalid based on the message type or membership. Seek support from Qvalent helpdesk . FF08 - Invalid End to End Id The End to End ID is missing or invalid in the payment instruction. Seek support from Qvalent helpdesk . FF10 - Bank System Processing Error Unable to process due to back office issues or outage. Retry payment . FF11 - Clearing Request Aborted Clearing Request is rejected due to being subject to a previous abort operation. Seek support from Qvalent helpdesk . G005 - Delivered With Service Level Payment has been delivered to payee agent with agreed service level. Check payment has been received in payee account . G006 - Delivered Without Service Level Payment has been delivered to payee agent outside agreed service level. Check payment has been received in payee account . MD01 - No Mandate There is no PayTo Agreement information such as a PayTo/Mandate ID in the payment instruction. Seek support from Qvalent helpdesk . MD02 - Missing Mandatory Information In Mandate PayTo agreement related information data required by the scheme is missing in the payment instruction. Seek support from Qvalent helpdesk . MD20 - Mandate Expired PayTo agreement is cancelled following validity expiration. Create a new PayTo agreement . MS02 - Not Specified Reason Customer Generated Reason has not been specified by payer. Contact payer . MS03 - Not Specified Reason Agent Generated Reason has not been specified by payer agent. Contact payer . NAUT - Not Authorised Permission for payment instruction to be processed is not granted. Seek support from Qvalent helpdesk . RC05 - Invalid BIC Identifier The BIC identifier is invalid or missing in the payment instruction. Seek support from Qvalent helpdesk . RR02 - Missing Debtor Name Or Address Specification of the payer's name and/or address needed for regulatory requirements is insufficient or missing in the payment instruction. Check payer details . RR03 - Missing Creditor Name Or Address Specification of the payee name and/or address needed for regulatory requirements is insufficient or missing in the payment instruction. Check payee details . RR04 - Regulatory Reason Payment instruction rejected due to a regulatory reason. Seek support from Qvalent helpdesk . RR05 - Regulatory Information Invalid Regulatory or Central Bank Reporting information in payment instruction is missing, incomplete or invalid. Seek support from Qvalent helpdesk . RR07 - Remittance Information Invalid Remittance information structure in payment instruction does not comply with rules for this payment type. Seek support from Qvalent helpdesk . SL01 - Specific Service Offered By Debtor Agent Payment instruction rejected due to specific service offered by the payer agent. Seek support from Qvalent helpdesk . SL11 - Creditor Not On Whitelist Of Debtor Whitelisting service is offered by the payer agent; in the 'whitelist', the payer lists all payees allowed to debit payer's bank accounts. Payer has not yet included the payee on their 'whitelist'. Contact payer . SL12 - Creditor On Blacklist Of Debtor Blacklisting service is offered by the payer agent; in the 'blacklist', the payer may list any payees not allowed to debit payer's bank account. Payer has included the payee on their 'blacklist'. Contact payer . SL13 - Maximum Number Of Direct Debit Transactions Exceeded Payment instruction rejected because the number of transactions requested exceeds the payer agent offering. Retry payment . SL14 - Maximum Direct Debit Transaction Amount Exceeded Payment instruction rejected because the total value of transactions requested exceeds the payer agent offering. Retry payment . TD03 - Incorrect File Structure Payment instruction structure is incorrect. Seek support from Qvalent helpdesk . TM01 - Cut Off Time Payment instruction is received after agreed processing cut-off time. Retry payment . Privacy Statement (for individuals whose personal information may be collected - in this clause referred to as "you"). All personal information we collect about you is collected, used and disclosed by us in accordance with our Privacy Statement which is available at Privacy Statement or by calling us through your relationship manager or Westpac representative. Our Privacy Statement also provides information about how you can access and correct your personal information and make a complaint. You do not have to provide us with any personal information but, if you don't, we may not be able to process an application or a request for a product or service.
📥 下载地址(文章结尾)
装机神器,可以安装一切系统。