Concepts

What the chain shows

For each thing that happens to a remit, what anyone reads on an explorer and what only the parties read.

Every Remit transaction is an ordinary Solana transaction that anyone can open in an explorer. It names the accounts that took part and carries a proof. The amounts, the mint, the terms and the request are encrypted inside it, and only the people the payment belongs to hold the keys.

WhatOwnerAgentPayeeAnyone
That the agent paid the payeereads itreads itreads itreads it
The amount of a paymentreads itreads itreads it
The request it paid foras a hash; the owner’s statement also holds the URLreads itreads itreads it
The remit’s balancereads itreads it
The caps, the payee list and the expiryreads itreads it
The remit’s other paymentsreads itreads it

Instruction by instruction

"Anyone" is a person with an explorer and no keys. "The parties" are the owner, the agent and the payee, each reading what is encrypted to them.

ActionAnyone readsOnly the parties read
Register for a private balanceThe wallet, and the public viewing and nullifier keys it registers.Nothing is hidden. Nothing moves.
DepositThe wallet, the mint and the amount.The private balance it joins.
openThe owner's wallet, and the SOL the owner sends the agent key for fees.The amount, the mint and every term.
payThe agent key, the owner's wallet, the payee's wallet and the time.The amount, the mint, the request hash, the deadline, the terms, what the remit has left.
settleThe payee's wallet, the hold's deadline, the response hash, and the payee's settled count going up by one.The amount, the mint, the fee, the request hash.
refundThe payee's wallet, the hold's deadline, the account that sent it, and the payee's refunded count going up by one.The amount, the mint, the owner it returns to.
revokeThe owner's wallet.The amount returned.
WithdrawThe mint, the amount and the destination account.The private balance it left.

The two ends are public by design of the Default Ring: money entering a private balance and money leaving one are plain token transfers. Everything between a deposit and a withdrawal moves with its amount and mint encrypted.

The protocol's own settings are public too: the fee rate and the fee recipient in the program's config, and every payee's directory record with its standing.

What each party reads

The owner reads everything about their own remits: the balance, the terms, and each payment with its payee, amount, request hash, deadline and status. Each new state of a remit is encrypted to the owner's viewing key, which is fixed in the terms when the remit is opened and cannot be swapped by the agent.

The agent reads the remit it was given: what it holds and what its terms allow. It reads nothing else of the owner's.

The payee reads each hold made out to it: the amount, the mint, the request hash, the deadline and the owner it came from. It does not read the remit the payment came from, so it learns neither the agent's budget nor its caps nor who else the agent may pay.

Anyone else reads the rows of the table above. They can count how often an agent pays a payee and when. They cannot read what any payment was worth, what it bought, or what the agent is allowed to spend.

One payment, shown to one person

The owner or the payee can disclose a single payment. The person they send it to reads that payment's payee, owner, amount, mint, hashes, status and time, and no other payment. Receipts and disclosure explains how, and Verify checks a disclosed receipt against the chain.

Reading the public record

The API serves the public facts of any Remit transaction without keys:

HTTP
GET /v1/transactions/:signature

It returns the instruction (open, pay, settle, refund, revoke), the slot and block time, whether it confirmed, the fee payer and signers, and whichever of the owner, the agent and the payee the transaction names. Amounts, terms and requests are not in it: they are decrypted with the reader's own keys. The API lists every field.

Loading the index