- Don't require "check_type" field

[Business-OnlinePayment-AuthorizeNet.git] / AuthorizeNet.pm

diff --git a/AuthorizeNet.pm b/AuthorizeNet.pm
index 82c2be1..9ed5082 100644 (file)
--- a/AuthorizeNet.pm
+++ b/AuthorizeNet.pm
@@ -107,7 +107,7 @@ sub submit {
         expiration     => 'x_Exp_Date',
         cvv2           => 'x_Card_Code',
         check_type     => 'x_Echeck_Type',
-       account_name   => 'x_Bank_Account_Name',
+       account_name   => 'x_Bank_Acct_Name',
         account_number => 'x_Bank_Acct_Num',
         account_type   => 'x_Bank_Acct_Type',
         bank_name      => 'x_Bank_Name',
@@ -123,12 +123,12 @@ sub submit {
         if ($self->{_content}->{customer_org} ne '') {
             $self->required_fields(qw/type login password amount routing_code
                                   account_number account_type bank_name
-                                  account_name account_type check_type
+                                  account_name account_type
                                   customer_org customer_ssn/);
         } else {
             $self->required_fields(qw/type login password amount routing_code
                                   account_number account_type bank_name
-                                  account_name account_type check_type
+                                  account_name account_type
                                   license_num license_state license_dob/);
         }
     } elsif ($self->transaction_type() eq 'CC' ) {
@@ -260,12 +260,12 @@ Unlike Business::OnlinePayment or pre-3.0 verisons of
 Business::OnlinePayment::AuthorizeNet, 3.1 requires separate first_name and
 last_name fields.
 
-Business::OnlinePayment::AuthorizeNet uses the ADC direct response method,
-and sends a username and password with every transaction.  Therefore,
-Authorize.Net's referrer "security" is not necessary.  In your Authorize.Net
-interface at https://secure.authorize.net/ make sure the list of allowable
-referers is blank.  Alternatively, set the B<referer> field in the transaction
-content.
+Business::OnlinePayment::AuthorizeNet uses Authorize.Net's "Advanced
+Integration Method (AIM) (formerly known as ADC direct response)", sending a
+username and password with every transaction.  Therefore, Authorize.Net's
+referrer "security" is not necessary.  In your Authorize.Net interface at
+https://secure.authorize.net/ make sure the list of allowable referers is
+blank.  Alternatively, set the B<referer> field in the transaction content.
 
 To settle an authorization-only transaction (where you set action to
 'Authorization Only'), submit the nine-digit transaction id code in