White-label verifier

LiveUpdated September 14, 2026

Platforms. Written for PSPs, acquirers, orchestrators, dispute services and agent platforms that act for many customers.

Your customers, their issuers and their auditors can check an Enruta record where they already work with you. The page at https://app.enruta.ai/v/{platform_slug} shows your name, logo and accent color, and verifies a record and its bundle in the browser with @enruta/core: nothing is uploaded to Enruta. The same check is a web component for your own pages.

Set your brand

{
  "display_name": "Northwind Pay",
  "logo_url": "https://northwindpay.example/logo.svg",
  "accent_hex": "#0f766e",
  "support_url": "https://northwindpay.example/support"
}

The hosted page

• Paste a record and its bundle, or choose the two files: the checks run in the page, the same checks as enruta-verify, and each shows PASS or FAIL.
• Or enter a record id: the page asks Enruta’s public verify endpoint, which answers only when the record’s organization allows public verification.
• The page shows your brand and links to your support page.

The web component

<script src="https://app.enruta.ai/verify-widget.js" defer></script>

<enruta-verify platform="northwind-pay" record-url="https://northwindpay.example/records/rec_01M3D9….json"></enruta-verify>

verify-widget.js defines <enruta-verify> without a framework. platform is your platform slug and picks your brand; record-url is the record to verify. If your site sends a Content-Security-Policy, allow https://app.enruta.ai in script-src.

Why in the browser

A verifier that uploads the record asks the reader to trust whoever receives it. Checking in the page keeps the property the record was built for: anyone can verify it, without an account and without Enruta seeing it.