Support

August 12, 2019 at 8:38 am

Hello,
I need some help with Authorize.net. Apparently there are some new settings required in that we have to whitelist receipt url’s.
“Response/Receipt URLs Help
The Payment Gateway verifies the URL specified in the post string against the URLs in this list. If the URL provided does not match one of the values on this list, the transaction will be rejected. If no URL is provided, the Default URL value will be used. ”
Can you help me with what values to put here?

It requests the following info:

he Receipt Page is sent by the Payment Gateway in response to a transaction processing request. Use the settings below to configure how a customer is returned to your website from the Receipt Page. The Default Receipt Link URL, Receipt Method, and the Receipt Link Text all have to be specified.

Default Receipt Link URL
Enter a default URL to link the customer to your website from the Receipt Page. This default URL will be used in the event that a Receipt Link URL is not passed with the transaction.
URL

Receipt Method
Specify the method that should be used to render the page that the customer is linked to from the Receipt Page
Link GET POST

Receipt Link Text
Enter the text that will be displayed as a link.
Link Text

August 14, 2019 at 9:51 am

Thanks. I received an email from authorize.net regarding the urls, stating that i’d have to whitelist them or it would fail.

Regarding “accept”, i’m happy to implement, but i don’t see that option in the Event Espresso setup, is there something i need to do or some instructions you could send?

Here is the info i received from Auth.net:

Authorize.Net is enhancing security with our hosted payment form (Server Integration Method (SIM) or Direct Post Method (DPM)) with Relay Response and white listing what url(s) can be used with this integration method.
We have identified that you are using our hosted payment form (SIM or DPM) with Relay Response but you do not have a Relay Response url(s) listed in your Merchant Interface settings for white listing/approval.
On 08/15/2019 we plan on enhancing the white listing for Relay Response and will require the Relay Response url(s) or domain(s) to be listed. If it is not, the request will be rejected with Response Code 14 and this will prevent the payment form from loading successfully. This is to enhance security for both merchants and customers.
As a part of this update, we will no longer check the full url instead we will check the domain matches with any Relay Response url(s) passed in the API field x_relay_url for SIM and DPM. To assist with this update, Authorize.Net will add, to your account settings, the domains we see used on your account for the month of June 2019 to help prevent any issues.
For updates on the timing of this change please check the???Authorize.Net Status Page???for updates and subscribe there for further???email notifications.??? Updates will also be posted???in the Merchant and Partner Interface,???Support Center,???and???Developer Community.???
Ahead of time to help prevent any impact with the coming change you can review and add any Relay Response url(s) your solution/integration uses to the Merchant Interface and Relay/Receipt Urls settings. For steps on this process please see the support article: SIM Relay Response Basics & Whitelisting and How do I add or delete Relay or Response URLs?
Please contact and work with your web developer or solutions provider to verify if you are utilizing SIM or DPM with Relay Response url(s) and make sure those url(s) are listed in your Merchant Interface and Relay/Receipt Urls settings.
Thank you for your attention to this matter and for being an Authorize.Net