Phase VII · Institutional interface

For banks, platforms, and regulators

Put a calm second voice inside your own payment flow, without taking on any of your customers’ data.

What your organisation never receives

Your customers’ answers and notes stay on their device, and Vireth keeps no record of them at all. The Pause check runs in their browser. You receive only their final choice, and only if they choose to send it. That keeps your data-protection burden close to zero.

1. The Pause check, inside your payment flow

Show the Pause check before a customer confirms a payment you consider risky: a new payee, an unusually large amount, or a request your own systems have flagged. It asks a few questions, explains any scam pattern it recognises with the evidence behind it, and leaves the decision with your customer.

<iframe
  src="https://vireth.traceriskadvisory.com/embed/pause?country=uk&partner=https://bank.example&name=Example%20Bank"
  title="Pause check by TRACE Vireth"
  style="width:100%;min-height:720px;border:0"
></iframe>

Parameters: country (india, uk, australia, or other) sets the helplines and rights shown; partner is your site’s origin; name is how your organisation is named to the customer.

If your customer chooses to tell you their decision, your page receives one message:

window.addEventListener("message", (event) => {
  if (event.origin !== "https://vireth.traceriskadvisory.com") return;
  if (event.data?.type !== "trace-vireth.decision") return;
  // event.data.decision is "stop", "verify", or "proceed".
  // Sent only if your customer pressed "Tell Example Bank my choice".
});

For security, embedding only works once your origin is added to Vireth’s approved list. Until then, browsers refuse to show it inside another site.

2. For regulators and industry bodies

Vireth’s reasoning is rule-based, versioned, and published: every pattern, its sources, its evaluation results, and every change are on the governance page. Anonymised pattern sharing across users (Phase VI) is designed but switched off, and has no client in the app today.

Working with us

Integrations start as a pilot. We’ll agree your approved origins, the payments that trigger the check, how you’ll measure outcomes (harm prevented and false alarms, not alert counts), and your security requirements.

Contact [email protected].