Stria and Stripe

Your Stripe account, your money, your merchant relationship — Stria issues the invoice.

Plans: Available on every plan, including free. See plans and pricing

Stria issues invoices and collects payment through your own Stripe account, not through a Stria

balance you withdraw from. That distinction decides who owns the customer relationship, who handles

a dispute, and whether card data ever reaches us.

What the connection is

Stripe Connect Standard. You connect an existing Stripe account, or create one during the flow,

and it stays yours: you can log into it directly, it keeps its own dashboard, and disconnecting Stria

does not affect it.

Your connected account is the merchant of record. It owns payouts, refunds, disputes and tax.

Stria never holds your funds at any point.

Card entry happens only on Stripe-hosted pages, reached by a full redirect rather than an embedded

frame. Stria never sees, stores or transmits a card number.

That arrangement is what keeps this on the SAQ A side of PCI — the lightest self-assessment tier,

which applies when all cardholder data functions are outsourced to a validated third party. It is a

statement about scope, not a certification: Stria is not PCI certified and does not claim to be.

Stria takes no percentage of what you collect. Stripe's own processing rates apply exactly as they

would if you invoiced from Stripe directly.

Stated precisely, because comparison pages tend to overclaim here: on card payments this is roughly a

wash against any tool that also uses your own Stripe. The saving is the absence of a platform fee on

top, not a better card rate.

Issues an invoice, including to a client with no project and no deliverable attached
Records partial payments against it
Applies a discount before tax, with the reason recorded against the client
Carries a required purchase-order number where a client needs one
Runs a reminder ladder and a stated late fee, on a Stripe invoice rather than only an offline one
Writes off what will never arrive, without deleting the record of it

Payment state is writable only by the signature-verified Stripe webhook under a service role,

never by a browser. The payment ledger is append-only, enforced by database triggers, and a late fee

can apply once.

A deposit invoice can gate the work: deliverable files are withheld server-side until the deposit

clears, at the same chokepoint that mints the signed URL. The withholding is real rather than a

hidden button.

One connected account per workspace.
Refunds and disputes are handled in your Stripe dashboard, because your account owns them.
Payout timing is Stripe's and your bank's, not Stria's.

Reconciling into a ledger is a separate connection — see Xero or

QuickBooks Online. For where an invoice gets its due date, see

Stria and Slack — Scope checks on the channels you nominate — and a consent screen with four scopes on it.
Stria and Xero — Invoices and payments pushed to your ledger, and reconciliation read back.
Stria and QuickBooks Online — Invoices and payments pushed to your ledger, and reconciliation read back.
Stria and Asana or Linear — Push an approved item to the tracker your team already works in. One way, one item at a time.
Webhooks and the API — Signed HTTPS events when work is approved or money moves, plus token-authenticated endpoints.