Recurly affiliate program software, gateway-agnostic and void-aware.
Recurly is subscription billing that runs on top of the payment gateway you already use, and Rekomi supports it natively: pick your US or EU data region, paste a read-only private API key, and add one XML webhook in Recurly with the Basic Authentication credentials Rekomi generates. From then on paid invoices, subscription renewals, refunds, and voided payments credit and debit the right affiliate automatically, with no relay code to write or maintain.
Connect your region, stamp the referral, let the invoices flow.
Pick your data region (US or EU) and paste a read-only private API key; Rekomi validates it live against your region, and a key that belongs to the other region gets a region suggestion instead of a cryptic error. Then add one webhook endpoint in Recurly with the URL and Basic Authentication credentials Rekomi generates for you: XML format, subscribed to the invoice, payment, refund, and subscription notifications Rekomi uses.
Recurly hosts the checkout, so the referral travels on the subscription. Install the head script, create a rekomi_ref custom field on the Subscription object (optionally Account as a fallback), and set it from window.Rekomi.getReferral() when your backend creates the subscription or purchase. Custom fields need Recurly Pro or Elite; the FAQ covers the Starter plan honestly.
The first paid charge invoice books the conversion, and every renewal arrives as another paid invoice and accrues recurring commission, matched from customer history with zero extra API calls. Refunds claw back proportionally per refund transaction, and voided payments reverse in full, all in the same audit trail.
The money rides XML, so Rekomi authenticates XML.
Recurly signs its JSON webhooks but not its XML ones, and the XML payloads are the only ones that carry full money data, so the honest response is to engineer around that rather than gloss over it. Rekomi generates Basic Authentication credentials and authenticates every delivery before anything is processed; the per-workspace URL is unguessable, and deliveries are de-duplicated so Recurly's multi-day retry ladder never double counts a sale. The read-only API key is health-checked continuously, and because Recurly keys never expire, a failed check always means something real: you get an email the moment the connection needs attention.
Recurly affiliate tracking that matches how Recurly actually bills.
Gateway-agnostic by design
Recurly sits on top of the payment gateway you already run (Stripe, Adyen, Braintree, GoCardless, and more), and Rekomi listens to Recurly, the billing source of truth, not the gateway underneath. Whichever gateway processes the card, the same webhooks report the payment, and your payment routing does not change.
Honestly secured webhooks
Recurly signs JSON webhooks only, and the money lives in the unsigned XML ones, so this page says so. Rekomi mints Basic Authentication credentials, authenticates every delivery before processing, and stores the credential and your read-only key encrypted at rest.
Renewals on autopilot
Every renewal arrives as a paid charge invoice and records a recurring conversion, matched from your customer history with zero API calls, so revshare keeps accruing for the life of the customer with no further work.
Refunds and voids claw back
Refunds reverse commission proportionally, per refund transaction, until the original amount is exhausted; a voided payment reverses the full amount. Chargebacks handled through Recurly's Chargeback Management feature arrive as refund-shaped events and claw back the same way.
A key with a narrow job
The API key is read-only and used sparingly: connection validation, health checks, and one bounded read on each subscription's first payment to fetch the referral. Renewals never touch the API, and Recurly keys never expire, so a failed health check always means something real.
Part of a bigger stack
Stripe, Paddle, Braintree, Chargebee, and more are native alongside Recurly, and any other billing system attributes through the HMAC-signed S2S API.
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 Recurly questions.
Is the Recurly integration native?
Yes. You pick your US or EU data region, paste a read-only private API key, then add one webhook endpoint in Recurly using the URL and Basic Authentication credentials Rekomi generates for you, set to the XML format. Paid invoices, subscription renewals, signups, refunds, and voided payments are all recorded automatically, with no relay code to write or maintain. Rekomi also health-checks the connection and emails you if the key ever stops validating.
Which payment gateways does it work with?
All of them, because Rekomi listens to Recurly, not to the gateway. Recurly sits on top of the payment gateway you already run (Stripe, Adyen, Braintree, GoCardless, and the rest), and its webhooks report every payment the same way regardless of which gateway processed the card. You keep your gateway setup exactly as it is; nothing about your payment routing changes.
How are the webhooks secured if Recurly does not sign XML?
Plainly: Recurly's signature verification applies to JSON webhooks only, and JSON payloads are lightweight identifiers; the XML payloads that actually carry the money are unsigned, so Rekomi does not pretend otherwise. Rekomi generates Basic Authentication credentials for the endpoint, and every delivery is authenticated against them before anything is processed; deliveries that fail the check are rejected. The credentials and your read-only API key are stored encrypted at rest and never returned by the API, the per-workspace URL is unguessable, and everything travels over HTTPS.
Which affiliate platforms have real Recurly integrations?
The credible list is short. FirstPromoter and impact.com are the only established platforms running true server-side Recurly rails, and impact.com's is in beta; most others settle for thank-you-page scripts or Zapier relays that miss renewals and refunds. Rewardful has no Recurly support at all; its integrations are Stripe and Paddle. If your search through affiliate platforms' Recurly integrations kept coming up empty, that is the gap Rekomi covers: a modern native Recurly rail alongside Stripe, Paddle, Braintree, Chargebee, and more, with recurring commissions, refund-aware clawbacks, and done-for-you payouts.
How do affiliates get credited when Recurly hosts the checkout?
The referral travels on the subscription. The Rekomi head script captures the affiliate click in a first-party cookie; you create a rekomi_ref custom field on the Subscription object in Recurly (optionally a second one on Account as a fallback) and set it from window.Rekomi.getReferral() when your backend creates the subscription or purchase. On the first payment Rekomi reads the field back with your read-only key and records the conversion; renewals are matched from customer history with no further work.
I am on the Recurly Starter plan. Does attribution work?
Partly, and this page will not pretend otherwise. Recurly custom fields are plan-gated: Pro allows up to 5 and Elite up to 10, and the Starter plan does not support them at all, so there is no field for the referral to ride on and new-customer attribution is not available on Starter. Renewals of customers Rekomi has already attributed still track on any plan, because renewals are matched from customer history, not custom fields.
Are renewals, refunds, voids, and chargebacks handled?
Yes, with one plainly stated edge. Every renewal arrives as a paid charge invoice and records a recurring conversion, so revshare keeps accruing for the life of the subscription. Refunds claw commission back proportionally, per refund transaction, and a voided payment reverses the full transaction amount. The edge is chargebacks: Recurly has no dispute webhooks, so card disputes reach Rekomi only if your site uses Recurly's early-access Chargeback Management feature, where they arrive as refund-shaped events and claw back like refunds; disputes settled directly at your gateway are invisible to Recurly, and you adjust those manually.
What does Rekomi do with the API key?
As little as possible, and never a write. The key is created read-only in Recurly, and Rekomi uses it for exactly three things: validating the connection when you paste it, periodic health checks, and one bounded read on the first payment of each subscription to fetch the rekomi_ref custom field. Renewals never trigger an API call; they are matched from your customer history. The key is stored encrypted at rest, never returned by the API, and wiped on disconnect.
Can I run Recurly alongside another billing connection?
No; Rekomi enforces one conversion source of truth per workspace so the same sale is never recorded twice. Pick one rail for Recurly sales and keep it; if you genuinely sell on two platforms, run them as separate workspaces.
Selling somewhere else too? Also covered.
Ten minutes to first click.
Pick your region, paste a read-only key, add one webhook in Recurly, and paid invoices start crediting affiliates today. 14-day free trial, no card.
- 14-day free trial
- Cancel anytime, $0 charged