Skip to main content

​
Architecture

Sonar Architecture Sonar sits between your frontend application and your on-chain sale contract, handling compliance verification and authorization. Your project always owns the contract—Sonar never holds administrative keys.

​
The Integration Flow

​
1. Entity Authentication & Verification

Investors authenticate with Sonar using OAuth 2.0 PKCE flow, completing required KYC/KYB verification and accreditation processes based on your sale’s compliance requirements.

Authentication Details

Learn about the OAuth flow and configuration options

Frontend Integration

Connect your web application to Sonar

​
2. Eligibility Assessment

Your application queries Sonar’s API to verify that a connected wallet address is linked to an entity that meets your sale’s eligibility criteria.

Entities

Understand entity states and eligibility checks

​
3. Purchase Permit Generation

When an eligible entity initiates a purchase, Sonar generates a signed permit containing:
  • Entity ID and verification proof
  • Purchase limits (minimum, maximum amounts)
  • Price limits (for auctions)
  • Expiration timestamp for security

Purchase Permits

Deep dive into permit structure and validation

​
4. On-Chain Execution

Your smart contract validates the ECDSA permit signature against Sonar’s authorized signer and executes the token purchase according to your sale logic.

SettlementSale Contract

Reference for the standard Sonar sale contract

Custom Contracts

Build your own contract with permit validation