Skip to main content
Treat StarkFi KYC as a managed service: we run verification sessions and decisions on Didit, a leading global provider for identity and compliance. You do not need a separate contract, certification path, or second vendor integration for end users who onboard through StarkFi.
The kyc product must be enabled on your deployment. Check GET /config/products with your API key, or contact your account manager.

​
Two onboarding paths

You can verify identity before opening a Didit session using email or wallet:
PathBest forSteps
EmailWeb apps with email loginprepare → send OTP → verify OTP → create session
WalletCrypto-native appswallet challenge → prepare-wallet → create session
Both paths converge at create session and get status.

​
Email flow

1

How StarkFi KYC works (Didit)

Identity verification is powered by Didit, with strong coverage for document checks, liveness, screening, and fraud signals. Instead of wiring your product directly to Didit dashboards, API keys, and workflows, StarkFi exposes a single API for starting sessions, tracking progress, and receiving outcomes.
2

Shared verification across StarkFi

When someone has already completed verification elsewhere on StarkFi, that identity can be recognized across the network. You are not charged again for a full verification cycle for users who are already approved in the ecosystem.
Exact reuse rules and commercial pricing depend on your StarkFi agreement. Contact support@starkfi.io or your account manager for details.
3

API sequence (email)

POST /kyc/prepare
POST /security/email/send-otp
POST /security/email/verify-otp
POST /kyc/create/verify_public_kyc
GET  /kyc/status?email=
StepMethod and pathPurpose
1POST /kyc/prepareRegister the user’s email for KYC
2aPOST /security/email/send-otpSend the email verification code
2bPOST /security/email/verify-otpConfirm the code
3POST /kyc/create/verify_public_kycCreate or resume the Didit session
4GET /kyc/status?email=Read approval state, session URL, and risk signals
Use the same email address in every step. We recommend lowercase addresses.

​
Wallet flow

1

API sequence (wallet)

POST /security/wallet/challenge
POST /kyc/prepare-wallet
POST /kyc/create/verify_public_kyc
GET  /kyc/status?wallet=
StepMethod and pathPurpose
1POST /security/wallet/challengeGet a signable message (expires in 10 min)
2POST /kyc/prepare-walletProve ownership with message + signed_bytes
3POST /kyc/create/verify_public_kycBody: { "wallet": "..." }
4GET /kyc/status?wallet=Poll until approved or declined
See Wallet challenge and Prepare KYC (wallet) for request bodies and error codes.

​
Verify quota

KYC session creation consumes your integration’s monthly verify quota. When quota is exceeded, prepare and session endpoints return 429 with status verify_quota_exceeded. Contact StarkFi to increase your limit or wait for the 30-day renewal window.

​
StarkPay and KYC/KYB

KYC/KYB rules depend on the payment context:
ContextKYC/KYB
Checkout (order)Not required — payments linked to an order via order_code or executor_id: order_transaction
Financial transaction (fiat methods)Required when you send payer_email or payer_wallet
Financial transaction (crypto only)Not required — 100% on-chain crypto never triggers KYC/KYB
See StarkPay overview for the full checkout vs transaction distinction.

​
Prerequisites

  • A valid end-user email or wallet you control for testing.
  • A way to open HTTPS (browser or in-app web view) when StarkFi returns a hosted Didit URL.
  • For email flow: outbound email delivery for OTP codes enabled for your environment.

​
Common issues

What you seeWhat to check
403 identity_not_verifiedComplete email OTP or wallet prepare before starting the KYC session.
403 user_not_preparedCall prepare (email or wallet) before create session.
404 user_not_found on OTPCall POST /kyc/prepare first for that email.
404 method_not_foundUse the path segment verify_public_kyc exactly as shown.
403 product_disabledKYC product not enabled — see Products.
429 verify_quota_exceededMonthly KYC session quota exhausted.