E00051 during authorize.net CIM Void

[jserrano]

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>

[RaynorC1emen7]

could the cc in that payment profile got change?

[jserrano]

It wasn't changed.

[jserrano · Accepted solution]

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.