topic Re: CIM live transaction error E00027/ response 207 in Integration and Testing

CIM live transaction error E00027/ response 207

aneesshoukat — Thu, 15 Dec 2011 06:09:50 GMT

I have do live transction and getting following error on charge transction

<messages><resultCode>Error</resultCode><message><code>E00027</code>

<text>This transaction has been declined</text></message></messages>

<directResponse>2,2,207,This transaction has been declined............auth_capture

Re: CIM live transaction error E00027/ response 207

stymiee — Thu, 15 Dec 2011 12:49:00 GMT

So what is your question? Why is it declined? The card issuing bank is declining the card for reasons only they know. But if the card is declined then the transaction is processing successfully.

Re: CIM live transaction error E00027/ response 207

TJPride — Thu, 15 Dec 2011 16:33:45 GMT

Error code 207 says:

This error code applies only to merchants on FDC Omaha. The merchant account is closed.

Re: CIM live transaction error E00027/ response 207

aneesshoukat — Mon, 19 Dec 2011 05:47:37 GMT

Merchant account closed mean credit card has been closed?

Re: CIM live transaction error E00027/ response 207

TJPride — Mon, 19 Dec 2011 14:09:19 GMT

I would assume so. Authorize.net's services sit on top of the merchant services - they aren't actually the merchant services themselves. Though their parent company can help supply that if you sign up through them.

Re: CIM live transaction error E00027/ response 207

aneesshoukat — Tue, 20 Dec 2011 05:57:56 GMT

If it create payment profile successfully then why it not charge the credit card and giving the error 'E00027/ response 207'

Re: CIM live transaction error E00027/ response 207

TJPride — Tue, 20 Dec 2011 15:46:31 GMT

The contact and credit card info can be valid, and Authorize.net can create the profile, without the merchant actually allowing a charge to run through. As I said before, Authorize.net is like an interface layer that sits on top of the merchant account.