Integrations

Rekomi connects to the rest of your stack in two ways. Native billing connections drive the money flow: incoming sales become attributed conversions. Stripe Connect is the deepest (it also powers outgoing payouts as Stripe transfers); Paddle, Braintree, and Shopify connect natively for conversion tracking too, and any other billing platform attributes via the server-to-server API. Zapier drives the operational flow: Slack pings, Mailchimp tags, HubSpot deal updates, Google Sheets rows, Typeform-driven approvals, anything you want to wire across the 8,000+ apps Zapier supports, with no code.

Zapier

The Rekomi app on Zapier exposes 9 triggers, 9 actions, and 4 searches. Use it to notify your team when an affiliate signs up, sync conversions into your CRM, send urgent emails on failed payouts, auto-tag approved partners in your email tool, or approve vetted applicants the moment they submit a Typeform, all without writing code.

Connection is one click: search for Rekomi in Zapier, click Connect, sign in at app.rekomi.com/oauth/authorize, pick your org, click Allow. Connections are per-Zapier-account, so each teammate connects their own Rekomi login and the audit trail stays clean. Requires the Starter plan or above.

Full walkthrough, trigger / action / search catalog, six worked recipes, error handling, and the OAuth security model are in the Zapier integration guide.

Stripe Connect

Stripe Connect is the deepest native connection. Sales come from your Stripe webhooks, and payouts flow through Stripe Connect transfers. (Paddle, Braintree, and Shopify connect natively too, covered below; any other gateway tracks via the S2S API.) We never hold your customer's money or your affiliate's money. This section explains the Stripe connection flow and the data model.

Where to connect

/dashboard/integrations shows your Stripe connection status. If you are not connected yet, click "Connect Stripe" and Rekomi sends you to Stripe's OAuth authorize page.

What Rekomi requests

The OAuth scope set we request:

• Read your subscriptions, invoices, customers (to identify which customer was referred and how much they paid).
• Write transfers via Stripe Connect (to pay affiliates out of your balance when you run a payout batch).
• Read your account information (to display your account ID and prevent accidental rebinding to a different Stripe account).

What Rekomi stores

After OAuth completes, we store on your organization record:

• StripeConnectAccountId (your acct_... identifier)
• StripeConnectScope (the scope strings you authorized)
• StripeConnectConnectedAt (the timestamp)

We never store your raw API key. The OAuth flow gives Rekomi a per-org access token managed by Stripe.

Rebinding protection

If you try to connect a different Stripe account to an organization that already has one connected, the callback rejects the rebind. This is a security control: it prevents a compromised Clerk session from silently swapping in an attacker-controlled Stripe account. To change Stripe accounts, contact support.

Webhooks Rekomi listens for

Once connected, Rekomi processes these Stripe events to drive the platform:

• checkout.session.completed (for billing on your Rekomi subscription)
• customer.subscription.created, customer.subscription.updated, customer.subscription.deleted (your customers' subscriptions)
• customer.subscription.trial_will_end (for your own Rekomi trial)
• invoice.paid, invoice.payment_failed, invoice.upcoming (drives sales attribution and refund clawback)
• customer.updated (syncs billing email)
• payment_method.attached (logged for audit)

The webhook handler verifies signatures with the webhook signing secret and sets the org context before any writes, so multi-tenant isolation holds.

Disconnecting

There is no in-app disconnect today (no /integrations UI button for revoke). To disconnect, revoke the Rekomi connection from your Stripe dashboard's "Connected applications" page and contact support to clear the stored fields on your org record. We will add a self-serve disconnect flow in a future release.

Affiliate-side Stripe Connect

Note that affiliates also use Stripe Connect, but on the affiliate side. They connect their own Stripe Express account to receive payouts. That is a separate flow documented in Affiliates: Stripe Connect. Brand Stripe Connect and affiliate Stripe Connect are independent.

Paddle

Brands on Paddle Billing connect natively, with no backend relay to build. You point a Paddle notification destination at a webhook URL unique to your workspace and paste its signing secret into Rekomi; Rekomi verifies every event and records the conversion. This is for tracking your sales (so affiliates get credited) and is independent of how you pay for Rekomi.

Where to connect

Setup → Connect payment processor → Connect Paddle. Rekomi shows your unique webhook URL and the exact events to enable. The step-by-step guide is Install on Paddle.

How it works

• You carry the affiliate referral into Paddle Checkout via customData.rekomi_ref (the affiliate's link slug).
• Paddle sends transaction.completed, subscription.created / subscription.updated / subscription.canceled, and adjustment.created / adjustment.updated to your Rekomi webhook URL.
• Rekomi verifies the Paddle-Signature (HMAC-SHA256 over the timestamp-prefixed raw body) with your destination's signing secret, then records sales and reverses commission proportionally on refunds and chargebacks.

What Rekomi stores

The destination signing secret and the optional read-only API key are encrypted at rest and never returned by the API. Rekomi also keeps a per-workspace routing token (the id in your webhook URL) and connection-health timestamps.

Security

The webhook endpoint is public but every event must carry a valid HMAC signature over the exact request body, inside a short replay window; unknown tokens and bad signatures are rejected. The org is resolved from the routing token and the tenant context is set before any write, so multi-tenant isolation holds. The optional API key is read-only and used only for health checks and reconciliation, never on the event-recording path.

Braintree

Brands on Braintree (a PayPal company) connect natively for subscriptions, with no backend relay to build. You point a Braintree webhook at a URL unique to your workspace and paste read-only API credentials into Rekomi; Rekomi verifies every event and records the conversion. This tracks your recurring sales (so affiliates get credited) and is independent of how you pay for Rekomi.

A scope note, stated plainly: Braintree fires webhooks only for subscriptions and disputes, not for one-time card sales or card refunds. So the native flow covers recurring revenue and automatic chargeback clawback; one-time sales use the server-to-server API, and one-time card refunds are handled by denying the commission manually.

Where to connect

Setup → Connect payment processor → Connect Braintree. Rekomi shows your unique webhook URL and the exact notification kinds to enable. The step-by-step guide is Install on Braintree.

How it works

• You carry the affiliate referral onto each sale via a Braintree custom field named rekomi_ref (the affiliate's link slug), read back from the charge transaction.
• Braintree sends subscription_charged_successfully, subscription_canceled / subscription_expired, and the dispute_* events to your Rekomi webhook URL.
• Rekomi verifies the bt_signature (the Braintree SDK validates it offline against your stored keys), then records recurring sales and reverses commission proportionally when a dispute is lost.

What Rekomi stores

Your Braintree Merchant ID plus the Public and Private keys are encrypted at rest and never returned by the API (the Merchant ID is shown back as a non-secret identifier). Rekomi also keeps a per-workspace routing token (the id in your webhook URL) and connection-health timestamps.

Security

The webhook endpoint is public but every event is verified by the Braintree SDK against your stored keys before anything is trusted; unknown tokens and bad signatures are rejected. The org is resolved from the routing token and the tenant context is set before any write, so multi-tenant isolation holds. The recording path verifies offline (no Braintree API call), so a Braintree API outage cannot stop verified conversions from being recorded. Use a read-only Braintree user for the credentials.

Shopify

Brands on Shopify connect natively through the Rekomi app on the Shopify App Store, with no theme edits and no relay to build. Install the app, approve the read-orders scope, and pick the campaign you want orders attributed to; Rekomi captures the affiliate click and reads each order through Shopify's order webhook server-side. This tracks your store's sales (so affiliates get credited) and is independent of how you pay for Rekomi.

Most Shopify affiliate apps charge a percentage of your referral sales. Rekomi charges 3% of the commissions you actually pay out, not on sales, and runs the payouts and taxes for you.

Where to connect

In your Shopify admin, go to Apps → Shop the App Store, search for Rekomi, and click Install. After install, the embedded setup screen links your store to a campaign. The step-by-step guide is Install on Shopify.

How it works

• The app captures the affiliate click and stamps the referral onto the order, so no theme or checkout edits are required.
• Shopify sends order and refund webhooks to Rekomi; verified orders record conversions and refunds reverse commission proportionally.
• If you prefer to wire it up yourself, a manual Custom Pixel plus webhook-to-S2S fallback is documented in the install guide.

What Rekomi stores

The Shopify access token granted at install is encrypted at rest and never returned by the API. Rekomi also keeps your shop domain and connection-health timestamps. Use the app's read-orders and read-customers scopes only; Rekomi never requests write access to your storefront.

Shopify Collabs

Shopify ships its own native affiliate program called Collabs. Rekomi adds cross-platform affiliate accounts (one affiliate working multiple brands), commission tiers, sub-affiliate recruiting, and the open creator network on top. You can run both side by side on the same store.