- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DPM and HTTPS relay
Based on the documentation for DPM, it appears there is no issue with using an HTTPS address in "x_relay_url." I have DPM up and running with HTTP. When I switch my site over to HTTPS, which changes to the relay address to HTTPS, the relay does not compelete.
Any ideas where I could have gone wronog?
โ04-23-2012 11:39 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you have a valid SSL Certificates?
Can you access the https URL from outside of your network without getting any error?
Did you change the valid relay response URL in your merchant account setting?
โ04-23-2012 11:56 AM - edited โ04-23-2012 12:06 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yep, SSL is valid (or at least Firefox recognizes the certificate as valid). I'm not really sure how to confirm that Authroize.net regonizes the certificate as valid.
I can access the HTTPS relay url from outside of the network without issue.
I have not set the valid relay response URL. The instructions did indicate that this was required, however, it was working just fine with HTTP without a relay repsonse URL.
I'm currently encoding some transaction information in the GET parameters of the relay url. I assume this won't work once I set the relay response URL. Is there some way I can encode custom field information in the POST relay response?
โ04-23-2012 12:06 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have not set the valid relay response URL. The instructions did indicate that this was required, however, it was working just fine with HTTP without a relay repsonse URL.
I'm getting (14) The referrer, relay response or receipt link URL is invalid. If I didn't set the relay response URL as one of the valid URL.
Do you mean you didn't pass a "x_relay_url" on the form post? It mean you are using the default on your merchant account setting.
You can set merchant defined fields on the form post to https://???.authorize.net/gateway/transact.dll
http://developer.authorize.net/guides/SIM/Submitting_Transactions/Merchant-defined_Fields.htm
โ04-23-2012 12:21 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, no I set "x_relay_url" in my form post. I did not set the "Default Relay Response URL" in my account settings.
โ04-23-2012 12:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And you didn't get the "(14) The referrer, relay response or receipt link URL is invalid" error?
Are you getting any error at all? Or it is just return a blank page?
โ04-23-2012 01:01 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I get the following message
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.
โ04-23-2012 07:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Relay Response Basics and Troubleshooting pretty much summarized all the common problem.
If all you did is change it from HTTP to HTTPs and nothing else, not sure what else to test.
Can you tell if it even make it to your relay URL page?
โ04-24-2012 04:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It isn't making it back to my relay URL page. That's what I can't figure out. It makes it back just fine when my relay url is HTTP. As soon as I change it to HTTPS the relay fails.
โ04-24-2012 11:10 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Maybe it didn't like your SSL Certificates. Who the provider? and what type. could be the same problem as
โ04-24-2012 12:27 PM

