PayPal Payflow Pro - 2007 Guia do Utilizador descarregar pdf (Página 19)

Payflow Pro Developer’s Guide 19

Performing Credit Card Transactions

How To Format a Transaction

z Spaces are allowed in values.

z Enclose the PARMLIST in quotation marks (“”).

z Quotation marks (“”) are not allowed within the body of the PARMLIST.

z Separate all name-value pairs in the PARMLIST using an ampersand (&).

z Set the VERBOSITY transaction parameter to MEDIUM (default is LOW) if you want the

response to return more detailed information. For details on VERBOSITY, see

Appendix B, “Verbosity: Viewing Processor-Specific Transaction Results

Using Special Characters in Values

Because the ampersand (&) and equal sign (=) characters have special meanings in the

PARMLIST, name-value pairs like the following examples are not valid:

NAME=Ruff & Johnson

COMMENT1=Level=5

To use special characters in the value of a name-value pair, use a length tag. The length tag

specifies the exact number of characters and spaces that appear in the value. The following

name-value pairs are valid:

NAME[14]=Ruff & Johnson

COMMENT1[7]=Level=5

N OTE: Quotation marks (“”) are not allowed even if you use a length tag.

How To Format a Transaction

For details on how to format a transaction based on the above information, refer to the

examples and the supporting documentation provided with your SDK.

Parameters Used in Credit Card Transactions

All credit card processors accept the parameters listed in Table 3.2 (required and optional

parameters are noted). “Values Required by All Transaction Types” on page 23 lists the

parameters required for each transaction type.

N OTE: Some processors require yet additional parameters. See the following sections:

z Appendix A, “Processors Requiring Additional Transaction Parameters,” provides

additional parameter requirements for non-PayPal processors.

1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 73 74

Sem comentários

PayPal Payflow Pro - 2007 Guia do Utilizador Página 19