canonical: https://jentic.com/apis/paypal.com/payment-method-tokens

# Paypal Payment Method Tokens

The Payment Method Tokens API saves payment methods so payers don't have to enter details for future transactions. Payers can check out faster or pay without being present after they agree to save a payment method.<br><br>The API associates a payment method with a temporary setup token. Pass the setup token to the API to exchange the setup token for a permanent token.<br><br>The permanent token re. The API exposes 6 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create payment token for a given payment source, list all payment tokens. Covers 6 operations with oauth2 authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Create payment token for a given payment source
- List all payment tokens
- Retrieve a payment token
- Delete payment token

## Use cases

### Payments Operations

Use the Payment Method Tokens to perform payments operations programmatically. The API provides 6 endpoints covering core functionality including create payment token for a given payment source, list all payment tokens, retrieve a payment token.

Example prompt: Call POST /v3/vault/payment-tokens to create payment token for a given payment source

### Automated payment-tokens Management

Automate payment-tokens operations by combining multiple Payment Method Tokens endpoints. Agents can list all payment tokens and then retrieve a payment token in a single workflow.

Example prompt: Call GET /v3/vault/payment-tokens to list all payment tokens, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Payment Method Tokens endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'create payment token for a given payment source', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v3/vault/payment-tokens | Create payment token for a given payment source |
| GET | /v3/vault/payment-tokens | List all payment tokens |
| GET | /v3/vault/payment-tokens/{id} | Retrieve a payment token |
| DELETE | /v3/vault/payment-tokens/{id} | Delete payment token |
| POST | /v3/vault/setup-tokens | Create a setup token |
| GET | /v3/vault/setup-tokens/{id} | Retrieve a setup token |

## Key resources

- **payment-tokens** — Use the `/vault/payment-tokens` resource to create, retrieve, and delete a payment token that may op
- **setup-tokens** — Use the `/vault/setup-tokens` resource to create and retrieve temporary vault payment methods.
- **tokens** — Use the `/vault/tokens` resource to detokenize a vault token to retrieve details associated to the u
- **tokens-session** — Use the `/vault/tokens/{id}/session` resource to read the token session cache and retrieve details a
- **customers** — Use the `/vault/customers` resource to create, update, get and delete a customer.

## Why Jentic

- **Setup:** Wiring PayPal Payment Method Tokens by hand means running its OAuth 2.0 flow, refreshing Bearer tokens, and choosing the right sandbox or live host before you can create or read vault tokens. Through Jentic you install once, import Payment Method Tokens from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Payment Method Tokens puts the token id in the URL path (/v3/vault/payment-tokens/{id}), so a rule can pin your agent to reading one payment token. You choose the operations it may call, so creating tokens or deleting a token is not included unless you add them.
- **Credential handling:** Your PayPal OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time, with token refresh handled for you. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a payment token for a given payment source' or 'read a vault token', and Jentic returns the matching Payment Method Tokens operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API

## FAQ

### What authentication does the Payment Method Tokens use?

The Payment Method Tokens uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create payment token for a given payment source with the Payment Method Tokens?

Yes. Use the POST /v3/vault/payment-tokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Payment Method Tokens?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create payment token for a given payment source through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create payment token for a given payment source'. Jentic returns the matching Payment Method Tokens operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Payment Method Tokens have?

The Payment Method Tokens exposes 6 endpoints covering payment-tokens, setup-tokens, tokens operations.

### Can I limit what my agent is allowed to do with the Payment Method Tokens API?

Yes. Because you run Jentic One yourself, your own rules decide which Payment Method Tokens operations and credentials the agent may use. Since the token id sits in the URL path (/v3/vault/payment-tokens/{id}), you can pin the agent to retrieving a single payment token and leave creating tokens (POST /v3/vault/payment-tokens) or deleting a token (DELETE /v3/vault/payment-tokens/{id}) out unless you explicitly add them. The stored PayPal OAuth client credentials are injected only for the operations you have allowed, so the agent never gains access beyond that scope.