E00051 during authorize.net CIM Void

jserrano — Tue, 08 Apr 2014 21:47:44 GMT

This is the xml passed to authorize.net:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://api.authorize.net/soap/v1/">
  <SOAP-ENV:Body>
    <ns1:CreateCustomerProfileTransaction>
      <ns1:merchantAuthentication>
        <ns1:name>xxxx</ns1:name>
        <ns1:transactionKey>xxxxxx</ns1:transactionKey>
      </ns1:merchantAuthentication>
      <ns1:transaction>
        <ns1:profileTransVoid>
          <ns1:customerProfileId>103152680</ns1:customerProfileId>
          <ns1:customerPaymentProfileId>96738309</ns1:customerPaymentProfileId>
          <ns1:transId>6078297495</ns1:transId>
        </ns1:profileTransVoid>
      </ns1:transaction>
      <ns1:extraOptions>x_delim_char=(~)</ns1:extraOptions>
    </ns1:CreateCustomerProfileTransaction>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The above numbers for customerProfileId, customerPaymentProfileId and transId match what's in my authorize.net account but the api still says they don't match via error E00051:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Body>
    <CreateCustomerProfileTransactionResponse xmlns="https://api.authorize.net/soap/v1/">
      <CreateCustomerProfileTransactionResult>
        <resultCode>Error</resultCode>
        <messages>
          <MessagesTypeMessage>
            <code>E00051</code>
            <text>The original transaction was not issued for this payment profile.</text>
          </MessagesTypeMessage>
        </messages>
      </CreateCustomerProfileTransactionResult>
    </CreateCustomerProfileTransactionResponse>
  </soap:Body>
</soap:Envelope>

Re: E00051 during authorize.net CIM Void

RaynorC1emen7 — Tue, 08 Apr 2014 23:24:09 GMT

could the cc in that payment profile got change?

Re: E00051 during authorize.net CIM Void

jserrano — Wed, 09 Apr 2014 15:07:05 GMT

It wasn't changed.

Re: E00051 during authorize.net CIM Void

jserrano — Thu, 10 Apr 2014 13:59:54 GMT

I found out that the magento extension was using the incorrect api keys and transaction key because it wasn't built to handle multi website settings correctly when in the admin. It always uses the default config because the current store is 0.

topic E00051 during authorize.net CIM Void in Integration and Testing

E00051 during authorize.net CIM Void

Re: E00051 during authorize.net CIM Void

Re: E00051 during authorize.net CIM Void

Re: E00051 during authorize.net CIM Void