Stripe API

Name: Stripe API
Brand: Stripe API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment Processingbearer, basic587 EndpointsREST

For Agents

Process payments, manage subscriptions, issue refunds, and handle invoicing for internet businesses. Supports 135+ currencies and 50+ payment methods with built-in fraud protection.

Install Jentic One Beta

Connect the Stripe API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Stripe API, 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.

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

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 Stripe API.

Accept one-time and recurring card payments with automatic 3D Secure handling

Create and manage subscriptions with metered billing, trials, and proration

Generate and send invoices with configurable line items and payment terms

GET STARTED

Start building with Stripe API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Stripe API for, with concrete tasks.

★ AI Agent Payment Processing

AI agents use the Stripe API through Jentic to create payment intents, confirm charges, and check payment status without handling API keys directly. The agent searches Jentic for the operation (e.g., 'process a payment'), receives the /v1/payment_intents endpoint schema, and executes. Jentic stores Stripe secret keys in its encrypted vault and injects them into requests — the agent never sees raw credentials.

Create a Payment Intent for $49.99 USD with card payment method type, confirm it with a test card token, then verify the status is 'succeeded'

Subscription Billing

Create and manage recurring subscriptions with flexible billing intervals, free trials, metered usage, and automatic proration on plan changes. Stripe handles dunning (retry failed charges), sends invoice emails, and applies tax rates automatically. Subscriptions support multiple price items, quantity adjustments, and pause/resume functionality.

Create a customer, attach a payment method, then create a subscription on the 'pro-monthly' price with a 14-day trial and confirm the subscription status is 'trialing'

E-Commerce Checkout

Accept payments for physical and digital goods using Stripe Checkout, a prebuilt hosted payment page that handles card input, validation, and 3D Secure authentication. Checkout sessions support one-time payments and subscription sign-ups, with configurable success and cancel URLs. Supports 50+ payment methods and 135+ currencies without additional integration work per method.

Create a Checkout session for a $99 one-time purchase in USD with card and Apple Pay enabled, set the success URL, and return the checkout URL to the user

Refunds and Dispute Management

Issue full or partial refunds against payment intents or charges, with refund reason tracking and status monitoring. For disputes (chargebacks), upload evidence documents, submit counter-arguments, and track outcomes. The API provides webhook events for real-time dispute status changes, enabling automated response workflows within the evidence submission deadline.

Create a partial refund of $15.00 against a specific payment intent, then retrieve the refund object to confirm the status is 'succeeded' and the amount matches

Invoice Generation and Delivery

Generate itemised invoices for customers with configurable line items, tax rates, discounts, and payment terms. Invoices can be finalised and sent via email with a hosted payment link, or marked as paid externally. Auto-advance invoices charge the customer's default payment method on the due date, enabling hands-off accounts receivable.

Create a draft invoice for a customer with two line items (consulting $500, software license $200), finalise it, and send the hosted payment link

Key Endpoints

587 endpoints — accept and process payments across 135+ currencies and 50+ payment methods including cards, bank debits, wallets, and buy-now-pay-later.

METHOD

PATH

DESCRIPTION

POST

/v1/payment_intents

Create a Payment Intent to collect a payment

POST

/v1/payment_intents/{intent}/confirm

Confirm a Payment Intent to initiate the charge

GET

/v1/charges

List all charges with optional filters

POST

/v1/refunds

Create a refund against a charge or payment intent

POST

/v1/customers

Create a customer record

POST

/v1/subscriptions

Create a subscription for recurring billing

POST

/v1/invoices

Create a draft invoice

POST

/v1/checkout/sessions

Create a Checkout session for hosted payments

POST

/v1/payment_intents

Create a Payment Intent to collect a payment

POST

/v1/payment_intents/{intent}/confirm

Confirm a Payment Intent to initiate the charge

GET

/v1/charges

List all charges with optional filters

POST

/v1/refunds

Create a refund against a charge or payment intent

POST

/v1/customers

Create a customer record

Why Jentic?

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

Credential isolation

Stripe API keys (sk_live/sk_test) are stored encrypted in the Jentic vault (MAXsystem). Agents receive authenticated requests with keys injected server-side — raw secret keys never enter the agent's context window or logs.

Intent-based discovery

Agents search by intent (e.g., 'process a payment' or 'create a subscription') and Jentic returns matching Stripe operations with input schemas and required parameters, so the agent calls the right endpoint without navigating Stripe's 587-endpoint documentation.

Time to first call

Direct Stripe integration: 2-5 days for auth, webhook handling, and error recovery. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Stripe API through Jentic.

What authentication does the Stripe API use?

Stripe supports HTTP Basic authentication (API key as username) and Bearer token authentication. Secret keys are prefixed with sk_live_ or sk_test_. Through Jentic, API keys are stored encrypted in the MAXsystem vault — agents receive authenticated requests and never handle raw secret keys directly.

Can I create subscriptions with free trials using the Stripe API?

Yes. POST to /v1/subscriptions with a trial_period_days parameter or trial_end timestamp. During the trial, no charge is made. When the trial ends, Stripe automatically creates an invoice and charges the customer's default payment method. Trials support conversion tracking via the subscription.trial_will_end webhook event.

What are the rate limits for the Stripe API?

Stripe allows up to 100 read requests per second and 100 write requests per second in live mode per account. Test mode has higher limits. When exceeded, the API returns HTTP 429 with a Retry-After header. Batch operations like list endpoints count as single requests regardless of result count.

How do I process a payment through the Stripe API via Jentic?

Search Jentic for 'process a credit card payment', then load the /v1/payment_intents operation schema. The agent provides amount (in cents), currency, and payment method type. Jentic handles API key injection and the agent receives the payment intent status. Install with pip install jentic or sign up at https://app.jentic.com/sign-up.

Does the Stripe API support marketplace payment splits?

Yes. Connected accounts enable platforms to split payments between themselves and sellers. The /v1/accounts endpoint onboards connected accounts, and payment intents accept transfer_data or application_fee_amount parameters to split funds. The Connect platform handles payouts to connected accounts on configurable schedules.

Can I issue partial refunds with the Stripe API?

Yes. POST to /v1/refunds with the payment_intent or charge ID and an amount parameter less than the original charge. Multiple partial refunds can be issued against the same payment until the total reaches the original amount. Each refund includes a reason field (duplicate, fraudulent, or requested_by_customer).

Stripe API

Connect the Stripe API to your agent

Capabilities

Start building with Stripe API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs