I have refunded the payment for this transaction là gì năm 2024

When payments are returned to an account from the recipient bank a return code is usually stated in the reference field of the return SWIFT (field 70). Please see below table for guidance on reason codes:

CodeISO definitionReason in the Rulebook or IGsType of R-trans.Exhaustive list of use-casesPossible root causeSuggested actionAC01Incorrect Account NumberAccount identifier invalid or incorrect (i.e. invalid IBAN or account number does not exist).Reject, Return

Reject: Invalid format of the IBAN; IBAN not ecisting at the Beneficiary Bank level.

Return: IBAN not existing at Beneficiary Bank level.

Beneficiary gave invalid IBAN; Originator used wrong IBAN data from its customers’ database; Originator had technical problem during the processing of the SCT instruction issuance.Originator to contact the Beneficiary to get the correct IBAN of the Beneficiary.AC03Invalid Creditor Account NumberWrong unique identifier of the Beneficiary account.RFRO.Originator has made an SCT transaction which was addressed to a wrong IBAN. Originator itself selected or entered a wrong IBAN if the beneficiary when issuing the SCT instruction. Originator: • Adapt this internal SCT instruction issuance processes to avoid the selection of a wrong IBAN in the future; • Pay more attention in selecting/ entering the IBAN when issuing a SCT instruction.AC04Closed account numberAccount closed.Return, Negative answer to a recall or to a RFRO.The account of the Beneficiary is closed at the Beneficiary Bank. Note: This code cannot be used in certain SEPA countries for reasons of data protection. MS03 could be used as an alternative. Beneficiary closed his account since the last time the Originator made a SCT instruction to his beneficiary.Originator to contract the Beneficiary for the new account. AC06Blocked accountAccount blocked.Return.Account blocked for any financial transaction. • Beneficiary Bank has blocked the account due to a Court Order; • Beneficiary Bank has blocked the account (e.g., suspicion of misuse, request from the Beneficiary).Originator to contact the Beneficiary for alternative account / solution to pay. ACNRAccepted Claim Non-ReceiptInterbank positive response to claim Non-receipt.Positive answer to SCT Inquiry "Claim Non-receipt".The Beneficiary Bank confirms to have credited the initial SCT transaction on the IBAN of the Beneficiary. It provides the Originator Bank with the date on which this SCT transaction has been credited.No root cause to be defined. Originator Bank to report back to the Originator that its SCT instruction was processed according to his/her instructions.ACVAAccepted Value Date AdjustmentInterbank positive response to Claim for Value Date Correction.Positive answer to SCT inquiry "Claim for the Value Date Correction".The Beneficiary Bank: • Accepts to correct the currently applied value date of the SCT transaction; and • Requests an interest compensation from the Originator Bank before it executes this correction.The cause for the claimed incorrect6 value date lies not with the Beneficiary Bank.Originator Bank to pay first the interest compensation to the Beneficiary Bank. AG01Transaction ForbiddenCredit transfer forbidden on this account (e.g. savings account).Return.A SCVT transaction cannot be booked on this type of account.Beneficiary gave information of an account on which SCT transactions cannot be booked.Originator to contract the Beneficiary to agree on another payment instrument. AG02Invalid Bank Operation CodeOperation code/ transaction code incorrect, invalid file format.Reject, Return.The identification code of the scheme (i.e. service level or local instrument) specified in the message is incorrect. For the specified XML file setting issues (i.e. invalid file format), please use FF01 instead. Originator: technical error or error due to the processing of the SCT transaction or the file containing SCT instructions.Originator to correct the wrong information.AM04Insufficient FundsInsufficient funds on the account.Negative answer to a Recall or to a RFRO: the Beneficiary has already transferred back the funds to the Originator (via SCT, SCT Inst or another payment means).

CommBank acknowledges the Traditional Owners of the lands across Australia as the continuing custodians of Country and Culture. We pay our respect to First Nations peoples and their Elders, past and present.

©2024 Commonwealth Bank of Australia ABN 48 123 123 124 AFSL and Australian credit licence 234945

For every payment transaction (this includes payment method authorizations, payments, void payments, and refunds), Zuora sends the transaction request to the payment gateway and the gateway replies back with a response code (for example, 110) and response message (For example, Insufficient Funds) indicating if the transaction was approved or declined. Zuora will map the approval to a payment status of "Processed" and a decline to a payment status of "Error" in Zuora Payments.

You must review your payment transactions on a regular basis for any errors that occur and follow up with either the customer, payment gateway, processor, or even card issuing bank (depending on the type of error) to address the issue. Most errors are the result of invalid payment methods, such as credit cards with insufficient funds or are expired. For invalid credit cards, we recommend following up with the customer immediately to request an alternative or updated payment method (you can automate this process using customer notifications).

On rare occasions, there may be errors with the gateway connection itself. In this case, contact the payment gateway.

Solution

Use information on the payment detail page

For failed transactions passed through your gateway, Zuora presents some important information on the payment detail page such as the gateway Response Code, Response Message, Bank Identification Number, as well as a Reference ID. These errors can be translated based on each gateway's response code definition.

In the Zuora UI, navigate to Payments > Payments and then click the payment number link in the list to open the payment detail page.

Export and use the payment transaction log

To find out more details than the information on the payment detail page, you can export the payment transaction log and use the request and response strings to analyze the transaction failure.

1. In the Zuora UI, navigate to Reporting > Data Sources.
2. In the Data Source field, select Payment Transaction Log.
3. Add fields to be exported, such as Gateway, Gateway Response Code, Gateway Response Code Description, Request String, and Response String.
4. Add filters, such as the payment number of the failed payment.
5. Click export.

The payment transaction log will be available in the file list for downloading when it is ready. If the error is returned from the payment gateway, you can send the information in Request String and Response String to the payment gateway for further investigation.

See Payment Transaction Log data source for more information about this data source.

Use gateway resources to troubleshoot errors

See the Troubleshooting Gateway Errors section in the article for each supported payment gateway for more information on how to troubleshoot gateway errors.