Credit Card Validation

[bobr2k]

So here's a question... would you rather it always redirect to the pay order screen if there is a balance and no pending payments?

That would be my vote! The customer knows there's a problem and can fix it.

[AbleMods]

So here's a question... would you rather it always redirect to the pay order screen if there is a balance and no pending payments?

I would say yes.

But can it be a popup "This order has a balance, pay now?" with a 'yes' response doing a redirect to the payment page you've designed. This would be elegant for a variety of reasons - that Pay Order button isn't exactly "obvious" sitting way on the right side of the screen.

[Logan Rhodehamel]

Draft 1 of this update is complete.

* I didn't make it automatically redirect. Instead at the top it shows a more prominent balance due message with a link to the payment. Probably this should be an option on the control... AutoRedirect true/false. This is only the case for orders that have a valid payment and then have an additional balance due - like when you add an item to the order.

* I didn't make a popup. I tried it out, but I could not make it work the way it should. The javascript popup was ugly and I can't make it appear at the right time. So we'd probably want a CSS powered popup, but I don't have time to sort that our right now.

I passed the patch on for review. It consists of updates to four ConLib controls, six payment forms, and one app_code file.

[WylieE]

So here's a question... would you rather it always redirect to the pay order screen if there is a balance and no pending payments?

That would be my vote! The customer knows there's a problem and can fix it.

I would agree. Let the customer know there is a problem and give them a chance to resolve it.

We're trying to eliminate as much billing at time of shipping as possible. If the customer can pay for additions at the time the addition is made, it would be great.

Thanks so much Logan.

[Logan Rhodehamel]

We have done initial tests on this code and it does as described throughout the thread. I am making the patch available now. If you consider yourself an "advanced" user and you want to pursue this customization, have at it. Consider it a beta - if you install these files make a backup of your existing files FIRST.

ftp://ftp.ablecommerce.com/patches/Card ... nPatch.zip

From the readme inside:

The files in this patch make adjustments to the checkout flow. If the payment processor cannot authorize payment, the customer will not see the standard receipt page. Instead they will see the pay order page with an explanation of what went wrong.

This includes an updated pay order page, which also improves the experience when a balance becomes due on a previously paid order (for example if something is added to the order).

This is intended to be used on the RC3 build 9381. Future builds will include this modification by default. This patch is untested on the RC2 build and not guaranteed to work for that version.

[Logan Rhodehamel]

Has anyone implemented the patch? It seemed like there was a lot of interest, but I haven't heard anything since it was posted.

[bobr2k]

Has anyone implemented the patch?

I've implemented it but store owners are still tweaking their products and getting gateway licenses so I can't really test it yet.

[AbleMods]

I'm waiting to hear some results from others.

I don't know about anybody else, but modifying my entire checkout process into an unsupported state isn't really doing me alot of favors. That just sets me up for bigger problems down the road when something else related to checkout doesn't work and I can't get help fixing it.

[Shopping Cart Admin]

Hello Joe,

Once this is fully tested it will be a 'supported' change.

[Logan Rhodehamel]

Perhaps I should have placed the download in the "evals" folder instead. This change will be incorporated into any future release. And it has been tested, but only by me. That's not enough for something to be marked official. If it has some problem, you would not be without support.

[bhill]

Logan, Thanks for the solution it is exactly what we need. I've installed the patch and testing on it now. We hope to go live with AC7 this week. I'll post on how the modification works out over the next few weeks, we receive up to 50 orders a day so this was a big deal. Good work, thanks again!

[bobr2k]

I'll post on how the modification works out over the next few weeks,

we're about to go live (finally) ... bhill do you have anything to add after your experiences of the past couple weeks?

[batmike]

I put this up on our site and after my quick testing of my own card, it seemed to work great. I did change the wording of the error message as I think some customers would get confused by the bank message (which is shown at the bottom of the page, if they're interested) and just told them to double-check their card and re-enter it. I also noticed that the "checkoutAlert" class is not in the stylesheet, so I added that in to make the text stand out more.

Great update though, we've gotten maybe about 5% of our orders with some authorization problem, so if we can cut a few off with this method, that would be very nice.

Thanks, Logan!

Mike

***edit***
After some more testing, I realized that the CSS thing I mentioned above was just a typo on my part. I did change it to display in red, but under a new class, so it wouldn't mess up my normal checkout page.

I do have a question. Potentially, an error could be caused by an address mismatch, though there's no way to change that on the new page. This would be fine, especially if they choose to use a new card, unless that new card needed a work address, etc. in which case maybe a radio button or something to mark that the card is different and then have an ajax form come up to enter a new billing address.

Just a thought for future updates.

Thanks,
Mike

***edit***

[bobr2k]

Background: test gateway is in place, I created an order, the order went thru as Authorized although I entered an invalid verification code. Acting as a customer, I could not see a way to correct the order or know the reason the order was still in a pending status.

questions to be resolved (any comments welcome) ...
1. when the gateway is "live" will the patch allow the customer to correct the verification code, enter the correct credit card number (if it was entered incorrectly), etc.
2. I cancelled the order (as admin) and marked the reason "private" - as a result there was no email to "the customer" notifying the order had been cancelled. If the order is not marked private, is there a way to use the "status of order" to notify the customer to get back in and correct their order or is that something the store owner has to do? (does the admin user have that capability based on the patch, etc.?)

I plan to update this note over the next couple days but am hoping someone who is using the patch and has been "live" for a while has answers so I don't have to find out the hard way, by getting charges going thru, etc.

Thanks for any help, tips, etc.

[Logan Rhodehamel]

Background: test gateway is in place, I created an order, the order went thru as Authorized although I entered an invalid verification code. Acting as a customer, I could not see a way to correct the order or know the reason the order was still in a pending status.

What test gateway are you using?

[bobr2k]

What test gateway are you using?

Authorize.net with Authorization Mode: Authorize
Gateway Mode: Production Gateway, Test Mode
Debug Mode Off

[Logan Rhodehamel]

To test a failed CVV, use Visa number 4222222222222 and make sure the transaction amount is 70.71.

More ways to decline: http://developer.authorize.net/guides/A ... umbers.htm

Give that a try and see if you need to amend your questions?

[bobr2k]

Thanks Logan, there's certainly a lot of information out there - not sure it's going to help me with my questions. I can't see how I'd change the amount on the order ... not sure I'd want that capability to be available. Actually I already "tested" the cvv by having it fail. Guess I'll do the trial and error thing to answer the questions of what is possible and what is not.

[Logan Rhodehamel]

Thanks Logan, there's certainly a lot of information out there - not sure it's going to help me with my questions.

Well you asked about the fail handling but it seemed like you weren't able to see it because the gateway accepts your transaction. You could create a product that is "hidden", costs 70.71, is not taxable, has no discounts, and is not shippable. Then go buy that item for your test.

If the gateway rejects the payment request at checkout, the customer is taken to a screen that explains what went wrong and gives them a chance to correct it.

[bobr2k]

Well you asked about the fail handling but it seemed like you weren't able to see it because the gateway accepts your transaction. You could create a product that is "hidden", costs 70.71, is not taxable, has no discounts, and is not shippable. Then go buy that item for your test.

You sly dog ... that's a great idea ... actually I was wondering why as a customer I didn't get to see what went wrong and have a chance to correct it as you describe:

If the gateway rejects the payment request at checkout, the customer is taken to a screen that explains what went wrong and gives them a chance to correct it.

I found some other interesting info. on the site you gave me in the AIM authorization guide http://developer.authorize.net/guides/AIM/ which makes me think there might be some wrong settings on the merchant interface which I currently do not have access to but your little tip above will help me check that out. Thanks again Logan.

[bobr2k]

I turned Debug On in the payment gateway. the note says: Debug Mode:
When debug mode is enabled, the communication between AbleCommerce and
Authorize.Net is recorded in the store "logs" folder. Sensitive information is
stripped from the log entries. I thought I'd see something in the Error Log but I do not. Is there something else that might affect that?

[Logan Rhodehamel]

In RC3 there is not a way to see the logs other than to physically look at the store folder on the server. There is a "logs" folder, inside there will be an authorizenet.log file. In a future update there will be a merchant interface to get to these files.

[bobr2k]

In RC3 there is not a way to see the logs other than to physically look at the store folder on the server. There is a "logs" folder, inside there will be an authorizenet.log file. In a future update there will be a merchant interface to get to these files.

on the server via ftp: I see admin/store but no logs folder in the store folder. I don't see a /store folder.

Nevermind, I found it here:

/App_Data/Logs

[batmike]

I was just wondering if anyone had any opinons on my thought below. I've been using it now for a week or so, and this is the only thing I'm thinking would help improve it.


[quote="batmike"]I do have a question. Potentially, an error could be caused by an address mismatch, though there's no way to change that on the new page. This would be fine, especially if they choose to use a new card, unless that new card needed a work address, etc. in which case maybe a radio button or something to mark that the card is different and then have an ajax form come up to enter a new billing address.
[quote]

[AbleMods]

The customer can't change the billing address?

About 70% of my failures are because of wrong billing address. 25% of them are wrong C.V.V. and about 5% just flat out fail authorization.