Finance

Web Credits

The cc: vocab defines web credits, web ledgers, and web wallets.

Payment pointers

See the Open Payments Account API. This could live at https://alice.com/.well-known/pay (for payment pointer $alice.com), or at https://alice.com/any/other.location (for payment pointer $alice.com/any/other.location).

Transactions

Solid OS stores Two-Line Transaction. See Quicken interchange format, qif2n3.py and the qu: vocab.

Half Trades

The MoneyPane of Solid OS imports bank statements into half-trade entries in a ledger view. A half-trade is half a trade, so either a payment or a purchase. If you pay 1 dollar for a banana, then receiving the banana is one half-trade, and paying 1 dollar (which is the event that may show up in your bank statements) is another. These look as follows:

@prefix halftrade: <https://ledgerloops.com/vocab/halftrade#> .
<> a halftrade:Ledger .
<#d6e6bf16-759a-450d-92d9-02c109d97e34> a halftrade:HalfTrade ;
  halftrade:date  "2019-04-17T07:50:18Z"^^XML:dateTime ;
  halftrade:from <iban:CH93-0076-2011-6238-5295-7> ;
  halftrade:to <../shops.ttl#gumus> ;
  halftrade:amount 13.84 ;
  halftrade:unit "EUR" ;
  halftrade:impliedBy <../my-bank-statement.csv> ;
  halftrade:description "Electronic payment in shop" .

<#c1ed80a9-e7b1-4ba3-8877-a8656c6823b2> a halftrade:HalfTrade ;
  dct:date  "2019-04-17T07:50:18Z"^^XML:dateTime ;
  halftrade:from <../shops.ttl#gumus> ;
  halftrade:to <https://alice.com/#me> ;
  halftrade:amount 13.84 ;
  halftrade:unit "EUR" ;
  halftrade:impliedBy <#d6e6bf16-759a-450d-92d9-02c109d97e34> ;
  halftrade:description "Purchase implied by Electronic payment in shop" .

The document (<>) is a halftrade:Ledger. The halftrade:HalfTrades are on the ledger by virtue of being included in the document <#some-identifier>.

The effect of these two half-trades together is a change in balance between https://alice.com/#me and iban:CH93-0076-2011-6238-5295-7. Half trades can also be implied by SNAP messages, but only if they have snap:newState snap:Accepted. SNAP messages on top of Solid Chat are always stored twice (once by the sender and once by the receiver), but the convention is to link to the user’s own copy, on their own PDS, and not to the copy on the other party’s PDS.