Developer's Guide
Table Of Contents
- Adaptive Payments Developer Guide
- Contents
- What’s New?
- Introducing Adaptive Payments
- Adaptive Payments Actors and Objects
- Simple, Parallel, and Chained Payments
- Payment Approval
- Adaptive Payments Service Permissions
- Explicit Approval Payment Flow
- Preapproved Payments Flow
- Implicit Approval Payments Flow
- Embedded Payments
- Embedded Payment Flow Presentations
- Kinds of Embedded Payments
- Embedded Payments Implementation Basics
- Embedded Payment Experience
- Preapprove Future Payments Checkbox
- Shipping Address Information
- Embedded Payment Experience
- Setting Up Web Pages to Invoke the Embedded Payment Flow Using a Lightbox
- Setting Up Web Pages to Invoke the Embedded Payment Flow Using a Minibrowser
- Displaying and Collecting Shipping Addresses
- Guest Payments
- Fee Payment Configuration
- Getting Started
- Pay API Operation
- PaymentDetails API Operation
- ExecutePayment API Operation
- GetPaymentOptions API Operation
- SetPaymentOptions API Operation
- Preapproval API Operation
- PreapprovalDetails API Operation
- CancelPreapproval API Operation
- ConvertCurrency API Operation
- Refund API Operation
- GetFundingPlans API Operation
- GetShippingAddresses API Operation
- Adaptive Payment Commands and Redirects
- Instant Payment Notifications
- Older Versions of the Adaptive Payments API
- 1.8.0 Features
- 1.7.0 Features
- 1.6.0 Features
- New API Operations for Version 1.6.0
- Changes to PayRequest Fields for Version 1.6.0
- Changes to PayResponse Fields for Version 1.6.0
- Changes to ExecutePaymentRequest Fields for Version 1.6.0
- Changes to GetPaymentOptionsResponse Fields for Version 1.6.0
- Changes to SetPaymentOptionsRequest Fields for Version 1.6.0
- Changes to PreapprovalRequest Fields for Version 1.6.0
- Changes to Address Structure for Version 1.6.0
- Changes to DisplayOptions Structure for Version 1.6.0
- New CurrencyConversion Structure for Version 1.6.0
- New InvoiceData Structure for Version 1.6.0
- New InvoiceItem Structure for Version 1.6.0
- New SenderOptions Structure for Version 1.6.0
- New SenderIdentifier Structure for Version 1.6.0
- New AccountIdentifier Structure for Version 1.6.0
- New ReceiverOptions Structure for Version 1.6.0
- New ReceiverIdentifier Structure for Version 1.6.0
- Additional Error Messages for Version 1.6.0
- 1.5.0 Features
- 1.4.0 Features
- 1.3.0 Features
- 1.2.0 Features
- 1.1.0 Features
- Revision History
- Index
Adaptive Payments Developer Guide August 7, 2012 85
Pay API Operation
PayRequest Message
PhoneNumberType Fields
paymentType xs:string
(Optional) The transaction type for the payment.
Allowable values are:
GOODS – This is a payment for non-digital goods
SERVICE – This is a payment for services (default)
PERSONAL – This is a person-to-person payment
CASHADVANCE – This is a person-to-person payment for a cash advance
DIGITALGOODS – This is a payment for digital goods
BANK_MANAGED_WITHDRAWAL – This is a person-to-person payment for
bank withdrawals, available only with special permission.
NOTE: Person-to-person payments are valid only for parallel payments that
have the feesPayer field set to EACHRECEIVER or SENDER.
paymentSubType xs:string
(Optional) The transaction subtype for the payment.
phone common:PhoneNumberType
A type to specify the receiver’s phone number. The PayRequest must pass
either an email address or a phone number as the payment receiver.
primary xs:boolean
(Optional) Whether this receiver is the primary receiver, which makes the
payment a chained payment. You can specify at most one primary receiver.
Omit this field for simple and parallel payments.
Allowable values are:
true – Primary receiver
false – Secondary receiver (default)
Field Description
countryCode xs:string
(Required) Telephone country code.
phoneNumber xs:string
(Required) Telephone number.
extension xs:string
(Optional) Telephone extension.
Field Description