diff options
author | ivan <ivan> | 2009-11-24 17:56:33 +0000 |
---|---|---|
committer | ivan <ivan> | 2009-11-24 17:56:33 +0000 |
commit | f6147dc03e8036f80279998dbbddc51edf6c35cb (patch) | |
tree | ad1355b9435d3f527a7853d92c0eb79c1b99a439 /AuthorizeNet.pm | |
parent | ef5179790b43cdbbc54601d43dedec645c62d95d (diff) |
Clarified documentation wrt transaction key (closes: CPAN#23753)
Diffstat (limited to 'AuthorizeNet.pm')
-rw-r--r-- | AuthorizeNet.pm | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/AuthorizeNet.pm b/AuthorizeNet.pm index 70410d6..4688668 100644 --- a/AuthorizeNet.pm +++ b/AuthorizeNet.pm @@ -368,10 +368,11 @@ last_name fields. 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 |