Reply
Highlighted
Member
Posts: 2
Registered: ‎05-06-2014

dpm not redirect to my x-relay-url

Hi,

I'm trying out the 15 min php based dpm tutorial, and could not figure out how to make it works after 24 hours:) here is what I did:

1. download the sdk and set up a basic form, i was able to see the sample payment page.

2. in the sandbox account, I set up the two urls: Default receipt url, Default relay response url, all to :

https://<my_public_ip>/dpm_response

3. in the php post form, x-relay-url is set to the same url as #2

4. click 'buy' and got following:

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 verify that you will receive the product or service.

but my server at this url (https://<my_public_ip>/dpm_response) never got any post, why?

thanks,

Angelo

Highlighted
Member
Posts: 2
Registered: ‎05-06-2014

Re: dpm not redirect to my x-relay-url

somehow found a solution, if the relay-url is in my laptop, got a timeout, putting it up in production server, relay-url got called.

is it because of the speed? sure not because of firewall, I was able to do a post from outside into my relay-url in my laptop. 

or is there a way to adjust the time out value of authorize.net? thanks

 

Highlighted
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: dpm not redirect to my x-relay-url

it your laptop have a public acessiable url?

From Relay Response Basics and Troubleshooting

If the merchant’s Web server is not available on the public Internet, has authentication enabled, or if the Relay URL uses a non-standard port for HTTP or HTTPS traffic, Relay Response timeouts will occur. Authorize.Net will not have any means to connect to your server or authenticate itself on your server, and can only use ports 80 and 443 for all Web traffic.