Skip to main content
Create and manage customizable payment resources using the Payment Links and Buttons API. A payment link is a shareable URL that takes customers to a PayPal‑hosted payment page where they can complete purchases securely. Each payment link is unique to a product but can be shared and reused multiple times. Customers who open a payment link see a PayPal-hosted checkout page displaying product details such as name, price, description, variants, shipping fees, and taxes. The Payment Links and Buttons API helps you:
  • Accept payments through PayPal-hosted links.
  • Offer multiple payment methods, including PayPal, Venmo, Pay Later, Apple Pay, and major credit and debit cards.
  • See transactions happen in real time. PayPal sends email notifications to both buyers and merchants.
  • Protect eligible online sales with PayPal Seller Protection.
The following is a list of endpoints.

Eligibility

  • This API is available in all countries where PayPal operates.
  • See Countries and Currencies for a list of supported currencies.

Prerequisites

How it works

The Payment Links and Buttons API helps merchants create and manage PayPal-hosted checkout experiences.
  1. Obtain an OAuth access token using your PayPal Business account credentials.
  2. Use the API to create payment links that define items, pricing, and return URLs.
  3. Share the generated links directly or embed them on your website. The API doesn’t currently support button code snippets, but you can create your own embeddable button using the link.
  4. Buyers select the link to complete payment securely through PayPal’s hosted checkout page. The payment is completed in real time.
  5. Both merchants and buyers receive an email notification for each transaction. Merchants can view all transactions in their PayPal Business account. PayPal customers can view transaction details in their PayPal accounts.
  6. You can retrieve, update, or delete existing payment links as needed.

Endpoints

The following table lists the available endpoints for managing payment links.

Product fields

Payment Links use product information and prices to showcase to buyers what your business is selling. To create a payment link, create a product with the following information.

Use cases

See how to create payment links that address common scenarios and requirements.

Sample POST requests

The following are different sample use cases of the POST API that demonstrate how to create payment links for various scenarios. Create a payment link for a wireless mouse priced at $39.99 USD. After completing payment, customers are redirected to the specified return URL, such as https://merchant.example.com/thank-you.
Create a payment link for a T-shirt priced at $20.00 USD. The Color dimension is marked as primary and includes two options: White and Black. The Size dimension is secondary and includes 11oz and 15oz options. The base price of $20.00 applies to all variant combinations.
Create a payment link for a T-shirt with variant-specific pricing. The Color dimension is marked as primary and includes two options: White priced at $19.00 USD, and Black priced at $20.00 USD. The Size dimension is secondary and includes 11oz and 15oz options, with no price difference. No base unit_amount shows up in the payload because each color variant specifies its own price.
Create a payment link for a coffee mug priced at $12.00 USD with tax and shipping calculations. The taxes and shipping arrays specify type: PREFERENCE and value: PROFILE to apply the merchant’s preconfigured tax and shipping settings from their PayPal account. Merchants must configure these tax and shipping settings in their PayPal account for this feature to work.

Create payment links and buttons (POST)

Create a buy now payment URL that links directly to a PayPal-hosted checkout experience. Use this endpoint to generate shareable payment URLs or various purchase flows. Endpoint: POST /v1/checkout/payment-resources

Request

The following sample request includes these key settings:
  • Creates a reusable payment link for Premium Wireless Headphones with Noise Cancellation.
  • Includes variant-specific pricing for four primary colors.
  • Includes three variants where the color dimension is marked as primary and includes four options. The other two variants are Warranty, which has three options, and Package Type, which has two options. These variants do not affect pricing.
  • Adds an 8.25% tax, applies a flat shipping rate, and requires customers to provide a shipping address.
  • Provides customers with the option to add a gift message at checkout.
  • Sets a maximum order quantity of 10 units.
  • Redirects customers to a return URL after the transaction.

Response

The following response contains a fixed-price payment resource link with product details and variants. The API returns HTTP status code 201 Created and content type application/json.
Retrieve a paginated list of all payment links created by the merchant. This endpoint supports filtering and pagination through query parameters, including filtering by link status and tags. Endpoint: GET /v1/checkout/payment-resources

Request

The following sample request includes these key details:
  • Sends a GET request to list payment links you created.
  • Uses the page_size parameter to limit results. For example, setting page_size=2 returns two payment links per page.
  • Includes an OAuth 2.0 Bearer token for authentication.
  • Headers set to Accept: application/json and Content-Type: application/json.
  • Uses a page_token from the response to retrieve additional pages.

Response

The following sample response includes these key details:
  • Returns a resources array with two payment links.
  • The first payment link is for a Wireless Mouse, priced at $29.99 USD. This link is active, set to BUY_NOW, and is reusable.
  • The second payment link is for a Wireless Keyboard, priced at $99.99 USD. It has the same status, type, and reusability settings as the first link.
  • Each resource includes a shareable payment_link URL, metadata such as ID, product name, price, status, type, and creation timestamp, and a links array with HATEOAS actions to retrieve, update, edit, delete, or access the payment link.
  • The response also includes a top-level links array for navigation, with a self link referencing the current request and a next link with a page_token for retrieving additional results.
Get the details of a specific payment link by its unique ID. This endpoint returns all available metadata, including payment status, links, reusable type, and line item details for the requested payment link. Endpoint: GET /v1/checkout/payment-resources/{id}

Request

The following sample request includes these key details:
  • Includes the complete details for a specific payment link identified by the resource ID PLB-X7MNK9P2QR8T using a GET request.
  • Uses an OAuth 2.0 Bearer token in the Authorization header to authenticate the request.
  • Sets the Accept and Content-Type headers to application/json for proper formatting.

Response

The following response contains the complete details for a single fixed-price payment link. The API returns status code 200 OK and content type application/json. The following sample response includes these key details:
  • Returns the full details of payment link PLB-X7MNK9P2QR8T.
  • The payment link is active, set to BUY_NOW, and configured for multiple uses.
  • Shows a product called Wireless Mouse, priced at $29.99 USD
  • The link was created on 2025-11-29T13:13:25.832592Z with integration mode LINK.
  • After payment, customers are redirected to https://merchant.example.com/thank-you that is specified by return_url.
  • Includes a shareable payment link URL at https://www.paypal.com/ncp/payment/PLB-X7MNK9P2QR8T.
  • Provides a links array with HATEOAS actions: retrieve the link details (self), update the link (replace), delete the link (delete), and access the customer-facing payment page (payment_link).
Update a specific payment link by its unique identifier. This endpoint helps you replace the product and checkout details for a fixed price payment link with new configuration data. Endpoint: PUT /v1/checkout/payment-resources/{id}

Request

The following sample request includes these key details:
  • Sends a PUT request to update the payment link with ID PLB-X7MNK9P2QR8T.
  • Uses an OAuth 2.0 Bearer token in the Authorization header for authentication.
  • Includes the Accept and Content-Type headers set to application/json.
  • Sends the updated link configuration in the request body, replacing the existing product information entirely.
  • Maintains the same payment link ID and URL while applying the new settings.
Note: The API currently only uses PUT calls instead of PATCH calls.

Response

The following response contains the confirmation details of an updated payment link. The API returns HTTP status 204 No Content or, in some cases, a confirmation response body with the content type application/json. The following sample response includes these key details:
  • Confirms that the updated payment link PLB-X7MNK9P2QR8T has been successfully applied.
  • Returns the payment link with ACTIVE status, maintaining the same ID and payment link URL.
  • Preserves the original creation time.
  • May include a response body with updated configuration details, depending on implementation.
Delete a specific payment link by its unique identifier. This endpoint permanently removes a payment link or button associated with the specified ID. Endpoint: DELETE /v1/checkout/payment-resources/{id}

Request

The following sample request includes these key details:
  • Sends a DELETE request to permanently remove the payment link with ID PLB-X7MNK9P2QR8T.
  • Uses an OAuth 2.0 Bearer token in the Authorization header for authentication.
  • Includes the Accept and Content-Type headers set to application/json.

Response

The API returns HTTP status 204 No Content with the content type application/json, indicating that the payment link was deleted. No response body is returned.

Error handling

For more information, see Common errors overview.

Test

  • Create a sandbox account through the PayPal Developer Portal.
  • Use your sandbox environment for all development and testing.
  • All endpoints are duplicated for the sandbox (api-m.sandbox.paypal.com) and live environments​.
  • Test your live payment link by making a purchase. Then verify the transaction in the Activity section of your PayPal account. Be sure to refund the test transaction afterward.