Overview

The Upload Transaction File feature in Authorize.net supports the submission of refund (credit) transactions to the payment gateway via batch upload. This article outlines the conditions that must be met before submitting a credit, the minimum required fields, and how to configure your Transaction Batch Upload settings to include the necessary data.

This article applies to merchants using Authorize.net who need to submit credit transactions through the Upload Transaction File feature. Use this article when you need to issue a refund against a previously settled transaction using a batch upload file.

This article does not apply to credit transactions submitted through methods outside of the Upload Transaction File feature in the Authorize.net Merchant Interface.

For a full overview of Batch Upload configuration and usage, see: What is Batch Upload and how to use and configure it? - Classic Experience (1.0)

Conditions for Submitting Credit Transactions

Before submitting a credit transaction via the Upload Transaction File feature, ensure all of the following conditions are met:

• Include the Transaction ID of the original transaction. You can locate Transaction IDs in the transaction details or by downloading the transaction history.
• Provide the full or last four digits of the credit card number. For eCheck.Net (Electronic Check) credits, provide the bank account number and American Bankers Association (ABA) routing number. Accepted formats are:
  • The full number with no spaces
  • The last four digits only
  • The masked number (for example, XXXX4455)
• Submit credits within 180 days of the original transaction's successful settlement on the payment gateway. The gateway will reject all credits submitted after the 180-day period.
• Do not submit credits against transactions that failed, were declined, or were submitted as Authorization-Only (AO) transactions. Credits cannot be issued against these transaction types.
• Ensure the total sum of credits does not exceed the amount of the original transaction.

Minimum Requirements for Uploading Credits

Each credit transaction submitted via batch upload must include the following minimum fields:

• Original Transaction ID
• Credit card number or eCheck bank account number and ABA routing number
• Dollar amount
• Transaction type (Credit)

Configuring Transaction Batch Upload Settings to Issue Credits

Configure your Transaction Batch Upload settings to ensure the Transaction ID field is included in your batch upload file before submitting credit transactions.

1. Sign in to the Merchant Interface.
2. Click Account from the main toolbar.
3. Select Upload Transaction File Format.
4. Select or verify that the Transaction ID field is included as part of the batch upload file.
5. Click Submit.

Frequently Asked Questions

• • What information is required to submit a credit transaction via Batch Upload?
  • Each credit transaction must include the original Transaction ID, the full or last four digits of the credit card number (or bank account number and ABA routing number for eCheck.Net transactions), the dollar amount, and the transaction type set to Credit.
• • Where can the Transaction ID for the original transaction be found?
  • Transaction IDs can be located in the transaction details within the Merchant Interface or by downloading the transaction history.
• • What credit card number formats are accepted for credit transactions?
  • Accepted formats include the full card number with no spaces, the last four digits only, or the masked number (for example, XXXX4455).
• • How long is there to issue a credit against an original transaction?
  • Credits can only be issued within 180 days of the date and time the original transaction successfully settled on the payment gateway. Credits submitted after the 180-day period will be rejected.
• • Can a credit be issued against a declined or failed transaction?
  • No. Credits cannot be submitted against transactions that failed, were declined, or were submitted as Authorization-Only transactions.
• • Is there a limit on the total amount that can be credited against an original transaction?
  • Yes. The total sum of all credits issued against an original transaction cannot exceed the amount of that original transaction.
• • What settings need to be configured before submitting credit transactions via Batch Upload?
  • Verify that the Transaction ID field is included in the Upload Transaction File Format settings. Navigate to Account in the main toolbar, select Upload Transaction File Format, confirm the Transaction ID field is selected, and click Submit.
• • What information is required for eCheck.Net credit transactions?
  • For eCheck.Net credits, provide the bank account number and ABA routing number in place of the credit card number.

Additional Resources

• What is Batch Upload and how to use and configure it? - Classic Experience (1.0)

Glossary

• ABA Routing Number (American Bankers Association Routing Number) — A nine-digit number that identifies a financial institution in the United States, used for eCheck transactions.
• ACH (Automated Clearing House) — A network used for electronic financial transactions in the United States, including eCheck payments.
• AO (Authorization-Only) — A transaction type that authorizes a charge but does not submit it for settlement. Credits cannot be issued against AO transactions.
• ABA (American Bankers Association) — The organization that issues routing numbers used to identify financial institutions in the United States.
• CSV (Comma-Separated Values) — A plain text file format that uses commas to separate data fields, commonly used for spreadsheet and database data.
• eCheck.Net — Authorize.net's electronic check processing solution, which enables merchants to accept ACH payments directly from customers' bank accounts.
• Transaction ID — A unique identifier assigned by the payment gateway to each transaction. Required when submitting credit transactions via Batch Upload.
• TXT — A plain text file format with no special encoding, supported for batch upload files.
• XSS (Cross-Site Scripting) — A type of security vulnerability where malicious scripts are injected into web content. XSS content is prohibited in batch upload files.
• SQLi (Structured Query Language Injection) — A type of cyberattack that inserts malicious SQL code into a query to manipulate a database. Characters such as < and > are associated with this attack type and are prohibited in batch upload files.