How to charge a subscription in an AI-built app and unlock features only for those who paid Ciro Cesar Maciel released Payments, an infrastructure product that lets AI-built apps charge subscriptions through the developer's own Stripe account while gating features by entitlement rather than plan. The system organizes projects, gateways, plans and features so the app checks whether a user has a specific feature such as advanced-reports, with a React SDK (PaymentsProvider, Pricing, FeatureControl, PortalButton) and a server-side /sdk/v1/permissions endpoint that returns active subscription status and unlocked features. Maciel stresses that client-side feature checks only control the interface, and the paid resource itself must be refused on the server: "That one line on the server is the difference between a paywall and a hidden button. The app the AI helped you build has users, and now you want to charge. The agent usually proposes wiring Stripe directly: products, checkout, a webhook endpoint, subscription state in your database, a check on every screen. It works, but those pieces have to agree with each other. And the classic mistake of an app built in a hurry is hiding the paid button in the frontend while the server route stays open. This is the path with Payments, from the Infrastructure line by Ciro Cesar Maciel, who writes this . A project holds gateways ; each gateway holds plans ; a customer subscribes to a plan and gets the features linked to it. The app never asks "which plan is this user on?". It asks "does this user have advanced-reports ?". Changing what each plan includes needs no code change. Recurring billing happens in your Stripe account: the money, the invoices and the receipts live there. Payments organizes plans, follows subscriptions through Stripe's events and tells the app who can do what. https://myinfrastructure.click/products/payments/llms.txt . No account yet? The agent creates it and the project itself; you only read the e-mail code. sk test … connects, answers everything with success and charges no one. @ciromaciel/payments-react , a PaymentsProvider with the project's public key, your own stable userId and the customer's e-mail. Then