Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Payments / Paypal / Payments
Payments logo

Paypal Payments

Browse all Paypal APIs
✓ 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

Not supported: Does not handle communications, crm, or developer tools — use for payments only.

Call the Payments API to authorize payments, capture authorized payments, refund payments that have already been captured, and show payment information. Use the Payments API in conjunction with the <a href="/docs/api/orders/v2/">Orders API</a>. For more information, see the <a href="/docs/checkout/">PayPal Checkout Overview</a>. The API exposes 7 endpoints secured with oauth2 authentication.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Payments to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Payments, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

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

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

POST

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

Refund captured payment

GET

/v2/payments/refunds/{refund_id}

Show refund details

Why Jentic?

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

Credential management

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

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

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.

GET STARTED

Start building with Payments API

Explore with Jentic
View OpenAPI Document