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
Preapproval API Operation
PreapprovalRequest Message
168 August 7, 2012 Adaptive Payments Developer Guide
paymentPeriod xs:string
(Optional) The payment period. It is one of the following values:
NO_PERIOD_SPECIFIED
DAILY – Each day
WEEKLY – Each week
BIWEEKLY – Every other week
SEMIMONTHLY – Twice a month
MONTHLY – Each month
ANNUALLY – Each year
pinType xs:string
(Optional) Whether a personal identification number (PIN) is required. It is
one of the following values:
NOT_REQUIRED – A PIN is not required (default)
REQUIRED – A PIN is required; the sender must specify a PIN when
setting up the preapproval on PayPal
requestEnvelope common:RequestEnvelope
(Required) Information common to each API operation, such as the language
in which an error message is returned.
returnUrl xs:string
(Required) The URL to which the sender’s browser is redirected after the
sender approves the preapproval on paypal.com.
Maximum length: 1024 characters
senderEmail xs:string
(Optional) Sender’s email address. If not specified, the email address of the
sender who logs in to approve the request becomes the email address
associated with the preapproval key.
Maximum length: 127 characters
startingDate xs:dateTime
(Required) First date for which the preapproval is valid. It cannot be before
today’s date or after the ending date.
displayMaxTotalAmount xs:boolean
(Optional) Whether to display the maximum total amount of this preapproval.
It is one of the following values:
TRUE – Display the amount
FALSE – Do not display the amount (default)
Field Description