Authorize.net token billing integration with CIM?

[wrhansen]

It looks like Authorize.net has support for token billing with a feature called Customer Information Manager (CIM) that allows you to save customer information on their server, and later access it via a token.

Is there plans for Omnipay's token billing methods to support CIM for this gateway?

[amacneil]

No plans, but would be happy to accept a pull request. See thephpleague/omnipay#37 and thephpleague/omnipay#51 for previous discussion on this.

[bosschuyler]

I'm looking to implement the CIM card storage for omnipay. However, I've been looking at their API and I've noticed in order to use a stored card I need the customer profile id and the customer payment profile id. in your docs you send "cardReference" to look up the card, but that doesn't seem to be enough information to locate the stored card on their system. Am I missing something? Or how are you thinking of handling this? Does an example like this already exist?

[amacneil]

Is it possible to have a 'default' card for a customer profile? Can you create a customer and stored card at the same time?

Ideally we can do it in one request/response class and ignore the whole separate customer entity. If that's not possible, we may need to add the concept of a Customer object to Omnipay (it seems to be common in a few gateways now).

[clphillips]

The customer profile has to be created separately and before the payment profile.

Having a separate Customer object would be ideal.

[greydnls]

A separate customer object is being planned for V3.

[mansouralex]

Does the library now supports token billing for Authorize.net ?