Skip to main content

​
What the App is for

The App is the main control surface for Parly users. It is where a user connects a wallet, authenticates private state, shields supported stablecoins, executes private payouts, reviews activity, prepares selective-disclosure records, and hands a disclosed lane to the Verify portal when proof is needed.

​
Connect and authenticate

Parly separates wallet connection from private-state access. Connecting a wallet gives the application an active address. Authenticating that wallet activates private-state recovery and execution by asking the wallet to sign a fixed authentication message. That message is used to derive the recovery identity used for private note recovery. The flow is:
  1. Connect wallet
  2. Authenticate
  3. Recover private state
  4. Use Shield, Execute, Ledger, and Verify

​
Shield

Shielding moves supported stablecoins into a private balance on Tempo. There are two shielding paths:
  • deposit from wallet
  • one-time deposit address
The Shield flow guides the user through network selection, asset selection, amount entry, approval where required, confirmation, and confirmed private-balance entry. Supported cross-chain deposits use Parly payment-route APIs. The app shows the route, status, and refund path without exposing the user’s private balance history.

​
Execute

The Send surface is where a user spends from private balance. It supports:
  • single send
  • batch send for up to 10 same-chain payout lanes
  • private same-network payouts on Tempo
  • private relay by default
  • self-relay fallback
Cross-chain private sends are available only where the active public route supports them. The App clearly separates submitted, pending, confirmed, and failed states.

​
Ledger and Compliance

The App includes a Ledger and Compliance surface directly below the main execution console. This is where users review deposits, private executions, change-note activity, scoped payout records, and disclosure-preparation flows. The compliance model is selective by design. A user can review one payout scope at a time, export a lane-scoped record, and hand that record to a counterparty, auditor, or exchange without exposing the wider private execution set. This surface supports:
  • activity review
  • scoped receipts
  • proof preparation
  • receipt PDF download where a receipt token is available
Privacy Links let users create profile links for open-ended payments and invoice links for a specific amount, asset, and recipient context. Payment links support deposit from wallet and one-time deposit address flows. Payers can keep a receipt or verify settlement without exposing the recipient’s private Parly balance. For the full user manual, see:

​
Scoped receipts

A scoped receipt is a record for one disclosed payout lane. A scoped receipt may include confirmed settlement facts, the disclosed payout scope, local note relationship details where appropriate, and provenance details where the source and settlement path can be linked accurately.

​
Verification handoff

When a scoped receipt is shared, the recipient can independently verify the disclosed payout lane using the Verify portal. The typical handoff is:
  • the confirmed Tempo transaction hash
  • the disclosed child key

​
Product behavior

The App keeps execution, review, and proof connected. Shielding, sending, history, receipts, and verification handoff belong to one coherent operating surface.