Lanlan.docs

Connect Stripe

Send Stripe payments straight to your site — a public donor wall, a fundraiser total, a private record of every transaction, or all three.

Connecting Stripe needs the Make-it-mine plan or higher ($15/month). See plans.

What this does

When someone pays you through Stripe, Lanlan can pick up the payment in real time and route the relevant pieces wherever you want them on your site:

  • A public list (collection) — e.g., a donor wall that grows automatically as donations come in.
  • A live counter — e.g., a fundraiser thermometer that ticks up with every payment.
  • A private record (form submission) — a record only you can see in your dashboard, kept separate from the public bits. Useful when the public-facing thing should be anonymous but you need the full info for thank-yous and accounting.

You can use any combination. A typical fundraiser uses all three: public donor wall + public total + private full records.

Set it up

This is a multi-step setup that touches both Lanlan and your Stripe dashboard. Claude walks you through it:

  1. Decide where Stripe payments should land. Tell Claude what you're trying to build and which fields from each Stripe payment matter to you. Example: "I want to wire Stripe to a donor wall — show the donor's first name and the amount, and total it on the home page."
  2. Claude creates the connector. Lanlan generates a unique webhook URL and a list of next steps in your Stripe dashboard.
  3. Add the webhook in Stripe. In Stripe: Developers → Webhooks → Add endpoint. Paste the URL Lanlan gave you. Subscribe to checkout.session.completed (and any other events Lanlan suggests).
  4. Copy the signing secret. Stripe shows a whsec_... string. Give it back to Claude — it tells Lanlan how to verify the webhooks really came from Stripe.
  5. Test with a test payment. Use Stripe's test mode to send a payment through. Lanlan shows it landing on your site within seconds.

Manage all of this from your dashboard's connectors page any time — swap field mappings, add destinations, rotate the signing secret.

Field mapping

You tell Lanlan which Stripe fields go where. The common ones are:

  • amount_total — the dollar amount (in cents — Lanlan can divide by 100 for you)
  • customer_name, customer_email — who paid
  • metadata_<key> — anything you stuffed into the Stripe payment's metadata at checkout
  • custom_fields_<key> — fields you defined on a Stripe Payment Link

Stripe Payment Links + custom fields is the easiest way to capture extras like "Make this donation anonymous (yes/no)" or "In honor of:".

Anonymous donors

If your public list should sometimes hide names, you handle that in the field mapping — typically a Stripe custom field "Make this donation anonymous?" maps to a display name that's either the donor's first name or the literal string "Anonymous." The full name still lands in the private record so you can write thank-you notes.

Anything you map into the public collection is public. No PII filter sits between Stripe and your site — you decide what's safe to show.

What's supported

  • One-time charges — checkout.session.completed, charge.succeeded, payment_intent.succeeded. The Stripe events that fire when someone pays.

What's not supported yet

  • Recurring subscriptions — the events that fire when a subscription renews aren't handled yet. One-time donations work fine; monthly recurring billing doesn't surface on your site.
  • Refunds, chargebacks, and disputes — these don't reverse a public list entry or roll back a fundraiser total.

If either of those is a hard requirement, email support and tell us what you're trying to do.

What to try next

If you get stuck

Ask Claude. "I can't figure out how to…" almost always gets you unstuck. For anything Claude can't help with, email support.