Stripe powers online and in-person payment processing and financial solutions for businesses of all sizes.
48 actions Leo can use in the apps and agents it builds for you: 19 that read Stripe data, 29 that create or update it.
Search for subscriptions.
Docs ↗Search customers by various attributes like email domain, created date, etc.
Docs ↗Retrieves the details of an existing refund.
Docs ↗Retrieve a product by ID.
Docs ↗Retrieves the details of an existing product price.
Docs ↗Retrieves the details of an existing payout.
Docs ↗Retrieves the details of a payment intent that was previously created.
Docs ↗Retrieves the details of an existing invoice.
Docs ↗Retrieve a single line item on an invoice.
Docs ↗Retrieves the details of an existing customer.
Docs ↗A Checkout Session represents your customer's session as they pay for one-time purchases or subscriptions through Stripe Checkout.
Docs ↗Given a checkout session ID, retrieve the line items.
Docs ↗Retrieves the current account balance, based on the authentication that was used to make the request.
Docs ↗Find or list refunds. By default returns an array of refund objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate.
Find or list payouts. By default returns an array of payout objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate.
Retrieves a list of payment intents that were previously created. By default returns an array of payment intent objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate.
Find or list invoices. By default returns an array of invoice objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate.
Find or list customers. By default returns an array of customer objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate.
List all balance transactions. By default returns an array of transaction objects (auto-paginated up to Limit). Set Return Pagination Info to true to instead receive { data, has_more, next_starting_after } for a single Stripe page (max 100 per call) — pass next_starting_after as Starting After on the next call to iterate.
Mark an invoice as uncollectible.
Docs ↗Void an invoice.
Docs ↗Update the metadata on a refund.
Docs ↗Update the metadata on a payout.
Docs ↗Update a payment intent.
Docs ↗Update an invoice.
Docs ↗Update an invoice line item.
Docs ↗Update a customer.
Docs ↗Manually send an invoice to your customer out of the normal schedule for payment (note that no emails are actually sent in test mode).
Docs ↗Finalize a draft invoice.
Docs ↗Delete a draft invoice, or void a non-draft or subscription invoice.
Docs ↗Delete a line item from an invoice.
Docs ↗Delete a customer.
Docs ↗Create a subscription.
Docs ↗Create a refund.
Docs ↗Creates a new product object in Stripe.
Docs ↗Creates a new price for an existing product. The price can be recurring or one-time.
Docs ↗Create a payout.
Docs ↗Create a payment intent.
Docs ↗Create an invoice.
Docs ↗Add a line item to an invoice.
Docs ↗Create a customer.
Docs ↗Creates a billing meter.
Docs ↗Confirm that your customer intends to pay with current or provided payment method.
Docs ↗Capture the funds of an existing uncaptured payment intent.
Docs ↗Cancel a subscription.
Docs ↗Cancel a PaymentIntent.
Docs ↗Cancel a pending payout or reverse a paid payout. See the documentation here and here
With metered billing, you charge your customers based on their consumption of your service during the billing cycle, instead of explicitly setting quantities. Use this action to create a usage record for metered billing. See the docs for more information
Leo connects Stripe to the ERP your business already runs on: the records it reads in Stripe land in your ERP, and what changes in the ERP flows back.
Authorize Stripe once, in a couple of clicks. Leo only gets the permissions you grant.
In plain language: the dashboard, portal or agent you want across Stripe and your ERP. No code, no mapping spreadsheets.
Leo builds it, you review, it goes live. Agents run on a schedule or on events, under the guardrails you set.