Skip to main content
White-label support lets a partner serve the Yuno Web SDK from their own origin without the string Yuno leaking into the merchant page — neither in the DOM, globals, dispatched events, nor outgoing network traffic.
Shipped in Web SDK 1.9.1. The legacy window.Yuno global and yuno-sdk-ready event remain as backwards-compatibility aliases, so existing integrations continue to work unchanged.

What the SDK exposes

Both the new and legacy globals reference the same object, and both events are dispatched on bundle load — you can mix them during a migration without breaking either form.

Runtime URL overrides

Partners hosting the SDK on their own origin point the SDK at custom endpoints at initialize() time, instead of relying on the compile-time defaults.
What each override affects end-to-end:
For a typical white-label deployment, pass the same value to both options. The SDK uses the value verbatim — it no longer appends a /v<x.y> segment when assetUrl already ends with one, and it does not prepend a regional prefix to overrides.The static-CDN host-swap (icons, brand logos, flags) routes onto assetUrl when set, otherwise falls back to apiUrl — so passing both the same value sends every request through a single origin. Only *.y.uno asset URLs are rewritten; merchant-supplied icons on external CDNs are left untouched.

Neutral merchant callbacks

Callback names gained whitelabel-neutral aliases. The legacy yuno* names are still accepted and forwarded internally, but are deprecated and will be removed in a future major release.

Integration example

Verifying a white-label setup

After loading the SDK from a non-Yuno origin, none of the following should appear in the merchant page:
  • Elements with class="yuno-*" or id="yuno-*".
  • A resolved font family of Yuno-Inter.
  • Network requests to *.y.uno hosts — including the static CDNs icons.prod.y.uno and sdk.prod.y.uno for icons, brand logos, and flags. These are host-swapped onto your origin only on recent SDK builds; older builds still fetch them straight from the CDN.
And these should be present:
  • window.SdkPayments resolves to the SDK instance factory.
  • 'sdk-payments-ready' fires once on bundle load.
  • DOM nodes use class="sdk-payments-*" / id="sdk-payments-*".

Local test harness

A throwaway proxy server lives in the yuno-payments/yuno-sdk-web repo under white-label-proxy-server/. It listens on http://localhost:9090, serves a landing page from a non-Yuno origin, and transparently proxies SDK asset / API / WebSocket traffic upstream — point a partner test page’s <script src> at http://localhost:9090/v1.7/main.js to exercise the white-label code paths end-to-end.
The same harness also fronts the hosted Payment Link checkout (normally checkout.<env>.y.uno), so that surface can be white-labeled onto a merchant origin/sub-path too. For the merchant-facing flow — rewriting the redirect URL and appending apiUrl / assetUrl — see Payment Link White Label. See White Label Proxy Server for the full architecture, the hosted checkout white-label flow, the SDK_MAIN_JS version-pinning behaviour, the env-var matrix (prod / staging / dev upstreams), and the routing table.