Hi. Thanks for this module and patches. I have the option for 'Preauth' set but it's charging my credit card right away. This doesn't seem right since it shouldn't be charging my card right away.

The LinkPoint Transaction Reports are showing the transaction in 3 separate instances marked with type 'Auth' then 'Ticket' then 'Void Sale'. Also, when I check the order detail it is marked with a 'Y' as shipped but the Linkpoint FAQ says that this should be marked with 'N' as not shipped. The shipping status should be changed to 'Y' when the order has shipped at which point the credit card will be charged.

Also, when going through the checkout process, I received the error message that the order could not be processed. However, the credit card was charged and the order did post to Linkpoint Central but the order is not recorded in the Ubercart list of Orders.

I'm using the latest CVS version 1.10 of uc_linkpoint_api.module

Any help is much appreciated.
Thanks!

Comments

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
commented
Status: Active » Postponed (maintainer needs more info)

Interesting problems here. My suspicion is that you have AVS/CVV checking in place.... if you do, and the codes come back unsatisfactory to what you selected in admin settings, then it will move the order to POSTAUTH, and then VOID.

When an order goes to POSTAUTH (also known as a Ticket transaction), Linkpoint will mark the transaction as shipped. They probably do this because it's technically illegal to charge a CC unless the order has shipped. So once the card HAS been charged, they assume it has been shipped.

Everything you've written points to you using AVS/CVV checking. Can you confirm?

imrubio22’s picture

imrubio22 commented

AVS/CVV was enabled. I will try it disabled and post my findings. Thanks for your help!

imrubio22’s picture

imrubio22 commented

@bkosborne, It was the AVS checking. I tried with AVS on and CVV off (did not work), AVS off and CVV off (worked), then AVS off and CVV on (worked). The transaction record in Linkpoint is now showing up properly as just Auth. Thank you very much for the help!

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Glad to see it worked. I think we may update the documentation to more clearly state that AVS checking results in a credit charge and then void...

PatW’s picture

PatW commented

imrubio22 stated that it worked for him with AVS off and CVV on, but this is the documentation on 6.x-1.8:

Fraud prevention
When a credit card transaction occurs, AVS and CVV response codes are returned. These can be used to determine fraud. Unfortunately, this information is received after a transaction has already occured. If you chose to use the fraud detection, the transaction will be voided after the card has already been charged. This in unavoidable.

Is there a workaround for this, or is there no way to check the AVS and CVV for fraud prevention? I'm using the "Authorize and capture immediately".

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
commented

Pat, if you enable AVS/CVV protection with Authorize and capture immediately, the module will first complete that transaction to the card, and then void it right away. Like the documentation says, this seems to be unavoidable. Something to look forward to is that First data should soon be launching their fraud "flex detect" system, which to my (hopeful) understanding will handle AVS/CVV checking on their end. This would ideally allow you to deny transaction in your settings with your Fist Data account.

I believe jrust is utilizing the fraud detection of the module, considering he wrote most of it in. Not sure if he is using it for Authorize & capture, but it's programmed to handle that.

PatW’s picture

PatW commented
Priority: Major » Minor

With release 6.x-1.5, it was working for me with AVS on and CVV off, but I updated to 6.x-1.8 yesterday and it did exactly as you stated by completing the transaction, then voiding it right away. I have now disabled both AVS & CVV. I hope First Data's "flex detect" system works out. Thanks for the quick response!