# Stripe

Connect a Stripe account so its payments count as sales on the ad campaigns that brought them, with refunds taken off.

Connect a Stripe account and each paid charge becomes a `Purchase`, counted on the ad campaign that brought the buyer. New customers can reach your ad platforms too.

A connected account uses `platform: "stripe"` and represents one Stripe account.

## Quick reference

| Property | Value |
|----------|-------|
| Platform value | `stripe` |
| What arrives | A `Purchase` event for each paid charge, from Checkout, Payment Links, invoices, subscriptions or the API |
| Refunds | A partial refund lowers the sale's value; a full refund retracts it |
| Event source | `stripe` in `GET /v1/events` |
| Tied to its ad | When the payment carries a click id or UTM tag in its metadata |
| Auth | Stripe Connect OAuth, read-only |
| Accounts per profile | One |
| Subscriptions | `StartTrial` when a trial starts, `Subscribe` on the first paid invoice |
| Forwarded to ad platforms | Optional, off by default: one-off sales, new subscribers and trials, never renewals |
| Social posting | No |

## Before you start

Stripe is in private beta. Until it opens, connecting it answers `403 feature_not_available`.

The person connecting must be able to sign in to the Stripe account. Zernio asks for read-only access: it can see payments but change nothing.

## Connect

Call `GET /v1/connect/stripe` with the profile and send the user to the returned `authUrl`. They pick the Stripe account and approve read-only access. See [Connect](/platforms/stripe/connect).

## In this section

<PlatformPages platform="stripe" />

## Related

- [Get Stripe connect URL](/connect/get-stripe-connect-url)
- [Conversions API](/products/conversions-api)
- [Campaign results](/guides/campaign-results)
- [Connecting accounts](/guides/connecting-accounts)