Skip to main content
No. Your access token identifies them. Bluprynt links their progress to the token’s sub under your partner ID.
No. KYC verifies a person. KYI verifies an issuer, which is the organization (through KYB) and its control of a token (through wallet signatures). See Know Your Issuer.
The SDK is a browser library. It works in mobile browsers, and the drawer takes the full width on narrow screens. For a native app, ask your Bluprynt representative.
Not in SDK 0.1.1. The member pastes the address and Bluprynt detects the chain.
There’s no completion callback. After onClose, look the asset up with the Public API: check business_details.business_verified and each authority’s verified flag. Or show a KYI badge, which always reflects the current status.
The default one hour (3600 seconds) or less. Mint a new token every time you open the widget.
Yes. Any HS256 JWT library works. See the Python examples and the claims.
No. It renders Bluprynt’s interface in an iframe. You control the button that opens it.
No. Nothing about the member or the asset becomes public until they sign and the application is approved.
Use the SDK playground and an allowlisted localhost origin. Ask Bluprynt for test credentials.
Related: Overview · Errors and troubleshooting