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 and payouts. Your cross-project totals show on /my/ambassadors.

Where do I find the ambassador hub for a project?

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

What is the public ambassador board?

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

Is there an API?

For now only the conversion endpoint (GET /c/<token>) is documented and stable. Other endpoints exist but are not promised stable yet — contact us for early access.

How fast are ambassador payouts?

The Stripe Connect transfer fires the moment the source event succeeds (a tip lands or a conversion fires). Funds appear on the ambassador Stripe balance immediately; payout timing depends on their Connect settings.

What if the ambassador has not onboarded Stripe Connect?

The commission row stays pending. As soon as they finish Connect onboarding, 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. For 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. The 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 applies on tip checkouts and wallet top-ups (shown at checkout). Stripe Connect transfers to ambassadors are full-amount.

What if a builder does not fire conversions despite getting traffic?

We cannot run code on their server, so we surface conversion rate publicly on the ambassador board (/p/<slug>/ambassadors-board) and the application landing. 100 or more ambassador visits in 30 days with zero conversions reported shows a red warning to every prospective ambassador.

Can someone fire fake conversions to drain a builder wallet?

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

Can ambassadors self-refer?

No — the system skips commission and conversion when the referrer user id matches the project owner 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), truncated source IP, truncated user agent, timestamp and 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, with a 30-day TTL.

Do I need a DPA?

For EU integrations, yes. Email info@raws.dev with your project handle and we will send the template.