
Gateway Developer Guide and Reference 07 January 2014 159
Payflow Header Parameters
Posting Transactions Directly Without the Payflow SDK
C
Host: payflowpro.verisign.com
X-VPS-REQUEST-ID: [See Required Payflow Headers]
X-VPS-CLIENT-TIMEOUT: 45
X-VPS-VIT-[See Integrator-Provided Data]
X-VPS-VIT-[See Integrator-Provided Data]
The following is an example of a transaction request header associated with a message in
name-value format. For XMLPay, it would follow the same format except the content-type
would be text/xml and the body of the request and response would contain the XML
document.
Name-Value Pair Transaction Request Body
The transaction request body contains the transaction information. The following is an
example transaction request body in name-value pair format.
TRXTYPE[1]=S&ACCT[16]=5105105105105100&EXPDATE[4]=0109&TENDER[1]=C&INVNUM[8
]=INV12345&AMT[5]=25.12&PONUM[7]=PO12345&STREET[23]=123 Main
St.&ZIP[5]=12345&USER[6]=jsmith&VENDOR[6]=jsmith&PARTNER[6]=PayPal&PWD[8]=t
esting1
NOTE: The bracketed numbers are length tags which allow you to use the special characters
of "&" and "=" in the value sent. See
“Using Special Characters In Values” on page 53
for more information.
The Request Body should NOT be URL-encoded. Pass the data as a standard data and use the
length tags if needed.
Transaction Response
The transaction response consists of a transaction response header and body.
Name-Value Pair Transaction Response Header
The following is an example transaction response header associated with a message in name-
value format.
Connection: close
Server: VPS-3.028.00
Date: Mon, 16 May 2005 22:48:06 GMT
Content-Type: text/name value
Commenti su questo manuale