From: fbriere Date: Tue, 14 Feb 2006 00:46:11 +0000 (+0000) Subject: s/Internet Secure/InternetSecure X-Git-Tag: V0_01~49 X-Git-Url: http://git.freeside.biz/gitweb/?p=Business-OnlinePayment-InternetSecure.git;a=commitdiff_plain;h=117b28d8b8364db55a208e9c6c9bdcc750becbcf s/Internet Secure/InternetSecure --- diff --git a/InternetSecure.pm b/InternetSecure.pm index 1280c88..58a6ce7 100755 --- a/InternetSecure.pm +++ b/InternetSecure.pm @@ -339,7 +339,7 @@ Business::OnlinePayment::InternetSecure - InternetSecure backend for Business::O Business::OnlinePayment::InternetSecure is an implementation of L that allows for processing online credit card -payments through Internet Secure. +payments through InternetSecure. See L for more information about the generic Business::OnlinePayment interface. @@ -348,7 +348,7 @@ Business::OnlinePayment interface. Object creation is done via L; see its manpage for details. The I processor option is required, and corresponds -to the merchant ID assigned to you by Internet Secure. +to the merchant ID assigned to you by InternetSecure. =head1 METHODS @@ -430,7 +430,7 @@ C (default) or C. =item taxes Taxes to be added automatically. These should not be included in B; -they will be automatically added by Internet Secure later on. +they will be automatically added by InternetSecure later on. Available taxes are C, C and C. Taxes can be combined by separating them with spaces, such as C. @@ -481,7 +481,7 @@ following: =item avs_response() / cvv2_response() -Results of the AVS and CVV2 checks. See the Internet Secure documentation for +Results of the AVS and CVV2 checks. See the InternetSecure documentation for the list of possible values. =item products_raw() @@ -532,9 +532,9 @@ be left undefined. =head2 Character encoding -Since communication to/from Internet Secure is encoded with UTF-8, all Unicode +Since communication to/from InternetSecure is encoded with UTF-8, all Unicode characters are theoretically available when submitting information via -B. (Further restrictions may be imposed by Internet Secure itself.) +B. (Further restrictions may be imposed by InternetSecure itself.) When using non-ASCII characters, all data provided to B should either be in the current native encoding (typically latin-1, unless it was modified