OroPocket
Whitelabel

Connect your domain for white-label

White-label runs our app on your address, under your brand. It starts with one DNS record — and we cannot issue a certificate for a name that is not yet pointing at us, which is why the check comes before everything else.

5 min read · 3 screenshots
The Whitelabel page only appears in your sidebar once Whitelabel is ticked on the Capabilities page. If you cannot see it, that is the reason.
The Whitelabel page of the OroPocket developer dashboard, showing a status badge and banner at the top followed by the Your domain configuration card.
The status badge at the top tracks the request through its whole lifecycle.

  1. Choose a subdomain you control

    Most partners use something like gold.yourbank.com. It has to contain at least one dot, be ASCII (convert an internationalised name to punycode yourself), and not be a wildcard. One domain per partner.

    The Your domain card on the OroPocket whitelabel page, with a Domain input field, a copyable CNAME target value, guidance on the record to create, and a Check DNS button.
    The CNAME target is copyable — paste it straight into your DNS provider.

  2. Create the CNAME record

    In your DNS provider, add a record pointing the subdomain at the target shown in the card:

    gold.yourbank.com.   CNAME   whitelabel.oropocket.com.

    The host is just the subdomain part — gold — in most providers’ interfaces, not the full name.

    Pointing at a name we control rather than an IP address is deliberate: it means we can move infrastructure without every partner having to edit DNS again.

  3. Run the DNS check

    Type the domain into the field and press Check DNS. Until the record has propagated you will see exactly this — which is normal, not a misconfiguration:

    The Your domain card after running a DNS check, showing a red message reading that no CNAME or A record was found for the domain yet and that DNS can take a few minutes.
    Before propagation. Wait a few minutes and check again — the button is rate-limited to ten checks a minute.

    When it resolves, the message turns green and reads Pointing at us. You may also see “Pointing at us (flattened record — that’s fine)”: Cloudflare and Route 53 flatten a CNAME at the zone apex into A records, and we accept those rather than telling you your correct configuration is wrong.

What the check will refuse

ReasonWhat to do
NOT_POINTEDNo CNAME or A record found at all. Either the record has not propagated yet, or it was created on the wrong host.
POINTS_ELSEWHEREThe name resolves, but not to us. Check for an existing record on that host — a parked page or an old redirect is the usual culprit.
HOST_TAKENAnother partner already has this domain. One domain per partner.
A reserved nameoropocket.com, oropocket.in, localhost and bare IP addresses are not accepted.
The domain locks once you submit. Your brand and your sign-in copy stay editable for the life of the partnership, but changing the domain after submission needs re-provisioning and a word with support. Pick the name you actually want.

Your account does not have to be live yet

You can configure all of this before production access is approved — the page says so at the bottom. What you cannot do is go live on the domain until it is. The two approvals are separate and can proceed in parallel.

Next: add your logo, icon and wordmark. For hostname rules and the branding endpoint, see the whitelabel reference.
← Set up webhooksAdd your brand →