Stripe

Stripe handles card payments, subscriptions, and invoicing for the apps you build with Appsanic. Connect it once and the agent can wire a real checkout into your app, set up recurring plans, and keep your backend in sync with what Stripe knows about each customer.

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 Stripe connected and Account access on, the agent works inside your Stripe account using 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 endpoints. It registers webhook endpoints and captures their signing secrets, so your backend can trust the payment events Stripe sends.
• Embedded publishable key. Your publishable key is placed where the app needs it on the client, while the secret key stays server-side.

Every action lands in the connector's Activity feed, so you can see exactly what was created in your account and when.

Connecting it

Stripe gives you two keys, plus an optional third value:

• 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.
• An optional webhook signing secret - used to verify that incoming events really came from Stripe.

Find the keys in the Stripe Dashboard under Developers then API keys.

To connect, go to Dashboard then Connectors then Stripe. Stripe is one of the two connectors with one-click OAuth, so you can use Connect with Stripe to authorise without copying keys by hand, or paste the keys into the form as the fallback. Saved secrets are shown as dots once stored, never the value. The page has a Test connection control to re-check the credentials against the live service, and a Disconnect control to remove them.

Connectors are account-wide: connect Stripe once and every project in the account can use it. Connecting requires a paid plan.

Keys and security

Stripe is an Account access connector, alongside Supabase and Resend. The Account access toggle is off until you opt in. With it on, the agent acts inside your Stripe account with server-side tools - creating products and prices and registering webhook endpoints - and it never sees your secret key. Left off, the agent writes the payment code plus step-by-step setup instructions for you to run yourself.

Managed connector secrets are encrypted at rest with AES-256-GCM. The browser only ever sees that a secret exists, shown as dots, never the value. The agent never sees a decrypted secret and never asks for a key in chat. Your secret key stays server-side; only the publishable key is embedded in the app.

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.