Stripe

Connect Stripe so Bantico can attribute completed payments back to the tracked link, campaign, source, medium, content, and lead that drove the customer.

How to connect Stripe

Here's the quickest way to connect Stripe to Bantico.

1. Open Stripe API keys.
2. Create a restricted key for Bantico.
3. Name it something like Bantico.
4. Add https://app.bantico.com as the allowed domain if Stripe asks for one.
5. Copy the generated key.
6. Open your Bantico project settings.
7. Go to Integrations.
8. Click Connect for Stripe.
9. Paste the restricted key.
10. Save the integration.

After that, Bantico can start using Stripe payment outcomes in your attribution reporting.

Consent-gated loading

Bantico uses visitor and session cookies to persist attribution on the same site. If you need consent-first behavior for EU users, only load Bantico after consent is granted.

1<script>2  window.BANTICO_TOKEN = "YOUR_TOKEN";3</script>4<script src="https://app.bantico.com/bantico.js"></script>

How attribution works

When a Stripe payment arrives, Bantico tries to resolve attribution using the strongest available context.

1. Stripe Checkout metadata
2. Tracked-link and campaign context already present on the session
3. Identified user data such as email, if available

The most reliable setup is always sending Bantico context directly into Stripe metadata when you create the checkout session.

Stripe Checkout metadata

When creating a Stripe Checkout session on your server, pass Bantico attribution context into metadata.

1import Stripe from "stripe";2 3const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!);4 5export async function POST(request: Request) {6  const { priceId, bantico } = await request.json();7 8  const session = await stripe.checkout.sessions.create({9    mode: "payment",10    line_items: [{ price: priceId, quantity: 1 }],11    success_url: "https://yourapp.com/success",12    cancel_url: "https://yourapp.com/pricing",13    metadata: {14      linkId: bantico?.linkId || "",15      campaignId: bantico?.campaignId || "",16      source: bantico?.source || "",17      medium: bantico?.medium || "",18      content: bantico?.content || "",19      leadId: bantico?.leadId || "",20    },21  });22 23  return Response.json({ url: session.url });24}

These metadata fields should match the same Bantico context you use in tracked links and events: linkId, campaignId, source, medium, content, and leadId.

Email fallback with identify

If a checkout is missing full link metadata, Bantico can still use identified user data as fallback context.

Call bantico.identify() when the user signs in or becomes known:

1bantico.identify({2  id: "user_123",3  email: "jane@example.com",4  name: "Jane Smith",5});

Direct Stripe metadata is still the preferred setup. Identify-based fallback is helpful, but it should not replace proper checkout metadata.

Learn more about identifying users.

Troubleshooting

If Stripe payments are showing up but attribution looks wrong, check the following:

1. You pass Bantico metadata when creating the checkout session.
2. The metadata values match the same tracked link, campaign, source, medium, content, and lead context used elsewhere in Bantico.
3. Stripe is connected in your Bantico project settings.
4. If you use consent-gated loading, Bantico only loads after consent.
5. Your checkout flow actually sends the metadata to Stripe on the server.

If everything looks correct and attribution is still off, contact support with an example checkout or payment so it's easier to debug.