Stripe

• Read paymentspayment.readDry run

  Settled and pending charges with their intent, status and the fee deducted.

  Reads: accountIdenvironmentcurrencytimezoneRaises: nothing
• Read subscriptionssubscription.readDry run

  Recurring agreements with their status, current period and collection method.

  Reads: accountIdenvironmenttimezoneRaises: nothing
• Create invoiceinvoice.writeDry run

  Raises a draft. Nothing is owed until it is finalised.

  Reads: accountIdenvironmentcurrencytimezoneRaises: stripe.invoice.created
• Read customerspayer.readDry run

  Lists billing entities with their contact details, balance and default payment method.

  Reads: accountIdenvironmentenabledResourcesRaises: nothing
• Write customerpayer.writeDry run

  Creates a billing entity, or amends one that exists. Holds no instrument by itself.

  Reads: accountIdenvironmentcurrencyRaises: stripe.customer.createdstripe.customer.updated
• Archive customerpayer.archiveDry run

  Retires a billing entity. Payment history and closed-period figures are retained.

  Reads: accountIdenvironmentRaises: stripe.customer.updated
• Read payment methodspaymentmethod.readDry run

  Instruments on file, by type and by the customer they are attached to.

  Reads: accountIdenvironmentenabledResourcesRaises: nothing
• Attach payment methodpaymentmethod.attachDry run

  Binds an already-tokenised instrument to a billing entity. No instrument details cross this boundary.

  Reads: accountIdenvironmentRaises: stripe.customer.updated
• Detach payment methodpaymentmethod.detachDry run

  Removes an instrument, and says what was collecting against it.

  Reads: accountIdenvironmentRaises: stripe.customer.updated
• Create paymentpayment.createDry run

  Raises a payment intent, and attempts the charge in the same request only when asked to.

  Reads: accountIdenvironmentcurrencyRaises: stripe.payment.createdstripe.payment.succeededstripe.payment.failed
• Cancel paymentpayment.cancelDry run

  Cancels an intent that has not captured. Nothing had moved, so nothing is returned.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Create payment linkpaymentlink.writeDry run

  Creates a reusable hosted URL. Collects nothing until somebody follows it.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Create checkout sessioncheckout.writeDry run

  Creates a single-use hosted checkout that expires. One attempt, one payer.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Read checkout sessionscheckout.readDry run

  Hosted checkouts and whether each completed, expired or was abandoned.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Read refundsrefund.readDry run

  Refunds against settled charges, whole and partial, with their stated reason.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Refund paymentrefund.writeDry run

  Returns a settled charge to the payer, whole or in part. The processing fee is not returned.

  Reads: accountIdenvironmentcurrencyRaises: stripe.payment.refundedstripe.balance.updated
• Read invoicesinvoice.readDry run

  Invoices in every state, with their totals, due dates and amount outstanding.

  Reads: accountIdenvironmentcurrencytimezoneRaises: nothing
• Finalise invoiceinvoice.finaliseDry run

  Closes a draft for edits and makes it payable. The step that turns a description into a debt.

  Reads: accountIdenvironmentcurrencytimezoneRaises: nothing
• Send invoiceinvoice.sendDry run

  Delivers a finalised invoice. Does not collect — the payer follows the link.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Pay invoiceinvoice.payDry run

  Charges the default payment method against an open invoice, and reports whether it collected.

  Reads: accountIdenvironmentcurrencyretryLimitRaises: stripe.invoice.paidstripe.invoice.failedstripe.payment.succeededstripe.payment.failed
• Void invoiceinvoice.voidDry run

  Cancels an unpaid debt and retains the record. Deletion is not offered.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Write subscriptionsubscription.writeDry run

  Creates a recurring agreement, or amends one and prorates the difference.

  Reads: accountIdenvironmentcurrencytimezoneRaises: stripe.subscription.createdstripe.subscription.updated
• Cancel subscriptionsubscription.cancelDry run

  Ends a recurring agreement now or at period end, and states the recurring revenue lost.

  Reads: accountIdenvironmentcurrencytimezoneRaises: stripe.subscription.cancelled
• Pause or resume subscriptionsubscription.pauseDry run

  Suspends and resumes collection. One field, both directions — a pause is not churn.

  Reads: accountIdenvironmentcurrencyRaises: stripe.subscription.updated
• Read subscription itemssubscriptionitem.readDry run

  The priced lines subscriptions are composed of, with quantities.

  Reads: accountIdenvironmentenabledResourcesRaises: nothing
• Write subscription itemsubscriptionitem.writeDry run

  Adds or requantifies a priced line, and prorates against the current period.

  Reads: accountIdenvironmentcurrencyRaises: stripe.subscription.updated
• Read productsbillingproduct.readDry run

  Billable products with their active state and default price.

  Reads: accountIdenvironmentenabledResourcesRaises: nothing
• Write productbillingproduct.writeDry run

  Creates or updates a billable product. It cannot be sold until a price is attached.

  Reads: accountIdenvironmentRaises: nothing
• Archive productbillingproduct.archiveDry run

  Stops new sales. Existing subscriptions keep collecting and must be ended separately.

  Reads: accountIdenvironmentRaises: nothing
• Read pricesprice.readDry run

  Prices attached to products, with their interval, tiers and currency.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Write priceprice.writeDry run

  Attaches a new price. Prices are immutable, so this adds rather than replaces.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Create couponcoupon.writeDry run

  Creates the discount rule. Not customer-facing until a promotion code wraps it.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Create promotion codepromotioncode.writeDry run

  Creates the customer-facing code that applies an existing coupon.

  Reads: accountIdenvironmentRaises: nothing
• Read disputesdispute.readDry run

  Chargebacks with their reason, evidence deadline and current status.

  Reads: accountIdenvironmentcurrencytimezoneRaises: nothing
• Respond to disputedispute.writeDry run

  Files evidence contesting a chargeback. The amount is already withheld either way.

  Reads: accountIdenvironmentcurrencytimezoneRaises: stripe.dispute.updated
• Read payoutspayout.readDry run

  Transfers from the account balance to a bank account, with arrival dates.

  Reads: accountIdenvironmentcurrencytimezoneRaises: nothing
• Create payoutpayout.writeDry run

  Moves settled funds from the account balance to the bank account on file.

  Reads: accountIdenvironmentcurrencyRaises: stripe.payout.createdstripe.payout.failedstripe.balance.updated
• Read balancebalance.readDry run

  Available, pending and reserved funds held on the operator's behalf, per currency.

  Reads: accountIdenvironmentcurrencyRaises: nothing
• Read balance transactionsbalancetransaction.readDry run

  Every movement into and out of the balance, with the fee attributed to each.

  Reads: accountIdenvironmentcurrencytimezoneRaises: nothing
• Read connected accountsconnectedaccount.readDry run

  Accounts this platform acts on behalf of, with their onboarding and payout state.

  Reads: accountIdenvironmentappTypeRaises: nothing
• Write connected accountconnectedaccount.writeDry run

  Onboards or updates an account this platform acts for. Verification is the account holder's.

  Reads: accountIdenvironmentappTypeRaises: nothing
• Read usage recordsusagerecord.readDry run

  Metered consumption already reported against subscription items this period.

  Reads: accountIdenvironmenttimezoneRaises: nothing
• Report usageusagerecord.writeDry run

  Files metered consumption against a priced line. Charged on the next invoice, not now.

  Reads: accountIdenvironmentcurrencytimezoneRaises: nothing
• Read tax ratestax.readDry run

  Declared tax rates and the jurisdictions and treatments they apply to.

  Reads: accountIdenvironmentenabledResourcesRaises: nothing
• Write tax ratetaxrate.writeDry run

  Declares a rate. Does not resolve which jurisdiction applies to a sale.

  Reads: accountIdenvironmentRaises: nothing

Inbound deliveries and outbound operations both raise these onto the internal bus. The Hub is the emitter — an external platform cannot reach the bus, which is what stops it raising arbitrary internal events.

• Customer Createdstripe.customer.created

  A billing entity was created. Not a storefront shopper — this is something an invoice can be raised against.

• Customer Updatedstripe.customer.updated

  A billing entity changed. Also raised when one is archived or when an instrument is attached or detached, because all three amend the same record.

• Payment Createdstripe.payment.created

  A payment intent exists. NOT money — an intent may never be confirmed, and revenue is not entitled to move on this.

• Payment Succeededstripe.payment.succeeded

  A charge settled. This is the topic revenue moves on, and the reason it is separate from the one above.

• Payment Failedstripe.payment.failed

  A charge was declined. Distinct from an invoice failure: this is a checkout problem, that one is dunning.

• Payment Refundedstripe.payment.refunded

  Money was returned to a payer. Negative revenue — a report that added it would count a return as a sale.

• Checkout Completedstripe.checkout.completed

  A hosted checkout was paid. Arrives from the far side; no operation here raises it, because creating a session is an invitation and not a transaction.

• Subscription Createdstripe.subscription.created

  A recurring agreement began. Recurring revenue moves on this; the first collection is a separate payment event.

• Subscription Updatedstripe.subscription.updated

  An agreement was amended, paused or resumed. A pause raises this and never the cancellation below — a paused subscription is not churn.

• Subscription Cancelledstripe.subscription.cancelled

  An agreement ended, immediately or at period end. This is the topic a churn figure counts.

• Invoice Createdstripe.invoice.created

  A draft invoice exists. Nothing is owed yet — finalising is what turns a description into a debt.

• Invoice Paidstripe.invoice.paid

  An invoice collected. A receivable became money, which is two facts and not one.

• Invoice Payment Failedstripe.invoice.failed

  A recurring collection failed and the invoice stays open. This is where dunning begins, and it is the highest-value subscriber hook on this connector.

• Dispute Createdstripe.dispute.created

  A chargeback was raised by an issuing bank. Arrives from the far side — no operation here creates one, and one that claimed to would attribute a customer's action to the operator.

• Dispute Updatedstripe.dispute.updated

  Evidence was filed or a decision landed. The disputed amount is withheld from the moment the dispute opens, not from this.

• Payout Createdstripe.payout.created

  Settled funds left the balance for a bank account. The operator's own money moving, not a customer's.

• Payout Failedstripe.payout.failed

  A transfer was rejected and the funds returned to the balance. A treasury incident rather than a customer one.

• Balance Updatedstripe.balance.updated

  Available funds changed. Raised by refunds as well as payouts — a treasury view hearing only about payouts would drift by the refund total.

• Webhook Receivedstripe.webhook.received

  An inbound delivery arrived and verified. Raised before it is interpreted, so an unrecognised payload is still visible.

• Sync Completedstripe.sync.completed

  A scheduled reconciliation finished. Declared and raised by nothing here — reconciliation is a schedule, and this runtime resolves calls rather than running schedules.

Routed by the event bus alongside the platform's own topics. See the fan-out chains.

What a future workflow step can request. Several share one capability — the capability is what the gateway routes on, the action is what an operator building a workflow recognises.

• Create Customerpayer.write

  Creates a billing entity. The step a completed company.created fan-out resolves to — a new company acquires somewhere to be billed, not an invoice.

• Update Customerpayer.write

  Amends contact details or metadata on an existing billing entity. Same capability, different payload.

• Attach Payment Methodpaymentmethod.attach

  Binds an already-tokenised instrument. The tokenisation happens in the vendor's hosted field and never in a workflow.

• Create Paymentpayment.create

  MOVES MONEY. Raises a charge for a stated amount. A step wanting a customer to pay at their own pace wants a payment link instead.

• Refund Paymentrefund.write

  MOVES MONEY, outward. The processing fee is not returned, so a fully refunded payment leaves the operator down the fee rather than square.

• Create Payment Linkpaymentlink.write

  A reusable URL. Collects nothing until somebody follows it, so the step completes without money having moved.

• Create Checkout Sessioncheckout.write

  Single-use and expiring, unlike a payment link. A step creating one per customer and one creating a link per campaign are both correct and are not interchangeable.

• Create Invoiceinvoice.write

  The step a completed workflow resolves to. Raises a draft — nothing is owed until it is finalised.

• Finalise Invoiceinvoice.finalise

  Turns a description into a debt. Separate from creation precisely so an approval gate has somewhere to stand.

• Send Invoiceinvoice.send

  Delivers a finalised invoice. Does not collect — the payer follows the link at their own pace.

• Collect Invoiceinvoice.pay

  MOVES MONEY. Charges the method on file against an open invoice, and reports whether dunning begins.

• Create Subscriptionsubscription.write

  Begins a recurring agreement. Every later collection follows from this one step, which is why it is worth a review gate even though it collects nothing itself.

• Cancel Subscriptionsubscription.cancel

  Ends an agreement now or at period end. Counted as churn either way.

• Pause Subscriptionsubscription.pause

  Suspends collection without ending the agreement. Not churn, and a metric that counted it as such would understate retention.

• Resume Subscriptionsubscription.pause

  The same capability in the other direction — on this platform both are one write to one field. See the plugin's operations header.

• Publish Product and Priceprice.write

  Attaches a price to a billable product, making it sellable. Prices are immutable, so a price change is a new price rather than an edit.

Node kinds this connector would project. External entities enter the graph on exactly the terms internal ones do — the graph owns neither, and no database change is implied by any of it.

• Customerroot nodepayer.read

  A root. A billing entity may appear under several Stripe accounts on a multi-account estate and is still one entity.

• Productroot nodebillingproduct.read

  A root, and DISTINCT from a storefront product even where an enterprise sells the same thing through both. One is merchandised, the other is billed.

• Pricechild of billing-productprice.read

  A child. Prices are immutable, so a product accumulates them — a graph showing one price per product would show the wrong one for most subscriptions.

• Paymentroot nodepayment.read

  A root. It references a payer and a product and belongs to neither — it is the event that connects them.

• Refundchild of paymentrefund.read

  A child. A refund cannot exist without the charge it reverses, and is a fact about that charge rather than about the customer.

• Disputechild of paymentdispute.read

  A child, for the same reason. Raised by an issuing bank rather than by either party in the graph.

• Invoicechild of payerinvoice.read

  A child. An invoice is always raised against one billing entity, and an unpaid one is a receivable rather than a payment.

• Subscriptionchild of payersubscription.read

  A child. The agreement that generates invoices, which is why it hangs from the payer and not from the invoices it produces.

• Payoutroot nodepayout.read

  A root, and the operator's rather than a customer's. Hanging it under a payer would put the operator's treasury inside somebody's account record.

• Connected Accountroot nodeconnectedaccount.read

  A root. An account this platform acts for is a party in its own right, not a property of the platform that onboarded it.

Advisory reads this connector's data would support. The Decision Engine sees one instant and stores no history, so each insight states whether it is instantaneous or needs a series.

• Revenuepayment.read · refund.read

  Instantaneous. Settled charges less refunds. Both reads are required — revenue net of nothing is gross receipts, which is a different and larger number.

• Recurring Revenuesubscription.read · subscriptionitem.read · price.read

  Instantaneous, and the one figure here that is a projection rather than a measurement — it states what would be collected if nothing changed, which is never quite true.

• Subscription Growthsubscription.read

  Needs a series. A count of active agreements at one instant says nothing about direction, and direction is the whole question.

• Churnsubscription.read · subscriptionitem.read

  Needs a series. Cancellations over a period against the base at its start. A paused agreement must be excluded — counting it would report churn that reverses itself.

• Failed Paymentspayment.read · invoice.read

  Instantaneous. Both reads, because a declined checkout and a failed recurring collection are different problems needing different work.

• Refund Raterefund.read · payment.read

  Needs a series to be useful. The instantaneous ratio is computable and nearly meaningless — a refund is usually issued in a later period than the charge it reverses.

• Customer Lifetime Valuepayer.read · payment.read · subscription.read

  Needs a series, and a long one. The measured half is what a customer has paid; the projected half needs a churn rate, which itself needs history.

• Average Transaction Valuepayment.read

  Instantaneous. Settled charges over their count. Refunds are excluded deliberately — netting them in would report an average nobody was ever charged.

• Outstanding Invoicesinvoice.read

  Instantaneous. Finalised and uncollected. This is a receivable, and an alert reading it as revenue would report money the operator does not have.

• Payment Failure Ratepayment.read · invoice.read

  Needs a series. A rate that moved is the signal; a rate that is merely high may be the account's normal, and an alert on the level alone would fire forever.

• Payout Healthpayout.read · balance.read · balancetransaction.read

  Needs a series. A single failed payout is an incident; repeated ones are a bank detail problem, and only the second is worth waking somebody for.

• Dispute Ratedispute.read · payment.read

  Needs a series, and it is the one insight here with a hard external consequence — card networks impose monitoring above a threshold, so the trend crossing it matters more than the count.

• Revenue Trendpayment.read · refund.read · balancetransaction.read

  Needs a series, by definition. Included rather than omitted so a future rule author can see the shape it will read when history exists.

Figures this connector would publish to the Intelligence Center. Each names the capability that supplies it, so a metric cannot be charted for a grant that does not cover the read behind it.

• Total Revenuecurrencypayment.read

  Settled charges. Follows payment.succeeded rather than payment.created — an unconfirmed intent is not revenue.

• Paymentspaymentspayment.read

  Count of settled charges. Beside the revenue figure rather than instead of it — the two move independently and a change in either alone is the interesting case.

• Refundscurrencyrefund.read

  NEGATIVE REVENUE. Subtracted from the revenue figure, never added to it. The processing fee is not returned, so a full refund costs more than the charge earned.

• Subscriptionssubscriptionssubscription.read

  Active agreements, including paused ones. A pause is a suspension and not an ending, and excluding them would report churn that has not happened.

• Active Customerscustomerspayer.read

  Billing entities with a payment or an active agreement. Not the same population as a storefront's customers, and the two must not be added together.

• Failed Paymentspaymentspayment.read

  Declined charges. A rising count against flat revenue is the earliest visible sign of an expiring card estate.

• Outstanding Invoicescurrencyinvoice.read

  RECEIVABLE, not revenue. Finalised and uncollected, some of which will be voided. Adding it to revenue would book money that may never arrive.

• Payoutscurrencypayout.read

  Funds moved to the bank. A TRANSFER rather than a gain — the money was already the operator's, and counting it as income would count every payment twice.

• Disputesdisputesdispute.read

  Open chargebacks. The count matters more than the amount, because card networks monitor the RATE and impose programmes above a threshold.

• Recurring Revenuecurrencysubscription.read

  A projection of what would be collected if nothing changed. Beside total revenue and never summed with it — the same money appears in both.

• Churn% of subscriptionssubscription.read

  Needs a series the Intelligence Center does not store yet. Declared so the tile has a defined meaning when it does, rather than acquiring one later.

• Payment Success Rate% of attemptspayment.read

  Settled attempts over all attempts. Distinct from the connector's own health score: one measures whether customers can pay, the other whether the Hub can reach Stripe.

Shapes of agent this connector was built for, and the capabilities each requests. Never a connector key — an agent that could name a connector could import one, and the Fleet's isolation would be a convention rather than a structure.

• Finance Agentpayment.read · refund.read · refund.write · balance.read · balancetransaction.read · payout.read · invoice.read

  The one archetype trusted to return money. Reads treasury and issues refunds; cannot create a payout, because moving the balance is a decision above an agent.

• Billing Agentinvoice.read · invoice.write · invoice.finalise · invoice.send · invoice.pay · payer.read · paymentmethod.read

  Runs the invoice lifecycle end to end, including collection. Cannot refund — issuing money back is Finance's, behind a review gate.

• Revenue Agentpayment.read · subscription.read · subscriptionitem.read · billingproduct.read · price.read · price.write · coupon.write

  Prices and packages. Writes prices and coupons and touches no payment — the closest it comes to money is deciding what something costs.

• Sales Agentpayer.read · payer.write · paymentlink.write · checkout.write · checkout.read · promotioncode.write · price.read

  Creates customers and ways for them to pay. Cannot cancel an agreement or refund — both are retention and finance decisions rather than sales ones.

• Customer Success Agentpayer.read · payment.read · subscription.read · subscription.pause · invoice.read · paymentmethod.read

  Sees the whole customer and can pause an agreement to defuse a cancellation. DELIBERATELY CANNOT REFUND — a support conversation is the commonest route to an unreviewed refund.

• Subscription Managersubscription.read · subscription.write · subscription.cancel · subscription.pause · subscriptionitem.read · subscriptionitem.write · usagerecord.read · usagerecord.write

  Owns the agreement lifecycle and metered usage. Cannot refund and cannot invoice ad hoc — it changes what recurs, not what has already been charged.

• Accounts Receivable Agentinvoice.read · invoice.send · invoice.pay · invoice.void · payer.read

  Chases and collects. Can void a debt and cannot refund one — writing off what was never paid and returning what was are different acts with different approvals.

• CFO Agentbalance.read · balancetransaction.read · payout.read · dispute.read · payment.read · invoice.read · connectedaccount.read · tax.read

  Reads treasury and writes nothing. Not redundant with Analytics: this one sees balance, payouts and disputes, which is the operator's own position rather than customer behaviour.

• Analytics Agentpayment.read · refund.read · subscription.read · subscriptionitem.read · payer.read · invoice.read · checkout.read · usagerecord.read

  Eight reads, zero writes, read-only by construction. An analytics agent that could write is an analytics agent that can restate the thing it is measuring.

Archetypes, not roster entries. The Agent Fleet's own registry is unchanged by this connector existing.