Tylt Embedded Wallet Service
Tylt Embedded Wallets enables merchants and platforms to provide crypto-wallet functionality directly to their end users through a secure, white-label API.
Merchants can create and manage wallet accounts for their users without requiring those users to interact directly with Tylt. The wallet experience can be integrated into the merchant’s existing website, application, or back-office system while Tylt manages the underlying wallet infrastructure, transaction processing, security controls, and compliance workflows.
What End Users Can Do
Once an end user has been provisioned and completed the required verification, they can:
Receive crypto-assets through dedicated blockchain wallet addresses
Send crypto-assets to external blockchain addresses
Transfer crypto-assets internally to other users belonging to the same merchant
Receive internal transfers from other users within the merchant’s ecosystem
View wallet balances and asset holdings
View transaction history and transaction details
Download transaction and ledger reports
On-Chain Transactions
On-chain transactions allow users to send and receive supported crypto-assets over public blockchain networks.
Each user can be assigned wallet addresses for supported assets and networks. Incoming transactions are detected and credited to the user’s wallet balance after the required blockchain confirmations.
Users may also withdraw assets to external wallet addresses, subject to applicable verification, security, compliance, and transaction-authorization requirements.
Internal Transfers
Internal transfers allow users to send supported crypto-assets to other users belonging to the same merchant.
These transfers are processed within the Tylt platform and do not require a blockchain transaction. As a result, internal transfers can be completed faster and without blockchain network fees.
Merchants can identify the sender and recipient using their own user identifiers, email addresses, or Tylt end-user IDs. Tylt resolves the underlying wallet accounts securely on the merchant’s behalf.
Wallet and Transaction Information
Merchants can retrieve wallet information for each end user, including:
Available balances
Asset holdings
Supported tokens
Supported blockchain networks
Deposit wallet addresses
Transaction history
Individual transaction details
Ledger and transaction reports
All user-level API requests are scoped to the merchant account. A merchant cannot access or transact on behalf of users belonging to another merchant.
Security and Authorization
The Embedded Wallets API is designed for server-to-server integration.
Requests are authenticated using an API key and an HMAC-SHA256 signature. Additional controls include:
IP address whitelisting
Merchant-level user scoping
Replay protection using timestamps and unique nonces
KYC approval requirements
Email OTP authorization
Authenticator-app two-factor authentication
User and account status checks
Sensitive API credentials must remain on the merchant’s backend and must never be exposed in a browser or mobile application.
Compliance
Wallet operations may be subject to identity verification, sanctions screening, wallet screening, Travel Rule requirements, transaction monitoring, and other compliance controls.
Wallet operations are enabled only when the end user has completed the required KYC process and is permitted to transact.
Tylt may request additional information, restrict a transaction, or suspend wallet operations where required by applicable law, regulation, internal risk controls, or compliance policies.
Typical Integration Flow
A standard Embedded Wallets integration follows these steps:
The merchant provisions an end user through the Tylt API.
The end user completes the required KYC process.
The end user enrolls in two-factor authentication.
The merchant retrieves the user’s supported wallet addresses and balances.
The end user receives crypto through an on-chain deposit or internal transfer.
The end user initiates an on-chain withdrawal or internal transfer through the merchant’s interface.
The merchant collects the required OTP and two-factor authentication code.
The merchant signs and submits the transaction request to Tylt.
The merchant retrieves the transaction status and displays it to the end user.
Intended Users
Embedded Wallets is designed for:
Fintech platforms
Payment service providers
Crypto and Web3 applications
Digital marketplaces
Remittance platforms
Merchant ecosystems
Loyalty and rewards platforms
Applications that require embedded crypto balances and transfers
Integration Model
The merchant owns the end-user interface and customer experience.
Tylt provides the underlying APIs and infrastructure for:
User provisioning
Wallet creation
Blockchain address generation
Balance management
On-chain transaction processing
Internal transfers
Transaction reporting
Security controls
Compliance workflows
All API calls must be made from the merchant’s secure backend environment.
Last updated