Payments and product emails wired before you start customising.
Toolbound Stack gives you a working checkout, webhook, buyer delivery email, onboarding email, and purchase records so your first agent session can focus on the product.
Stripe Checkout handles the founder licence purchase flow.
Resend sends buyer delivery and onboarding emails after the paid webhook lands.
Postgres stores purchases and release metadata for fulfilment.
The included docs explain which keys to add and how to verify the flow.
Payment flow
Stripe is treated as a production path, not a demo button.
The stack is built around the moment money changes hands: checkout creation, paid webhook verification, purchase records, delivery state, and buyer email. That gives your agent a working payment path to preserve while it builds the product-specific parts.
Checkout session creation for the one-time product licence.
Webhook verification before a purchase is treated as paid.
Postgres records for purchase and release delivery state.
Setup checks that flag missing payment configuration before launch.
Email flow
Resend gives the product a clean transactional email layer.
New SaaS builders often leave emails until the last minute, then discover confirmation, onboarding, and support handoff messages are part of the product. Toolbound centralises that layer so an agent can extend it safely.
Buyer delivery and onboarding templates are included.
Support and internal seller alerts have a documented path.
Agent-added email events can reuse the same provider and conventions.
Secrets stay in local env or deployment secret stores, not pasted into chat.
FAQ
Common questions
Can I take one-time payments?
Yes. Toolbound is currently packaged around a one-time founder licence flow, with Stripe Checkout and webhook verification included.
Can I change it to subscriptions later?
Yes, but that is a product customisation task. The existing billing docs and commercial flow notes give your agent a safer starting point.
Can an agent send emails through Resend?
Yes, if you wire the product event deliberately. The stack documents the email provider and keeps API keys in environment secrets.