Architecture for wallet-direct Solana payments.
Trezalink coordinates hosted checkout, payment links, API credentials, webhook delivery, and Solana settlement without taking custody of merchant funds.
System route map
Checkout to settlement
Experience
Dashboard, hosted checkout, payment links
Application
Next.js routes, auth, merchant APIs
Integration
API keys, checkout endpoint, webhooks
Settlement
Solana wallet-to-wallet transactions
Records
Transactions, revenue, logs, merchant settings
0.3%
Platform routing fee
<2s
Median confirmation path
100%
Merchant wallet settlement
HMAC
Signed webhook delivery
Reduce payment risk without slowing your team
The architecture keeps checkout, custody, settlement, and automation boundaries explicit so teams can move fast without hiding operational risk inside a black box.
Common platform risks
- Custodial fund exposure from pooled processors
- Limited traceability across checkout and settlement
- Weak event authenticity in backend payment sync
How Trezalink responds
- Wallet-direct settlement keeps merchant custody boundaries clear
- Shared flow for payment links and API checkout reduces integration drift
- Signed webhooks and transaction records support auditable operations
One route for no-code links and API checkout
The same architecture supports a merchant creating a payment link from the dashboard or an application creating checkout sessions through the REST endpoint.
Payment intent
Checkout links and API requests create a controlled payment session with amount, description, and merchant wallet context.
Wallet authorization
The payer approves the transaction from a Solana-compatible wallet. Trezalink never receives private keys.
On-chain settlement
SOL moves directly across Solana with the platform fee separated by the payment route.
Webhook sync
Final payment state is reflected to the merchant dashboard and delivered to the configured webhook endpoint.
Security boundaries match how the app is used
Trezalink separates merchant configuration, payment execution, event delivery, and reporting so each product surface has a clear operational responsibility.
Non-custodial fund path
Merchant balances are not pooled inside Trezalink. Funds settle to the wallet configured in merchant settings.
Scoped credentials
API keys are regenerated from the merchant console and used to create checkout sessions programmatically.
Verifiable events
Webhook payloads are signed so your backend can validate that status updates came from Trezalink.
Operational visibility
Dashboard analytics, payment links, transaction tables, and webhook logs keep finance and engineering aligned.
Shared responsibility
Product surfaces covered
Integration contract
API and webhook loop
POST /api/v1/checkout
Authorization: Bearer <API_KEY>
{
"amount": 10,
"currency": "SOL",
"orderId": "inv-1042"
}Every payment creates an auditable trail
Checkout creation, wallet confirmation, transaction state, platform fee, and webhook delivery are visible through the merchant dashboard and supporting admin views.
Transaction records
Checkout, settlement, fee, and order context stay queryable.
Signed status events
Webhook delivery gives backends a verifiable payment state.
Real-time dashboards
Finance and support can inspect payment movement without engineering handoffs.
Architecture ready for merchants and developers
Start with payment links, then graduate to API checkout and webhook automation when your workflow needs deeper integration.