Business::OnlinePayment::AuthorizeNet uses Authorize.Net's "Advanced
Integration Method (AIM) (formerly known as ADC direct response)" and
"Automatic Recurring Billing (ARB)", sending a username and password (or
-transaction_key) 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.
+transaction key as 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
to avoid overriding admin settings. (closes: CPAN#51501)
- Patch from Josh Rosenbaum to fix encapsulation problems. Thanks!
(closes: CPAN#15210)
+ - Clarified documentation wrt transaction key (closes: CPAN#23753)
3.20 Wed Jun 18 16:46:10 PDT 2008
- Patch from Erik Hollensbe <erikh@opensourcery.com> implementing