Attach Stripe Payment to Invoice
Attach exactly one previously verified PaymentIntent or PaymentRecord to one invoice. Allocation and matching decisions remain in the workflow.
Stripe API transport for customers, invoices, payment lifecycle evidence, and balances. It contains no bookkeeping, collections, tax, or approval policy.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
26 matching actions
Attach exactly one previously verified PaymentIntent or PaymentRecord to one invoice. Allocation and matching decisions remain in the workflow.
Create a Stripe draft invoice in the explicitly approved currency that will later be explicitly finalized and sent.
Create one Stripe customer from explicit approved details and return an account-bound customer reference.
Add one explicit positive-amount line item to an explicit Stripe customer and draft invoice.
Finalize one reviewed draft invoice with auto_advance=false; this does not send it.
Return one bounded Stripe balance transaction page with gross, fee, refund, and net evidence.
Return one bounded Stripe charge page and a safe continuation reference, optionally filtered by customer or payment intent.
Return one bounded page of Stripe customers matching one exact email, so an existing customer can be used without a raw provider ID.
Read one bounded dispute page for exactly one charge or payment intent; no evidence content or dispute mutation is exposed.
Read one bounded page of items for exactly one invoice or customer; descriptions are exact UTF-8 SHA-256 digests by default, with optional scoped business text.
Return bounded payment lifecycle evidence for one Stripe invoice. Missing or null payment linkage preserves facts and pagination but cannot establish a payment match or settlement.
Return one bounded Stripe invoice page and a safe continuation reference when more results exist.
Temporarily unavailable in StackOS while the documented Stripe PaymentRecord listing endpoint availability mismatch is resolved. Inspect retained action audit/response files and retrieve a known PaymentRecord ref; if the ref is missing, hold for owner/provider recovery and never create a replacement report.
Return one bounded Stripe refund page for reconciliation evidence; this action never creates refunds.
Mark one verified fully settled invoice paid without creating a Stripe charge. It is never a partial-settlement fallback.
Report one verified bank transfer with a fixed custom Bank transfer method and guaranteed outcome. The bank reference is materialized only for provider dispatch and is never returned.
Retrieve current available and pending Stripe balance buckets for cashflow evidence; it never moves funds.
Retrieve gross, fee, and net evidence for one previously discovered Stripe balance transaction.
Retrieve one previously discovered Stripe charge by its safe reference; optionally include its description, receipt link and safe customer reference for matching.
Retrieve one previously discovered Stripe customer by an account-bound reference; optionally return reviewed name, email and description as sensitive business details.
Read a previously discovered dispute by its account-bound reference, excluding submitted evidence and customer content.
Retrieve one invoice with its current customer expanded, primary email digests and observed due date. Optional business details include invoice number, memo, customer snapshot name/email and hosted invoice/PDF links; additional billing recipients remain outside API visibility.
Retrieve verified PaymentIntent settlement evidence by an account-bound reference, excluding payment method, PII, metadata, and client-secret data.
Retrieve one reported PaymentRecord by an account-bound reference, exposing only settlement state, safe account references, and a bank-reference digest.
Retrieve one previously discovered Stripe refund; this action never creates a refund.
Request a send for one already finalized Stripe invoice. Sandbox/test mode sends no email; an accepted test request is not sent/delivered. Live acceptance is not inbox-delivery proof. Workflow approval and exception policy remain outside the connector.
Direct answer
People continue using Stripe as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
Common questions
The current catalog includes 26 Stripe actions across Stripe invoicing, Stripe payment lifecycle evidence. The exact actions used depend on the workflow and approval rules.
No. Stripe remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.