
Reference
Transaction message
10 August 2007 HTTPS Interface Developer’s Guide
N OTE: The examples below are in NVP format. XMLPay uses the same format as NVP except
that the content-type is text/xml and the body of both the request and response
contain the XML document.
Transaction request
The transaction request consists of a transaction request header and body.
Transaction request header
The following is an example of a transaction request header associated with a message in NVP
format:
Connect: close
Content-Length: ...
Content-Type: text/namevalue
Host: payflowpro.verisign.com
X-VPS-REQUEST-ID: 9a5534f7e4f3a5e5138b062e000b279a
X-VPS-CLIENT-TIMEOUT: 45
X-VPS-VIT-CLIENT-CERTIFICATION-ID: 33baf5893fc2123d8b191d2d011b7fdc
X-VPS-VIT-Integration-Product: MyApplication
X-VPS-VIT-Integration-Version: 0.01
Transaction request body
The transaction request body contains the transaction information. The following is an
example of a transaction request body in NVP 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[8]=PayPal&PWD[8]=testing1
The bracketed numbers are length tags that allow you to use the special characters & and = in
the value sent. See the Website Payments Pro Developer’s Guide for more information.
Transaction response
The transaction response consists of a transaction response header and body.
Transaction response header
The following is an example of a transaction response header associated with a message in
NVP format:
Connect: close
Server: VPS-3.033.00
X-VPS-REQUEST-ID: 9a5534f7e4f3a5e5138b062e000b279a
X-VPS-RESPONSE-ID:
V7sMZIeBBmrPMwNM7sZkPi3bLsaJ/QusF0LoEroT8/QD9d/AwUQbFYbKnhDOQ4HXRJ
Date: Mon, 16 May 2005 22:48:06 GMT
Content-Type: text/namevalue
Content-Length: 145
Comentarios a estos manuales