Information about http://www.authorize.net/files/creditreturnsummary.pdf

Issuing Credits Guide …

Tags: aim, credit card, credit transaction, credit transactions, guide details, introduction 3, merchant interface, payment gateway, sim, table of contents, terminal 3, transaction file, virtual terminal,
Pages: 6
Language: english
Created: Tue Jun 24 09:42:03 2008

Display cached document

Page 1

Page 2

Page 3

Page 4

Page 5

Page 6

Issuing Credits Guide
Issuing Credits Guide
Page 2 of 6

Table of Contents
ISSUING CREDITS GUIDE .........................................................................................................1

TABLE OF CONTENTS ...............................................................................................................2

INTRODUCTION ..........................................................................................................................3

ISSUING CREDITS USING THE VIRTUAL TERMINAL .....................................................3

ISSUING CREDITS VIA UPLOAD TRANSACTION FILE ....................................................4
Configure Batch Upload to Issue Credits ........................................................................ 5

ISSUING CREDITS USING AIM AND SIM ..............................................................................5

Last revised 6/24/2008
� 2008 Authorize.Net, a CyberSource solution
Issuing Credits Guide
Page 3 of 6

Introduction
This guide details the field requirements and conditions for submitting Credit transactions to the
Payment Gateway. A Credit transaction is submitted only against an original credit card or
eCheck.Net transaction that has already been settled on the Payment Gateway. For a Credit
transaction, funds flow back from the merchant's bank account to credit, or refund, the
customer's credit card or bank account. The following sections describe how to submit credits via
the following methods:

� Using the Virtual Terminal in the Merchant Interface
� Using the Upload Transaction File feature in the Merchant Interface
� Via your Web site integration to the Payment Gateway

Issuing Credits Using the Virtual Terminal
To successfully submit a Credit transaction to the Payment Gateway via the Virtual Terminal, the
following conditions apply:

� Credits must include the Transaction ID of the original transaction the credit is being
issued against. Transaction IDs can be located by viewing the transaction details or by
downloading the transaction.
� Credits require the full or last four digits of the credit card number; or for eCheck.Net
Credits, the bank account number and ABA routing number (accepted formats are: the
full number with no spaces; the last four digits only; or the masked number, like
XXXX4455).
� Credits can only be issued within 120 days of the date and time the original transaction
successfully settled on the Payment Gateway. ALL Credits submitted after the 120-day
period will be rejected.
� Credits cannot be submitted against transactions that failed, were declined, or were
submitted as Authorization-Only transactions.
� The sum total of the credits issued cannot exceed the amount of the original transaction.

Credits are processed at settlement time with all other transactions.

To issue a credit using the Virtual Terminal:

1. Log into the Merchant Interface.
2. Click Virtual Terminal in the Main Menu.
3. From among the choices displayed in the category Select Payment Method, select
Refund a Credit Card or Refund a Bank Account.
4. Provide payment and customer information as required on the Virtual Terminal screen.
5. Provide the Customer's Credit Card/Bank Account Information.

Note: Below are examples of accepted and unaccepted formats for credit card, bank
account, and ABA routing numbers when issuing a Credit.

Last revised 6/24/2008
� 2008 Authorize.Net, a CyberSource solution
Issuing Credits Guide
Page 4 of 6

Accepted Formats (full, masked or unmasked number):
Credit Card Number Bank Account Number ABA Routing Number
4100000000895612 100023 011000090
XXXX5612 XXXX0032 XXXX0090
5612 0023 0090

Note that the masked number includes four Xs, regardless of the actual full
length of the information. So, for example, a six-digit bank account number (see
the example in the table above) would still display like XXXX0032.

Unaccepted Formats (any more than four numbers but less than the full
number):
Credit Card Number Bank Account Number ABA Routing Number
895612 00023 1000090
95612 000090

Note: Expiration Dates are not required for refunding a credit card. However, if an
expiration date is provided, it should be entered in the format of MMYY. For
example, an expiration date of July 2005 should be entered as 0705.

6. Enter any additional information in the remaining fields, such as Order Information or
Customer Billing Information. These fields are optional.
7. To submit the credit, scroll down to the bottom of the page and click Submit.

Issuing Credits via Upload Transaction File
To successfully submit a Credit transaction to the Payment Gateway via Upload Transaction File,
the following conditions apply:

Credits are processed at settlement time with all other transactions.

Last revised 6/24/2008
� 2008 Authorize.Net, a CyberSource solution
Issuing Credits Guide
Page 5 of 6

Note: See below for examples of accepted and unaccepted formats for credit card, bank
account, and ABA routing numbers when issuing a Credit.

Accepted Formats (full, masked or unmasked number):
Credit Card Number Bank Account Number ABA Routing Number
4100000000895612 100023 011000090
XXXX5612 XXXX0032 XXXX0090
5612 0023 0090

Note that the masked number includes four Xs, regardless of the actual full length of the
information. So, for example, a six-digit bank account number (see the example in the
table above) would still display like XXXX0032.

Unaccepted Formats (any more than four numbers but less than the full number):
Credit Card Number Bank Account Number ABA Routing Number
895612 00023 1000090
95612 000090

Note: Expiration Dates are not required for refunding a credit card. However, if an expiration
date is provided, it should be entered in the format of MMYY. For example, an expiration
date of July 2005 should be entered as 0705.

Configure Batch Upload to Issue Credits
To configure Transaction Batch Upload Settings to issue credits, perform the following:

1. Log into the Merchant Interface.
2. Click Settings.
3. Select Upload Transaction Files.
4. Select or verify that the Transaction ID field is included as part of the batch upload file.
5. Click Submit.

Remember: The original transaction ID must be included when uploading a batch containing
credits.

Note: For more information on how to upload a batch, click the Help link located on the Batch
Upload screen of the Merchant Interface.

Issuing Credits Using AIM and SIM
To successfully submit a Credit transaction to the Payment Gateway via Advanced Integration
Method (AIM) and Simple Integration Method (SIM), the following conditions apply:

Last revised 6/24/2008
� 2008 Authorize.Net, a CyberSource solution
Issuing Credits Guide
Page 6 of 6

The form field that should be used to pass the Transaction ID is x_trans_id. Because
credit transactions issued outside of the Virtual Terminal require the use of a transaction
key (with the corresponding field, x_tran_key) you must remember to only issue the
credit, and consequently send your transaction key, from within a secure environment.

Note: For SIM, credit transactions also require the unique transaction fingerprint.
However, if you use SIM, the recommended way to submit credits is via the
Virtual Terminal or Upload Transaction File features of the Merchant Interface.

� Credits require the full or last four digits of the credit card number; or for eCheck.Net
Credits, the bank account number and ABA routing number (accepted formats are: the
full number with no spaces; the last four digits only; or the masked number, like
XXXX4455).
� Credits can only be issued within 120 days of the date and time the original transaction
successfully settled on the Payment Gateway. ALL Credits submitted after the 120-day
period will be rejected.
� Credits cannot be submitted against transactions that failed, were declined, or were
submitted as Authorization-Only transactions.
� The sum total of the credits issued cannot exceed the amount of the original transaction.

Credits are processed at settlement time with all other transactions.

Note: See below for examples of accepted and unaccepted formats for submitting credit card,
bank account, and ABA routing numbers when issuing a Credit.

Accepted Formats (full, masked or unmasked number):
Credit Card Number Bank Account Number ABA Routing Number
4100000000895612 100023 011000090
XXXX5612 XXXX0032 XXXX0090
5612 0023 0090

Note that the masked number includes four Xs, regardless of the actual full length of the
information. So, for example, a six-digit bank account number (see the example in the
table above) would still display like XXXX0032.

Unaccepted Formats (any more than four numbers but less than the full number):
Credit Card Number Bank Account Number ABA Routing Number
895612 00023 1000090
95612 000090

Note: Expiration Dates are not required for refunding a credit card. However, if an expiration
date is provided, it should be entered in the format of MMYY. For example, an expiration
date of July 2005 should be entered as 0705.

For more information on transaction types and form field requirements, please see the
Implementation Guides located in the Documentation and References section of the Help Menu
in the Merchant Interface.

Last revised 6/24/2008
� 2008 Authorize.Net, a CyberSource solution