White-label ramp experiences
Understand the boundary between 0Gate co-branding and unsupported claims that the partner owns the hosted ramp infrastructure.
0Gate supports hosted, co-branded ramp experiences. That is different from a fully partner-owned white-label ramp stack. The hosted 0Gate surface remains the product boundary for the user-facing ramp, verification, payment, and completion journey unless a separate contract says otherwise.
Boundary
| Experience | Supported public description |
|---|---|
| Embedded widget | Hosted 0Gate iframe inside your product. |
| Kit block | Hosted 0Gate iframe locked to a single flow. |
| Hosted redirect | Top-level 0Gate-hosted page reached from your product. |
| Co-branding | Approved logo, brand name, and color tokens surfaced by the hosted widget. |
| Full white-label infrastructure | Do not claim this from generic 0Gate docs. Requires separate product, legal, and commercial approval. |
Architecture
Copy rules
| Avoid | Prefer |
|---|---|
| "Our fully white-label ramp." | "A hosted 0Gate ramp experience embedded or redirected from our product." |
| "We operate all KYC and settlement." | "The hosted flow handles the approved ramp experience; backend events drive our order state." |
| "Partner-owned payment rails." | "Payment/ramp availability depends on approved 0Gate product configuration." |
| "Invisible 0Bit infrastructure." | "Co-branded hosted experience where required notices and support paths remain intact." |
Implementation guidance
- Use Theming and branding for approved visual tokens.
- Use flow-locked kit blocks for dedicated buy, sell, or swap entry points.
- Keep required disclosures, support instructions, and hosted flow behavior visible where required.
- Do not suppress or rewrite compliance, payment, or settlement language unless product/legal approval covers it.