Reservation terms
1. What a reservation is
A reservation is an authorisation to charge your payment method once in the future. It is not a subscription, a membership, or a recurring payment of any kind.
2. Nothing is charged today
$0 is charged when you reserve. We do not create a payment and we do not place an authorisation hold on your card. Stripe securely stores your payment method for later use; Longrad Ltd never receives or stores your full card details.
3. The single future charge
By ticking the authorisation box you permit Longrad Ltd to charge your saved payment method a one-off amount of $199 (USD) when Production Stripe Billing is ready for delivery. No other charge will be made.
4. Advance notice
We will email you 3–5 days before we charge you. That email will state the exact amount and date and will contain a cancellation link.
5. Cancellation
You may cancel at any time before delivery, from the link in any email we send you or at Udria/cancel. On cancellation we detach your payment method from our Stripe account and you will never be charged. No reason is required and no contact with us is necessary.
6. If we do not ship
If Production Stripe Billing is never delivered, you are never charged. There is nothing to refund because nothing is taken up front.
7. Delivery date and remedy
Delivered by 31 October 2026. If Production Stripe Billing is not ready by then, your reservation automatically expires and you will not be charged.
Expiry is automatic. Your payment method is detached and you do not need to do anything to claim this.
8. Compatibility scope
V1 of Production Stripe Billing is designed for Next.js applications written in TypeScript using PostgreSQL or Supabase, installed by Claude Code or Codex. We do not claim compatibility with other frameworks, languages, databases or agents. If your stack is outside this scope, please do not reserve.
9. What the product is
Production Stripe Billing is a versioned, agent-readable capability package installed into your own repository: implementation instructions, architecture and decision records, compatibility rules, the billing domain specification, data model, webhook behaviour, idempotency and event-ordering rules, subscription lifecycle, entitlements, plan changes, customer portal, security requirements, an implementation sequence, acceptance criteria, runnable TypeScript acceptance tests, and troubleshooting.
You give the package to Claude Code or Codex. It analyses your existing repository, adapts the implementation to it, builds the capability, and verifies the result against the included acceptance tests. We do not ship application code you have to adopt, and we do not run the implementation ourselves.
It is software tooling. It is not a hosted service, it does not process payments, and it does not replace your relationship with Stripe.
It is not a guarantee of the correctness, security, tax position, accounting treatment or regulatory suitability of your application. You remain responsible for reviewing, testing and operating the code in your product.
10. Costs not included
- Stripe’s payment-processing fees, which remain between you and Stripe.
- Your own Claude, Codex or other AI usage costs.
- Your own hosting and infrastructure.
11. Licence
The founding release is licensed for your own use and for the projects you or your company build. You own the code your agent produces in your repository, permanently and without restriction.
We ask that you do not redistribute or resell the specification files themselves. We are aware that a text package is trivially copyable and that this request is not technically enforceable; we are stating the expectation rather than pretending to police it.
12. Price and founding status
Your founding price of $199 is fixed at the moment you reserve and will not increase, whatever the eventual public price is. We expect that price to be $299 at public release.
Founding customers receive every update to Production Stripe Billing v1.x at no further cost, retain founding-customer status and pricing, and can ask us directly for help if their coding agent hits a problem installing the package. Installation support covers the Udria package and getting it installed. It is not general engineering support for your application.
13. Contact
Questions about these terms: hello@udria.co.