[gb2world]

Hopefully I am just missing something obvious.

With:
X-CART 4.4.1, X-Payments 1.0.2, Authorize.net AIM in test mode, the shop closed with key access required, FLC enabled.

X-Payments and the built in X-Payments Connector are set up. The X-Payments Connector returns a "Test transaction completed successfully" message. It was able to import successfully the Authorize.net payment method from X-Payments. It also successfully imported all the keys when I entered the Store ID and deployed it.

Now what? Is the X-Payment method supposed to be set up for use by the front end now - or is there another setting that needs to turn off the normal X-CART payment methods?

I turned all payment methods off, as the Authorize.net method set up in X-Payments is the only method required. The customer front end then does not see a checkout payment method. If Authorize.net is set up in the non-compliant way - the X-Payments Connector does see it and warns you to disable it.

If anyone has any hints about how it is supposed to work - I'd appreciate them. I am not sure what the relationship is between the old way of setting up payment methods and what is supposed to happen after X-Payments and the connector have been set up. I assumed either X-Payments would take over, or I would see some sort of X-Payments option as a payment method.

----