White label
White label covers the checkout page the buyer opens and, if you want, the console on a domain of yours. You put your logo, your colour and point a CNAME at hosted.tonramp.io.
USDT payment happens in the TonRamp app, opened by the buttons on the checkout page. Branding applies to the entry (checkout and panel), not the whole payment flow.
On the same Checkout screen:
| Field | What it does |
|---|---|
| Logo | PNG, JPEG or WebP, up to 96 KB. A transparent background works better: the page has light and dark themes. With no logo, the TonRamp mark is shown. |
| Brand colour | Hex #rrggbb. On checkout, used on the amount and the pay button. On the console, it paints the chrome (buttons and focus ring). Text colour over it is chosen by contrast, so a light brand does not produce an unreadable button. |
The “Powered by TonRamp” signature stays in the checkout footer.
On console.tonramp.io the login screen keeps the TonRamp identity (we do not yet know who is signing in). After login, the partner logo and colour appear on the panel. On a custom console domain, the brand already appears on the login screen.
Custom domain
Section titled “Custom domain”The CNAME is the same in both cases: hosted.tonramp.io. What changes is the hostname kind.
| Kind | Limit | With no domain | With an active domain |
|---|---|---|---|
| Checkout | 3 | https://trp.tonramp.io/trp/{payload} |
https://trp.yourstore.com/trp/{payload} |
| Console | 1 | https://console.tonramp.io |
https://console.yourstore.com |
hosted.tonramp.io is not a website: on its own it returns 404. It is only the stable CNAME target. On a console hostname, traffic goes to the panel (console.tonramp.io); on a checkout hostname, to the payment page.
Magic links and invites start pointing at the console domain as soon as it is active.
How to point DNS
Section titled “How to point DNS”-
Register the hostname in the console first.
Under Checkout, enter the host in Checkout domain (e.g.
trp.yourstore.com) or Console domain (e.g.console.yourstore.com). Do not use a*.tonramp.iodomain.Order matters: if you create the CNAME before registration, Cloudflare rejects the record (error 1014).
-
Create the records in your DNS zone.
The console shows the exact values. In short:
Type Name Value CNAMEthe registered hostname hosted.tonramp.ioTXTthe name Cloudflare returns (certificate validation) the matching TXT value -
Click Check.
There is no Cloudflare webhook for this. When the certificate becomes active, the host starts answering.
| Status in the console | Meaning |
|---|---|
| Waiting for DNS | Registered, but CNAME or TXT have not matched yet. |
| Active | Certificate issued. Checkout or console already serves that host. |
| Failed | Something in DNS or issuance. The last error is shown on the screen. |
Checkout URL once active
Section titled “Checkout URL once active”The API deep_link still points at trp.tonramp.io. In your frontend, build the link with your host:
https://trp.yourstore.com/trp/{payload}The iframe uses the same URL in src. The domain of the page that embeds the iframe still needs to be allowed under Checkout (frame-ancestors); that is independent of the custom domain. See Iframe.
What white label does not change
Section titled “What white label does not change”- Mini App / Telegram: a buyer who pays via Telegram sees the TonRamp app.
- PIX checkout (
https://api.tonramp.io/v1/c/{id}): our URL and certificate. TRP page branding does not apply to that rail. - Fees and settlement: the amount goes to the partner’s registered wallet; TonRamp keeps its share of the spread and the fixed fee.
Where to configure it
Section titled “Where to configure it”- Open the console.
- Go to Checkout.
- Upload the logo and set the colour (they apply to checkout and the panel).
- If you want a custom domain, register the hostname before creating the CNAME to
hosted.tonramp.io.