The method of transferring transaction results to the merchant's site so that it can take action based upon the result and display an appropriate message to the customer.
If you choose to use relay response, your receipt generating script must be able to parse the results of the transaction and print the response to the screen. With relay response, you have more options for using the transaction response, including updating a database, writing to log files, sending customer receipt e-mails, etc.
There are no plans to introduce breaking changes into the JSON request/response. We are only marking it as beta in the chance that we are forced to make a breaking change in order to address a bug or unexpected behavior.
Please contact us so we can add name to a list of contacts and let you know if we are introducing any potentially breaking changes, but we would not recommend using it for a production system if you are not prepared to maintain it in the case of those changes being required.
· Both opaque params must be specified
· Cannot include with card number or expiration date
· Cannot include track data
· Must be ecommerce transaction, please make sure your gateway is setup as CNP (card Not Present)
· Must be auth or authcapture type of transaction
· Cannot include 3DS data
· Must be data that can be successfully decrypted
· Decrypted data must belong to the merchant submitting the request
· The submitted data must be base 64 encoded
An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card. This transaction cannot be accepted.
An error occurred while trying to report this transaction to the merchant.An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.
This transaction has been approved.
It is advisable for you to contact the merchant to verifythat you all will receive the product or service.
This error indicates that Authorize.Net is unable to connect to the page that you have specified as your relay response url. This error is commonly encountered during development if you are using an internal test environment that is not publicly accessible. In order for relay response to function, Authorize.Net must be able to load your site. Relay response will work with http or https provided you have a valid SSL certificate.
We also recommend triple checking the URL within your code making sure it is the correct one and same one specified in your Authorize.Net settings page.
This is applicable when using our XML or SOAP APIs. This error indicates only invalid credentials. If you have confirmed that your API login ID and transaction key are accurate, you may need to confirm that you are submitting to the correct URL. If you are using a test account, please make sure to post to the sandbox URL and vice versa.