Ship deep Stripe integrations in days
Stripe spreads payments, billing, Connect, Issuing, and Treasury across more than a hundred API objects, and every account runs its own products, prices, and metadata. With Ampersand, you can get this integration live for your customers in days.
Build a custom data model to handle
complex configurations
No two Stripe accounts are the same. Every customer has their own products, prices, and metadata, and uses a different mix of Billing, Connect, and Issuing. AI agents need infrastructure that understands Stripe at the per-tenant level.
3 / 8 customers
- Customer A: Customer (standard), Subscription (standard), Invoice (standard)
- Customer B: Payment Intent (standard), Charge (standard), Refund (standard)
- Customer C: Customer (standard), Quote (standard), Connected Account (standard)
Enable software and agents to take bi-directional action
With Ampersand, your engineers don’t need to learn Stripe’s resource model, its expand rules, or its webhook endpoints. Simply declare the actions you want your agents to take: read, write, subscribe, proxy.
Example. Subscribe: “Notify me as soon as a subscription’s status changes.”
- Ampersand registers a webhook endpoint in this customer’s Stripe account.
- Events arrive, and Ampersand verifies each signature and detects which fields changed.
- Ampersand keeps only the events where the status changed and drops the rest.
- Ampersand applies this customer’s field mappings.
- Ampersand sends the subscription to your product.
Ensure your Stripe integration is always available
-
Managed API keys
Your customers enter a Stripe API key in Ampersand’s install flow, and Ampersand stores it for every call. There’s no Stripe app to register first.
-
Managed webhooks
Ampersand registers the webhook endpoint in each customer’s Stripe account, verifies every event’s signature, and routes the changes to your product.
-
Expanded related data
Read fields Stripe doesn’t return by default, such as a balance transaction’s payment intent, through Stripe’s expand feature.
Not all Stripe integrations are created equal
Stripe is where many internet businesses take payments and run billing. With Ampersand, your developers can create a best-in-class Stripe integration.
The Stripe objects your agents can read and write
Ampersand reads, writes, and subscribes to Stripe’s payments, billing, Connect, and Issuing objects, and covers Treasury, reporting, and configuration objects too.
Treasury received credits, received debits, and transactions are read-only. Among balances and reporting, subscribe covers application fees, early fraud warnings, and reviews. Incremental reads cover most payments, billing, and Issuing objects; others are read in full on each scheduled read.
Questions people ask
before they book a demo
-
Which Stripe objects can I read and write?
You can read and write payment intents, charges, refunds, disputes, payouts, customers, subscriptions, invoices, products, prices, coupons, checkout sessions, connected accounts, Issuing cards, and more. Balance transactions, events, and reviews are read-only, and subscription items, meter events, and customer sessions are write-only.
-
Can I get real-time updates from Stripe?
Yes. Subscribe Actions deliver create, update, and delete events for most payments, billing, and Issuing objects as they happen. Ampersand registers the webhook endpoint in each customer’s Stripe account for you, and the first events arrive within minutes of install.
-
How do my customers connect Stripe?
With an API key. Stripe doesn’t need a provider app, so you deploy your integration and embed Ampersand’s install component, which asks each customer for their key and links to Stripe’s guide to creating one.
-
Does Ampersand offer a unified API?
Ampersand doesn’t offer a unified API. It works with Stripe’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.