cancel
Showing results for 
Search instead for 
Did you mean: 

I am not receiving Silent Posts for ARB transactions

I have set up a Silent Post URL on a live (production) authorize.net account and then created subscriptions using ARB integration from my web site.  I'm using the trial credit card number: 4 followed by 15 1s.  The subscriptions show up on my authorize.net account and later on they attemt to process and the transaction is declined (since it is a bogus card).  My understanding is that even though that was a declined transaction, it should still post to my Silent Post URL, but it isn't.  I've tried invoking my Silent Post URL with a test authorize.net account as well and also get no posts.  I have built a web page with a form to directly post to my Silent Post URL and that works fine.  It seems that authorize.net is not posting anything to my specified Silent Post URL.

 

Am I mistaken in thinking that using credit card 411111... will still post to my Silent Port URL as a declined transaction?

 

Or is there a problem because I'm using a secure https://..... URL for my Silent Post URL?

 

Or is there something else I need to setup to get SIlent Posts from authorize.net, like setting up an MD5 Hash?

 

Thanks

 

Oliver

 

 

ogtopramen
Member
1 ACCEPTED SOLUTION

Accepted Solutions

I fixed my problem the other day and wanted to share the solution.  The following artilce was helpful: http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Relay-Response-Basics-a...

 

One of the points it lists is that authorize.net needs a signed SSL certificate for https URLS.  My site did not have that, so I'd always get a time out.  Once I set up a signed certificte, everything worked fine.  Some users said they could use a http URL, but this did not work in my case as it just would be translated to a https URL and not work.  This issue effected both silent posts and relay responses from coming through, and once I set up the signed certificates, both of these worked just fine.

View solution in original post

6 REPLIES 6

Easiest way to test your silent post URL, it to set it up as a relay response URL and then run a SIM test on it.

RaynorC1emen7
Expert

Thanks - I'll give that a try

I tried Relay Response with SIM and I get a timeout error:


Your script timed out while we were trying to post transaction results to it.

 

My script is very simple and I can invoke it directly, again just authorize.net isn't running it.

 

I tried changing the URL from https://.... to http://.... and that makes no difference.

 

Do I need to have my URL return something in specific?

Have you try just a static page without any script.

 

There are some who report they getting the timeout when the user-agent is blank(which both the silent post and relay response use). Block on their hosting site or their firewall.

 

Or could be related to http://community.developer.authorize.net/t5/Integration-and-Testing/Relay-response-problems-after-ho...

Thanks for the suggestions.

 

I tried it with a page that just has "Done" in it.  I still get a timeout error.  This happens immediately - so its not a true timeout.

 

The link you gave refers to issues going from a test account to a production account.  I'm doing everything in a test account.

 

I also have been using an http (unsecure) URL even though I tyically use secure URLs on my site.  I had problems with secure links because we don't have signed certificates.  People have claimed that switching to http from https helps then, but perhaps that is causing my problem.

 

I just looked up some of the comments on user-agent - that could be the issue.  I'll look into that.

 

My relay response URL works fine when I post to it using a test form.

 

 

I fixed my problem the other day and wanted to share the solution.  The following artilce was helpful: http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Relay-Response-Basics-a...

 

One of the points it lists is that authorize.net needs a signed SSL certificate for https URLS.  My site did not have that, so I'd always get a time out.  Once I set up a signed certificte, everything worked fine.  Some users said they could use a http URL, but this did not work in my case as it just would be translated to a https URL and not work.  This issue effected both silent posts and relay responses from coming through, and once I set up the signed certificates, both of these worked just fine.