topic Using CIM XML API for tokenizing CC data only in Integration and Testing

Using CIM XML API for tokenizing CC data only

shop201 — Thu, 06 Feb 2014 00:05:38 GMT

I have an existing checkout pipeline that's fairly standard (Basket, Ship-to, Ship-Method, Bill-to, Review, Confirm). On the Bill-to page we collect both billing address and CC payment info.

I need to tokenize the user-entered CC info *and only the CC info* (name/number/expy/cvv) and store that token ID in the receipt database record so that it can be passed on to the fullfillment service for actual payment processing and order fullfillment as part of a separate process.

We don't want CIM to manage addresses and payment profiles... just create and store a unique CC payment profile for each order that can be pulled up for processing that order later at the fullfillment warehouse.

Thinking to create a CIM profile based on receipt ID rather than customer ID...

Does anyone have any tips on how best to accomplish this? Also note that this is a temporary setup while some additional systems are integrated.

Re: Using CIM XML API for tokenizing CC data only

RaynorC1emen7 — Thu, 06 Feb 2014 00:44:48 GMT

http://developer.authorize.net/api/cim/

The CIM XML documentation said the only fields that are required for createCustomerProfileRequest are 1 of the 3, email, description or merchantCustomerId.

You could use your order receipt ID as the merchantCustomerId.

Then use that to saved the cc payment profile.

Not sure what you mean by We don't want CIM to manage payment profiles, then just create and store a unique CC payment profile.

So you would need to save the customer proifile id and payment profile id.

Re: Using CIM XML API for tokenizing CC data only

shop201 — Thu, 06 Feb 2014 16:08:59 GMT

@RaynorC1emen7 wrote:
http://developer.authorize.net/api/cim/

Not sure what you mean by We don't want CIM to manage payment profiles, then just create and store a unique CC payment profile.

In other words, we are not interested in storing shipping and billing addresses using CIM as is usually the case in a typical AuthNet CIM implementation. The primary concern is simply to eliminate the "storage" of CC info on our dB servers.

Thanks for your input!

Re: Using CIM XML API for tokenizing CC data only

RaynorC1emen7 — Thu, 06 Feb 2014 16:22:16 GMT

Then you are good, cause billing/shipping address is optional