International Tele Communications

Intent. Route. Execute. Settle.

Payphone is a non-custodial cross-asset orchestration layer on top of communications, escrow, and Circle USDC. Say what you want—"50 MATIC to USDC in my wallet"—and Payphone evaluates paths across Uniswap, Stellar SDEX, Circle, and BTCPay, shows every fee before you confirm, and executes step by step. We never hold your keys or your assets.

Download App
Route 0.05 BTC → USDC for escrow ctr_abc 11:53

Payphone

Best path: bridge + Circle · 0.5% service fee · confirm in 28s 11:59

Start with intent

Register with email and phone—then swap, call, and settle

Non-custodial: your Stellar keys and wallet signatures stay on your device. Payphone coordinates execution only.

🇺🇸+1
Create account

Already registered? Log in

Like a travel platform for money—Payphone does not own the airlines. We read your intent, quote optimal paths across external networks, and orchestrate execution while cryptographic authority stays with you.

V6 orchestration layer

One intent, every asset

Submit a canonical intent: asset in, amount, asset out, purpose, urgency. The Haskell intent engine validates. The routing engine quotes Uniswap V3, Stellar path payments, Circle transfers, and BTC bridges concurrently. You see the full fee breakdown—0.5% service fee plus network fees at cost—before anything executes.

Download desktop

Intent → Route → Execute

MATIC 50 → USDC 10.89

0.5% service · Uniswap 0.3% network

valid 28s · confirm to execute

Non-custodial by design

We coordinate—we never custody

Stellar secrets stay on your device. Circle programmable wallets are yours on mainnet. Uniswap swaps are signed by your wallet. BTCPay invoices go to your Bitcoin wallet. Payphone's routing and execution orchestrator calls external APIs in sequence; it does not maintain a balance sheet of user funds.

Security model
🔐

Session-scoped

Mapping destroyed on close

+1 (555) ***-**42 → seller
+1 (555) ***-**87 → buyer
SESSION_ENDED ✓

Communications + payments

Call, message, and move value

RingCentral-style phone and iMessage-style threads sit beside a Cash App–style USDC wallet. Masked lines, tolls, and peer payments flow through the same payment layer as escrow, procurement, and cross-asset swaps.

See features
🔒

Escrow & procurement

Fiverr-style orders with on-chain settlement

Fund escrow contracts, release milestones, post job bonds, and resolve disputes through admin arbitration. Appeals cost $10 USDC. Every outcome is written to MongoDB and the immutable ledger event chain.

Create account

npm run services:dev

Gateway · Intent · Routing · Ledger · Telephony

IntentRouteExecuteCircleEscrowBTCPay

Transparent fee architecture

0.5% service fee. No hidden spread.

Service fee: 0.5% of transaction value—Payphone's only orchestration revenue. Network fees: passed through exactly as quoted by Uniswap, Stellar, Circle, or bridge providers. Quotes expire in 30 seconds; execution requires explicit confirmation after you review the breakdown.

Download

IntentValidated

RoutePlanSelected

StepCompleted

TransactionFinalized

Auditable execution

Immutable ledger with hash chains

Every intent, route selection, step execution, and fee collection emits an append-only ledger event. SHA-256 hash chains link events per intent—verify integrity with GET /api/ledger/verify/:intentId.

For developers

IntentValidated

RoutePlanSelected

StepCompleted

TransactionFinalized

Whitepaper v6.0

Payphone V6 — financial OS, not another wallet

Version 6 adds non-custodial cross-asset orchestration to the existing Payphone stack: masked calls, Haskell escrow, Circle mainnet USDC, BTCPay storage, bonds, and admin dispute resolution all continue to work.

New capability: express financial intent in plain terms (BTC → USDC, MATIC → USDC, USDC → XLM) and let Payphone route through the optimal path with deterministic fees and real-time execution status.

Built for desktop users funding Circle wallets without juggling DEXs, and for SDK integrators (AutoEquityGroup, marketplaces) whose end users hold any asset but need USDC settlement.

Problem definition

Built for high-velocity marketplaces

Cross-border traders

Hold BTC or MATIC but need USDC in Circle to fund escrow—one intent, one confirmation, full fee disclosure.

AutoEquityGroup & dealers

Vehicle transactions settle in USDC while buyers may hold heterogeneous assets. SDK intents route to escrow automatically.

Marketplace operators

Sellers answer calls in minutes, settle milestones on-chain, and appeal disputes through a Fiverr-style admin process.

Developers

Intent → route → execute APIs with ledger verification. Non-custodial guarantees documented and enforced at the API layer.

System overview

Six core services

Intent engine, routing, execution orchestrator, ledger, telephony, and escrow—plus MongoDB and Redis. Start with docker compose up

1

Intent engine (:4008)

Haskell (or Node shim): validates asset pairs, amounts, purpose—returns CanonicalIntent.

2

Routing engine (:4009)

Rust (or Node shim): concurrent provider quotes, path scoring by urgency, 30s quote window.

3

Execution orchestrator (:4011)

Step-by-step adapter dispatch with retries, partial completion handling, Redis events.

4

Ledger service (:4012)

Append-only SHA-256 hash chain for every intent and execution step.

5

Payment layer

V5 unified Payment objects—transfers, escrow, procurement, swaps, appeals.

6

Communications

Telephony engine, masked lines, messaging, BTCPay $9.99/mo storage.

Why Payphone

🛡️

Non-custodial

No pooled user funds. No private key storage. Coordinator, not carrier.

Intent-based

One form: asset in, asset out, purpose, urgency. Everything else is orchestration.

📊

Transparent fees

0.5% service fee + network pass-through. Shown before execution. No spread markup.

📦

Full stack

Calls, escrow, procurement, bonds, swaps, and ledger in one desktop app.

Case studies

Proven workflows

MATIC → USDC wallet fund

~3 second Uniswap path

User submits intent for 50 MATIC → USDC. Routing selects Uniswap V3 on Polygon. Fee breakdown shown. User confirms. USDC arrives in Circle wallet. Ledger records 8 events.

USDC → XLM peer payment

Stellar path payment

Send USDC from Circle through Stellar SDEX to @alice. Non-custodial: transaction envelope signed on device.

Escrow + dispute

Admin arbitration

Buyer funds escrow via intent purpose fund_escrow. Seller delivers. Dispute filed. Admin resolves. Outcome in MongoDB + ledger.

Design principles

Coordinator not carrier

Payphone routes and executes through external providers—you hold the keys.

Confirm before execute

30-second quote window. userConfirmation: true required on every execution.

Replayable audit trail

Hash-chained ledger events reconstruct any transaction timeline.

Extend V5, don't replace

Telephony, escrow, Circle, BTCPay, and payment layer remain first-class.

Use cases

Where Payphone fits

  • Fund Circle USDC wallet from MATIC, ETH, or BTC without leaving Payphone
  • Cross-chain peer payments USDC → XLM to Stellar names
  • AutoEquityGroup vehicle escrow with heterogeneous buyer assets
  • International calls with masked lines and USDC toll settlement
  • Procurement milestones, job bonds, and admin dispute resolution

Monetization

Monetization without hidden spread

Orchestration service fee: 0.5% per executed cross-asset intent. Plus existing V5 revenue: 5% escrow/procurement settlement, 1% P2P, 10% toll commission, $10 appeals, $9.99/mo BTCPay storage.

  • Cross-asset intent execution: 0.5% service fee
  • Escrow & procurement settlement: 5% platform fee
  • P2P USDC transfer: 1% platform fee
  • Storage & comms: $9.99/mo via BTCPay Bitcoin
Integrate your marketplace

Download Payphone

Non-custodial cross-asset orchestration desktop app—Intent · Route · Execute · Settle.

Get the desktop app