topic CIM or Gateway charge in Integration and Testing

CIM or Gateway charge

glerler — Tue, 03 Jan 2012 18:55:20 GMT

What is the best way to handle this. We charge membership for a site and we keep the info in CIM. Should I charge via the gateway and then create the CIM profile, or create the CIM and do transaction via the CIM? Both have ways have issues. I would lke to to see a complete charge history in their profile. Idealy it seems the order should be;

1. Successful Gateway charge

2. Create CIM payment profile

3. Be able to reference the first transaction in their profile.

Creating the CIM has issues with bad or incorrect payment.data.

How have others dealt with this?

Re: CIM or Gateway charge

stymiee — Tue, 03 Jan 2012 19:04:41 GMT

If you've had issues with the first transaction failing using CIM you can alsways run the first transaction using AIM and if it is successful then go through the process of setting up CIM profiles. You can still references the AIM transaction in your Authorize.Net control panel. But if the credit card is bad it will still be declined just like it would if you ran it through CIM. The only difference is it would require less overhead then doing it through CIM.

Re: CIM or Gateway charge

glerler — Tue, 03 Jan 2012 19:25:38 GMT

Thanks for replying. The complications I have run into deal with keeping the data in sync since I store the profileID and payentID as well as include my memberID with the CIM profile. is there a request that that will reference the intial gateway transaction on the CIM profile?

Re: CIM or Gateway charge

stymiee — Tue, 03 Jan 2012 19:28:53 GMT

Which part gets out of sync? The profile ID and payment profile ID should never change unless you delete them in which case they go away forever. The membership ID can be associated with the profile ID in yoru database which you can update as often as you want without ever having to touch Authorize.Net's servers since that information is irrelevant to them.