Charging Saved Credit Cards Question
 

We are using X-Payments with the Authorize.Net CIM method and I have been testing the Charge Saved Credit Card function on the X-Payments back end. There are 3 types of orders, one where the registered user has checked the "... use credit card for future orders ..." box, another where the registered user does not check the box, and another where the user does not register. In all 3 cases the X-Payments back end shows the "Charge this card again" button, and a new order is created, and an additional charge amount is approved by Authorize.Net. I asked Authorize.Net about this and they stated that the tokenization used in CIM allows this. When the additional charges are captured, X-cart sends a message to the user with the new order number and states that the saved credit card was used, even when the box was not checked. When the user does not register, the user information is not added to the new order, and it would have to be done by hand using Advanced Order Management if the user was to receive notice of the transaction. I have read the X-Payments manual and it states that this function is intended to be used when the user has opted to save the card, but the back end does not seem to support that. Does anyone else see this problem, or am I missing something here?

Re: Charging Saved Credit Cards Question
 

Technically, X-Payments allows to make a new charge for every payment placed using a payment method that supports tokenization. So when you do it from X-Payments back-end you can charge a customer even if he/she didn't opt to save their card during checkout.