Payments

Name: Payments API
Brand: Payments
Availability: InStock

✓ Official Vendor SpecPaymentsPayment Processingoauth27 EndpointsREST

For Agents

Programmatically show details for authorized payment, capture authorized payment. Covers 7 operations with oauth2 authentication.

Use for: I need to show details for authorized payment, I want to capture authorized payment, Search for reauthorize authorized payment, Find all void authorized payment

Quickstart

Get started with Payments 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:
"show details for authorized payment"

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

Capabilities

What an agent can do with Payments API.

Show details for authorized payment

Capture authorized payment

Reauthorize authorized payment

Void authorized payment

Refund captured payment

GET STARTED

Start building with Payments API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Payments API for, with concrete tasks.

★ Payments Operations

Use the Payments to perform payments operations programmatically. The API provides 7 endpoints covering core functionality including show details for authorized payment, capture authorized payment, reauthorize authorized payment.

Call GET /v2/payments/authorizations/{authorization_id} to show details for authorized payment

Automated authorizations Management

Automate authorizations operations by combining multiple Payments endpoints. Agents can capture authorized payment and then reauthorize authorized payment in a single workflow.

Call POST /v2/payments/authorizations/{authorization_id}/capture to capture authorized payment, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Payments 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 'show details for authorized payment', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — call the payments api to authorize payments, capture authorized payments, refund payments that have already been captured, and show payment information.

METHOD

PATH

DESCRIPTION

GET

/v2/payments/authorizations/{authorization_id}

Show details for authorized payment

POST

/v2/payments/authorizations/{authorization_id}/capture

Capture authorized payment

POST

/v2/payments/authorizations/{authorization_id}/reauthorize

Reauthorize authorized payment

POST

/v2/payments/authorizations/{authorization_id}/void

Void authorized payment

GET

/v2/payments/captures/{capture_id}

Show captured payment details

POST

/v2/payments/captures/{capture_id}/refund

Refund captured payment

GET

/v2/payments/refunds/{refund_id}

Show refund details

GET

/v2/payments/authorizations/{authorization_id}

Show details for authorized payment

POST

/v2/payments/authorizations/{authorization_id}/capture

Capture authorized payment

POST

/v2/payments/authorizations/{authorization_id}/reauthorize

Reauthorize authorized payment

POST

/v2/payments/authorizations/{authorization_id}/void

Void authorized payment

GET

/v2/payments/captures/{capture_id}

Show captured payment details

Why though Jentic?

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

Credential isolation

Payments 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., 'show details for authorized payment') and Jentic returns the matching Payments operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Payments 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 Payments API through Jentic.

What authentication does the Payments use?

The Payments 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 show details for authorized payment with the Payments?

Yes. Use the GET /v2/payments/authorizations/{authorization_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Payments?

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 show details for authorized payment through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'show details for authorized payment'. Jentic returns the matching Payments operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Payments have?

The Payments exposes 7 endpoints covering authorizations, captures, refunds operations.