amount => '49.95',
invoice_number => '100100',
customer_id => 'jsk',
+ email => 'jason@example.com',
first_name => 'Jason',
last_name => 'Kohles',
address => '123 Anystreet',
city => 'Anywhere',
state => 'UT',
zip => '84058',
+ country => 'US',
card_number => '4007000000027',
expiration => '09/02',
cvv2 => '1234', #optional
amount => '49.95',
invoice_number => '100100',
customer_id => 'jsk',
+ email => 'jason@example.com',
first_name => 'Jason',
last_name => 'Kohles',
address => '123 Anystreet',
city => 'Anywhere',
state => 'UT',
zip => '84058',
+ country => 'US',
card_number => '4007000000027',
expiration => '09/02',
cvv2 => '1234', #optional
Use your transaction key in the password field.
-Unlike Business::OnlinePayment or pre-3.0 verisons of
+Unlike Business::OnlinePayment or pre-3.0 versions of
Business::OnlinePayment::AuthorizeNet, 3.1 requires separate first_name and
last_name fields.
method that returns the MD5 hash which is returned by the gateway.
Steve Simitzis contributed a patch for better compatibility with
-eProcessingNetwork's AuthorizeNet compatability mode.
+eProcessingNetwork's AuthorizeNet compatibility mode.
Michael G. Schwern contributed cleanups, test fixes, and more.
Thomas Sibley <trs@bestpractical.com> wrote B:OP:AuthorizeNet::AIM::ErrorCodes
which was borged and used to provide more descriptive error messages.
+Craig Pearlman <cpearlma@yahoo.com> sent in a patch to more accurately declare
+required fields for E-check transcations.
+
=head1 CONTRIBUTIONS AND REPOSITORY
Please send patches as unified diffs (diff -u) to (in order of preference):