Work in Progress (WIP) draft, Nov 15, 2026
What VPay gives you
VPay gives your app a programmable token ledger you already know how to talk to. The wire
your SDK speaks — TPL, the Tikoly Program Library, the token-program protocol VPay serves —
carries the JSON-RPC methods your code already calls: sendTransaction,
getTokenAccountBalance, getLatestBlockhash, and the rest.
Keep your @solana/web3.js or solana-go client. Change the endpoint. You’re building on
VPay.
Why it’s safe to build on
- Retries are safe. Send the same transaction twice and you get the original result back — the same receipt, the same movement, never a second charge. Your retry logic can be dumb and still be correct.
- Errors are typed. Every refusal comes back as a matchable code —
insufficient_balance,cap_exceeded,wrong_payee— not prose to parse or strings to guess at. Branch on the code, show your user the right message. - Money moves exactly once, or not at all. Every transfer is a single atomic double-entry movement. A failed call commits nothing; there is no partial state to reconcile.
- Big payments can require a second confirmation. An optional per-deployment threshold asks the sender to re-authenticate with their passkey before a large transfer clears. The challenge is bound to that exact transaction — a confirmation for one payment can never be replayed on another.
Under the hood: one endpoint, one ledger, your API keys (sk-tikoly-*, with short-lived
scoped tokens when you want them). Accounts render as base58 addresses your tools already
display. A transaction’s signature fixes what was sent; your key authorizes the movement —
and nothing moves unless both agree.
The two surfaces
-
The methods your SDK already calls —
sendTransaction,getTokenAccountBalance,getTokenAccountsByOwner,getTokenSupply,getLatestBlockhash,getSignatureStatuses. Same shapes you know, with the improvements a payments ledger can make (no rent, deterministic commits, safe replays). -
The
tpl.*extension —tpl.transfer,tpl.authorize,tpl.capture,tpl.release,tpl.getIntent, and friends, for everything the token-program shape can’t express: holds with expiry, quotes, capture evidence, and exact decimal amounts. A wallet can retire — burn — its own balance, but only its own; supply itself stays with the operator team.Two more surfaces round out the set:
tpl.getIntentreads back any transaction’s original result by its intent id — the same reply you got at commit time, retrievable forever — andtpl.getSpecInforeports exactly what the endpoint serves (methods, instructions, unit, mint), generated from the running code so it can never disagree with reality.
What’s real today
The API design is complete and locked — the shapes above are final — and the code behind them already passes its own spec’s tests: every example in the specification, replayed against the serving code, nine for nine. The public endpoint is coming next; that’s what the banner at the top means. When it opens, this page becomes your quickstart, and nothing you read here will have changed.
Build with us
We’re building VPay with early adopters, not for them. If you’re putting token payments into a product, write to [email protected] — you’ll get the endpoint, the attention, and a say in the surface.