Stripe API

Name: Stripe API API
Brand: Stripe API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment Processingbearer, basic563 EndpointsREST

For Agents

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

Quickstart

Get started with Stripe API 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:
"process a credit card payment"

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

Capabilities

What an agent can do with Stripe API API.

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

Create and manage subscription plans with usage-based metering, trial periods, and proration

Issue full or partial refunds and track dispute evidence submission deadlines

Split payments across multiple recipients using Connect with configurable fee structures

GET STARTED

Start building with Stripe API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Stripe API API for, with concrete tasks.

★ AI Agent Payment Automation

AI agents discover and execute Stripe payment operations through Jentic without managing API keys directly. An agent searches for 'process a payment' via Jentic, receives the Payment Intent schema with required fields, and executes the call with credential isolation. This eliminates the need for agents to store Stripe secret keys or parse API documentation, reducing integration from days to minutes.

Search Jentic for 'create a payment intent', load the operation schema, and execute a $99.00 USD card payment with automatic confirmation enabled

E-Commerce Checkout

Accept one-time payments for physical and digital goods with support for 135+ currencies and 50+ payment methods. Stripe handles card validation, 3D Secure authentication, and settlement automatically. The Payment Intents API tracks payment state from creation through confirmation, authorization, and capture, with built-in retry logic for declined cards.

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

Subscription Billing

Bill customers on recurring schedules with support for fixed-rate plans, per-seat pricing, and metered usage. The Subscriptions API manages trial periods, proration on plan changes, and automatic dunning for failed payments. Invoices are generated at each billing cycle with line items, taxes, and discount codes applied automatically.

Create a customer, attach a payment method, then create a monthly subscription at $29/month with a 14-day trial period

Marketplace Payouts

Split payments between a platform and connected sellers using Stripe Connect. The API supports destination charges where the platform collects a fee, separate charges and transfers for complex splits, and direct charges on behalf of connected accounts. Payouts to seller bank accounts are scheduled automatically or triggered on demand.

Create a payment intent for $100 with a $10 application fee directed to a connected account, then verify the transfer was created

Refund and Dispute Management

Issue full or partial refunds on charges and Payment Intents with automatic balance deductions. The Disputes API allows submitting evidence documents, tracking deadlines, and receiving webhook notifications when dispute status changes. Refunds can be issued within 180 days of the original charge and support metadata for internal tracking.

Retrieve a charge by ID, issue a partial refund of $15.00 with reason 'requested_by_customer', and confirm the refund status is 'succeeded'

Key Endpoints

563 endpoints — accept and process online payments across 135+ currencies with support for cards, wallets, bank debits, and buy-now-pay-later methods.

METHOD

PATH

DESCRIPTION

POST

/v1/payment_intents

Create a Payment Intent to initiate a payment

POST

/v1/payment_intents/{intent}/capture

Capture an authorized Payment Intent

POST

/v1/refunds

Create a refund for a charge or Payment Intent

POST

/v1/customers

Create a new customer record

POST

/v1/subscriptions

Create a new subscription for a customer

GET

/v1/charges

List all charges with filtering and pagination

POST

/v1/invoices

Create a draft invoice for a customer

GET

/v1/balance

Retrieve the current account balance

POST

/v1/payment_intents

Create a Payment Intent to initiate a payment

POST

/v1/payment_intents/{intent}/capture

Capture an authorized Payment Intent

POST

/v1/refunds

Create a refund for a charge or Payment Intent

POST

/v1/customers

Create a new customer record

POST

/v1/subscriptions

Create a new subscription for a customer

Why though Jentic?

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

Credential isolation

Stripe API keys (secret keys and restricted keys) are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access tokens — the raw sk_live key never enters 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 their full input schemas and required fields, so the agent can call the right endpoint without browsing documentation.

Time to first call

Direct Stripe integration: 2-5 days for auth setup, webhook handling, idempotency, and error recovery. Through Jentic: under 1 hour — search for the operation, load the schema, execute with credential isolation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PayPal Orders API

PayPal-native checkout flow with buyer and seller protection built in

Choose PayPal when buyers prefer paying with their PayPal balance or when seller protection and dispute resolution through PayPal is required

Alternative

Adyen Checkout API

Enterprise payment gateway with strong European market coverage and local payment methods

Choose Adyen when processing high-volume enterprise payments or when local European payment methods (iDEAL, Bancontact, Giropay) are primary requirements

Alternative

Paddle API

Merchant-of-record billing platform handling tax, compliance, and payouts

Choose Paddle when you need a merchant-of-record model where Paddle handles sales tax, VAT, and compliance obligations for SaaS products

Complementary

Recurly API

Subscription management platform with advanced dunning and revenue recognition

Choose Recurly alongside Stripe when you need advanced subscription analytics, revenue recognition, and multi-gateway dunning workflows

Complementary

Plaid API

Bank account verification and financial data aggregation

Use Plaid to verify bank accounts and retrieve financial data before processing payments through Stripe

FAQs

Specific to using Stripe API API through Jentic.

What authentication does the Stripe API use?

The Stripe API accepts Bearer token authentication with your secret API key in the Authorization header, or HTTP Basic auth with the API key as the username and an empty password. Through Jentic, your Stripe API keys are stored encrypted in the MAXsystem vault. Agents receive scoped access tokens so the raw secret key never enters the agent's context window.

Can I create subscriptions with trial periods using the Stripe API?

Yes. The POST /v1/subscriptions endpoint accepts a trial_period_days parameter or a trial_end timestamp. During the trial, no invoice is generated. When the trial ends, Stripe automatically creates an invoice and attempts to collect payment using the customer's default payment method.

What are the rate limits for the Stripe API?

Stripe applies rate limits of 100 read operations per second and 100 write operations per second in live mode per account, with higher limits in test mode. If you exceed limits, the API returns HTTP 429 with a Retry-After header. Batch operations like list endpoints support pagination with up to 100 objects per page.

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

Search Jentic for 'issue a refund' to find the POST /v1/refunds operation. The required field is either charge or payment_intent ID. Optionally specify amount for partial refunds and reason (duplicate, fraudulent, or requested_by_customer). Jentic loads the full schema so your agent knows exactly which fields to include. Sign up at https://app.jentic.com/sign-up to get started.

How many payment methods does the Stripe API support?

The Stripe API supports over 50 payment method types including cards (Visa, Mastercard, Amex), digital wallets (Apple Pay, Google Pay), bank debits (ACH, SEPA, BACS), buy-now-pay-later (Klarna, Afterpay), and local methods (iDEAL, Bancontact, Boleto). Each method is configured via the payment_method_types parameter on Payment Intents.

Can I split payments between multiple parties using the Stripe API?

Yes. Stripe Connect supports three charge models: destination charges (platform creates the charge and specifies a transfer destination), separate charges and transfers (platform creates independent charge and transfer objects), and direct charges (charge is created on behalf of the connected account). Application fees can be specified on destination charges via the application_fee_amount parameter on POST /v1/payment_intents.

Does the Stripe API support webhook event delivery?

Yes. Create webhook endpoints via POST /v1/webhook_endpoints specifying the URL and list of event types to listen for (e.g., payment_intent.succeeded, invoice.payment_failed). Stripe signs each webhook delivery with a timestamp and signature in the Stripe-Signature header for verification. The API supports up to 16 webhook endpoints per account.