Stripe
Read and work a Stripe account - customers, payments, charges, refunds, invoices, subscriptions, catalogue and balance - and create hosted Checkout links.
Connect a Stripe account with a secret or restricted API key to answer questions about payments and act on them: look up customers and their payment history, read payment intents, charges, invoices and subscriptions, reconcile the balance transaction by transaction (gross, fee and net), issue full or partial refunds, cancel subscriptions immediately or at the period end, and create hosted Checkout links for a customer to pay. Amounts are handled in minor units with the currency's own exponent, so a JPY amount is never silently multiplied by a hundred.
Connect
| Credential field | Required | Where it comes from |
|---|---|---|
Secret API key (API_KEY) | Yes | A Stripe secret key (sk_live_…, sk_test_…) or restricted key (rk_…) from Developers → API keys. It selects both the identity and the mode - test keys see only test data. |
Tools
| Tool | Access | What it does |
|---|---|---|
Get account (yekar.stripe.get-account) | Read | The Stripe account this connection acts on: display name, country, default currency, whether charges and payouts are enabled, and - most importantly - whether the stored key is a LIVE or TEST key. Test-mode and live-mode objects are invisible to each other, so run this first when a lookup unexpectedly 404s. |
List customers (yekar.stripe.list-customers) | Read | A page of customers, newest first, optionally filtered by exact email or a created window. Stripe reports no total - page until hasMore is false. Note that an email is NOT unique in Stripe: the same address can belong to several customer records. |
Get customer (yekar.stripe.get-customer) | Read | One customer by id, with their email, name, account-credit balance and metadata. A negative balance is CREDIT the customer holds, not money they owe. |
Create customer (yekar.stripe.create-customer) | Write | Create a customer. Stripe does NOT deduplicate by email - running this twice for the same address creates two customers. Search with List customers (email filter) first if the record may already exist. |
Update customer (yekar.stripe.update-customer) | Write | Update a customer's email, name, phone, description or metadata. Only the fields you pass are changed - omitting a field leaves it as it is. Metadata keys you send replace those keys; keys you don't mention survive. |
List payment intents (yekar.stripe.list-payment-intents) | Read | A page of payment intents, newest first, optionally for one customer or a created window. A payment intent's amount is what was REQUESTED; amountReceived is what was actually collected - they differ for anything that has not succeeded. Stripe offers no status filter here: filter the returned page yourself, and remember the page is a window, not the account. |
Get payment intent (yekar.stripe.get-payment-intent) | Read | One payment intent by id: its status, the requested amount, the amount actually received, the charge it produced (use that id to refund it), and the last payment error if the customer's bank refused. |
List charges (yekar.stripe.list-charges) | Read | A page of charges, newest first. A charge is the money movement a payment intent produced, and it is what a refund attaches to. fullyRefunded is true only when the WHOLE amount came back - a partly-refunded charge has fullyRefunded false and a non-zero amountRefunded, so read both. |
Refund a charge (yekar.stripe.create-refund) | Write | Refund a charge (or a payment intent's latest charge), fully or partially. Amounts are in MINOR units of the charge's currency. This moves real money back to the customer and cannot be undone - a refund cannot be 'un-refunded', only re-charged. |
List refunds (yekar.stripe.list-refunds) | Read | A page of refunds, newest first, optionally for one charge or payment intent. A refund with status pending has been issued but has NOT reached the customer's bank yet, and one with status failed returned the money to your balance - neither is a completed refund. |
List invoices (yekar.stripe.list-invoices) | Read | A page of invoices, newest first, optionally filtered by customer, subscription or status. The status filter is applied by Stripe, not by this tool, so it holds across the whole collection rather than just this page. |
Get invoice (yekar.stripe.get-invoice) | Read | One invoice by id with its line items, amounts, hosted payment page and PDF link. At most 25 lines are returned; anything beyond that is counted in linesOmitted rather than dropped silently. |
List subscriptions (yekar.stripe.list-subscriptions) | Read | A page of subscriptions, newest first. Stripe's own default returns only ACTIVE subscriptions - pass status all to see canceled, past-due and trialing ones too. cancelAtPeriodEnd true means the customer has already cancelled even though the status is still active. |
Get subscription (yekar.stripe.get-subscription) | Read | One subscription by id with its items, prices and current period. Read cancelAtPeriodEnd alongside status: a subscription the customer has cancelled stays active until the period ends, so status alone reports it as ongoing. |
Cancel subscription (yekar.stripe.cancel-subscription) | Write | Cancel a subscription - immediately by default, or at the end of the current period with atPeriodEnd: true. Immediate cancellation ends access now and CANNOT be undone (you would have to create a new subscription); period-end cancellation can be reversed until the period closes. |
List products (yekar.stripe.list-products) | Read | A page of catalogue products, newest first. A product carries the name and description; the money lives on its PRICES (List prices) - defaultPriceId is the one to use when a product has several. |
List prices (yekar.stripe.list-prices) | Read | A page of prices - the amounts a product is sold at. unitAmountMinor is what Stripe stores (2000 = $20.00, but 2000 = ¥2000 for a zero-decimal currency) and unitAmount is its major-unit reading. A recurring price also carries its billing interval. Price ids are what Create checkout session takes. |
Get balance (yekar.stripe.get-balance) | Read | The Stripe account's current balance, per currency: available is settled funds that can be paid out, pending has not settled yet. The rows are separate currencies and must not be added together. |
List balance transactions (yekar.stripe.list-balance-transactions) | Read | A page of balance transactions - every movement into or out of the Stripe balance (charges, refunds, fees, payouts, adjustments), newest first. Each row carries gross amount, Stripe's fee and the net that actually moved: reconcile on net, not on amount. Filter by payoutId to see exactly what made up one bank deposit. |
Create checkout session (yekar.stripe.create-checkout-session) | Write | Create a Stripe Checkout session and return its payment URL - a hosted page the customer completes themselves. This does NOT charge anyone; it produces a link that expires (24 hours by default). Line items reference EXISTING price ids; the mode must match them (payment for one-off, subscription for recurring). |
Notes
- In the Stripe Dashboard go to Developers → API keys and reveal a SECRET key (sk_live_… or sk_test_…). The publishable key (pk_…) cannot call the API and is refused with a message saying so.
- Prefer a RESTRICTED key (rk_…): create one under Developers → API keys → Create restricted key and grant only what these tools need - read on Customers, Charges, PaymentIntents, Invoices, Subscriptions, Products, Prices and Balance transactions, and write on Customers, Refunds, Subscriptions and Checkout Sessions.
- The key decides the MODE as well as the identity: a test key sees only test-mode objects and a live key only live ones. A live id looked up with a test key answers 404, so run Get account first to confirm which mode this connection is in.
- Amounts are in the currency's MINOR unit - 2050 means $20.50, but 2050 means ¥2050 because JPY has no minor unit, and KWD amounts must be a multiple of 10. Read
amountMinoralongsideamountand sendamountMinor. - Refunding is real money leaving the account and cannot be undone. Cancelling a subscription immediately cannot be undone either - cancel at the period end if the customer should keep access until then.
- There is deliberately no tool that charges a card: the money-in path is Create checkout session, which returns a link the customer completes themselves.
- Every action is attributed to this API key, not to the person who triggered the automation, and Stripe's own logs show it that way. Bind automations using this integration as a service connection.