I have been writing a client service for interacting with Authorize.net. Our business analyst didnt like the idea that our customers would be getting a receipt on Authorization only and not on the actual capture of the funds. So we explictly turned off the sending of the email receipt for our auth-only call with the x_email_customer field being set to false, but not doing anything for the charge call, letting the receipt be sent for that. However, it has stopped sending the receipt even on the charge (i.e. AUTH_CAPTURE_TRANSACTION) even though we don't set it false for that particular transaction(I've even set it to true explicitly before calling it and it still doesn't send). We are at a loss as why this is happening. I even sent a raw JSON call for a charge to see if it would send the receipt, but no dice.
Also, it does send the receipt when we explicitly do the charge in the console on the site. Here is the raw JSON request that is still not sending the receipt:
{
"createTransactionRequest": {
"merchantAuthentication": {
"name": "mynameis",
"transactionKey": "thekeyis"
},
"refId": "123456",
"transactionRequest": {
"transactionType": "authCaptureTransaction",
"amount": "45",
"profile": {
"customerProfileId": "39622210",
"paymentProfile": { "paymentProfileId": "35955134" }
},
"lineItems": {
"lineItem": {
"itemId": "1",
"name": "vase",
"description": "Cannes logo",
"quantity": "18",
"unitPrice": "45.00"
}
}
}
}
} Any thoughts? Thanks in advance.
