Brand the app; the tunnel stays the same.

White-Label VPN and Merchant Of Record

Merchant Of Record can sit on a branded KloxVPN client. It does not replace WireGuard, OpenVPN, OpenConnect, Shadowsocks, the five-device limit, or the 7-day first-purchase refund.

KloxVPN Team
12 min readPublished 2025-02-12Updated 2025-10-27
White-Label VPN and Merchant Of Record
Brand the app; the tunnel stays the same.

We keep commercial facts upfront: consumer pricing reference is $2.83/month on the yearly plan with 7-day money-back on your first purchase; partner economics live on /white-label and /reseller.

Merchant Of Record may appear in your stack — website, comments, installers, or admin tools. None of that replaces the VPN protocol or adds a secret "Merchant Of Record mode" inside the tunnel.

This page is for founders, agencies, and IT shops packaging Klox under their own name. It is not a consumer setup guide — end users still download your app build and press Connect.

White-label VPN partners often ask how Merchant Of Record fits next to a branded Klox client. Short answer: branding, billing, and support are yours; the tunnel is still WireGuard, OpenVPN, OpenConnect, and Shadowsocks on five devices.

Looking for a reliable VPN?

KloxVPN — from $2.83/month. Apps for every device.

View Plans

What Merchant Of Record is in your stack

When unsure, link to /white-label instead of improvising specs in sales email.

Document decisions in your runbook so marketing and engineering do not talk past each other.

It is not a request for a new protocol. Klox white-label ships the same four-protocol core consumers get.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Run quarterly content audits on blog posts that mention `Merchant Of Record` so partners do not contradict each other.

WireGuard versus OpenVPN
Klox ships four protocols: WireGuard by default, OpenVPN when UDP fails.

    How to read this page

  1. 1Skim the diagram above.
  2. 2Do the numbered steps once on your real network.
  3. 3Use the FAQ if a sentence was too long.
  4. 4Follow one related article — not ten tabs.
Roles, not a contract. Your live agreement can move a column. Silence does not. Confirm Klox MoR status with sales. Klox is not Stripe.
RoleOn the statement?Collects VAT/GST on the sale?User emails whom about the charge?Who answers the dispute?
You as merchant + a processorUsually your DBA / entityYou, where you are the sellerYou (if you printed that)You, with the processor
Third-party merchant of recordOften their name or a blended DBAUsually themThem, or you under their rulesThem, you supply evidence
Apple IAP / Play BillingApple or GoogleStore tax rulesThe store, then you for the appThe store
Reseller selling Klox brandWhoever the reseller contract saysThat merchantOften Klox or mixedThe merchant on the charge
White-label, entity unconfirmedUnknown — this is the bugUnknownWhoever they GoogleWhoever the bank billed

If the app says your brand and the bank says someone else, you already wrote the ticket.

— KloxVPN operator notes

Cloudflare Learning: What is a VPN?

Wikipedia: Virtual private network

IETF RFC 8446 (TLS 1.3)

Surfshark pricing (competitor specimen)

Store vs tunnel

App Store screenshots and Play listing text are marketing surfaces. The tunnel handshake is engineering. Keep tickets separated.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

When users mention Merchant Of Record

If a subscriber cites `Merchant Of Record` in a ticket, clarify whether they mean your website, your installer, or a VPN error message.

Store reviewers compare screenshots to real behavior. Mislabelled `Merchant Of Record` strings are an easy rejection reason.

What the tunnel still does

Document which version removed or renamed `Merchant Of Record` so SEO pages like this one stay truthful.

Store reviewers compare screenshots to real behavior. Mislabelled `Merchant Of Record` strings are an easy rejection reason.

You inherit server capacity, protocol maintenance, and core app updates from Klox infrastructure. You own front-line support and brand promise.

Regardless of brand paint, the client wraps traffic the same way: encrypted tunnel to your chosen server, DNS through the tunnel when configured, kill switch optional per platform.

Do not promise features Klox does not ship — extra protocols, unlimited devices beyond plan limits, or compliance badges you cannot show.

Device cap

five devices per subscription is still enforced. Your pricing page should say so clearly.

Keep marketing, engineering, and support in one thread when `Merchant Of Record` changes. Silent renames cause refund spikes.

Protocol choice

WireGuard first, OpenVPN fallback — same as consumer. Document that in partner FAQs.

Run quarterly content audits on blog posts that mention `Merchant Of Record` so partners do not contradict each other.

Branding checklist around Merchant Of Record

Keep /download logic in mind: consumer links on your domain should point to your build, not klox.app, unless that is intentional.

Reseller and white-label paths differ; pick one story on your homepage.

Confirm `Merchant Of Record` still appears where you expect: installer metadata, about screen, support templates, and marketing site.

If you rebrand, update every surface in one release when possible. Half-old names confuse users and app review.

When unsure, link to /white-label instead of improvising specs in sales email.

Download, sign in, connect WireGuard, fall back to OpenVPN
Install from klox.app/download. WireGuard first. OpenVPN if UDP is blocked.

Comments and CMS plugins

Some partners embed comment systems or CMS tools named `Merchant Of Record`. That is website plumbing, not VPN configuration.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

2FA and admin panels

Protect reseller panels separately. See admin 2FA checklist if you have not locked down logins.

Reseller and white-label paths differ; pick one story on your homepage.

Support scripts that work

Escalate tunnel failures to infrastructure. Escalate storefront or installer naming to your release manager.

Keep marketing, engineering, and support in one thread when `Merchant Of Record` changes. Silent renames cause refund spikes.

When unsure, link to /white-label instead of improvising specs in sales email.

Never tell a user to edit Linux sysctls because a partner string appeared in a log — that is a different team.

Reseller and white-label paths differ; pick one story on your homepage.

Refund policy

Mirror 7-day money-back on your first purchase in your terms or explain differences in writing before checkout.

Store reviewers compare screenshots to real behavior. Mislabelled `Merchant Of Record` strings are an easy rejection reason.

Launch week

Use launch checklist so `Merchant Of Record` questions do not land on day one.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

What not to promise

Run quarterly content audits on blog posts that mention `Merchant Of Record` so partners do not contradict each other.

Document which version removed or renamed `Merchant Of Record` so SEO pages like this one stay truthful.

No invented "Merchant Of Record encryption." No secret city counts. No SOC 2 badge unless you actually hold one.

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

White-label is speed to market with a proven tunnel — not a license to invent physics.

Competitor comparisons

Compare features you ship. Avoid review-farm copy; it ages badly and triggers store rejection.

Document which version removed or renamed `Merchant Of Record` so SEO pages like this one stay truthful.

Next step

Talk to sales via /white-label when you are ready to ship glass with your logo.

When unsure, link to /white-label instead of improvising specs in sales email.

Release checklist when Merchant Of Record appears in builds

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Run smoke tests: install, connect WireGuard, switch to OpenVPN, sign out, reinstall.

Update release notes if `Merchant Of Record` is user-visible.

Archive old screenshots so marketing does not resurrect retired strings.

When unsure, link to /white-label instead of improvising specs in sales email.

App review

Apple and Google reject inconsistent VPN claims. Keep copy aligned with actual protocols.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Versioning

Tag builds that change `Merchant Of Record` so support can map tickets to releases.

Store reviewers compare screenshots to real behavior. Mislabelled `Merchant Of Record` strings are an easy rejection reason.

Partner FAQ snippets

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Q: Where is pricing? A: You set retail; reference $2.83/month on the yearly plan only if you mirror consumer tiers.

Q: Can we sell unlimited devices? A: Only if your commercial plan allows it; default is five devices.

When unsure, link to /white-label instead of improvising specs in sales email.

Q: Do we operate servers? A: You brand and support; infrastructure follows your Klox agreement.

Sales

Point enterprise buyers to /trust-center for published policies.

Keep marketing, engineering, and support in one thread when `Merchant Of Record` changes. Silent renames cause refund spikes.

Reseller

Reseller program if you want volume without full white-label.

Run quarterly content audits on blog posts that mention `Merchant Of Record` so partners do not contradict each other.

Long-term maintenance

Keep a single internal doc listing approved product claims.

Collect user feedback on confusing labels — rename in the next release rather than debating in chat.

When unsure, link to /white-label instead of improvising specs in sales email.

Partners win when support scripts are boring and accurate. Excitement in copy usually means someone promised a protocol feature that does not exist.

Reseller and white-label paths differ; pick one story on your homepage.

Branding

Branding checklist

Your brand promise should match Klox capabilities: WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, honest refund language.

Contact

White-label for partnership questions.

Reseller and white-label paths differ; pick one story on your homepage.

Key Takeaways

Key takeaway: Merchant Of Record is part of your brand or stack — not a new tunnel protocol. Klox white-label still ships WireGuard, OpenVPN, OpenConnect, and Shadowsocks on five devices.

Document naming decisions, split support tickets, and do not promise features the core app does not have.

White-label · Launch checklist · Download reference app

Launch your branded VPN

KloxVPN — WireGuard, OpenVPN, OpenConnect, and Shadowsocks, five devices, $2.83/month on the yearly plan. 7-day money-back on your first purchase.

Explore white-label

Frequently Asked Questions

No. Partner apps still use WireGuard, OpenVPN, OpenConnect, and Shadowsocks.

KloxVPN Team

Experts in VPN infrastructure, network security, and online privacy. The KloxVPN team has been building and operating VPN services since 2019, providing consumer and white-label VPN solutions to thousands of users worldwide.