Integration and Testing

Authorize.Net API questions and help with your payment integration.

Reply
Contributor
Posts: 38
Registered: ‎05-08-2012

CIM: Billing Address and Transactions

Each person has a customer profile. Each customer profile has one or more payment profiles. And each of our payment profiles has a billing address for each card.

 

When we make a call to CreateCustomerProfileTransaction, we provide the customer profile, payment profile, amount, and (if it was provided at the time of transaction) the code on the back of the card.

 

Everything works great.

 

I've seen charts that show various cost-savings if extra cardholder details are provided with a transaction. This might be as simple as a zipcode or it can be as complete as the customer's full name and billing address. The more (correct) information provided, the more the cost savings.

 

How does that work with CIM, though? Does it automatically use the information stored in the payment profile? Or is it information that has to explicitly be passed in through the "extraOptions" parameter?

Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: CIM: Billing Address and Transactions

As far as I know, the billing address is send with the CC info.

Member
Posts: 1
Registered: ‎10-02-2012

Re: CIM: Billing Address and Transactions

Does CIM allow the creation of customer profiles and the storage of payment information but for the payments ot be processed at a later date that is set by the seller?  For ex, if the customer is to be charged say $100 on Oct 2nd, but the payment should not be processed until 10/31, can the CIM allow the seller to store the credit card info and payment amount at on 10/2 but then set the transaction process for 10/31?

 

Thanks

aryavish

Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: CIM: Billing Address and Transactions

CIM allow you(the merchant) to store customer(the user) payment profile(cc or bank account info) and create transaction when ever you need.  So to answer your question, yes, create the payment profile on 10/2, then create the transaction on 10/31.