Ambassly FAQ
Ambassly tracks Stripe affiliate programs with first-party referral capture, webhook reconciliation, and a commission ledger. These answers cover the real operational questions founders and creators ask before trusting an affiliate system.
Does Ambassly cap referred revenue?
No. Ambassly plans limit operational usage like programs and active affiliates, but referred revenue is uncapped on every plan.
How does Ambassly attribute a Stripe customer?
Ambassly stores a referral code from `?via=` or `?ref=`, then the merchant passes that code into Stripe Checkout as `client_reference_id` and/or `metadata.ambassly`. Stripe webhooks create the referral and commission ledger entries.
What happens when Stripe sends the same webhook twice?
Ambassly records each Stripe event ID in a webhook ledger before processing. If the same event ID arrives again, it is skipped so the same invoice cannot create duplicate commissions.
How does Ambassly handle refunds and cancellations?
Refund and cancellation events can claw back pending or approved commissions. If a commission was already paid, Ambassly records a negative adjustment instead of silently changing the old payout.
What should I know about Safari and affiliate cookies?
Safari can cap client-set cookies to about 7 days in common referral flows. Ambassly documents this directly and recommends passing the referral code server-side into Stripe for long buying cycles.
Are payouts automatic in the MVP?
No. Ambassly v1 supports payout exports, including CSV and PayPal mass-pay format, plus marking payouts paid. Fully automated payouts are not part of the MVP.
Can affiliates create separate links for each piece of content?
Yes. Ambassly supports per-content links so a creator can track a YouTube video, newsletter mention, repo README, or course module separately.
Is Ambassly only for Stripe?
Yes for the MVP. Ambassly is built around Stripe Checkout, Stripe webhooks, and Stripe invoice events rather than trying to support every processor at launch.