AbleCommerce Shopping Cart Software

Is it possible to store an order and credit card payment info without performing the authorization?

I've looked extensively at OnePageCheckout and the payment form code. It doesn't appear to be possible to prevent the authorization. All I can think of now is creating a new "fake" credit card payment method that doesn't actually perform the authorization.

So I'm left the bigger issue of how to store the order, the payment, the shipment info etc. without firing the basket.checkout() method. Boy I hate the idea of skipping all those methods.....

Thoughts?

Like you said, you can create charge card methods that don't use a gateway. Then everything would be stored except for the card security code. I've got a client who does that because they want to run the charges manually later.

yeah that's exactly what I need.

So how is the basket getting saved as an order without firing the checkout method??

Well, I was assuming it was like Able 5, but I haven't tested. In Able 5, the customer went thru the checkout, filled in charge card info, and order was created. Then the charge could be run later. It didn't authorize thru the gateway.

jmestep wrote:Well, I was assuming it was like Able 5, but I haven't tested. In Able 5, the customer went thru the checkout, filled in charge card info, and order was created. Then the charge could be run later. It didn't authorize thru the gateway.

That's how it works in 7 also. If you create a cc payment method (e.g. Visa) without a gateway assigned, then checkout just records the information. The merchant manually processes the charge.

We do it by two of each of the CC in our payment methods. Here in an example with visa.... The first one is just named "Visa" and it doesn't have any gateway assigned to it, which is the one the customer sees when they checkout. This one is assigned to all groups. Using this way the order is submitted without any authorization involved, and the CC info the customer submitted is stored in the payment section of the admin. The second, we have named "Visa ANet," which has our gateway assigned to it and it's only assigned to the admin group so it only appears in the admin area and isn't an option for the customer when they checkout. Once the order is submitted and we make any final adjustments, we process the CC with the "Visa ANet" payment method right in the payment section of the Admin.

Very interesting, didn't realize you could make cc-based payment methods without a gateway assigned.

Thanks guys!

Ok this leaves me with one question....

Doing it this way, you aren't going to be able to use a gateway to perform the authorization later are you?

You'd have to manually key the card numbers into a separate card machine to get the charges to go through right? Which also means a manual posting back to AC7 to mark the payment authorized, captured etc?