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 Syntax
The XMLPayRequest Document (Transactions)
2
16 XMLPay Developer’s Guide
(Transaction)+
</Transactions>
</RequestData>
(RequestAuth)?
</XMLPayRequest>
Transaction
XMLPay supports up to 32 transactions per XMLPay document submission.
<Transaction Id=? CustRef=?>
(Authorization|Capture|Sale|Credit|Void|
ForceCapture|RepeatSale|GetStatus|
VerifyEnrollment|ValidateAuthentication|
TransactionUpdate|SetExpressCheckout|
GetExpressCheckout|DoExpressCheckout)
</Transaction>
Authorization Transaction
An authorization transaction verifies the availability of funds and reserves them for later
capture.
Attribute Description
Vendor Identifies the merchant of record for the transaction within the target
payment processing network. In a delegated processing model, the
merchant of record may be different from the submitting party.
Partner Identifies the submitting party.
Transaction Defined on page 16. XMLPay supports up to 32 transactions per
XMLPay document submission.
RequestAuth Defined on page 21.
Timeout The value of this attribute is ignored.
Attribute Description
Id
Optional attribute that tracks the transaction through the payment-
processing network. The submitting merchant generates this transaction
identifier, which must be unique among all transactions submitted by that
merchant.
Id need not be globally unique across merchants, since the payment-
processing network interprets it within the context of the merchant
associated with the transaction. If an Id attribute is provided in a
transaction, it will be included in the matching TransactionResult in the
resultant XMLPayResult.
Similarly, CustRef is a merchant-generated ID identifying a specific
customer of this merchant and associating it with this transaction.