Theming and branding
Use approved co-branding tokens for the hosted 0Gate widget without presenting the flow as partner-owned compliance infrastructure.
0Gate supports partner co-branding for the hosted widget. Branding tokens can include logo URL, primary color, secondary color, accent color, and brand name. These values are read by the hosted surface during embed bootstrap and can be managed through the branding API where your account is enabled.
Branding model
Supported token categories
| Token | Use | Review note |
|---|---|---|
brand_name | Display partner name where the hosted surface supports it. | Must not imply the partner owns 0Gate compliance or settlement. |
logo_url | Load an approved HTTPS logo. | Use stable, accessible, HTTPS-hosted assets. |
primary_color | Main brand accent where supported. | Ensure contrast and accessibility. |
secondary_color | Secondary UI treatment where supported. | Keep consistent with hosted theme behavior. |
accent_color | Supporting accent where supported. | Avoid color meaning that conflicts with status or warning states. |
Update example
curl -X PATCH https://gate-api-sandbox.0bit.app/v1/branding \
-H "Authorization: Bearer $GATE_KEY" \
-H "Content-Type: application/json" \
-d '{
"brand_name": "Example Wallet",
"logo_url": "https://assets.example/logo.svg",
"primary_color": "#FF4B1F"
}'Only documented tokens should be sent. Branding updates are server-side operations and should not be driven from arbitrary browser input.
Co-branding boundary
| Do | Do not |
|---|---|
| Present 0Gate as a hosted payment or ramp experience inside your product. | Claim the partner owns KYC, compliance screening, payment rails, or settlement infrastructure unless contract wording explicitly says so. |
| Keep disclosure, support, and compliance wording consistent with approved copy. | Hide required user-facing notices or misrepresent the hosted flow as fully white-labeled infrastructure. |
| Test light/dark and responsive states before production. | Use colors that break contrast, error states, or warning states. |
| Use HTTPS logo URLs and stable assets. | Inject scripts, trackers, or dynamic unsafe content into the hosted surface. |