Currently the webid profile has a payment pointer field and you can log in to your Uphold account to see your transactions.
upload a bank statement to your pod
The file should be stored in its original format but also translated to RDF:
the original facts, as triples
the fact that statements about those facts exist
the fact that those statements were communicated
upload e-invoices from service providers
Not just banks but also for instance PayPal. And credit cards. And the services you use also often give you a usage history overview, which relates to the invoices which you pay via your bank, credit card, or PayPal. Let's try to link that data!
Unfortunately it seems there is not much support yet anywhere for exporting your invoices in a machine-readable format. But if we find them, we can also store invoices in the user's pod. And then cross-reference them with the bank statements! :)
categorise transactions
A bank transaction often implies a purchase. For instance, you paid at a supermarket, so probably you bought groceries.
The implied purchases can be generated, stored, and categorised.
budget insight
When you have categorised expenses data, it's easy to compare those with your monthly budget.
bilateral ledger
Via the one-to-one chat, you could use SNAP to keep a bilateral ledger. Although if I had to design SNAP from scratch now, I would maybe directly implement a more generic World Ledger Gossip protocol.
web monetisation settings
Currently the webid profile has a payment pointer field and you can log in to your Uphold account to see your transactions.
upload a bank statement to your pod
The file should be stored in its original format but also translated to RDF:
upload e-invoices from service providers
Not just banks but also for instance PayPal. And credit cards. And the services you use also often give you a usage history overview, which relates to the invoices which you pay via your bank, credit card, or PayPal. Let's try to link that data!
Unfortunately it seems there is not much support yet anywhere for exporting your invoices in a machine-readable format. But if we find them, we can also store invoices in the user's pod. And then cross-reference them with the bank statements! :)
categorise transactions
A bank transaction often implies a purchase. For instance, you paid at a supermarket, so probably you bought groceries. The implied purchases can be generated, stored, and categorised.
budget insight
When you have categorised expenses data, it's easy to compare those with your monthly budget.
bilateral ledger
Via the one-to-one chat, you could use SNAP to keep a bilateral ledger. Although if I had to design SNAP from scratch now, I would maybe directly implement a more generic World Ledger Gossip protocol.