From http://developer.authorize.net/api/reference/features/customer_profiles.html
If you are submitting a refund against a previous CIM transaction, the following guidelines apply: Include customerProfileId, customerPaymentProfileId, and transId. customerShippingAddressId is optional. creditCardNumberMasked, bankRoutingNumberMasked, and bankAccountNumberMasked do not need to be included, but they are validated if they are included.
If you are submitting a refund for a non-CIM transaction, the following guidelines apply: You must include transId, creditCardNumberMasked (or bankRoutingNumberMasked and bankAccountNumberMasked). Do not include customerProfileId, customerPaymentProfileId, or customerShippingAddressId.
You can also issue an unlinked refund for a CIM transaction. In this case, the following rules apply: You must be enrolled in Expanded Credit Capabilities (ECC). For more information about ECC, go to http://www.authorize.net/files/ecc.pdf. You must include customerProfileId and customerPaymentProfileId. customerShippingAddressId is optional. Do not include transId, creditCardNumberMasked, bankRoutingNumberMasked, or bankAccountNumberMasked.
Both in testing and API reference, profile related fields are not allowed in a createTransactionRequest request of type voidTransaction. How should I be submitting a refund for a CIM charge?
08-24-2016 11:11 AM - edited 08-24-2016 11:12 AM
Hi monki,
A void and refund are two different transaction types and different requests. We do have not a specific example for unlinked refunds against a profile. However the API reference refund can be followed http://developer.authorize.net/api/reference/index.html#payment-transactions-refund-a-transaction and you only need to add the profile IDs as you add them in an authorization request.
Thanks,
Joy