FAQ

Short answers to the questions teams ask most often. For token-specific questions, see the dedicated token FAQ.

Product

What does Passify actually do?

It turns a one-time KYC check into a portable, on-chain attestation, then enforces per-asset compliance rules at mint and transfer time.

Do I need to deploy a smart contract?

No. Attestations use an existing attestation program and tokens use Token-2022 over RPC. There is no custom program to deploy or maintain.

What is an attestation valid for?

Until its expires_at timestamp. After that, token operations are refused until the wallet re-verifies.

Does any personal data go on-chain?

No. The on-chain record is a SHA-256 hash plus metadata (wallet, schema, expiry, attester). Identity data stays with the KYC provider. See Security.

Can the hash be reversed into identity data?

No. SHA-256 is one-way. The hash proves a verification happened; it reveals nothing about who the investor is.

Who holds the investor's documents?

The KYC provider (for example Blockpass), under its own retention policy. Passify never receives them.

How do users sign transactions?

Passify returns an unsigned transaction. The user signs it in their own wallet; Passify never holds keys. See the mint & transfer guide.

Can one attestation work across platforms?

Yes — that is the point. Any integrated platform can read the same attestation for a wallet with one GET /kyc/status/:pubkey call.

What happens when I exceed my quota?

Requests return 429. Usage resets monthly and is visible in the dashboard. See rate limits.

Last updated June 30, 2026