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
Instant Payment Notifications
Preapproval Message Variables
260 August 7, 2012 Adaptive Payments Developer Guide
Preapproval Message Variables
PayPal generates an IPN message that contains information about a preapproval in response to
the Adaptive Payments Preapproval API operation.
fees_payer The payer of PayPal fees. Possible values are:
SENDER – Sender pays all fees (for personal, implicit simple/parallel
payments; do not use for chained or unilateral payments)
PRIMARYRECEIVER – Primary receiver pays all fees (chained payments
only)
EACHRECEIVER – Each receiver pays their own fee (default, personal and
unilateral payments)
SECONDARYONLY – Secondary receivers pay all fees (use only for chained
payments with one secondary receiver)
trackingId The tracking ID that was specified for this payment in the
PaymentDetailsRequest message.
preapproval_key The preapproval key returned after a PreapprovalRequest, or the
preapproval key that identifies the preapproval key sent with a PayRequest.
reason_code Whether this transaction is a chargeback, partial, or reversal. Possible values
are:
Chargeback Settlement – Transaction is a chargeback
Admin reversal – Transaction was reversed by PayPal administrators
Refund – Transaction was partially or fully refunded
Variable Description
transaction_type The type of transaction. For a preapproval, this variable returns Adaptive
Payment Preapproval.
NOTE: If this variable is set to Adaptive Payment Pay or Adjustment,
refer to the Pay Message Variable section.
preapproval_key The preapproval key returned after a PreapprovalRequest.
approved Whether the preapproval request was approved. Possible values are:
true – The preapproval was approved
false – The preapproval was denied
cancel_url The URL to which the sender’s browser is redirected if the sender decides to
cancel the preapproval as requested. Use the preapproval key to identify the
payment as follows: preapprovalKey=${preapprovalKey}
current_number_of_paymen
ts
The current number of payments made for this preapproval.
Variable Description