Through the API
With Chargebee, your server reports the sale to Meritt through the API, in three calls, as soon as Chargebee confirms the payment. Attribution and the ledger are the same as for Stripe.
MerittPOST /v1/conversions to report the sale, POST /v1/identify to tie a customer to a visit, POST /v1/conversions/reverse for a refund. A sale sent twice is counted once.meta_data at checkout.meta_data is not shown on hosted pages; a cf_ custom field, created in the Chargebee interface, can be added to them.meta_data.payment_succeeded, call POST /v1/conversions with the amount, the currency, the click and the customer id.payment_refunded, call POST /v1/conversions/reverse with the payment reference.One key, and two calls added to your webhook handling.
At that moment the payment is not confirmed, and when it is, in the webhook, the cookie is gone. The Chargebee passthrough field carries the click between the two.
No. With the same reference, the second call answers “already received” and nothing is added.
subscription_renewed and payment_succeeded arrive at each term; report the payment with the same customer id and it goes to the first sale's affiliate.
credit_note_created signals a credit note. If your policy treats it as a refund, call the reversal with the payment reference.
Chargebee documentation checked on October 19, 2026: apidocs.chargebee.com › event types, apidocs.chargebee.com › advanced features
Your affiliates' links run through your site, so ad blockers do not cut them.
An affiliate program on Recurly: the click in a custom field, the paid invoice and the refund reported to Meritt through the API.
Meritt connects to Stripe in one click and reads payments, renewals, refunds and disputes, then pays your affiliates.
Free until your first commission. No card asked for.