Need a better understanding of user connection with Authorize.net

We are migrating a site from another payment processing Joomla component to CB Subs. Since this includes the member management of both the core Joomla users and their ARB subscriptions with Authorize.net, we need to know the hinge point for the two.

Ultimately the question is how are the CB Subscriptions linked with the Subscription ID at Authorize.net?

Also, is there a good case example prepared for adding existing ARB subscribers at Authorize.net as active CB Subs users without interrupting the existing login flow of users?

Ultimately the question is how are the CB Subscriptions linked with the Subscription ID at Authorize.net?

The gateway subscription id is stored to the users basket as subscr_id.

Also, is there a good case example prepared for adding existing ARB subscribers at Authorize.net as active CB Subs users without interrupting the existing login flow of users?

That will likely never work as often information unique to the system is stored at the gateway to be sent with the IPN, which will not translate to another system like CBSubs.

All recurring subscriptions should be cancelled and when they expire the user should renew in CBSubs. You can use the CBSubs Import feature to give them free subscriptions and as long as subscribe date is set properly they should expire when their existing subscription in the previous system expires.

often information unique to the system is stored at the gateway to be sent with the IPN

I see the cb_custom value set as merchant defined with the cb subs transaction to authorize.net. Is this the unique information? If so, is there a way to manually transfer this over to cb from other software's IPN?

That will likely never work

I understand that it is best if you can start fresh with a new user in the system, but is that truly our only option?

There must be some way to manually filter through each user and successfully migrate them into CB Subs without interrupting the workflow. You referenced the unique identifiers required. As long as we can find a way to determine where those unique identifier live in cb subs, then we could just copy them over, right?

This would be a very beneficial thing to know for our business, as many clients already have active subscriptions with Authorize.net. I have really appreciated all the feedback from your team over the past few months and so if you could dig deep and throw us a bone on this one it would be greatly appreciated. I would go so far as to say that if this is a concern for public publishing purposes, we would be willing to discuss a contract for a specialized documentation that spells it out. Any possibility either way?

I see the cb_custom value set as merchant defined with the cb subs transaction to authorize.net. Is this the unique information?

Yes, that's the basket id which is needed to match the IPN against a basket in CBSubs. Without it CBSubs has no idea what to do with the IPN.

If so, is there a way to manually transfer this over to cb from other software's IPN?

No.

I understand that it is best if you can start fresh with a new user in the system, but is that truly our only option?

Yes.

There must be some way to manually filter through each user and successfully migrate them into CB Subs without interrupting the workflow.

There isn't. The IPNs from your other system will not work in CBSubs. You can use CBSubs Import to give them a subscription in CBSubs and if you supply the subscribe date from your other system then CBSubs will calculate the expiration properly. However, it will expire and the user will have to manually renew with either single or recurring payments.

As long as we can find a way to determine where those unique identifier live in cb subs, then we could just copy them over, right?

Probably not. As far as I am aware you can't modify an IPNs information in Authorize.net. If Authorize.net has an GUI interface or something of the sort to do this then it could be possible. I am aware of no gateway that allows recurring profiles to be modified and those that do have an extremely small window (1-8 days) that they do allow modifications.

This would be a very beneficial thing to know for our business, as many clients already have active subscriptions with Authorize.net. I have really appreciated all the feedback from your team over the past few months and so if you could dig deep and throw us a bone on this one it would be greatly appreciated. I would go so far as to say that if this is a concern for public publishing purposes, we would be willing to discuss a contract for a specialized documentation that spells it out. Any possibility either way?

You can not migrate recurring subscriptions from 1 system to another. The IPN information and handling is typically so widely different it's impossible for it to work.