Our client has both Auth.net and NMI. Auth was the default and now the client wants to use NMI. The client has 41 subscriptions created in GHL that live on GHL's billing engine while Auth.net was the default processor and needs them moved over to NMI the current default processor.

We had tokens for the cards moved from Auth.net to NMI on the processor end and just needed to move the subscriptions. GHL support said to move the subscriptions to use the "Add Subscription" button from subscriptions to create a new subscription using the card details on file so we can move the existing sub in GHL to the new default processor as long as it is marked "default".

The problem is that the new sub just created a new sub on the original payment processor and has no way of being able to designate or direct it to go to NMI or the one of choice.

If this is supposed to be the way to move the subscription then we need the ability to select the payment processor we want the subscription to be created on. The other alternative would be to create subs directly in the payment processor but this would then take the management out of GHL and would defeat the purpose of creating subscriptions in GHL.