- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
E00027 error in payment responses for production transactions by profiles
I have a sandbox account. There is a customer profile with payment profile assigned in CIM.
I send request to URL https://apitest.authorize.net/xml/v1/request.api
<?xml version="1.0" encoding="utf-8"?> <createTransactionRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"> <merchantAuthentication> <name>...</name> <transactionKey>...</transactionKey> </merchantAuthentication> <transactionRequest> <transactionType>authCaptureTransaction</transactionType> <amount>3.00</amount> <profile> <customerProfileId>33328253</customerProfileId> <paymentProfile> <paymentProfileId>29941781</paymentProfileId> </paymentProfile> </profile> </transactionRequest> </createTransactionRequest>
And receive response:
<?xml version="1.0" encoding="utf-8"?> <createTransactionResponse xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <messages> <resultCode>Ok</resultCode> <message> <code>I00001</code> <text>Successful.</text> </message> </messages> <transactionResponse> <responseCode>1</responseCode> <authCode>M2539Z</authCode> <avsResultCode>Y</avsResultCode> <cvvResultCode/> <cavvResultCode>2</cavvResultCode> <transId>2233251497</transId> <refTransID/> <transHash>E261C989841E209F899F7E82B4C6747C</transHash> <testRequest>0</testRequest> <accountNumber>XXXX0027</accountNumber> <accountType>Visa</accountType> <messages> <message> <code>1</code> <description>This transaction has been approved.</description> </message> </messages> </transactionResponse> </createTransactionResponse>
And this is ok. But after subsequent request with the same profiles within e.g. 10 seconds I receive response:
<?xml version="1.0" encoding="utf-8"?> <createTransactionResponse xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <messages> <resultCode>Error</resultCode> <message> <code>E00027</code> </message> </messages> <transactionResponse/> </createTransactionResponse>
Ok. I can guess that this is some kind of fraud/overdraft protection, but I have another big problem. There is another production account with multiple customer profiles (which have payment profiles assigned with real credit cards). But for every post on production URL with production merchantAuthentication I receive response with error E00027 without any error description. I other words payments by profiles in production mode don't work for me at all. BTW, these rejected transactions are not present in reposrts/transactions history.
Is there any possibility to get the real reason of this issue?
05-08-2015 03:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Andrui
I've reported your issue to the product team for analysis.
I'd recommend subscribing to this topic so that you'll be alerted via email if there are updates. To subscribe, click Topic Options at the top of this thread and then select Subscribe. You'll then receive an email once anyone replies to your post.
Thanks,
Richard
05-14-2015 12:53 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @RichardH
Thank you for this. I will be waiting for the information from you and product team because this issue is very important.
BTW, I have tried to search information/solution for similar issues but without success.
05-14-2015 11:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2015 01:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am also having the same issue with my own card and address on card is right. The CIM/[Charge] allows you to [Charge] the profile. When you use the API to charge the 'same' profile, I receive E00027.
The behavior is the seen in bth Sandbox and in Production environment,
Appreciate your help to resolve this issue E00027 with Charging a Profile in CIM.
06-23-2015 11:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2015 04:19 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I used SOAPUI as the Client from Windows to eliminate any user related coding errors.
BTW I sort of figured out the issue. In Payment Form, we made certain fields manadatory and the CIM API doesn't have any elements that would allow to send those fields. (ex) one such field is Invoice No. Once I made the Invoice No as optional in Payment Form, the call went through fine. Call was executed with error E00027 as the mandatory fields were not passed in the API Call.
Apparently, Authorize.Net was not returning any direct response in the above case. If I had received any direct response, it would have made it easier to troubleshoot.
Note: Payment Form is located in Autorize.Net Portal and one can configure mandatory fields in that form.
Check the mandatory fields in Payment form and make sure you indeed pass those mandatory fields in the CIM call. If you are not able to pass those manadtory fields, make it optional in Payment Form and give it a try. It should fo through without any issues.
Hoep it helps.
07-03-2015 07:40 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2015 11:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, @MuthuUVA
I have checked, but I don't have fields marked as 'Required'. So, this seems is not my case :(
07-22-2015 01:41 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @RichardH
Is there any news from the product team?
Does authorize.net have possibility to gather low-level debug in order to detect the root of the issue?
Thank you.
07-22-2015 01:44 AM