Documentation Index
Fetch the complete documentation index at: https://paywithz.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
KYC Submission
Users must complete KYC before they can transact on the platform. After KYC submission, a Soulbound Token (SBT) is issued to prove identity verification.Submit KYC
Request Fields
| Field | Required | Description |
|---|---|---|
wallet | Yes | Solana wallet address |
kycData.fullName | Yes | User’s full name |
kycData.country | Yes | Country code (ISO 3166-1 alpha-2) |
kycData.dateOfBirth | Yes | Date of birth (YYYY-MM-DD) |
kycData.email | No | Email address |
kycData.phoneNumber | No | Phone number with country code |
Response Fields
| Field | Description |
|---|---|
kycHash | Cryptographic hash of KYC data |
sbtTokenAccount | SBT token account address |
txSignature | Solana transaction signature |
expiry | SBT expiry timestamp (Unix) |
explorerUrl | Link to view transaction on Solana Explorer |
What Happens
- Backend validates KYC data format
- Creates hash of KYC data
- Stores full KYC data in database (secure)
- Calls SBT Manager program
- Issues SBT to user’s wallet
- Stores hash on-chain in SBT metadata
Privacy: Full KYC data is never stored on-chain. Only a cryptographic hash is stored. This protects user privacy while proving verification.
SBT Characteristics
Non-Transferable
SBT cannot be sent to another wallet. Bound to original wallet.
Contains KYC Hash
Cryptographic hash of KYC data stored on-chain.
Required for Transfers
Both sender and receiver must have SBT to transfer.
Revocable
Admin can revoke SBT if compliance fails.
Verify KYC Status
After submission, check wallet status:Get Your API Key
Request API Key
Join our pilot program to get API access. Banks, fintechs, and financial institutions welcome.
Next Steps
Stablecoin Operations
Mint and transfer tokens after KYC
Overview
See all API examples