cancel
Showing results for 
Search instead for 
Did you mean: 

Authorize.net DPM in WooCommerce Issue...

Hi - I'm having an issue with a new site being launched.  It is initially sitting at a domain like vps.reseller.com/~example   It will launch at example.com.   I am using the latest versions of Wordpress, WooCommerce and the Woo Commerce Authorize.net DPM plugin.

 

Purchases using a coupon work perfectly, so the store is working...

 

I use a Sandbox account - not set to test mode on auth.net (as per docs).  When I purchase something:

 

   -  I lan on https://test.authorize.net/gateway/transact.dll with this message:

 

              1,1,1,This transaction has been approved.,WPP9EZ,Y,2251841562,531,Order 531,534.79

 

   - The order sits as "pending"

 

I read the docs and tried everything - but did notice the suggestion to change $post_url references a .php file that does not exist.

 

Questions:

 

    - should this work at vps.reseller.com/~example or does it need to be on the domain?

 

    - Do Sandbox transactions just end like this by default, or should they generate

      a complete processing order???

 

    - What is the issue in the docs regarding "reseller" accounts and where/what do I

      modify?

 

Thanks VERY much!

 

- Lou

 

ljudice
Member
1 ACCEPTED SOLUTION

Accepted Solutions

Hello @ljudice

 

I notice in your return URL you're using a tilde which points to a specific user directory.  We suggest you explore a better-optimized web server config that does not rely on mod_userdir while testing with our Sandbox.

 

Richard

View solution in original post

8 REPLIES 8

read about relay response

https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Relay-Response-Basics-...

 

not sure how you will set it up on woocommerce, probably go to their forum

RaynorC1emen7
Expert

Thanks very much for the suggestions...   I had actually read that post though...

 

What is odd is I am not getting an error - in fact I get an email back from auth.net saying transaction approved.

 

It just never returns to the Wordpress site to complete things....

 

The plug-in support folks have offered no help and ignore the fact that their own documentation refers to non-existent files.

 

/Lou

 

 

did you set up a default relay response url? or passing it as a param?

 

that "1,1,1,This transaction has been approved.,WPP9EZ,Y,2251841562,531,Order 531,534.79"

is the response when it doesn't know what to do. It is the AIM response

 

If the plug in don't offer any support maybe you want to get another plugin?

No, according to the documentation, nothing needs to be set on the server.

 

What stands out is this:

 

Problems with payments and reseller accounts

Some special reseller accounts require different post urls. If you account is affected, edit class-wc-authorize-net-dpm.php and change $post_url to ‘https://secure.authorize.net/gateway/transact.dll’.

 

This is a reseller account sitting at  http://vps.foo.com/~example

 

However class-wc-authorize-net-dpm.php is nowhere to be found.

 

Also the process DOES seem to get to secure.authorize.net - just can't get back..   I do not believe it is a firewall issue either....

 

Baffled...

 

/lou  (ps. thanks for your help!!!)

No idea, but that is wrong. relay response need to be either set on the server or pass as a param.

If it doesn't do either, it will do just as what you are seeing now.

 

You can read the SIM/DPM doc on relay response too.

http://www.authorize.net/content/dam/authorize/documents/SIM_guide.pdf

Hello @ljudice

 

I notice in your return URL you're using a tilde which points to a specific user directory.  We suggest you explore a better-optimized web server config that does not rely on mod_userdir while testing with our Sandbox.

 

Richard

Ah ha!!!!   That's it!

 

That is only for the pre-launch development system...

 

I am guessing a move to the domain will fix the problem as it will have no ~~~'s

 

Thanks everyone... 

 

- Lou

 

(ps.  tilde's are very common in reseller cPanel world for development sites - this should be noted in the documentation)

@ljudice

 

Good suggestion, I'll pass that on to the documentation team.

 

Richard