Introduction to Vaulty Integration
Vaulty is a non-custodial Solana wallet platform. Partners and developers can plug in payments, sign-in and white-label wallets while users keep full control of their keys and funds.
What is Vaulty integration?
Vaulty integration is a set of drop-in tools — payment links, a 1-line embed, a JavaScript SDK, REST API and a white-label wallet — that let any product accept crypto, request signatures, or offer a full wallet experience without building one from scratch.
How it works
- Step 1Sign in with GoogleOne tap. Google is just the doorway — we never see your wallet.
- Step 2Your wallet syncs securelyVaulty stores a secure copy in a hidden, app-only folder on your own Google Drive.
- Step 3Permanent backup, on usVaulty writes an encrypted copy to Arweave's permanent network. Fees are fully covered — nothing extra to pay.
- Your app generates a payment request, sign request, or connect request.
- Vaulty opens a secure flow (popup, redirect, or in-app) where the user approves with biometrics or PIN.
- Vaulty signs and broadcasts on-chain on the user’s behalf — never on yours.
- Your app receives a result + transaction reference, optionally confirmed by webhook.
Why it is secure
- Vaulty is non-custodial — private keys never leave the user's device.
- Every action requires explicit user approval; partners cannot move funds.
- All transactions are verifiable on-chain via Solscan.
- Partner credentials are scoped, rotatable and rate-limited.
Storage architecture (Always-there)
Vaulty's wallet storage is a hybrid stack designed for survivability without compromising self-custody. Encrypted material flows from device → Google Drive App Folder (appDataFolder) for fast primary sync, optionally → Arweave (via Irys/Bundlr) for one-time, pay-once permanent backup, indexed by a minimal Solana account (~128–256 bytes) recording only the Arweave TX ID and content hash.
- Primary sync — Google Drive App Folder (hidden, app-only scope).
- Optional permanent backup — Arweave (immutable, pay-once).
- Solana index pointer — TX ID + hash + primary/secondary flags only.
- Fallback order — Google first, Arweave only if the Google copy is missing or corrupted.
See Account → Security for the end-user view and Whitepaper § Wallet Storage Architecture for the full technical summary.
Sign-in methods
Storage, sync, multi-account, Portal and Telegram integrations behave identically across both methods. Your login method is locked to the account it created — Google and wallet accounts stay separate.

