PayPal Merchant API Release Notes - Version 92.0
This release note addresses the API operations within the PayPal Merchant API WSDL and associated schemas:
The document covers changes to the Merchant APIs, which include:
- Express Checkout
- Direct Payment
- Recurring Payments
- Mass Pay
- Button Manager
- PayPal Payments Standard
- Website Payments Pro
No new announcements.
These products are affected by this release:
- Express Checkout
- PayPal Payments Pro - see Express Checkout section for related release notes
- New Calls
- Changed Calls
- Schema Changes
- New Features
- Changed Functionality
- Additional Documentation Updates
For a current list of known issues, go to the PayPal Notifications page.
Express Checkout - New Calls
No new calls in this release.
Express Checkout - Changed Calls
Express Checkout - Schema Changes
|Name||Part of Schema||Type of Change|
Express Checkout - New Features
Idempotency via MsgSubID
Idempotency has been added to the request and response for following API calls:
Idempotency is useful in cases where a request has failed or if you are unsure about the results of an original request. It also helps to eliminate duplicate requests. A request sent with a previously accompanying MsgSubID (Message Submission ID) will return with latest status of of the previous request that used the same MsgSubID. In contrast, a request with no accompanying MsgSubID will instead duplicate the request.
Scenarios in which idempotency come into play:
- In an API request sent with a MsgSubID times out, a client application can retry the original request using the accompanying MsgSubID. If the request has finished processing, PayPal then provides the latest status of the request. If the request is still or returns a 11607 warning code (Duplicate request for specified Message Submission ID).
- If a client application sends two API requests with same MsgSubID at the same time, PayPal processes the first request and the other may fail with 11604 error code (Request for Message Submission ID already in progress).
Note: For DoExpressCheckoutPayment, you can use the token in place of the MsgSubID. For multiple payments, a combination of the token and PaymentRequestID should be used in place of the MsgSubID.
- The MsgSubID must be unique for each request and API call type (e.g. DoAuthorization, DoCapture).
- PayPal recommends using the UUID standard for assigning MsgSubIDs to your requests.
- Idempotency only applies when the original request was successful. If the original request results in an error, the original request is not saved.
- PayPal reserves the right to expire a MsgSubID after 13 days.
- PayPal provides the status of a request at the current time and not the status of the initial request. Take for example, an initial request that makes a payment (status is Complete). The payment is later refunded. If the original request with the original MsgSubId is resubmitted, the response will indicate that the payment status is Refunded.
- The result in subsequent responses to an original transaction will be different from the original response and will return
Express Checkout - Changed Functionality
None for this release.
Express Checkout - Additional Documentation Updates
Correction to TransactionSearch API Reference Documentation
The following TransactionSearch response field has been updated with additional values that were missing:
- Type (SOAP), L_TYPEn (NVP)
Correction to DoExpressCheckout API Reference Documentation
The description for the following DoExpressCheckout response field has been updated with clarification on on the redirect URL:
- SuccessPageRedirectRequested (SOAP, NVP)