Authorize.net and GeneralCredit
Hi-
According to the docs (https://docs.spreedly.com/payment-gateways/authorize-net/) the Authorize.net gateway supports the GeneralCredit transaction type.
According to the Authorize.net docs (http://developer.authorize.net/api/reference/#payment-transactions-refund-a-transaction), a reference transaction ID has to be passed in to any credit transaction - which isn't a field I can pass in the GeneralCredit API call.
I'm only trying to use GeneralCredit because the Spreedly Credit method doesn't allow me to pass a description along. With multiple systems dumping transactions into that particular gateway account they're not enjoying separating which refund corresponds to which source system.
So am I wrong, are your docs wrong, or did Authorize change their requirements on you?
-
Hi Steve,
That's a great question and thanks for bringing this to our attention. I do see that we have a few successful General Credits processed this week on Authorize.net and it is possible that they've updated their documentation since we've implemented them. Could you tell me if you've attempted a General Credit request and if it failed at the gateway? I'm also checking internally for the documentation we implemented against so I can compare that to their currently published documentation. I'll be back in touch shortly!
-
I did, and yes it was a gateway response. Some relevant bits:
<state>gateway_processing_failed</state> <transaction_type>GeneralCredit</transaction_type><message>A valid referenced transaction ID is required</message><gateway_specific_response_fields> <authorize_net> <response_reason_code>33</response_reason_code> </authorize_net> </gateway_specific_response_fields> -
Hi Steve,
I appreciate the sample. Being that we do see successful transactions being processed but you are experiencing a gateway failure, I would like to take a closer look at your examples and compare them to the successful transactions I see. I'll be following up with you in a direct email momentarily to discuss further. Thanks!
Please sign in to leave a comment.
Comments
4 comments