A WhatsApp-native AI payment agent and a two-server MCP layer for B2C payments in Colombia — VIIO accounts for onboarding, the user’s USDT balance for funding, a transactional engine driving a universal connector for utility billers as the first provided connector, and the TRON network (USDT) as the funding, settlement and reference layer.
The grant funds a complete WhatsApp-to-utility-payment loop with the TRON network in the funding, settlement and reference path, ending in a controlled live mainnet pilot. Go-to-market and brand positioning run through VIIO’s existing, proven infrastructure at no incremental cost to the grant.
A live mainnet pilot — users paying USDT-funded utility bills from WhatsApp, with every payment reconciled across VIIO, the universal connector and TRON references.
Account infrastructure, treasury controls, Fireblocks MPC custody/signing, and the internal services the transactional engine reuses. The grant builds the agent, the two-server MCP layer, the engine and the connector on top.
Not a custody change. VIIO keeps custody, KYC and treasury; the MCP layer and the transactional engine orchestrate and call internal services. They do not custody funds.
A user types an instruction in plain language. VIIO turns it into a structured, validated payment intent and executes it through controlled infrastructure — starting with Colombian public-utility bills (energy, water, gas, internet / telco).
“Pay my electricity bill — EPM, 85,000 COP.” The agent parses intent, fills any missing fields, shows a quote, and asks for explicit confirmation.
A read/validation server with no execution authority, plus a tool-execution server. Together they validate, quote, create intents, gate confirmation and trigger execution. They do not custody funds.
On confirmation, the engine debits the user’s USDT once the transaction is validated and creates the treasury / conversion / payment order on VIIO’s own ledger.
The universal connector disperses the payment to the public-utility biller. TRON/USDT is the funding, settlement and reference layer, with a full reconciliation chain.
Every step stays inside VIIO-controlled infrastructure. Explicit user confirmation is required before any execution; funds are debited once the transaction is validated, then the universal connector disperses the payment.
| Stage | What happens |
|---|---|
| 01–02 · WhatsApp → MCP | Instruction becomes a structured, validated payment intent. |
| 03–05 · Validate & quote | Identity, balance, limits, compliance and connector; then the COP / USDT quote. |
| 06–07 · Confirm & fund | User confirms in WhatsApp; USDT debited once validated → treasury order on VIIO’s ledger. |
| 08 · Connector disperse | The universal connector pays the public-utility biller. |
| 09–10 · Settle & reconcile | TRON/USDT reference + reconciliation; status returned in WhatsApp. |
MCP tools · launch set: validate_user_session validate_payment quote_payment create_payment_intent confirm_payment_intent reserve_user_funds create_treasury_order execute_service_payment get_payment_status reconcile_payment
“From a WhatsApp message to a paid utility bill, in seconds.”
VIIO has run production payment infrastructure since January 2023, across product, engineering, treasury, stablecoin operations, compliance, security and partnerships. The grant builds on systems already in operation.
100+ corporations served, plus a growing individual user base and a Visa card program for individuals and businesses. Infrastructure & compliance partners include Visa, Fireblocks, Chainalysis, FV Bank, BVNK, Tether, Circle, Sphere, Dock, Bitso and Binance.
Team: Sebastian Rocha, Santiago Hernandez, Andres Fonseca, Camilo Echeverri, plus VIIO engineering, treasury, compliance and GTM.
Payments are gated and controlled until the mainnet pilot. Testnet work uses dry-run and mock execution where a live environment is not yet authorized.
WhatsApp agent, VIIO login/session, USDT balance check, MCP read/validation server, connector registry, TRON testnet setup, and the universal-connector integration kickoff.
MCP tool-execution server, transactional engine + universal connector integration, full WhatsApp→MCP→engine orchestration on testnet/dry-run, reconciliation records and safety gates.
Controlled mainnet pilot: 5–15 USDT-funded live utility payments, 100% reconciled, ≥90% orchestration success. Adoption and PR delivered via VIIO’s existing channels at zero cost.
| Category | Amount | Share |
|---|---|---|
| Transactional engine + universal connector integration | $15,000 | 30% |
| Two MCP servers (read/validation + tool-execution) | $13,000 | 26% |
| WhatsApp agent + user session | $8,000 | 16% |
| TRON testnet/mainnet reference layer | $7,000 | 14% |
| Fireblocks MPC, security & compliance controls | $4,000 | 8% |
| Reconciliation & pilot reporting | $3,000 | 6% |
| B2C adoption, local PR & biller exploration | $0 | 0% |
| Total | $50,000 | 100% |
By tranche: T1 · Month 1 — $15,000 (30%) · T2 · Month 2.5 — $20,000 (40%) · T3 · Month 4 — $15,000 (30%). Tranches are milestone-gated; the largest (T2) delivers the transactional engine and universal-connector integration.
| KPI | Target |
|---|---|
| Production launch (agent + two MCP servers + transactional engine) | 1 |
| Live payment connector | Universal connector (utilities) |
| B2C users onboarded or invited | 25–50 |
| USDT-funded utility-payment intents created | 40+ |
| Explicit confirmation before execution | 100% |
| Live low-value utility payments (mainnet pilot) | 5–15 |
| Completed payments reconciled (VIIO + connector + TRON) | 100% |
| Orchestration success (excl. user declines) | 90%+ |
The product is centrally operated by VIIO within its existing compliance, account, treasury and security controls. VIIO is open to strategic investment, grant, or hybrid structures aligned with TRON’s regional payments strategy.
Consumer payment-orchestration fees, connector fees as new rails are added, USDT-to-fiat spread/conversion margin where movement is required, and future B2B/API access to VIIO-controlled connector tools once the B2C loop is proven.