Overview

The KYI (Know Your Issuer) widget lets token issuers on your platform verify their assets with Bluprynt, without leaving your product.

TL;DR

Contact your Bluprynt representative to set up a partner integration.

You send Bluprynt

  • Every origin that will embed the widget, including staging and local development (e.g. https://app.example.com, http://localhost:3000).

Bluprynt sends you

  • A partner ID that identifies your platform.
  • A SECRET_KEY for signing access tokens on your server.

After that, install @bluprynt/kyi-widget-sdk, generate an access token for the logged-in user on your backend, and pass it to kyi() on your frontend. The integration guide walks through each step.

What it does

A token issuer verifies their asset in three steps, all inside the widget:

  1. They complete a KYB (Know Your Business) check.
  2. They verify the wallets behind the asset, by signing a message or with one of the other methods.
  3. Bluprynt creates an on-chain identity for them, which is then subject to ongoing compliance checks.

The widget also lets issuers look back at the assets and wallets they've already verified. The SDK itself is a small JavaScript library that opens the widget as a drawer over your page.

Supported chains are Ethereum, Base, Plume, Avalanche, Solana and the XRP Ledger, with more EVM chains on the way. Verification has screenshots of the flow and the details of each method.

How identity works

Your users never sign up for Bluprynt. There's no Bluprynt account, no second login, nothing extra to authenticate. You've already logged them in, and a signed access token carries that identity into the widget, so to them verification feels like part of your product.

The token contains your own internal ID for the user, and Bluprynt takes it at face value. Whatever ID you put in a token, Bluprynt treats as that user, along with their KYB results, verified wallets and on-chain identity.

So keeping user IDs straight is on you: one permanent ID per user, never shared or reused, and tokens only for whoever is logged in. The integration guide covers this in Choosing a user ID.

What happens at runtime

  1. A user logs in to your platform as usual.
  2. Your backend generates a short-lived access token for them, signed with your SECRET_KEY.
  3. Your frontend passes the token to kyi(), and the widget opens.
  4. The user goes through verification. Bluprynt stores the result against your ID for them.

The SECRET_KEY never leaves your server. The browser only sees the short-lived token.

Next steps

VerificationThe user flow, supported chains and wallet methods. Integration guideStep-by-step setup for your backend and frontend. API referenceEvery function, option and type. PlaygroundGenerate a test token and open the widget.