10610

Returned from the following PayPal NVP/SOAP APIs:

• SetExpressCheckout
• GetExpressCheckoutDetails
• DoExpressCheckoutPayment
• DoUATPExpressCheckoutPayment
• GetBillingAgreementCustomerDetails
• CreateBillingAgreement

The Express Checkout token ("EC-" token) value passed in the NVP/SOAP API request was not recognized by PayPal. This can happen if:

• The token is invalid
• There is a typo or formatting error in the token
• The API caller’s account lacks the necessary permissions to access the receiver account’s resource IDs

As a result, the API request fails.

For Billing Agreement-related API calls—such as GetBillingAgreementCustomerDetails or CreateBillingAgreement—this error indicates an invalid Billing Agreement creation ID ("BA-" ID).

The payment is not initiated, or the Billing Agreement is not created as the API call failed. As the transaction doesn’t go through, the customer sees an impact, and they can drop-off from the checkout journey. This can lead to a poor customer experience, conversion rate decline, and potentially lost sales if the issue is not resolved promptly.

• Verify correct token: Review the token returned in the response of previous API calls in the flow, and ensure the right one is being used to make the current request.
• Check account permissions: If your account is an API actor account making transaction requests on a different account’s behalf, then ensure the other business account has granted your API caller account the necessary permissions to use the resources.
• Retry with new token: You may retry by invoking the payment flow again, getting a fresh token, and processing the payment.

The NVP/SOAP API integration method is deprecated. You can find more information about our latest integrations from the following resources:

• REST APIs
• PayPal Checkout
• PayPal Developer homepage

• See the Developer Portal for PayPal NVP/SOAP API.
• To see a complete list of error codes.