Braintree affiliate program software, webhook-native for subscriptions.
Braintree (a PayPal company) fires webhooks for subscriptions and disputes, and Rekomi listens natively: paste read-only API credentials, point a webhook at your unique Rekomi URL, and every recurring charge carrying rekomi_ref is verified and credited, with chargebacks clawed back automatically. One-time sales ride the S2S API; that split is a Braintree limitation, and we say so plainly.
A custom field, a webhook, and read-only keys.
Add a rekomi_ref custom field in the Braintree Control Panel, set to Store and pass back. Your backend stamps the referral captured by the Rekomi head script onto each transaction at sale time; that field is how the sale names its affiliate.
Create a Braintree webhook to your unique Rekomi URL with the subscription and dispute notification kinds, then paste a dedicated read-only user's Merchant ID, public key, and private key. Validated on connect, stored encrypted, never shown again.
subscription_charged_successfully books recurring commission on every cycle, dispute_lost claws it back proportionally, and cancellations stop the clock. One-time sales post through the HMAC-signed S2S API from your backend.
Webhooks where Braintree has them. S2S where it doesn't.
Braintree only emits webhooks for subscriptions and disputes; no gateway-side event exists for a one-time card sale or its refund. Tools that claim otherwise are polling or guessing. Rekomi splits the work honestly: the recurring lane and the chargeback lane run themselves off signed webhooks, and one-time sales arrive through a single HMAC-signed server-to-server call from your backend. Both lanes land on the same affiliate ledger.
Braintree fires no webhook for one-time card sales, so your backend relays them in one signed request instead. Same attribution, same ledger.
Built around Braintree's real event model.
Dispute-driven clawback
A lost dispute (dispute_lost) reverses the commission proportionally before it ever reaches a payout run. Other dispute notifications are acknowledged, but only a loss changes the ledger.
Read-only by design
Rekomi asks for a dedicated read-only Braintree user's keys, nothing more. Webhook signatures parse offline through the official Braintree SDK, and the keys live encrypted at rest.
Full lifecycle coverage
Charged, canceled, and expired subscription events drive the ledger, so recurring revshare stops exactly when the revenue does; the past-due and failed-charge kinds are subscribed for completeness.
The S2S side lane
One-time sales post to the HMAC-signed server-to-server API with the same rekomi_ref referral. Idempotency keys make retries safe, and the commission looks identical on the ledger.
Payouts unchanged
Billing on Braintree, paying through Rekomi: affiliates onboard via Stripe Express with KYC handled by Stripe, payout runs are done for you, and tax paperwork is handled at year end.
Part of a bigger stack
Stripe, Paddle, and more are native alongside Braintree, and any other gateway attributes through the same S2S API. Your program outlives any single processor choice.
All integrationsFlat plans plus 3% of payouts. No revenue cut.
For solo founders running a focused campaign.
For SaaS scaling beyond one campaign.
For mature SaaS with serious affiliate ambitions.
14-day free trial on every plan · 3% of affiliate payouts (2.5% on Enterprise), payouts and tax handled · Full pricing
Common Braintree questions.
Does the native Braintree integration track one-time sales?
Not over webhooks, because Braintree fires no webhook for one-time card sales; that is a Braintree limitation, not a Rekomi one. Subscriptions and disputes are fully webhook-native and hands-off. One-time sales are tracked through Rekomi's HMAC-signed server-to-server API: your backend POSTs the sale with the referral, and the commission books exactly like a webhook-delivered one.
Which Braintree events does Rekomi listen to?
The subscription lifecycle (subscription_charged_successfully, subscription_canceled, subscription_expired, subscription_went_past_due, subscription_charged_unsuccessfully) and the dispute set (dispute_opened, dispute_lost, dispute_won, dispute_accepted). Braintree's check notification on setup is acknowledged automatically.
What credentials does Rekomi need, and how are they stored?
A dedicated read-only Braintree user's Merchant ID, public key, and private key; read access is all Rekomi needs. Keys are validated against Braintree at connect time, stored encrypted, and never shown again. Webhook signatures are validated offline via the official Braintree SDK, so events are authenticated without a round trip.
How do chargebacks affect commissions?
Automatically. When Braintree delivers dispute_lost, Rekomi reverses the commission proportionally and updates the affiliate's pending balance, so you never pay out on a charge the bank took back. Only a lost dispute changes the ledger; other dispute notifications are acknowledged but not recorded.
What about voluntary refunds of one-time sales?
Braintree sends no webhook for one-time card refunds, so there is nothing to listen to; you deny the affiliate's commission manually from the conversion record in Rekomi, which takes one click. Recurring subscription churn (cancellations and expirations) is tracked automatically.
How is the affiliate attached to a Braintree sale?
Via a rekomi_ref custom field, created once in the Braintree Control Panel and set to Store and pass back. Your backend stamps the referral (captured client-side by the Rekomi head script) onto the transaction at sale time; Rekomi reads it off the charge transaction that arrives on the subscription webhook. It lives on the transaction, not the subscription, because Braintree subscriptions have limited metadata.
Can Braintree run alongside Stripe or Paddle in one workspace?
No. Rekomi enforces one conversion source per workspace, symmetrically across Stripe, Paddle, Braintree, and the S2S API, so the same sale can never be recorded twice. Disconnect the other rail first, or run a second workspace if you genuinely bill on two platforms.
On a different gateway? Also covered.
Ten minutes to first click.
Point a Braintree webhook at Rekomi, paste read-only keys, and recurring commissions start booking themselves. 14-day free trial, no card.
- 14-day free trial
- Cancel anytime, $0 charged