In both sandbox and production environments, the first transaction received by the CIM through the authorize.net API is not listed in the customer history. However, all subsequent transactions are listed. Note that the first transaction can be found by searching the transaction ID but I am puzzled why it's not listed in the history.
For example:
Any idea why this would be happening?
I spoke with the authorize.net Live Support Team and we examined production accounts where this occurred. They had to go into their internal documentation to find the answer.
This is expected behavior due to order of operations. Meaning, when the transaction is sent at the same time the customer profile is being created, the transaction is first run and verified prior to the profile being created so they don't end up creating a profile that is not going to be used.
For this reason, the transaction will never be tied back to the customer history because the profile didn't exist when the transaction was run. They understand this is confusing and suggested submitting a request to rectify this in future versions of the API.