Developer's Guide
Table Of Contents
- Contents
- Preface
- XMLPay Overview
- XMLPay Syntax
- XMLPay Elements
- XMLPay Transaction Profiles
- XMLPay Examples
- ACH Sale Request
- Card Authorization Request
- Card Capture Request
- Card Credit Request
- Card Credit Reference Credit Request
- Card Force Capture Request
- Card Sale Request
- Card Secure Request
- Card Status Request
- Card Void Request
- Check Sale Request
- Customer IP
- Express Checkout Authorization Transaction
- IAVS Result Request
- Level 3 Invoice
- Line Item Sale Request
- Merchant Description and Merchant Service Number
- Processor Result
- Recurring Billing Profile
- Shipping Carrier and Shipping Method
- Transaction Update
- ValidateAuthentication Request
- ValidateAuthentication Response
- VerifyEnrollment Request
- VerifyEnrollment Response
- XMLPay Schemas
- XMLPay DTD
- Transaction Results
- Index
XMLPay Developer’s Guide 13
XMLPay Overview
XMLPay Messaging
1
XMLPayRequest
Payment transactions are submitted, one or more at a time, as XMLPayRequest documents.
The high-level structure of a request looks like this:
Merchant ID identifies the merchant of record for the transaction within the target payment
processing network. The merchant of record may be different from the submitting party in a
delegated processing model.
Transactions is the list of payment transactions to be processed. XMLPay supports up to 32
transactions per XMLPay document submission.
RequestAuth is an optional structure used to authenticate the submitting party, in the absence
of transport level authentication.
See Chapter 2, “XMLPay Syntax,” for a detailed description of request documents.
XMLPayResponse
Each XMLPayRequest submission produces a corresponding XMLPayResponse document
containing results for each submitted transaction request. The high-level structure of a
response looks like this:
<RequestData>
<MerchantId>
<Transactions>
<RequestAuth>
<XMLPayRequest>