Payments

Overview

Solitud can wire payments directly into the app it builds for you — one-off checkout, subscriptions, donations, or paywalls. You bring an account with a payment provider; Solitud builds the checkout flow and the webhooks that keep your app in sync.

You ask in chat, the AI asks for what it needs, and the integration is built and verified like any other feature.

Recommended: a Merchant of Record

For most builders, Solitud recommends a Merchant of Record (MoR) such as Lemon Squeezy or Paddle.

A Merchant of Record sells your product on your behalf and takes on the parts that are painful to do yourself:

• Sales tax and VAT — calculated, collected, and remitted for you.
• Compliance and fraud handling.
• Customer invoices and receipts.

Why this matters. With a plain payment processor, you are responsible for tax registration and remittance in every jurisdiction you sell into. An MoR absorbs that, which is usually the right trade for small teams and solo builders.

Provider support

Solitud has no fixed, "supported" list — payments are integrated adaptively by the AI, not wired from a hardcoded set of connectors. Think of it as two tiers:

Highest success rate. The well-trodden providers below integrate the most reliably — clean APIs, standard checkout, well-understood webhooks. Reach for one of these when you can:

Anything else — ask anyway. Beyond this list, Solitud can attempt almost any provider that exposes a checkout link, or an API plus webhooks. There's no guarantee here: a niche or thinly-documented provider can be harder to implement, and some take a few rounds to get right — but Solitud's AI will persevere and do its best to make it work. If it hits a real wall, it'll tell you what's blocking and suggest the closest well-supported alternative.

How to add payments

Just describe what you want to charge for:

Add a $9/month Pro subscription. Subscribers get access to the reports page.
Use Lemon Squeezy.

Solitud will:

1. Recommend an approach (and a provider, if you didn't name one). For a multi-step provider you'll often get a setup card showing the steps and exactly which credentials you'll come back with.
2. Ask for the secrets it needs via a secret card (API key, webhook signing secret, etc.).
3. Build the checkout flow in your app.
4. Set up the webhook endpoint so your app knows when a payment succeeds.
5. Run and verify the flow.

Connecting securely

Payment providers issue secret keys. Solitud collects these through a dedicated, masked secret card — you can paste the value, upload it as a file, or have Solitud generate one — and stores it encrypted on the workspace.

Your secrets are never shown to the AI. You can reveal a stored secret yourself under Settings → Secrets after a two-factor check, where it stays visible for a short window. The AI building your app never sees the raw value — it's kept out of code, logs, exports, and screenshots.

Provide only what the AI asks for, when it asks — you don't need to paste keys preemptively.

Webhooks

Most payment flows depend on webhooks — the provider calling your app to confirm an event (payment succeeded, subscription cancelled, refund issued). Solitud builds the webhook endpoint inside your app and hands you the URL on an instructions card, with a Copy button.

Webhook URL:  https://ws-<id>.solitud.dev/api/webhooks/<provider>

Add that URL in your provider's dashboard, paste back the signing secret when the secret card asks, then use the card's Recheck button so Solitud can verify your app reacts to real payment events.

Going live checklist

Before you take real money:

• Switch your provider account from test/sandbox to live keys.
• Update the stored secrets in Solitud to the live values.
• Register the production webhook URL with your provider.
• Run one real, small end-to-end purchase and confirm your app reacts.
• If using a plain processor (Stripe/PayPal), confirm your tax approach.

Test thoroughly in sandbox first. Payment bugs are best caught with fake money.