Si,
If I remember, refunds required using a newer API which also required a
special setup via your authnet web account. I wasn't able to test that
part since no one could remember our password and we were too paranoid
to change it. Authnet also said that transaction was not testable via
the test account.
Fred
Si Chen wrote:
> Hi. I'm looking at the authorize.net stuff, and I found that authorize
> and capture both work (Good job, Fred!) Refunds, though, give this error:
> 2006-09-12 16:35:08,207 (http-0.0.0.0-8443-Processor4) [
> AIMPaymentServices.java:281:INFO ] --> TRANSACTION DECLINED <--
> 2006-09-12 16:35:08,210 (http-0.0.0.0-8443-Processor4) [
> AIMPaymentServices.java:282:INFO ] responseCode: 3
> 2006-09-12 16:35:08,212 (http-0.0.0.0-8443-Processor4) [
> AIMPaymentServices.java:283:INFO ] responseReason: 54
> 2006-09-12 16:35:08,214 (http-0.0.0.0-8443-Processor4) [
> AIMPaymentServices.java:284:INFO ] reasonText: The referenced
> transaction does not meet the criteria for issuing a credit.
> 2006-09-12 16:35:08,262 (http-0.0.0.0-8443-Processor4) [
> AIMPaymentServices.java:591:INFO ] processRefundTransResult:
> [responseMessage=success, refundResult=false, refundFlag=54,
> refundMessage=The referenced transaction does not meet the criteria for
> issuing a credit., refundAmount=0.0]
> 2006-09-12 16:35:08,265 (http-0.0.0.0-8443-Processor4) [
> AIMPaymentServices.java:201:INFO ] <-- Authorize.net ccCapture
> Transaction End -->
>
> I remember Fred saying that this was new -- has it been fully tested?
>
> Si
>
>
>
>
Locked
