diff options
author | ivan <ivan> | 2003-04-28 21:53:02 +0000 |
---|---|---|
committer | ivan <ivan> | 2003-04-28 21:53:02 +0000 |
commit | cb47790217d4900740290e0b31c7b076c4a488f4 (patch) | |
tree | 4c81d7d4773fe38b87d8d4dae8164b2646c480e9 /AuthorizeNet.pm | |
parent | 0a22d2dbe888f956e8ffc3e66ee390a2877c8a62 (diff) |
gratuitous TLD proliferation
Diffstat (limited to 'AuthorizeNet.pm')
-rw-r--r-- | AuthorizeNet.pm | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/AuthorizeNet.pm b/AuthorizeNet.pm index 82c2be1..b69d3f0 100644 --- a/AuthorizeNet.pm +++ b/AuthorizeNet.pm @@ -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 |