> For the complete documentation index, see [llms.txt](https://paypal.gitbook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paypal.gitbook.com/online-payments/one-integration-many-payment-methods.md).
# One integration, many payment methods
Introducing a new interactive experience to accelerate your Checkout integration! Build quickly and efficiently.
Start buildingLearn more
With Payment Links, Buy Buttons, and Shopping Cart Buttons, you can accept PayPal, Pay Later, Venmo, Apple Pay, and major debit and credit cards. Availability may vary by region.
***
{% columns %}
{% column %}
## Sell online or in person
Create a Payment Link in just a few clicks to sell products or services online or in person, or embed a Buy Button or a Shopping Cart Button to your website.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
## Pay as you go
With no subscription fees or contracts, you only pay us when you get paid.
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
## Go international
We make it simple to accept payments from customers around the globe. Access PayPal’s coverage for over 200 countries and regions, supporting 24 currencies and 25 languages to support sales around the globe.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://paypal.gitbook.com/online-payments/one-integration-many-payment-methods.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
