Frequently asked questions

Do I need a Raws.dev account to receive ambassador payouts?

Yes — you need an account on Raws.dev to be an active ambassador and to receive any payout via Stripe Connect.

Can I be an ambassador for multiple projects at the same time?

Yes — every project keeps its own ambassador list, missions, payouts. Your cross-project totals show on /my/ambassadors.

Where do I find the ambassador hub for a project?

/p/<slug>/ambassadors — only visible to the owner and active ambassadors. Owners see invite + moderation tools, ambassadors see their referral URL and stats.

What's the public ambassador board?

/p/<slug>/ambassadors-board — public-facing leaderboard ranked by visits driven, with the project's payout transparency metrics. Anyone can view.

Is there an API?

For now, only the conversion endpoint (GET /c/<token>) is documented and stable. Other endpoints exist but aren't promised stable yet — contact us if you want early access for a real use case.

How fast are ambassador payouts?

Stripe Connect transfer fires the moment the source event succeeds (tip lands, conversion fires). The funds appear on the ambassador's Stripe balance immediately, payout schedule depends on their Connect settings.

What if the ambassador hasn't onboarded Stripe Connect?

The commission row stays in pending. As soon as they finish Connect onboarding (account.updated → enabled webhook), every pending row settles automatically.

Can I have different payouts for different ambassadors?

Not at the moment — the per-signup amount and tip commission tier are per-project. If you need tiered payouts, run separate projects and route referrals accordingly.

Can I clawback a payout I disagree with?

Within 7 days of the fire, dispute the conversion from the project hub. Stripe transfer is reversed and the wallet is credited back. Tip refunds also auto-reverse the commission.

Does Raws.dev take a fee?

A small platform fee on tip checkouts and on wallet top-ups (shown at checkout). Stripe Connect transfers to ambassadors are full-amount.

What if a builder doesn't fire conversions despite getting traffic?

We can't run code on their server, so we can't force the fire. What we do: surface conversion rate publicly on the ambassador board (/p/<slug>/ambassadors-board) and on the application landing. ≥100 ambassador visits in 30 days with zero conversions reported = red warning shown to every prospective ambassador. Vote with your time.

Can someone fire fake conversions to drain a builder's wallet?

Each fire is rate-limited 60/min per (token, IP). Dedupe is enforced on (project, external_id) — same id can never pay twice. Suspicious abuse: regenerate the project token from the hub to invalidate the leaked embed.

Can ambassadors self-refer?

No — the system explicitly skips commission and conversion when the referrer's user id matches the project owner's id, even if a stale cookie tries to trick attribution.

Can a banned ambassador re-apply?

Bans block re-application from the same account on the same project. The owner can lift a ban anytime.

What does Raws.dev store about my SaaS visitors?

Per fire: external_id (your identifier — keep it non-PII), source IP (truncated), user agent (truncated), timestamp, ambassador handle. Used for fraud review during the 7-day dispute window. See the Privacy & GDPR section for full detail.

Are there third-party cookies?

No. The tracking tag uses localStorage exclusively — only the ambassador handle, 30-day TTL.

Do I need a DPA?

For EU integrations, yes. Email info@raws.dev with your project handle — we'll send the template.