Use Payouts API

You can use this pattern to send payouts to multiple recipients with a single API call.

You can send payouts to PayPal accounts and Venmo users.

Useful resource: PayPal API Executor

Important information

Ensure to review the following information before you send payouts.

Rate-limiting guideline

PayPal does not have a published rate-limiting policy. To ensure site security and stability for merchants, we might temporarily apply rate limiting if we see unusual or abusive traffic. We hold the rate limit until we know the traffic is safe. For Payouts API, we allow 400 POST requests per minute. If you get an HTTP 429 Unprocessable Entity - RATE_LIMIT_REACHED message, you have exceeded the rate limit. If this affects your integration, contact Merchant Technical Support. You can use webhooks for status updates instead of repeated API calls through polling and reuse OAuth 2.0 access tokens (till their expiry time) to avoid unnecessary requests.

Payouts SDK

You can use the PayPal Payouts SDK as an alternative to direct API integration. The SDK provides methods for authentication, request construction, and error handling in multiple programming languages. For more information, see Payouts SDK.

End-to-end workflow

Prerequisites

Complete all mandatory steps to get started.
Ensure your PayPal business account is set up.
Ensure to fund your business account.

Send payouts

You can use the procedures in this section to send payouts using the Payouts API.

1. Create payout batch

Use a valid access token and make a POST call to the /v1/payments/payouts endpoint.

You can use the PayPal-Request-Id header parameter to implement idempotency.

Include the following parameters:

Parameter	Action
`sender_batch_header` Required, object	Use the `sender_batch_id` within this header to prevent duplicate requests.
`items.amount` Required, object	To pay a recipient in their local currency, set the `currency` parameter to the local currency code. PayPal converts the payment to the specified currency and applies conversion fees. When you retrieve the payout details, the response shows the funding source, payout amount, fees, and other currency conversion details. For a sample request and response for cross-currency payouts, see Pay in local currency. Review country exclusions and restrictions before sending cross-currency payouts.
`items.receiver` Required, string	Pass the value that identifies the recipient. For example, user@example.com, +15555550123, @venmousername, PAYPALUSERID123
`items.recipient_type` string	For Venmo payouts, set the recipient type to `USER_HANDLE` and pass the handle in `items.receiver`. Possible values: `PHONE`, `EMAIL`, `USER_HANDLE`, `PAYPAL_ID` Default value: `EMAIL` If you set the recipient type in `sender_batch_header`, all items use that type unless you override it per item.
`items.recipient_wallet` string	Set the recipient wallet type. Possible values: Venmo: Set to `Venmo` to send a payout to a Venmo account. Use `PHONE`, `EMAIL`, or `USER_HANDLE` as the `recipient_type`. Venmo payouts are available only in the US. If the recipient does not have a Venmo account, they receive instructions to create one and claim the payout. PayPal: Set to `PayPal` to send a payout to a PayPal account. This is the default value.

For information on all parameters, see API reference.

curl -X POST https://api-m.sandbox.paypal.com/v1/payments/payouts \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ACCESS-TOKEN' \
  -H 'PayPal-Request-Id: REQUEST-ID' \
  -d '{
    "sender_batch_header": {
      "sender_batch_id": "Batch-123",
      "email_subject": "You have a payout!"
    },
    "items": [
      {
        "recipient_type": "EMAIL",
        "amount": {
          "value": "10.00",
          "currency": "USD"
        },
        "receiver": "recipient@example.com",
        "note": "Thank you for your business!",
        "sender_item_id": "ITEM-ID-1"
      },
      {
        "recipient_type": "PHONE",
        "amount": {
          "value": "10.00",
          "currency": "USD"
        },
        "receiver": "+15555550123",
        "note": "Thanks for using Venmo!",
        "sender_item_id": "ITEM-ID-2"
      }
    ]
  }'

A successful call returns a 201 Created response. The response includes the following parameters:

Parameter	Description	Further action
`batch_header.payout_batch_id`	Unique ID for the payout batch.	Use this ID to track or reference the batch in future API calls.
`batch_header.batch_status`	Status of the payout batch. Possible values: `SUCCESS`, `PENDING`, `PROCESSING`, `DENIED`, `CANCELED`.	PayPal may process the batch immediately or later. If the status is `PENDING`, check again later. To retry after a server error (such as HTTP `5xx`), send the request again with the same `sender_batch_id` within 30 days.
`batch_header.sender_batch_header`	Metadata of the payout batch that the sender originally provided in the payout request.	You can use it to match the response with your original request parameters.
`links`	URLs to get batch or item status.	Use these URLs to check the status of the batch or individual items.

2. Track status

After placing the payouts request, you can code your app to track the payout status by polling for updates or using webhooks.

Poll for updates

Use a valid access token and make a GET call to the /v1/payments/payouts/{ID} endpoint.
Path parameter: ID is the payout_batch_id returned in the Create payout batch response.

You can customize the request and choose which information to get in the response. See Get specific payouts details.

curl -X GET https://api-m.sandbox.paypal.com/v1/payments/payouts/MJ77GF8MQ2TF6 \
  -H 'Authorization: Bearer ACCESS-TOKEN' \
  -H 'Content-Type: application/json'

A successful call returns a 200 OK response. The response includes the following parameters:

Parameter	Description	Action
`batch_header.batch_status`	Status of the payout batch. Possible values: `SUCCESS`: PayPal has processed and completed the payout batch. `PENDING`: PayPal has queued the payout batch for processing. `PROCESSING`: PayPal is processing the payout batch. `DENIED`: PayPal has denied the payout requests. `CANCELED`: PayPal has canceled the payout batch.	If the status is `PENDING` or `PROCESSING`, check again later. If the status is `DENIED` or `CANCELED`, review the error message or reason and resubmit if needed. For real-time updates about payout events, use webhooks.
`batch_header.sender_batch_header`	Metadata of the payout batch that the sender originally provided in the payout request.	You can use it to match the response with your original request parameters.
`items`	Array of payout items with details for each item.	Use the `payout_item_id` to track the status of each payout item.
`links`	URLs to get batch or item status.	You can use them to poll for updates.

For information on all parameters, see API reference.

Use webhooks

Webhook events are external events that your app does not know about unless it receives event notifications. For example, a payout processed or completed is a webhook event. You can subscribe to such events and register a callback (listener) URL. When the event occurs, PayPal sends a notification to the registered callback URL. You can code your app to perform relevant actions based on the event notification it receives. To handle webhook events:

Review the list of webhook events for Payouts and select the events for your app to subscribe.
Subscribe to the selected webhook events through one of the following means:
- PayPal developer account: Log in to your account, go to App details page > Features > Webhooks, and subscribe to webhook events.
- Webhooks management API.
In your server-side app code, define a webhook handler that:
- Listens to the webhook event.
- Confirms receipt of the webhook event to PayPal.
- Verifies the source of the event notification.
- Performs further actions based on event data.

For more information, see Webhooks overview and Webhooks integration guide.

3. Handle errors

PayPal uses standard HTTP status codes to indicate the result of an API request:

2xx: Success
4xx: Incorrect request (for example, missing parameter)
5xx: PayPal server error

When an API call returns an error, the response includes a JSON body with the error details and HATEOAS links to help you diagnose and resolve issues. In your app code, include the logic to review the error code, message, and related links to determine the cause. Implement actions based on the error processing. For more information, see API responses.

4. Test

Use the PayPal sandbox environment to ensure your integration works as expected and meets all business and technical requirements before you go live. Testing your Payouts API integration involves:

Testing end-to-end payouts flow to verify money movement from your business account to your personal account (in case of PayPal payouts) or out of your business account (in case of Venmo payouts).
Testing API calls.

Test API calls: use test values and simulate responses

To simulate Payouts API responses, inject test values in the request payload or as a path parameter in the request URL. These methods allow you to trigger specific error responses without creating actual payouts.

Sample - test value in request payload
Sample - test value as path parameter

Trigger	Test value	Simulated error response
items[0]/note	ERRPYO002	`SENDER_EMAIL_UNCONFIRMED`

curl -X POST https://api-m.sandbox.paypal.com/v1/payments/payouts \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ACCESS-TOKEN' \
  -d '{
    "sender_batch_header": 
    {
      "sender_batch_id": "1524086406556",
      "email_subject": "This email is related to simulation"
    },
    "items": [
      {
        "recipient_type": "EMAIL",
        "receiver": "payouts-simulator-receiver@paypal.com",
        "note": "ERRPYO002",
        "sender_item_id": "15240864065560",
        "amount": 
        {
          "currency": "USD",
          "value": "1.00"
        }
      }
    ]
  }'

Path parameter	Test value	Simulated error response
/v1/payments/payouts/	ERRPYO015	`CLOSED_MARKET`

curl -X GET https://api-m.sandbox.paypal.com/v1/payments/payouts/ERRPYO015 \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ACCESS-TOKEN'

5. Go live

Set up live account.
Set up webhooks to get real-time notifications about payout events, such as completed or failed payouts.
Go live with your app.

Grow your business

Send payouts

Manage disputes

Analyze reports

Agentic commerce

Important information

Rate-limiting guideline

Payouts SDK

End-to-end workflow

Prerequisites

Send payouts

1. Create payout batch

2. Track status

Poll for updates

Use webhooks

3. Handle errors

4. Test

Test API calls: use test values and simulate responses

5. Go live

Grow your business

Send payouts

Manage disputes

Analyze reports

Agentic commerce

​Important information

​Rate-limiting guideline

​Payouts SDK

​End-to-end workflow

​Prerequisites

​Send payouts

​1. Create payout batch

​2. Track status

​Poll for updates

​Use webhooks

​3. Handle errors

​4. Test

​Test API calls: use test values and simulate responses

​5. Go live

Important information

Rate-limiting guideline

Payouts SDK

End-to-end workflow

Prerequisites

Send payouts

1. Create payout batch

2. Track status

Poll for updates

Use webhooks

3. Handle errors

4. Test

Test API calls: use test values and simulate responses

5. Go live