An order paid on the ledger is paid in a payment asset: cash on the DA Registry, such as a bank’s tokenized deposit or a stablecoin. Its issuer, , keeps the asset’s registry: for a tokenized deposit, the bank. It can be the venue’s own bank, another bank, or none: an order paid by bank transfer needs no payment registry (Deployment patterns).

What it runs

What it signs

The payment asset and its number of decimals are terms of the fund’s standing consent, which the fund’s register keeper and treasury sign; the bank does not. Payments land in, and payouts leave, the fund treasury’s own account, in the payment asset only. Who signs each transaction is on The on-ledger payment leg.

What it sees

Its own registry’s batch of each settlement: the payment asset’s holdings and allocations. Nothing of the fund: its register, its orders or its units. The venue is the Registry’s provider for the payment asset too, so it sees the bank’s whole book on that registry, and it issues the payment asset’s admissions (Who sees what).

Its records at the venue

Its mints and burns are its own books. Where the venue configures a register statement for the payment asset, reconciliation compares it with the holdings on the ledger. A bank statement, such as an ISO 20022 camt.053, is kept as received and not compared.

Internal or external

Related: The on-ledger payment leg · Settlement across registries · Deployment patterns