Stripe API: what you can do and how to use it with AI agents
The Stripe API covers the whole online billing cycle: payments, customers, subscriptions, invoices, refunds and payouts. SaaS companies and businesses that sell internationally use it widely. Access uses the account's secret keys, with separate test and live modes.
What the Stripe API offers
Payments
Create and track payment intents with cards and other supported methods.
Customers
Customer records, saved payment methods and charge history.
Subscriptions and invoices
Plans, prices, recurring subscriptions and invoice issuing.
Refunds and disputes
Full or partial refunds and tracking of disputes.
Webhooks
Events sent to your system when something changes, such as a confirmed payment or a canceled subscription.
Reports and balances
Account balance, transactions and payouts for reconciliation.
How to access the Stripe API
- With your company’s credentialsUses the account's secret keys (with keys restricted per resource, if you prefer), separate for test and live modes. Platforms that act across several accounts use Stripe Connect.
- Prefer restricted keys to the full secret key.
- Refunds and cancellations should have human approval and an amount ceiling.
- Use test mode before any automation in production.
Official documentation: docs.stripe.com
What an iTeam agent does with the Stripe API
Failed subscription recovery
When a renewal is declined, the agent notifies the customer, sends the link to update the card and follows up until the charge goes through.
Recurring revenue close
The agent gathers the month's new subscriptions, cancellations and upgrades and delivers the MRR with an explanation of each variation.
Refund with a double check
The support agent finds the charge, proposes the refund with amount and reason, and only runs it after approval.
Dispute response
When a dispute appears, the agent collects the order, delivery and conversations and builds the file for the team to submit on time.
From the credential to the agent at work, with approval
Create a restricted key
In the Stripe dashboard, generate a restricted key with only the resources the agents will use, starting in test mode.
Store it in the iTeam vault
Register the key in the vault and define per agent who reads charges, who creates links and who can request refunds.
Validate in test mode
Run the flows with test data and only then switch to the live key, keeping approval on financial actions.
Ready-made AI teams that use Stripe
Online store support team
It looks up the real order in Shopify or WooCommerce and answers tracking, return and exchange questions in seconds.
WhatsApp sales team
It answers product questions, puts the quote together and follows up with the buyer who said "let me think about it".
Bank reconciliation team
Bank lines, Stripe payouts and ledger entries are matched each morning. You only see what did not match, with a reason.
Collections team
Before and after each due date, customers get a clear reminder with a payment link. Disputes and promises to pay go to your team.
Questions about the Stripe API
Is the Stripe API free?
The API is not charged separately. Stripe charges fees on transactions, and some additional products have their own pricing.
Do I need to write code to use the Stripe API with iTeam?
Not necessarily. iTeam uses Stripe through the app catalog or by reading the documentation, and the deployment team sets up the actions and approvals.
Can the agent see card data?
No. Stripe does not expose the full card number through the API. The agent works with identifiers, statuses and the last digits.
