
XMLPay Developer’s Guide 47
3
XMLPay Elements
The following tables define the existing Payflow SDK parameters (name/value pairs) and their
XMLPay equivalent. Some parameters cannot be processed by specific processors. For details
on what your processor can process, see Payflow Pro Developer’s Guide.
If you are developing applications that use the Recurring Billing Service, see Recurring
Billing Service User’s Guide.That document provides detailed information about Payflow
SDK parameters specific to Recurring Billing.
NOTE:ExtData is an optional XMLPay element for including parameter data not supported by
the schema you are using. Place the data at the appropriate element level in the
XMLPay hierarchy. If you can’t find or are unsure of the appropriate location, place the
data in the Invoice element. See the examples in “Express Checkout Authorization
Transaction” on page 84.
General Transaction Parameters
The following are general parameters accepted in Payflow SDK transactions.
TABLE 3.1 Retail credit card transaction parameters
Payflow SDK
Parameter Description XMLPay Element
COMMCARD Type of commercial card account number sent. Card
→CommercialCard
COUNTRYCODE Destination country code. (See the appendix
entitled “ISO Country Codes” in the Payflow
Pro Developer’s Guide.)
ShipTo
→Address→Country
COMPANYNAME Billing country code BillTo
→Address→Company
CUSTIP IP address of customer Invoice
→CustIP
ECI Values returned from Buyer Auth transaction Card
→BuyerAuthResult→ECI
MERCHDESCR Description of product. Invoice
→MerchantDescription
MERCHSVC Merchant telephone number, including area
code (XXX-XXX-XXXX)
Invoice
→MerchantServiceNum
ORDERDATE Date of invoice Invoice
→Date
RECURRING Recurring transaction? Invoice
→Recurring
UPDATEACTION Update action to take TransactionUpdate
→Action
VERBOSITY Verbosity level of response desired Transaction
→Verbosity
Comentarios a estos manuales