PHP  
downloads | documentation | faq | getting help | mailing lists | | php.net sites | links 
search for in the  
previouspdf_translatepfpro_cleanupnext
Last updated: Tue, 09 Jul 2002
view the printer friendly version or the printer friendly version with notes or change language to English | Brazilian Portuguese | Chinese | Czech | Dutch | Finnish | German | Hungarian | Italian | Japanese | Korean | Polish | Romanian | Russian | Spanish | Swedish | Turkish

LXXVII. Paiement par Verisign

Cette extension vous permet d'effectuer des transactions avec des cartes de cr�dits en utilisant les services Verisign Payment Services, anciennement connu sous le nom de Signio ().

Ces fonctions sont utilisables d�s que PHP a �t� compil� avec l'option --with-pfpro[=DIR]. Vous devez aussi utiliser le SDK appropri� sur votre plate-forme : il est disponible , une fois que vous vous �tes inscrit. Si vous avez l'intention d'utiliser cette extension sur un serveur web SSL ou avec d'autres composants SSL (tels que l'extension CURL et SSL) vous DEVEZ utiliser le SDK beta.

Une fois que vous avez t�l�charg� le SDK vous devez copier les fichiers depuis le dossier lib de la distribution. Copier le fichier d'en-t�tes pfpro.h dans /usr/local/include et la librairie libpfpro.so dans /usr/local/lib.

Lorsque vous utilisez ces fonctions, vous pouvez omettre d'appeler les fonctions pfpro_init() et pfpro_cleanup() : l'extension se chargera de le faire automatiquement. Cependant, elles sont toujours disponibles au cas o� vous auriez un grand nombre de transaction � traiter, ou que vous souhaiteriez un contr�le plus fin de la librairie. Vous pouvez effectuer autant de transaction que vous le souhaitez avec pfpro_process() lors d'une connexion.

Ces fonctions ont �t� ajout�e en PHP 4.0.2.

Note�: Ces fonctions ne font que fournir un acc�s aux services Verisign Payment Services. Assurez-vous bien de lire le "Payflow Pro Developers Guide" pour plus de d�tails sur les param�tres.

Table des mati�res
pfpro_cleanup -- Eteint la librairie Payflow Pro
pfpro_init -- Initialise la librairie Payflow Pro
pfpro_process_raw -- Envoie une transaction brute � Payflow Pro
pfpro_process -- Effectue une transaction avec Payflow Pro
pfpro_version -- Lit le num�ro de version de Payflow Pro
User Contributed Notes
Paiement par Verisign
add a note about notes
[email protected]
29-Nov-2000 03:39

You can always vfork (backticks, exec, whatever) to call the pfpro executable.

The basic idea is that that is a dangerous and stupid way to use a product for which an SDK is freely available. The problem is that Verisign's (closed source) SDK uses its own SSL implementation that conflicts with OpenSSL (and probably others) when it is linked into Apache. This is crippling both to the usefulness of the SDK and hence that of this module.

You are encouraged to contact Verisign and urge them to provide a better SDK, an open-source SDK, or the implementation details so we can write our own.

[email protected]
27-Jun-2001 03:57

If you decide not to use the pfpro functions for any one of several reasons and instead call the pfpro binary with the exec command please note that you must use the putenv function to set the environment variable PFPRO_CERT_PATH that is referred to in the PayFlowPro Developers Guide (see page 12). Otherwise verisign with always return a -31 error - certificate not found.
[email protected]
29-Aug-2001 02:28

Please also be aware that forking will allow any person with the access to the ps command to potentially see ALL account information: user, password, partner, credit card number, etc.

The preferred way to use the module is through the now-fixed extension.

[email protected]
02-Dec-2001 09:01

[Ed Note:
If server is unavailable, file can be downloaded from

[email protected]]

You can download the complete php_pfpro.inc and php_pfpro_com.inc files from my FTP site. They are WinZip'd.


[email protected]
08-Feb-2002 11:28

I was having problems with the PHP configuration recognizing that I had a recent version of the PFPRO SDK.

I found a bug in the config.m4 file for the pfpro extension as follows -

***********

PFPRO_VERSION3=`nm $PFPRO_LIB_DIR/$PFPRO_LIB | awk '{print $3}' | grep ^pfpro > /dev/null && echo 1 || echo 0`
PFPRO_VERSION2=`nm $PFPRO_LIB_DIR/$PFPRO_LIB | awk '{print $3}' | grep ^PN > /dev/null && echo 1 || echo 0`

************

When I issued the above 'nm' statement from the UNIX command line, two bugs were apparent: 1) the awk was looking at column 3, but should have been looking at column 8 instead and 2) the caret in the grep statement was causing the command to return a failure.

Here is the corrected syntax for the config.m4 file:
# Changed col to 8 from 3, removed caret from grep stmts
PFPRO_VERSION3=`nm $PFPRO_LIB_DIR/$PFPRO_LIB | awk '{print $8}' | grep pfpro > /dev/null && echo 1 || echo 0`
PFPRO_VERSION2=`nm $PFPRO_LIB_DIR/$PFPRO_LIB | awk '{print $8}' | grep PN > /dev/null && echo 1 || echo 0`

Once you've update the config.m4 file, you'll need to run ./buildconf before running your configure statement.

Make it a point to run ./buildconf and make distclean before configuring and building PHP. It could save you a lot of heartache.

Hope this helps.

[email protected]
27-Jun-2002 06:53

From Verisign's VPS support:

The Payflow Pro support in PHP must be configured/compiled as a shared object. In order to enable Payflow Pro support in PHP as a shared object, pass the following switch to the PHP ./configure script:

[root@localhost] # ./configure --with-pfpro=shared,/path/to/pfpro

The directory specified by /path/to/pfpro must contain *both* the libpfpro.so and pfpro.h files included in the Payflow Pro SDK (usually in the lib/ and/or bin/ subdirectories of the SDK), or the ./configure step will fail.


Versions of PHP prior to 4.0.2 did not contain the pfpro support functions. See for the latest stable version of PHP.

It appears to be impossible to use older versions of Apache in this sort of setup. Version 1.3.12 or greater are known to work, 1.3.9 may work, older versions reportedly do not work. See for the latest stable version of Apache.

The version of mod_ssl is closely tied to the version of Apache being used; there are sometimes multiple versions of mod_ssl available for a single version of Apache. See for the latest version of mod_ssl.

add a note about notes
previouspdf_translatepfpro_cleanupnext
Last updated: Tue, 09 Jul 2002
show source | credits | stats | mirror sites
Copyright © 2001, 2002 The PHP Group
All rights reserved.
This mirror generously provided by:
Last updated: Sat Aug 31 06:19:44 2002 CEST