This is an experiment in two things simultaneously:
The problem at hand is rather simple but has novel context requirements.
- An Actors style description
- A design for SRB.
Here are some early decisions:
Some (all?) of the objects:
- I will initially ignore issues of persistence.
- I will assume that some plug-in is invoked by an html payment request item.
- I will support multi account users.
- I will not require the single account user to understand multi account
The account custodian
- Info and authority (if necessary) to signal the bank (IP adderess or what
- account number with bank
- Secret shared with bank
- Optional Auditor reference
- Custodian of accounts
- Set of pairs of (user recognition info, alternatively(account reference,
- Transient payment context
- Exists until payment is acknowledged by server.
- Captures acknowledgment from bank.