I need to use Authorize.net SIM so I can avoid a bunch of difficult PCI requirements. I had it working on my old store for years. Now, I have built a new store with osCmax 2.5.4
So, I set up the SIM module, and it gets the customer to their page to enter the credit card #, but when they click "pay now" it POSTs back to my store WITHOUT an osCid. I'm thinking that is the problem. Here's a log of that POST :
198.241.206.38 - - [24/Jan/2018:12:37:46 -0600] "POST /osc2.5/catalog/checkout_process.php HTTP/1.1" 302 384 "-" "-"
I have authorize.net set to refer the receipt back to /osc2.5/catalog/checkout_process.php with a POST operation, which is how it was set for the old store. Is this still the correct URL to refer back when the CC processing is complete? (Because of the way Authorize.net's SIM works, it can't be tested behind a firewall with NAT.)
The code in the SIM module that seems to be responsible for sending the receipt link is now :
tep_draw_hidden_field('x_relay_response', 'TRUE') .
tep_draw_hidden_field('x_receipt_link_url', tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', false)) .
Although the stock module was this :
tep_draw_hidden_field('x_relay_response', 'TRUE') .
tep_draw_hidden_field('x_relay_url', tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', false)) .
Neither of these seems to make any difference. Does FILENAME_CHECKOUT_PROCESS have a proper value? It certainly doesn't occur anywhere else in the module.
What the customer sees is immediately after clicking "pay now" on authorize.net, they are back at my store's new customer login page. Authorize.net DOES charge the customer's card correctly, and email a receipt to them.
Thanks for any help with this. I have now gone LIVE with this store, so it is a fairly urgent issue!
Jon
Bookmarks