Payment Method Tokens

Name: Payment Method Tokens API
Brand: Payment Method Tokens
Availability: InStock

✓ Official Vendor SpecPaymentsPayment Processingoauth26 EndpointsREST

For Agents

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

Quickstart

Get started with Payment Method Tokens in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create payment token for a given payment source"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Payment Method Tokens API.

Create payment token for a given payment source

List all payment tokens

Retrieve a payment token

Delete payment token

Use Cases

GET STARTED

Start building with Payment Method Tokens API

Explore with Jentic

View OpenAPI Document

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.

★ 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.

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.

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.

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

Key Endpoints

6 endpoints — the payment method tokens api saves payment methods so payers don't have to enter details for future transactions.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Payment Method Tokens oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create payment token for a given payment source') and Jentic returns the matching Payment Method Tokens operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Payment Method Tokens integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

FAQs

Specific to using Payment Method Tokens API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.