Send "Customer Tag" to Openprovider for Multi-Brand ICANN Emails

The Use Case: Many of us manage multiple storefronts with different brands within Upmind. When registering domains via Openprovider, it is crucial that clients receive customized ICANN verification emails (with different sender emails, logos, and languages depending on the specific store they purchased from).

Openprovider handles this beautifully on their end through their "Reseller Branding" feature. It triggers specific email templates by associating the domain registration with a specific "Customer Tag" (or Customer Handle) created in their system.

The Issue: Currently, there isn't a way to configure Upmind to automatically send a specific Customer Tag to Openprovider when a new client registers a domain. Because this tag isn't passed through the API, all domains provisioned via Upmind fall under a single default brand in Openprovider. This causes brand confusion for the end-user (e.g., buying from Brand B, but receiving an ICANN email from Brand A).

The Solution: Please add the ability to map or send a "Customer Tag" to Openprovider during provisioning. This could be implemented by:

  1. Allowing us to define a specific Openprovider Customer Tag at the Upmind "Brand" settings level.

  2. OR allowing us to map a custom Provisioning Field to the Openprovider Customer Tag in the module configuration.

Ensuring domains are grouped under the correct customer tag in Openprovider would make Upmind an even more powerful tool for multi-brand agencies.

Feature Request
Pass Openprovider "Customer Tag" via API for Multi-Brand ICANN Emails
How Would You Use This in Upmind?
We run multiple storefronts with distinct brands in Upmind. I would use this feature by defining a specific Openprovider "Customer Tag" (or Customer Handle) at the Upmind Brand settings level, or by mapping it via a custom Provisioning Field. When a domain is provisioned, Upmind would send this specific tag in the Openprovider API payload so the domain is grouped under the correct sub-reseller identity.
What problem does this solve for you?
Openprovider uses these "Customer Tags" to trigger specific Reseller Branding for mandatory ICANN verification emails (allowing different sender emails, logos, and languages per store). Currently, because Upmind doesn't pass this tag, all domains from all our Upmind storefronts default to a single brand identity in Openprovider. This means a customer buying from "Brand B" receives an ICANN verification email from "Brand A", causing brand confusion and making the email look like phishing.
Impact of not having this feature
It severely limits the effectiveness of Upmind's multi-brand capabilities for domain resellers. If we cannot fully white-label the mandatory ICANN emails per brand, it damages customer trust and drastically increases support tickets from users who are afraid to click the verification link because they don't recognize the sender's email address.

Please authenticate to join the conversation.

Upvoters
Status

Suggested

Board

Provisioning

Date

5 days ago

Author

Geremias Daniel Rodriguez Santos

Subscribe to post

Get notified by email when there are changes.