Quote:
|
Originally Posted by finestshops
Vladimir,
Your CIM integration in X-Payments is done incorrectly.
tech support at Authorize.net identified the problem.
If a CIM profile for the customer exists, then the CVV result code will always come back as "not applicable."
Auth.net believes that X-Payment is creating the CIM profile first, then drawing a transaction against that profile.
which is confirmed by your statement in previous post : " even for "first" payment it saves a card and then use its token to pay."
This will not allow merchant to check CVV causing lots of fraud charges
X-Payments has to submit transaction first, then create the CIM profile.
for $1500 you want for x-payments, would be nice to have integration done properly at least with the largest and most popular payment gateway
Can we expect this to be fixed in the near future?
|
Authorize.net CIM API allows both ways (place transaction + create profile from it OR create profile + place transaction using it) so we can't say that the integration is done incorrectly.
However, since it causes some issues for you we'll consider to change the behavior in a next release.