DIY blueprint

Connect your AI-built web app to commerce, subscriptions and access.

Use this as a practical handoff for your AI coding tool or developer. The goal is simple: your app should not rebuild billing. LetsOrderIt powers commerce, subscriptions, CRM and customer records. AccessGate handles login and verified access.

Open full integration docs Ask us to help

Core architecture

Your web app = product experience
LetsOrderIt = commerce engine, checkout, subscriptions, customers, CRM
AccessGate = login, token verification, access status
Customer = pays/signs up through LetsOrderIt, logs in through AccessGate

Recommended app routes

/creator
/api/auth/accessgate/callback
/api/me/access
/api/loit/payment-confirmed
/api/loit/verify-payment
/activate
/connect-loit-item

Golden rule

Redirect is only user experience. Webhook is only a signal. Verified access/payment is proof. Fulfill or unlock features only after a server-side verification returns valid.

AI/developer prompt

Build this app using LetsOrderIt as the commerce and subscription engine and AccessGate as the login/access layer.

Do not build billing inside the app.

The app should:
1. Let customers log in through AccessGate.
2. Ask AccessGate/LetsOrderIt for the customer access status.
3. Unlock features based on the active plan, such as Free, Standard, Premium or Enterprise.
4. Treat redirects as UX only, not proof of payment.
5. Treat webhooks as a signal only.
6. Verify payment/access server-side before fulfillment.
7. Store fulfilled orders idempotently so the same order cannot issue twice.
8. Keep app-specific product logic inside the app, but keep commerce/subscriptions/customers in LetsOrderIt.