MyTonWallet API integration (TON / TRON / Solana OpenData)

1 · Multi-chain accounting export

A web3 fund holds operational balances in MyTonWallet across TON, TRC-20 USDT and Solana SPL stablecoins. We expose /wallet/{addr}/transactions and /wallet/{addr}/balances normalized to ISO 4217-style ledger rows. The result feeds directly into NetSuite or QuickBooks via the firm's existing CSV import job, replacing manual screenshots from the Activity tab.

2 · Staking-yield statement for tax

An EU resident uses native TON staking through MyTonWallet's nominator pools. Our staking statement API consolidates each daily reward, validator address, and effective APY into a single PDF and JSON for tax filing. Field naming aligns with the OECD Crypto-Asset Reporting Framework (CARF), so the same export plugs into Koinly, CoinTracking or a private accountant.

3 · Telegram Mini-App KYT layer

Telegram Mini Apps must use TON Connect to interact with wallets. We capture the connected MyTonWallet address, signed connect proof, and downstream transfer events through a webhook bridge. The mini-app backend then runs Know-Your-Transaction (KYT) scoring against on-chain risk lists before greenlighting payments — a pattern increasingly required under MiCA Travel Rule guidance.

4 · NFT & Telegram Gifts loyalty graph

A consumer brand running a Telegram channel rewards holders of specific Telegram Gifts and TON DNS names. Our integration walks the Collectibles tab, resolves .ton domains, and emits a daily Parquet file of qualifying members with token ids, mint dates and last transfer block — ready for marketing automation.

5 · Soundbox-style merchant alerts

For merchants accepting TON or USDT-TRC20 via a MyTonWallet address, we surface inbound transfers as an SSE / webhook stream within seconds. Each event carries amount, jetton master address, payer address and a memo decoded from the body cell — enough to trigger a thermal-printer receipt or a POS confirmation tone identical to the in-app notification.

TON Connect bridge handshake

// Pseudocode: open a TON Connect session against MyTonWallet
POST /api/v1/mytonwallet/connect
Content-Type: application/json

{
  "manifestUrl": "https://example.com/tonconnect-manifest.json",
  "items": ["ton_addr", "ton_proof:abcdef0123"],
  "wallet": "mytonwallet"
}

// 200 OK
{
  "session_id": "sess_8f3...",
  "universal_url": "tc://...",
  "expires_at": "2026-05-04T10:30:00Z"
}

Multi-chain transaction statement

// Pseudocode: paged transaction history (TON + TRON + Solana)
GET /api/v1/mytonwallet/wallet/{address}/transactions
  ?chains=ton,tron,solana&from=2026-04-01&to=2026-04-30
Authorization: Bearer <ACCESS_TOKEN>

{
  "items": [
    {"chain":"ton","hash":"...","jetton":"USDT","amount":"125.00","fee":"0.0042","memo":"INV-9931"},
    {"chain":"tron","txid":"...","contract":"TRC20-USDT","amount":"500.00"}
  ],
  "next_cursor": "eyJwYWdlIjoyfQ"
}

Staking-reward webhook

// Pseudocode: webhook delivered when a TON nominator-pool reward lands
POST https://your-app.example/hook/staking
X-OFL-Signature: t=1714824000,v1=...

{
  "event":"staking.reward",
  "wallet":"EQA...mytonwallet",
  "validator":"EQB...nominator",
  "reward_ton":"3.214",
  "epoch":"2026-W18",
  "tx_hash":"..."
}

// Verify HMAC, then persist to your data warehouse.

Compliance & privacy

Our MyTonWallet integrations follow the EU Markets in Crypto-Assets Regulation (MiCA), in force since 1 January 2025, including the embedded Transfer of Funds Regulation Travel Rule that requires sender and receiver information on every crypto-asset transfer. For non-EU clients we additionally align with FATF guidance and local AML/CFT rules, and we honor GDPR data-minimization on any personally identifiable metadata captured outside on-chain payloads.

Because MyTonWallet is non-custodial, we never request seed phrases or private keys. Read access is sourced from public on-chain data, signed TON Connect sessions, or backups the customer themselves provide. Audit logs, consent records and right-to-erase workflows are baked into every delivery.

Data flow / architecture

1. Edge clients — MyTonWallet mobile/extension or a backend signer hold the user’s addresses and TON Connect session.
2. Ingestion layer — Our connectors poll TON, TRON and Solana RPC endpoints and decode jetton / SPL transfer events.
3. Normalization & storage — Records are mapped to a unified schema and stored in Postgres + object storage with per-tenant encryption.
4. API / webhook output — REST endpoints, signed webhooks and batch CSV/Parquet exports feed your analytics, accounting or compliance tools.

Deliverables checklist

• OpenAPI / Swagger specification for every endpoint we ship
• Protocol report covering TON Connect handshake, jetton ABI decoding and SPL token resolution
• Runnable Python and Node.js source for balances, transactions and staking endpoints
• Webhook reference implementation with HMAC verification samples
• Automated test suite plus a Postman / Bruno collection
• Compliance pack: MiCA Travel Rule mapping, GDPR data-minimization notes, retention policy template

Engagement workflow

1. Scope confirmation: chains, data types, target environments and authorization model.
2. Protocol analysis and API design (2–5 business days).
3. Build, internal validation and replay tests against mainnet (3–8 business days).
4. Documentation, sample apps and test cases (1–2 business days).
5. Handover, optional follow-up support, and pay-per-call hosted endpoints if you prefer usage-based billing.

About OpenFinance Lab

We are an independent technical service studio focused on App interface integration and authorized API integration. Engineers on the team have shipped protocol analyses for fintech, payments, exchanges and crypto wallets across Android, iOS, browser extensions and desktop builds, and we are comfortable with the cryptography and BoC parsing that TON-side work requires.

• Crypto wallets, exchanges, payments, banking and brokerage integrations
• Source code delivery from $300 — runnable APIs, full docs, pay after delivery upon satisfaction
• Pay-per-call API billing — call our hosted endpoints and only pay per request, no upfront fee
• Coverage of TON Connect, jetton standards, SPL tokens and EVM JSON-RPC under one roof
• Compliance-aware delivery: MiCA, GDPR, FATF Travel Rule, regional AML/CFT rules

Contact

Send us your target wallet addresses, the data scope you need, and any sandbox or sample app you want us to start from. We respond within one business day.

Open contact page