Stripe
Stripe handles card payments, subscriptions, and invoicing for the apps you build with Appsanic. Connect it inside a project and the agent can wire checkout and subscription code for that project.
This is web and card payments. For native in-app purchases (the App Store and Play Store flows that platforms require for digital goods), use RevenueCat instead. The Payments guide covers which one your app needs.
What you get by connecting it
With a standard sk_ key connected and Account access on, an eligible build can use bounded server-side tools:
- Products and prices. The agent creates the products and prices your app charges for, directly in your account, so the IDs your app uses are real from the first build.
- Webhook guidance. It generates the backend handler and exact manual steps for registering a narrowly scoped endpoint and placing its signing secret in the backend environment.
- Embedded publishable key. Your publishable key is placed where the app needs it on the client, while the secret key stays server-side.
Every successful product action lands in the connector's Activity feed. A restricted rk_ key can connect for validation, but product automation stays unavailable because Stripe offers no non-mutating way to prove Products write permission.
Connecting it
Stripe gives you two connector keys:
- A publishable key (starts with
pk_) - safe to embed in the app. - A secret key (starts with
sk_) - server-side only, never bundled into the app.
Find the keys in the Stripe Dashboard under Developers then API keys.
Open the project build, select Connectors, choose Stripe, and enter a matched publishable and secret key from the same Stripe mode. Connector OAuth is not currently available. Saved secrets are shown as dots once stored, never the value. Use Test now to re-check them or Disconnect to remove them from the project.
If the app needs webhooks, deploy the signature-verifying handler first, register its exact HTTPS URL in Stripe, choose only the implemented events, and put that endpoint's whsec_ value directly in the deployed backend's secret manager. Appsanic does not collect it; never paste it into chat or the connector form.
The Stripe connection applies only to the project where you save it and requires a paid plan.
Keys and security
Stripe supports Account access, which is off until you opt in. With a standard sk_ key, eligible tools can create products and prices without placing the key in the model prompt. An rk_ connection remains validation-only even if toggled on; use Stripe Dashboard steps for its catalogue. Endpoint registration, webhook-secret provisioning, refunds, and destructive operations remain manual.
Managed connector secrets are encrypted at rest with AES-256-GCM. Browser JavaScript sees only that a secret exists, and the model prompt never receives it. The saved key is control-plane only. Only the publishable key can be embedded; provision a separate restricted key directly in the deployed payments backend regardless of which connector key you chose.
Useful links
- Stripe documentation: https://docs.stripe.com
- Appsanic Payments guide - when to use Stripe versus native in-app purchases.
Next
Read Payments for how to choose between Stripe and native in-app purchases, and how to wire each one into your app.