php-doc-en/reference/pfpro/reference.xml
John Donagher 490a6cf9f4 pfpro: name the example a bit better
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@162416 c90b9560-bf6c-de11-be94-00142212c4b1
2004-06-30 20:48:21 +00:00

115 lines
3.4 KiB
XML

<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.10 $ -->
<reference id="ref.pfpro">
<title>Verisign Payflow Pro Functions</title>
<titleabbrev>Verisign Payflow Pro</titleabbrev>
<partintro>
<section id="pfpro.intro">
&reftitle.intro;
<para>
This extension allows you to process credit cards and other financial
transactions using Verisign Payment Services, formerly known as Signio
(<ulink url="&url.pfpro;">&url.pfpro;</ulink>).
</para>
<para>
When using these functions, you may omit calls to
<function>pfpro_init</function> and <function>pfpro_cleanup</function>
as this extension will do so automatically if required. However the
functions are still available in case you are processing a number of
transactions and require fine control over the library.
You may perform any number
of transactions using <function>pfpro_process</function> between the two.
</para>
<simpara>
These functions were added in PHP 4.0.2.
</simpara>
<note>
<para>
These functions only provide a link to Verisign Payment Services. Be sure
to read the Payflow Pro Developers Guide for full details of the required
parameters.
</para>
</note>
&note.no-windows.extension;
</section>
<section id="pfpro.requirements">
&reftitle.required;
<para>
You will require the appropriate SDK for your platform, which may be
downloaded <ulink url="&url.pfpro.download;">from within the manager
interface</ulink> once you have registered.
</para>
<para>
Once you have downloaded the SDK you should copy the files from
the <filename class="directory">lib</filename> directory of the
distribution. Copy the header file <filename>pfpro.h</filename>
to <filename class="directory">/usr/local/include</filename>
and the library file <filename>libpfpro.so</filename> to
<filename class="directory">/usr/local/lib</filename>.
</para>
<para>
Alternatively, you can extract the tarball from Verisign in one
location, and reference it during build configuration with the <option
role="configure">--with-pfpro[=DIR]</option> option:
<example>
<title>Explicit Configuration</title>
<programlisting role="shell">
<![CDATA[
tar -zxf pfpro_sunsparc.tar.gz -C /usr/local/
./configure --with-pfpro=/usr/local/verisign/payflowpro/sunsparc
]]>
</programlisting>
</example>
</para>
<note>
<para>
The last portion of the path specified in the example above, in this
case <filename class="directory">sunsparc</filename>, will vary based on
which architecture your Verisign SDK was built for.
</para>
</note>
</section>
&reference.pfpro.configure;
&reference.pfpro.ini;
<section id="pfpro.resources">
&reftitle.resources;
&no.resource;
</section>
<section id="pfpro.constants">
&reftitle.constants;
&no.constants;
</section>
</partintro>
&reference.pfpro.functions;
</reference>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"../../../manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->