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.
37 matching actions
Attach exactly one previously verified PaymentIntent or PaymentRecord to one invoice. Allocation and matching decisions remain in the workflow.
Delete one private invoice PDF staging transfer by opaque reference, within the current project and Stripe account. Call only after external evidence custody and SHA-256 verification; never deletes external finance evidence or contacts Stripe.
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.
Create exactly one explicitly approved tax ID after an independently completed duplicate check. The connector performs no lookup, normalization, tax decision or retry. Reuse the exact idempotency key on an authorized retry and independently retrieve the result; creation does not establish verification or update issued invoice snapshots.
Add one explicit draft line using either a positive manual amount or an existing account-bound Stripe price and explicit quantity.
Retrieve the exact account-bound invoice and download its finalized PDF into private temporary local staging. Refuses drafts; never finalizes or sends. Copy the returned local file to external finance evidence storage, verify its SHA-256, then clean up the transfer. The staged file is not a public media artifact or delivery evidence.
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.
Read one bounded page of one customer's tax IDs, with safe refs, exact value hashes and observed verification status. Exhaust all pages and compare type plus exact value hash before deciding whether an approved identifier is absent; there is no atomic uniqueness guarantee.
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.
Read one bounded catalog page preserving price type, currency and pricing structure; optionally include nickname and lookup key.
Read one bounded catalog page with safe product and default-price references; optionally include product name, description, and unit label.
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; return exact billing-detail and ordered invoice custom-field digests for independent readback, with optional sensitive business details. Customer defaults do not rewrite finalized invoice snapshots.
Independently read one account- and customer-bound tax ID. Report actual provider verification status, including pending, unavailable, unverified or null; do not infer verified from successful creation.
Read a previously discovered dispute by its account-bound reference, excluding submitted evidence and customer content.
Retrieve one invoice with its current customer expanded, customer snapshot digests, observed due date, footer digest, PaymentIntent method list, and hosted/PDF link availability states. recipient_pay_online_button_state=unverified never proves the button absent; draft_dashboard_link_state=not_exposed_by_stripe_api means no stable saved-draft review link is returned. For a draft PDF, inspect the selected invoice manually in Stripe Dashboard and verify whether its Download PDF action is available. Optional business details include invoice number, memo, customer snapshot name/email and available hosted invoice/PDF URLs; 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.
Read an account-bound price with fixed tier and currency-option expansions; preserve pricing facts without computing totals.
Read one account-bound product and its default-price reference, with optional selected business details.
Retrieve one previously discovered Stripe refund; this action never creates a refund.
Request Stripe customer delivery for one finalized invoice; the API has no operator-review recipient override and does not document inheriting Dashboard Email invoice without link. Never use this action to send a review copy or assume a Dashboard-only choice makes this API route no-link. 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.
Update only selected fields of one existing customer. Custom fields replace the entire list; independently retrieve current defaults, preserve every unrelated field in the approved replacement, then retrieve again to verify exact values. Customer defaults do not rewrite existing finalized invoices; independently inspect each invoice snapshot.
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 37 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.