.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .ie \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . nr % 0 . rr F .\} .el \{\ . de IX .. .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. . \" fudge factors for nroff and troff .if n \{\ . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] \fP .\} .if t \{\ . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff .if n \{\ . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} .if t \{\ . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' .ds 8 \h'\*(#H'\(*b\h'-\*(#H' .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] .ds ae a\h'-(\w'a'u*4/10)'e .ds Ae A\h'-(\w'A'u*4/10)'E . \" corrections for vroff .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' . \" for low resolution devices (crt and lpr) .if \n(.H>23 .if \n(.V>19 \ \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} .rm #[ #] #H #V #F C .\" ======================================================================== .\" .IX Title "Vend::Payment::PayflowPro 3pm" .TH Vend::Payment::PayflowPro 3pm "2011-03-09" "perl v5.14.2" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" Vend::Payment::PayflowPro \- Interchange support for PayPal Payflow Pro HTTPS POST .SH "SYNOPSIS" .IX Header "SYNOPSIS" .Vb 1 \& &charge=payflowpro \& \& or \& \& [charge mode=payflowpro param1=value1 param2=value2] .Ve .SH "PREREQUISITES" .IX Header "PREREQUISITES" .Vb 5 \& The following Perl modules: \& LWP \& Crypt::SSLeay \& HTTP::Request \& HTTP::Headers \& \& OpenSSL .Ve .PP PayPal's Payflow Pro \s-1HTTPS\s0 \s-1POST\s0 does \s-1NOT\s0 require the proprietary binary-only shared library that was used for the Verisign Payflow Pro service. .SH "DESCRIPTION" .IX Header "DESCRIPTION" The Vend::Payment::PayflowPro module implements the \fIpayflowpro()\fR payment routine for use with Interchange. It is compatible on a call level with the other Interchange payment modules \*(-- in theory (and even usually in practice) you could switch from a different payment module to PayflowPro with a few configuration file changes. .PP To enable this module, place this directive in \fIinterchange.cfg\fR: .PP .Vb 1 \& Require module Vend::Payment::PayflowPro .Ve .PP This \fImust\fR be in interchange.cfg or a file included from it. .PP \&\s-1NOTE:\s0 Make sure CreditCardAuto is off (default in Interchange demos). .PP The mode can be named anything, but the \f(CW\*(C`gateway\*(C'\fR parameter must be set to \f(CW\*(C`payflowpro\*(C'\fR. To make it the default payment gateway for all credit card transactions in a specific catalog, you can set in \fIcatalog.cfg\fR: .PP .Vb 1 \& Variable MV_PAYMENT_MODE payflowpro .Ve .PP It uses several of the standard settings from Interchange payment. Any time we speak of a setting, it is obtained either first from the tag/call options, then from an Interchange order Route named for the mode, then finally a default global payment variable. For example, the \f(CW\*(C`id\*(C'\fR parameter would be specified by: .PP .Vb 1 \& [charge mode=payflowpro id=YourPayflowProID] .Ve .PP or .PP .Vb 1 \& Route payflowpro id YourPayflowProID .Ve .PP or with only Payflow Pro as a payment provider .PP .Vb 1 \& Variable MV_PAYMENT_ID YourPayflowProID .Ve .PP The active settings are: .IP "id" 4 .IX Item "id" Your account \s-1ID\s0, supplied by PayPal when you sign up. Global parameter is \s-1MV_PAYMENT_ID\s0. .IP "secret" 4 .IX Item "secret" Your account password, selected by you or provided by PayPal when you sign up. Global parameter is \s-1MV_PAYMENT_SECRET\s0. .IP "partner" 4 .IX Item "partner" Your account partner, selected by you or provided by PayPal when you sign up. Global parameter is \s-1MV_PAYMENT_PARTNER\s0. .IP "vendor" 4 .IX Item "vendor" Your account vendor, selected by you or provided by PayPal when you sign up. Global parameter is \s-1MV_PAYMENT_VENDOR\s0. .IP "transaction" 4 .IX Item "transaction" The type of transaction to be run. Valid values are: .Sp .Vb 7 \& Interchange Payflow Pro \& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \& sale S \& auth A \& credit C \& void V \& settle D (from previous A trans) .Ve .Sp Default is \f(CW\*(C`auth\*(C'\fR. .PP The following should rarely be used, as the supplied defaults are usually correct. .IP "remap" 4 .IX Item "remap" This remaps the form variable names to the ones needed by PayPal. See the \f(CW\*(C`Payment Settings\*(C'\fR heading in the Interchange documentation for use. .IP "host" 4 .IX Item "host" The payment gateway host to use, to override the default. .IP "check_sub" 4 .IX Item "check_sub" Name of a Sub or GlobalSub to be called after the result hash has been received from PayPal. A reference to the modifiable result hash is passed into the subroutine, and it should return true (in the Perl truth sense) if its checks were successful, or false if not. The transaction type is passed in as a second arg, if needed. .Sp This can come in handy since, strangely, PayPal has no option to decline a charge when \s-1AVS\s0 or \s-1CSC\s0 data come back negative. .Sp If you want to fail based on a bad \s-1AVS\s0 check, make sure you're only doing an auth \*(-- \fBnot a sale\fR, or your customers would get charged on orders that fail the \s-1AVS\s0 check and never get logged in your system! .Sp Add the parameters like this: .Sp .Vb 1 \& Route payflowpro check_sub avs_check .Ve .Sp This is a matching sample subroutine you could put in interchange.cfg: .Sp .Vb 12 \& GlobalSub <{RESULT} = 112; \& $result\->{RESPMSG} = "The billing address you entered does not match the cardholder\*(Aqs billing address"; \& return 0; \& } \& EOR .Ve .Sp That would work equally well as a Sub in catalog.cfg. It will succeed if either the address or zip is 'Y', or if both are unknown. If it fails, it sets the result code and error message in the result hash using PayPal's own (otherwise unused) 112 result code, meaning \*(L"Failed \s-1AVS\s0 check\*(R". .Sp Of course you can use this sub to do any other post-processing you want as well. .SS "Troubleshooting" .IX Subsection "Troubleshooting" Try the instructions above, then enable test mode. A test order should complete. .PP Then move to live mode and try a sale with the card number \f(CW\*(C`4111 1111 1111 1111\*(C'\fR and a valid future expiration date. The sale should be denied, and the reason should be in [data session payment_error]. .PP If it doesn't work: .IP "\(bu" 4 Make sure you \*(L"Require\*(R"d the module in interchange.cfg: .Sp .Vb 1 \& Require module Vend::Payment::PayflowPro .Ve .IP "\(bu" 4 Check the error logs, both catalog and global. .IP "\(bu" 4 Make sure you set your account \s-1ID\s0 and secret properly. .IP "\(bu" 4 Try an order, then put this code in a page: .Sp .Vb 8 \& 
\&    [calcn]
\&        my $string = $Tag\->uneval( { ref => $Session\->{payment_result} });
\&        $string =~ s/{/{\en/;
\&        $string =~ s/,/,\en/g;
\&        return $string;
\&    [/calcn]
\&
.Ve .Sp That should show what happened. .IP "\(bu" 4 If all else fails, consultants are available to help with integration for a fee. You can find consultants by asking on the \&\f(CW\*(C`interchange\-biz@icdevgroup.org\*(C'\fR mailing list. .SH "NOTE" .IX Header "NOTE" There is actually nothing in the package Vend::Payment::PayflowPro. It changes packages to Vend::Payment and places things there. .SH "AUTHORS" .IX Header "AUTHORS" .Vb 7 \& Tom Tucker \& Mark Johnson \& Jordan Adler \& David Christensen \& Cameron Prince \& Mike Heins \& Jon Jensen .Ve