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.
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.What an agent can do with Stripe API 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
Issue full or partial refunds against charges and payment intents
GET STARTED
Use for: I need to process a credit card payment for an order, Create a recurring subscription with a 14-day free trial, Check whether a refund was successfully issued, List all failed payment attempts in the last 7 days
Not supported: Does not handle accounting, tax filing, or payroll — use for payment processing, subscription billing, and invoicing only.
Accept and process payments across 135+ currencies and 50+ payment methods including cards, bank debits, wallets, and buy-now-pay-later. The API provides 587 endpoints covering payment intents, subscriptions, invoicing, refunds, disputes, connected accounts, and checkout sessions. Handles PCI compliance, 3D Secure authentication, and automatic retry logic for failed charges.
Onboard connected accounts for marketplace and platform payment splits
Run prebuilt Checkout sessions that handle payment form UI and validation
Track and respond to payment disputes with evidence submission workflows
Patterns agents use Stripe API 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
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
/v1/payment_intents
Create a Payment Intent to collect a payment
/v1/payment_intents/{intent}/confirm
Confirm a Payment Intent to initiate the charge
/v1/charges
List all charges with optional filters
/v1/refunds
Create a refund against a charge or payment intent
/v1/customers
Create a customer record
/v1/subscriptions
Create a subscription for recurring billing
/v1/invoices
Create a draft invoice
/v1/checkout/sessions
Create a Checkout session for hosted payments
/v1/payment_intents
Create a Payment Intent to collect a payment
/v1/payment_intents/{intent}/confirm
Confirm a Payment Intent to initiate the charge
/v1/charges
List all charges with optional filters
/v1/refunds
Create a refund against a charge or payment intent
/v1/customers
Create a customer record
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.
Alternatives and complements available in the Jentic catalogue.
Adyen Checkout API
Adyen offers similar payment processing with stronger in-person POS and enterprise acquirer features
Use Adyen when you need unified online and in-store payments or require a single acquirer across multiple regions; use Stripe for developer-friendly online payment integration
PayPal Payments API
PayPal provides wallet-based payments and buyer protection while Stripe focuses on card and bank-based processing
Use PayPal when buyers prefer wallet-based checkout or need buyer protection; use Stripe for direct card processing and subscription management
The Plaid API
Plaid verifies bank accounts that Stripe uses for ACH payments
Use Plaid to verify bank account ownership before setting up ACH debit through Stripe; use Stripe for the actual payment collection
Xero Accounting API
Xero records Stripe payments in the accounting ledger for reconciliation
Use Stripe to collect payments; use Xero to record those transactions in the general ledger and produce financial reports
Specific to using Stripe API 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).
/v1/subscriptions
Create a subscription for recurring billing
/v1/invoices
Create a draft invoice
/v1/checkout/sessions
Create a Checkout session for hosted payments