From cb47790217d4900740290e0b31c7b076c4a488f4 Mon Sep 17 00:00:00 2001 From: ivan Date: Mon, 28 Apr 2003 21:53:02 +0000 Subject: [PATCH] gratuitous TLD proliferation --- AuthorizeNet.pm | 12 ++++++------ 1 file 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 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 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 -- 2.11.0