Integration Note

The Advanced Integration Method (AIM), Server Integration Method (SIM), and Direct Post Method (DPM) are now obsolete and in the process of being phased out. We strongly suggest using one of our modern connection methods to integrate with the Authorize.net Payment Gateway. Visit our Developer Center and Upgrade Guide for more information on our updated APIs.

What is Relay Response?

Relay Response is a feature used by merchants utilizing the Server Integration Method (SIM) or Simple Checkout. It instructs the Authorize.net payment gateway to return transaction results to the merchant through an HTML form POST to a specified URL on the merchant's web server. A script or program at this URL can then create a custom receipt page using the transaction information. This custom receipt page is relayed back to the customer's browser. It's important to note that Relay Response does not redirect the end user back to your server. Instead, it relays your specified Relay URL to the end user through our receipt page, replacing our default receipt page.

Any Response/Receipt URLs submitted with a transaction request must exist in the Response/Receipt URLs list in the Merchant Interface, otherwise, the transaction will be rejected. If no URL is submitted, the Default Receipt or Default Relay Response URL configured in the Merchant Interface will be used. Keep in mind that Response/Receipt URLs should only be used in conjunction with SIM or Simple Checkout.

How to Add/Edit the default URL for Relay Response?

1. Sign in to the Merchant Interface.
2. Be on or switched into the New Merchant Interface (2.0)
3. Click on Payments in the left navigation.
4. Click on Payment Settings
5. Then click Transaction Response Urls
6. Next click on Relay Response
7. Add/Edit the default Relay Response Url.
8. In the URL text field, enter the URL where the payment gateway should send the transaction response. This URL must start with either "http://" or "https://". Parameterized URLs are not permitted.
9. To add additional url click on Configure additional receipt link url values.
10. Click Save.

Edit Note: When editing/changing the url this will not delete it but move the previous value to be in the additional url list.

How to Add/Edit the default URL for Receipt Page?

1. Sign in to the Merchant Interface.
2. Be on or switched into the New Merchant Interface (2.0)
3. Click on Payments in the left navigation.
4. Click on Payment Settings
5. Then click Receipt Page
6. Next click on Receipt Method
7. Add/Edit the default Receipt Link Url.
8. In the URL text field, enter the URL where the payment gateway should send the transaction response. This URL must start with either "http://" or "https://". Parameterized URLs are not permitted.
9. Select the Receipt Method you would like to use. The Receipt Method refers to the manner in which you would like transaction information to be passed back to your website when the customer clicks the default receipt link. The options are:
   • LINK – This method does not return any transaction information.
   • GET – This method returns order information in the HTTP header of the Web page targeted by the Default Receipt URL.
   • POST – This method returns information like an HTML form, with hidden fields containing the transaction information.
10. Enter any custom text you would like to use for the link back to your website.
11. To add additional url click on Configure additional receipt link url values.
12. Click Save.

Edit Note: When editing/changing the url this will not delete it but move the previous value to be in the additional url list.

This setting may depend on how your website is integrated with the payment gateway. Please consult with your Web developer or the person that integrated your website before changing these settings.

How to view and manage urls for Relay and Receipt?

1. Sign in to the Merchant Interface.
2. Be on or switched into the New Merchant Interface (2.0)
3. Click on Payments in the left navigation.
4. Click on Payment Settings
5. Then click Transaction Response Urls
6. Next click on Response/Receipt URLs
7. You will now see a list of the urls including defaults set for your account.
8. Additional urls can be deleted by clicking Delete under the action.
   1. A confirmation message will come up, click Delete to confirm the removal.
9. Additional urls can be added by clicking Add Url.
10. If you update an existing default Url, the Url is not deleted, but is moved to be an additional url. If you would like to remove the URL from the list, click Delete.

Relay Response Codes and Values

The following name/value pairs are among those Relay Response can send to the merchant website:

• x_response_code -- Indicates the result of the transaction:
  • 1 = Approved
  • 2 = Declined
  • 3 = Error
• x_response_reason_code -- Provides more details about the result of the transaction, including the nature of any error. For a complete list of these codes, please see the Response Code Details topic in the SIM Implementation Guide.
• x_auth_code -- The six-digit alphanumeric authorization or approval code.
• x_avs_code -- The result of Address Verification Service (AVS) checks:
  • A = Address (Street) matches, ZIP does not
  • B = Address information not provided for AVS check
  • E = AVS error
  • G = Non-U.S. Card Issuing Bank
  • N = No Match on Address (Street) or ZIP
  • P = AVS not applicable for this transaction
  • R = Retry – System unavailable or timed out
  • S = Service not supported by issuer
  • U = Address information is unavailable
  • W = Nine digit ZIP matches, Address (Street) does not
  • X = Address (Street) and nine digit ZIP match
  • Y = Address (Street) and five digit ZIP match
  • Z = Five digit ZIP matches, Address (Street) does not

Relay Response Allow List

With Relay Response, the URL used needs to be listed in your Merchant Interface and registered on your account. If a match is not found when sending a relay URL via SIM or DPM API (x_relay_url), a response code of 14 - The referrer, relay response or receipt link URL is invalid, will be returned.

Current scenarios for response code 14:

• x_relay_url sent via API – No relay Url registered in the Merchant Interface
  • Response code 14 returned
• x_relay_url sent via API - Relay URL registered but not matching
  • Response code 14 returned
• x_relay_url sent via API - Relay URL registered and matching in the Merchant Interface
  • No error, hosted payment form loads successfully

URL Matching Logic:

• Will allow registering just the domain if many relay URLs are used but on the same domain.