Skip Menu |

This queue is for tickets about the Business-OnlinePayment-AuthorizeNet CPAN distribution.

Report information
The Basics
Id: 52446
Status: open
Priority: 0/
Queue: Business-OnlinePayment-AuthorizeNet

People
Owner: Nobody in particular
Requestors: bbb [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in:
  • 3.20
  • 3.21
Fixed in: (no value)



Subject: Unimplemented Unlinked Credit Support for ECC Merchants
The AIM documentation at www.authorize.net/support/AIM_guide.pdf describes how to submit an "Unlinked Credit" for those special merchants that have applied for ECC support, but this capability does not work through this module. As explained in the documentation, "A transaction ID must not be submitted with an Unlinked Credit." Unfortunately, in order to credit customers for transactions that have been captured over 120 days ago, we need to utilize this "Unlinked Credit" feature. To provide this capability, here is a simple (one-liner) patch: --- Business-OnlinePayment-AuthorizeNet-3.21.ORIG/AuthorizeNet/AIM.pm 2009-11-24 10:46:01.000000000 -0700 +++ Business-OnlinePayment-AuthorizeNet-3.21/AuthorizeNet/AIM.pm 2009-12-04 09:26:05.000000000 -0700 @@ -221,6 +221,11 @@ $post_data{'x_Test_Request'} = $self->test_transaction() ? 'TRUE' : 'FALSE'; + # Handle "Unlinked Credit" functionality for those non-standard merchant accounts + # that applied for ECC (Expanded Credits Capability) and have it enabled. + # WARNING: This is a dangerous option so use at your own risk! + $post_data{'x_Trans_ID'} = '' if $post_data{'x_Type'} eq 'CREDIT' && $self->{_content}->{unlinked_credit}; + #deal with perl-style bool if ( $post_data{'x_Email_Customer'} && $post_data{'x_Email_Customer'} !~ /^FALSE$/i ) { -- Rob Brown bbb@cpan.org
I don't understand why you chose to solve the problem like this. Why would you make a new "unlinked_credit" field that blanks out x_Trans_ID? Why not just remove "order_number" (becomes x_Trans_ID) from the list of required fields for credits? On Fri Dec 04 17:38:55 2009, BBB wrote: Show quoted text
> The AIM documentation at www.authorize.net/support/AIM_guide.pdf > describes how to submit an "Unlinked Credit" for those special merchants > that have applied for ECC support, but this capability does not work > through this module. As explained in the documentation, "A transaction > ID must not be submitted with an Unlinked Credit." Unfortunately, in > order to credit customers for transactions that have been captured over > 120 days ago, we need to utilize this "Unlinked Credit" feature. > > To provide this capability, here is a simple (one-liner) patch: > > --- Business-OnlinePayment-AuthorizeNet-3.21.ORIG/AuthorizeNet/AIM.pm > 2009-11-24 10:46:01.000000000 -0700 > +++ Business-OnlinePayment-AuthorizeNet-3.21/AuthorizeNet/AIM.pm > 2009-12-04 09:26:05.000000000 -0700 > @@ -221,6 +221,11 @@ > > $post_data{'x_Test_Request'} = $self->test_transaction() ? 'TRUE' : > 'FALSE'; > > + # Handle "Unlinked Credit" functionality for those non-standard > merchant accounts > + # that applied for ECC (Expanded Credits Capability) and have it > enabled. > + # WARNING: This is a dangerous option so use at your own risk! > + $post_data{'x_Trans_ID'} = '' if $post_data{'x_Type'} eq 'CREDIT' > && $self->{_content}->{unlinked_credit}; > + > #deal with perl-style bool > if ( $post_data{'x_Email_Customer'} > && $post_data{'x_Email_Customer'} !~ /^FALSE$/i ) { > > > > -- Rob Brown > bbb@cpan.org