 |
UbercartOne cart to rule them all... |
|
| Donate | Affiliates | Sponsors | ||
Authorize.net errors and customer declinations
Submitted by Blessed_Steve on Mon, 09/24/2007 - 16:34
When a CC is declined, where is the error message supposed to show up? I am seeing the behaviour... i.e. real CC goes to completed page and bogus CC redraws the checkout page.... but I am not seeing the error message. Can someone walk me through what is supposed to happen so I can kill this final stage bug please?
 To clarify, are you saying that a declined CC through Authorize.net doesn't send an error message? I assume that Authorize.net IS sending messages to me because a bogus CC number causes the checkout page to reload and a valid CC number causes the process to move on to the review page. So I am happy that it appears to be functioning correct in that respect. BUT, when I provide a bogus CC number and the checkout page reloads, there is no message saying that my card number was invalid. The question I am asking is what is supposed to happen here? Do we expect a customer message to show up and if so, in what pane should it show by default? thanks. When I put in a bogus number and then go to Review Order, it refreshes the page and I see a "You have entered an invalid credit card number." in a box outlined in red at the top of the checkout page. ok, in the process of themeing the checkout page, I have definately broken the customer feedback/status display on return from a credit card error. Lyle, Ryan or other wandering beneficient guru, can you point me in the right direction to debug theme_2nd_round_checkout_form_after_CC_declination error please? I see where, in authorizenet.module the result of the auth request is put in an array. I know I'm just being stupid but where in the cart does ubercart display this please? Somehow it is getting squelched. The answer to my question is to add printing of messages into my template. <?phpNow my authorize.net messages are displayed in the cart review form. Unfortunately, so are code errors... Things like "warning: Invalid Argument supplied for foreach() in views_query.inc on line 81. etc. so new question is, can I have it both ways? functioning CC messages but no coding messages to users? You know... I was gonna ask about that. Honestly, I'd figure out what was going wrong w/ the Views query. If an error is being set by Drupal, there's probably something wrong with your View or some pertaining code. (Is there even a View displayed on your checkout page??) I stopped acting like a baby and debugged my views issue. I am getting just the feedback from Authorize.net now. Unfortunately, I am being told by Auth.net that they cannot check for over limit during the checkout/review stage of the cart. I guess this is fair, but I was hoping to not store CC numbers on the site which means I need some way of getting Authorize.net to hold that information. Am I correct that "out of the box" Ubercart wants to store the CC info with the order until the admin has processed and "captured" the purchase info on the back end? Is there anyway to have Auth issue me a transaction number which we store that references the CC info stored by Authorize.net? This way, our admin could go to authorize.net's site to manger capture/collection and then fulfill the order back on our site. Did this issue/question make sense? thanks. SO two months later I am just getting back to trying to solve this problem. here is a bump on it. Is anyone else using Authorize.net and if so... just using auth_only instead of auth capture? thanks. Still not perfect so yet another bump here. When there is an error, the shipping quote data is preserved as the checkout form repaints.... Thanks Lyle! The CC data in the Authorize.net gateway however, still gets wiped out. I lost track, is auth a core gateway or a contribution? Who can I bribe to help me fix this? Hey Steve, CC data is another animal, as those form fields are loaded and populated through an AJAX call to the payment method details form. I'm not sure what the best way to securely store that data and re-display it on a failed attempt would be (and I've been advised by some folks in the past that incorrect CC data should just be wiped altogether and not preserved, which is why I think I never worked on that before). Thoughts? Is there anyway to differentiate between errors in the credit card data, and errors that occur on other panes that cause the checkout page to repaint prior to verification of the authorize . net data? If I don't put in city data, for instance, how can I preserve CC data which is different from making a mistake in the CC data itself? Is this even reasonable thing to try and do?
|
|
Joined: 08/07/2007