# Production Stripe Billing

> The billing architecture, edge cases and tests your coding agent needs — installed into the app you already have.

Stripe solves payments. Udria solves the seam between Stripe and your application: how billing state maps onto your users, organisations and entitlements, what breaks, and how you prove it works. Your agent writes the code, in your repository, in your conventions.

Canonical product page: https://udria.co
Full research brief: https://udria.co/ai

## First product — Production Stripe Billing

Production Stripe Billing is Udria's first capability.

It is designed to help Claude Code or Codex implement production-grade Stripe subscription billing inside an existing SaaS application.

### Initial supported environment

| | |
| --- | --- |
| Framework | Next.js (App or Pages Router) |
| Language | TypeScript |
| Database | PostgreSQL or Supabase |
| Payments | Stripe |
| Coding agents | Claude Code and Codex |
| Prerequisite | An application that already exists |

> This list is the validated environment, not an aspiration. Compatibility with stacks outside it has not been validated and is not claimed.

## What Production Stripe Billing covers

> Status: this is the planned V1 scope. Production Stripe Billing has not been delivered yet — see "Current status" below. Nothing in this list should be read as already shipped.

The planned V1 package covers the following areas:

- Master implementation instructions
- Architecture and decision records
- Supported-stack and compatibility rules
- Stripe billing domain specification
- Database and data model
- Webhook behaviour
- Idempotency and event-ordering rules
- Subscription lifecycle
- Entitlements
- Upgrades, downgrades and cancellation
- Customer portal
- Security requirements
- Implementation sequence for Claude Code and Codex
- Acceptance criteria
- Runnable TypeScript acceptance tests
- Troubleshooting and verification

### Included with a founding reservation

- Every update to Production Stripe Billing v1.x
- Founding-customer status and pricing
- Direct installation support if your coding agent hits a problem with the package

Installation support covers the Udria package and getting it installed. It is not general engineering support for your application.

## What V1 does not cover

Production Stripe Billing does not attempt to reproduce the entire Stripe product suite.

### Stacks not supported in V1

- Rails, Django, Laravel, Go, .NET
- MySQL, MongoDB, Firestore
- Marketplaces and Stripe Connect
- Mobile app-store billing
- A greenfield project with no code yet

### Functionality outside V1

- Stripe Connect marketplace payments
- Complex multi-party payments
- Sophisticated tax configuration
- Physical point-of-sale
- App-store billing
- Complex enterprise invoicing
- Custom accounting system integration
- Arbitrary advanced usage-based pricing
- Enterprise revenue recognition

## How installation works

1. Customer adds the Udria capability package to their project (.udria/production-stripe-billing/).
2. Claude Code or Codex reads the capability.
3. The coding agent inspects the existing repository.
4. It identifies existing users, organisations, database conventions, authentication, design patterns and relevant infrastructure.
5. It maps the Udria billing architecture onto the existing application.
6. It creates the required database changes and Stripe integration.
7. It adapts billing UI and product behaviour to the existing application.
8. It runs the supplied acceptance tests.
9. Failures are repaired or clearly surfaced.
10. The customer reviews and deploys the resulting implementation.

> The coding agent executes the implementation. Udria supplies the implementation knowledge, architecture, edge cases and verification framework.

Udria does not deploy anything into a customer's production environment. Every change is made by the customer's own agent, in the customer's repository, and reviewed by the customer before it ships.

## Current founding offer

| | |
| --- | --- |
| Product | Production Stripe Billing |
| Founding price | $199 (USD) |
| Charged today | $0 |
| Payment type | One-off |
| Recurring Udria subscription | No |
| Expected price at public release | $299 |
| Current status | Founding reservation |
| Delivery deadline | 31 October 2026 |

### How the reservation works

1. The customer provides a valid payment method.
2. Stripe validates and saves the payment method.
3. Nothing is charged at reservation — $0 is taken.
4. The customer authorises a future one-off $199 charge.
5. Udria charges only when the founding product is ready for delivery.
6. The customer receives 3–5 days' notice by email before any charge.
7. The customer may cancel at any time before the charge.

> If Production Stripe Billing is not ready by 31 October 2026, reservations expire automatically and no card is charged.

The card is stored by Stripe, not by Udria. Cancelling a reservation detaches the saved payment method.

## Current status

Production Stripe Billing is currently offered as a founding reservation. It has not been delivered yet.

Udria is completing the first production release. The package described on this page is the planned V1 scope, not a shipped product, and this page will be updated as that changes.

| | |
| --- | --- |
| Release status | In development — founding reservations open |
| Delivery deadline | 31 October 2026 |
| What happens if it is late | Reservations expire automatically and no card is charged. |

---

Udria is operated by 815MC Ltd. Stripe is a trademark of Stripe, Inc. Udria is an independent product and is not affiliated with or endorsed by Stripe.