This effort is divided into three phases which will migrate data, connect recurring billing to customer profiles and expose functionality through the API. Phase 1 will begin shortly.
I personally need this solution sooner rather than later and have considered implementing a microservice written in golang to handle subscriptions/recurring payments seperately based on the CIM API.
It's fairly simple to implement. Since you can convert trasactions into CIM someone could easily take an existing ARB subscription and port it to CIM as well as this seperate reoccuring billing service.
I may open-source this project, so I will keep you all updated on the status as well as keep an eye on the status of ARB.
@Richard Not sure if you all considered that route... creating a brand new API for a new subscription service based on CIM rather than updating the existing ARB. Keep both alive and people will eventually transition away from ARB completely into a newer system. Just a thought. Golang is very suitable for this... fast dev time, concurrency, great standard net/http lib, and type safty.
We are going to use CIM at the moment with our own scheduler for recurring billing, with the hope that the new release would reduce our work load. Good luck.
I have one doubt regarding creating CIM profile from ARB transactions. Is there any restrictions to create a CIM profile from ARB transactions. Like the ARB transactions should not be more than few months ago.
Because I can't able to create a CIM profile for the ARB transaction which was made on 2014.
