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 259
Instant Payment Notifications
Pay Message Variables
transaction[n].status_fo
r _sender_txn
The transaction status, where [n] is a number from 0 to 5. For simple single-
receiver payments, this number will be 0. Numbers larger than 0 indicate the
payment to a particular receiver in chained and parallel payments.
Possible values are:
COMPLETED – The sender’s transaction has completed
PENDING – The transaction is awaiting further processing
CREATED – The payment request was received; funds will be transferred
once approval is received
PARTIALLY_REFUNDED– Transaction was partially refunded
DENIED – The transaction was rejected by the receiver
PROCESSING – The transaction is in progress
REVERSED – The payment was returned to the sender
REFUNDED – The payment was refunded
FAILED – The payment failed
transaction[n].refund_id The identification number for the refund
transaction[n].refund_am
ount
The amount that was refunded.
transaction[n].refund_ac
count_charged
The email address of the debit account of the refund.
transaction[n].receiver The receiver’s email address for the transaction
transaction[n].invoiceId The invoice number for this transaction
transaction[n].amount The payment amount of the transaction
transaction[n].is_primar
y_receiver
Whether there is a primary receiver for this transaction, which indicates
whether the transaction is a chained payment.
Possible values are:
true – There is a primary receiver (chained payment)
false – There is no primary receiver (simple or parallel payment)
return_url The URL to which the sender’s browser is redirected after approving a
payment on paypal.com. Use the pay key to identify the payment as follows:
payKey=${payKey}.
cancel_url The URL to which the sender’s browser is redirected if the sender cancels the
approval for a payment on paypal.com. Use the pay key to identify the
payment as follows: payKey=${payKey}.
ipn_notification_url The URL to which all IPN messages for this payment are sent.
pay_key The pay key that identifies this payment. This is a token that is assigned by the
Pay API after a PayRequest message is received and can be used in other
Adaptive Payments APIs as well as the cancelURL and returnURL to
identify this payment. The pay key is valid for 3 hours.
memo A note associated with the payment.
Variable Description