One-Page Checkout [Support Thread]

[EZorb]

That was the problem, after setting ($collectsCardDataOnsite = false;) back to TRUE; It will process credit cards.
Is this only happening with (AIM)?

Now I need to come up with some way to eliminate "by Clicking the Submit Order Button
you agree to our shipping & returns policies.........." when the "Continue Checkout" button is showing for Review.

After clicking the Review button (Continue Checkout) and Submit Order button is showing again & "by Clicking the Submit Order Button
you agree to our shipping & returns policies.........." as it should.

What would it take to blank out the message when the Review button is displayed?

Yes, the second part of the message is from the AIM module's generic decline secondary message.

So, the currency failure message comes from Authorize.net. You'll need to sort that out with them. Zen Cart won't be displaying that message if it didn't come from Authnet's servers as their response to your attempted transaction.

[lat9]

That was the problem, after setting ($collectsCardDataOnsite = false;) back to TRUE; It will process credit cards.
Is this only happening with (AIM)?

Now I need to come up with some way to eliminate "by Clicking the Submit Order Button
you agree to our shipping & returns policies.........." when the "Continue Checkout" button is showing for Review.

After clicking the Review button (Continue Checkout) and Submit Order button is showing again & "by Clicking the Submit Order Button
you agree to our shipping & returns policies.........." as it should.

What would it take to blank out the message when the Review button is displayed?

As shipped with Zen Cart, the Authorize.net/AIM and PayPal Payments Pro both collect-credit-card-data-onsite.

I've looked through the default OPC language files and the text you identify isn't there. You've apparently got a template-override version of the files. If you identify the language "definition" that you've found, I can help.

[EZorb]

@ lat9 & Dr Byte

I just got off the phone with Authorized.net (A.net) (see Dr Byte remark on post567) explaining to them what was happening using OPC with A.net (AIM). A person with A.net programming department informed me that they do not have any requirement on having a Review Page.

So why is this code being brought into A.net Payment page? Who is making this a requirement? I noticed when OPC is set to false that on the 3 step checkout this Review page does not happen. Must be more to this than being discussed.

A.net said when( (includes/modules/payment/authorizenet_aim.php about line 74 and $collectsCardDataOnsite = TRUE;)) this is set to FALSE; this does prevent the Review Page button from POP-UP but sending the transaction is still attempted to A.net without a proper code for currency or exchange rate causing A.net to reject attempted transition and attaching the first part of the error message. (The supplied currency code is either invalid, not supported, not allowed for this merchant or doesn't have an exchange rate. -)

Next zencart A.net Payment module attaches the 2nd part of the error message. (Your credit card could not be authorized for this reason. Please correct the information and try again or contact us for further assistance.)

At least 95% of my customers use Credit Cards subjecting them to a confusing message about submitting their order then pop's up a Continue Shopping button and next a Review Page with a Submit Order button again. It would seem A.net users would be better off just using the normal 3 step checkout.

Due to the potential confusion this causes customers and not being an A,net requirement could you please consider removing this part of OPC coding so all A.net (AIM) users customers could enjoy a real OPC experience?

Thank you,
Larry

As shipped with Zen Cart, the Authorize.net/AIM and PayPal Payments Pro both collect-credit-card-data-onsite.

I've looked through the default OPC language files and the text you identify isn't there. You've apparently got a template-override version of the files. If you identify the language "definition" that you've found, I can help.

[DrByte]

Larry, you make it sound like it's simple. It's not. OPC is trying to change a lot of other architecture that has specific business and security reasons for being the way it is.

Until a way is found to make OPC accommodate the way the AIM checkout is done, you'll have to temporarily live with the "popup"/review stage.
Or use something other than AIM, such as Square, if it works in your country.

Lat9 is working hard to accommodate the complexities of exactly what you're asking for. The "true OPC experience" you mentioned IS INDEED her goal. But please tighten your patience hat until the technical glitches are sorted out.

[EZorb]

Larry, you make it sound like it's simple. It's not. OPC is trying to change a lot of other architecture that has specific business and security reasons for being the way it is.

Until a way is found to make OPC accommodate the way the AIM checkout is done, you'll have to temporarily live with the "popup"/review stage.
Or use something other than AIM, such as Square, if it works in your country.

Lat9 is working hard to accommodate the complexities of exactly what you're asking for. The "true OPC experience" you mentioned IS INDEED her goal. But please tighten your patience hat until the technical glitches are sorted out.

I got the impression out here in West Texas OPC was going to be left the way it was because some goverment person sitting in an office thinks a review page is needed. Now that you have informed me on what is going on I can plan around the problem. I know the shopping cart checkout part is extremely complicated & complex due to so many different variables going on at same time plus the security issues. I did not mean to give the empression I was being pushey. I am very very impressed with lat9 OPC, works better than any other so called opc that I have seen absolutely brilliant.

Seems like I am breaking all of her mods EMC. hope she does not get mad at me.

Thanks for letting me know whats is going on.

Larry

[lat9]

... Seems like I am breaking all of her mods EMC. hope she does not get mad at me. ...

No getting mad here! I appreciate the heads-up when stuff "doesn't work".

I've made a modification to the default language text for the "email confirmation sent to" line, making it more generic:

A confirmation of this order will be emailed to <b>%s</b>.

where the %s value contains the associated email address.

I've also got 1.4.0-beta2 available on my website if anyone wants to see/test what's coming. That version includes the above language-text change as well as removing the requirement that payment-methods that "collect-card-data-onsite" must go through the review page. Those payment methods are now treated like any other payment method; if you want a confirmation page, you'll need to add the payment-method 'names' to the OPC's "Requires Confirmation" list.

I'll be poking around a bit more, having validated with authorize.net/AIM, BrainTree, PayPal Express Checkout and Square ... and all looks good so far.

[EZorb]

I must be blind can't find 1.4.0-beta2 on your website.

No getting mad here! I appreciate the heads-up when stuff "doesn't work".

I've made a modification to the default language text for the "email confirmation sent to" line, making it more generic:

A confirmation of this order will be emailed to <b>%s</b>.

where the %s value contains the associated email address.

I've also got 1.4.0-beta2 available on my website if anyone wants to see/test what's coming. That version includes the above language-text change as well as removing the requirement that payment-methods that "collect-card-data-onsite" must go through the review page. Those payment methods are now treated like any other payment method; if you want a confirmation page, you'll need to add the payment-method 'names' to the OPC's "Requires Confirmation" list.

I'll be poking around a bit more, having validated with authorize.net/AIM, BrainTree, PayPal Express Checkout and Square ... and all looks good so far.