npx @insforge/cli secrets get ANON_KEY, or in the dashboard: click Install and open API Keys.
InsForge Payments is provider-specific. Stripe uses hosted Checkout and Billing Portal. Razorpay uses provider-native Orders and Subscriptions plus Razorpay Checkout. The TypeScript SDK exposes separate provider modules for both.
Stripe Payments
Create Checkout and Billing Portal sessions with
insforge.payments.stripe.Razorpay Payments
Create Orders or Subscriptions with
insforge.payments.razorpay, then open Razorpay Checkout.Shared setup
Fulfillment
For both providers, create app-owned tables such aspublic.orders, public.credit_ledger, or public.team_entitlements, then populate them from verified provider webhook events in payments.webhook_events.
payments.transactions is a dashboard/reporting projection. Do not use it as the primary business workflow.
Next steps
- Use Stripe Payments for
insforge.payments.stripe.createCheckoutSession(...)andinsforge.payments.stripe.createCustomerPortalSession(...). - Use Razorpay Payments for
insforge.payments.razorpay.createOrder(...),createSubscription(...), verification, and subscription management. - Read Payments overview for the shared database architecture and fulfillment model.