authCaptureTransaction transactions with specific invoice numbers always fail

[dellsala]

We've noticed that all authCapture transactions we submit with certain invoice numbers have started returning errors. (This is only in our sandbox account).

If we send a request with <invoiceNumber> as "2", we always get <responseCode> 2 and <errorCode> 2, with message "This transaction has been declined." 

If we send a request with <invoiceNumber> as "3", we always get <responseCode> 2 and <errorCode> 35, with message "An error occurred during processing. Call Merchant Service Provider.".

Any other invoice number works fine. 

We're not sending any zip codes, so we shouldn't be triggering any test errors that way. Here's an example request that will always produce errorCode 35. When we use exactly the same request, but with any other invoice number, it succeeds. Why is this happening?

<?xml version="1.0"?>
<createTransactionRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
<merchantAuthentication/>
<transactionRequest>
    <transactionType>authCaptureTransaction</transactionType>
    <amount>66.23</amount>
    <payment>
        <creditCard>
            <cardNumber>4012888818888</cardNumber>
            <expirationDate>0417</expirationDate>
            <cardCode>321</cardCode>
        </creditCard>
    </payment>
    <order>
        <invoiceNumber>3</invoiceNumber>
        <description>fgdgdfg</description>
    </order>
    <lineItems>
        <lineItem>
            <itemId>dfgdfgdfg</itemId>
            <name>Some Service</name>
            <description>fgdgdfg</description>
            <quantity>1</quantity>
            <unitPrice>66.23</unitPrice>
        </lineItem>
    </lineItems>
</transactionRequest>
</createTransactionRequest>

[RichardH · Accepted solution]

Hello @dellsala

There are a few undocumented response code triggers currently in our sandbox.  To work around the issue, we suggest using invoice numbers that are more realistic rather than simple single-digit numbers.

We don't suggest using these triggers in the long term as they may be removed without notice.

Richard