Stripe for Sellers
The bounded Stripe surface the Recued seller substrate needs, and nothing else. Selling through Stripe takes ten operations; the Full Stripe API front door carries 611 across thirteen packs, and granting that to run a checkout is a consent surface nobody reads. Every operation here is hand-authored to one job: open one hosted Checkout Session — one-time over an inlined price, or recurring over a real recurring Price — with explicit Recued workflow correlation, and re-read Session, payment, refund, dispute, subscription, invoice, entitlement and invoice-payment truth at the provider so an order only ever moves on evidence. The reads never ask, because the verified-event flows that depend on them run unattended. Install the Full Stripe API alongside this if you also want the rest of Stripe; the two are independent, and a same-named read on each is a distinct operation id, so grants and consent never collide.
What this pack installs
- seller-stripe Ingredient
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.