Plans describe access
Attach stable feature keys to a plan instead of scattering payment-provider product IDs through application code.
Customer BillingPlanned
Connect paid access to the identity that owns it.
NamoID is designing provider-neutral billing in which a subscription belongs to a user or customer organization and produces a versioned entitlement snapshot your application can verify.
Organization context matters
Resolve paid access for the active organization while keeping any personal subscription separate from company access.
India operations are explicit
The design accounts for INR pricing, tax evidence, local processors, mandates, reconciliation, and billing-data privacy.
Product scope
The billing boundary we are designing—and what is not shipped.
Customer Billing is an approved design direction, not a generally available product. NamoID does not currently collect customer subscription payments, issue GST invoices, provide UPI Autopay or NACH, or place billing entitlements in production customer tokens. Processor support, tax behavior, pricing, and availability will be published only after implementation and review.
- Planned user and organization plan types
- Planned stable feature and entitlement keys
- Planned flat and per-seat subscription models
- Planned seat checks across invite, acceptance, and JIT
- Planned provider-neutral checkout boundary
- Planned Razorpay adapter as the first payment integration
- Planned signed provider webhooks and reconciliation
- Planned billing and entitlement audit events
Planned