Sounds good, Ryan. I can take care of the cim method on my end...the easiest way might be for me to create a new handler, which just changes the payment method to credit briefly, calls your handler, then changes it back to cim. Alternatively, if you ever wanted to integrate support for partial payments and pre-orders into the uc_credit module, I could probably go back to leaving the payment method as credit in the cim module.

There is one other point that I think may be important. I believe that most payment gateway modules will need to mark recurring transactions as recurring when they're processed. (In Auth.net AIM this is the x_recurring_billing option). The card associations seem to require this, plus I've read some reports that setting this option can save you some transaction fees, since the recurring transactions (except for the first) won't have any CVV data and might otherwise get downgraded as a result. If anyone has any experience with this I'd be curious to get their input.

The thing I'm not sure about is how to handle an order that contains some recurring and some non-recurring items. Should the whole order be flagged as recurring to the gateway? Or should the recurring portion be charged separately, with the flag? Or can we wait until the automatic recurring charge is made (as opposed to the first charge made when the user checks out)?

I'm just not quite sure how this is supposed to work. If anyone has any experience with this, it would be very helpful.

Best,
Chad