> For the complete documentation index, see [llms.txt](https://themochi-app.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themochi-app.gitbook.io/documentation/module-6-integrations-and-tracking/payment-integrations.md).

# Payment Integrations

## Payment Integrations

**What it is** — Connect Stripe, Whop, FanBasis, or Ablefy so payments sync into Mochi directly — clients, transactions, revenue, and costs, matched back to the leads and conversations that produced them. Once connected, commissions, processing fees, and net revenue calculate automatically.

**Who can use it** — Connecting a payment provider follows the same gating as the rest of Settings > Integrations: Creator and Manager roles, on web and iOS.

**Before you start** — An account with one of the four supported providers: Stripe, Whop, FanBasis, or Ablefy, and an API key from that provider.

### How to connect

1. Go to **Settings > Integrations > Payments**.
2. Choose your provider — Stripe, Whop, FanBasis, or Ablefy.
3. Paste the API key from that provider and save.

Repeat for any additional provider you use — connecting one doesn't stop you from connecting another.

### Real-time sync vs. delayed sync

If you're connecting Stripe, use an API key that includes **webhook-creation permission** — that gets you real-time sync, so payments show up in Mochi as they happen. Without that permission, Mochi still syncs your Stripe data, just on a delay of roughly 24 hours instead of instantly. This nuance is specifically documented for Stripe; the sync cadence for Whop, FanBasis, and Ablefy isn't separately detailed in current sources.

### What syncs

Once connected, Mochi brings in:

* Clients/customers from the provider
* Transactions
* Revenue
* Costs (processing fees, refunds)

Everything is matched back to your leads automatically, by **email and Instagram handle**. Some payments come through unmatched — usually because the identifying info on the provider side doesn't line up with what's saved on the lead — and need manual matching.

### Where it appears

**Dashboard > Payments** — a Payments tab sits alongside Home, Performance, and Links on the web Dashboard, when enabled for your organization (gated). See the Payments dashboard article for how to read it once connected.

### It also feeds your ad tracking

Connected payment data feeds Meta's Conversions API (CAPI) too — if you're running Meta ads, this helps close the loop between an ad and an actual sale, which can improve targeting and reduce acquisition cost over time. That's a separate setup from the payment connection itself; see `themochi.app/meta-ads`.

### Commissions, fees, and net revenue

Once a provider is connected, Mochi automatically calculates:

* **Setter/closer commissions** — from the commission % set on each team member (Settings > Team)
* **Processing fees** — per-provider fees on each transaction
* **Net revenue** — revenue after fees and refunds

No manual math, and no back-filling — figures update as payments come in.

### Manual logging (the fallback, not the primary path)

Before direct provider sync existed, teams logged collected payments by hand: from a lead's profile or conversation, an **Add Payment** action lets a Closer manually record a payment against that lead. That's still there as a fallback — useful for a provider outside the four directly-synced options, or for cash and off-platform payments — but it isn't the primary workflow anymore. If you're on Stripe, Whop, FanBasis, or Ablefy, connect it directly instead of logging payments by hand.

### Tips

* Connect your payment provider early so commission math and dashboard revenue are accurate from day one, instead of back-filling manually logged payments later.
* If you're on Stripe and want real-time sync, double-check the API key includes webhook-creation permission before you paste it in — it's the difference between instant updates and a \~24-hour delay.
* If a payment shows as unmatched, check that the email (and/or Instagram handle) on the provider side matches what's saved on the lead's Mochi profile.

### Common mistakes & fixes

| Mistake                                                                  | Fix                                                                                                                               |
| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| Using a provider outside the four supported ones                         | Not directly supported today — log payments manually with Add Payment instead.                                                    |
| Payments showing as unmatched                                            | The identifying info (email/Instagram handle) likely doesn't line up between the provider and the lead record — match it by hand. |
| Expecting real-time Stripe sync with a key that lacks webhook permission | Reissue a Stripe API key with webhook-creation permission, or expect syncing on a \~24-hour delay instead.                        |
| Assuming every role can see payment data                                 | Only Creator, Manager, and (where present) Finance roles see payment data.                                                        |

### Limits & good to know

* Only four providers are directly supported today: Stripe, Whop, FanBasis, and Ablefy.
* Real-time sync depends on Stripe webhook permissions specifically; otherwise expect up to a \~24-hour delay.
* Payment data visibility is limited to Creator, Manager, and Finance roles.

**Related:** Payments dashboard, Mochi AI (Ask Mochi), Mochi + Claude (MCP), Zapier integration