IS6523 Chap.4 Distributed Ledgers and Electronic Payment Systems
Distributed Ledgers and Electronic Payment Systems
Two answers to one commercial problem
Trading online means two parties who have never met, possibly in different jurisdictions, needing a record of value moving that both of them and a third party afterwards will accept. The session offers two arrangements in the same sitting. A distributed ledger removes the single custodian of the record.
A payment system keeps the custodian and judges it against four published criteria.
They are not alternatives so much as two places to put the trust, and the examinable skill is arguing for one.
Decentralisation drawn as a cost of attack
A distributed ledger is a decentralised database held on many computers as identical copies, containing a continuously growing linked list of records maintained with cryptographic techniques.
A block is a batch of transactions that have been validated and then hashed, and it carries a pointer back to the block before it. The security claim follows from the structure: the only way to alter or remove an entry is to change every node, which the session calls theoretically possible and practically impossible.
The two properties it attributes to the arrangement, transparency and incorruptibility, both carry obligations, because a record that is permanent and public by definition is the wrong design for anything an individual has a legal right to have corrected.
Four criteria that turn a technology argument into a business one
A payment system is judged as flexible, secure, efficient and auditable, with flexibility meaning convenience of use, security meaning robustness, efficiency meaning cycle time and auditability meaning traceability of operations.
Those four are the most reusable thing here, because they convert a question about which rail is better into a question about which property the business needs most.
The instruments the course names run from online card payment and electronic cash through cheques and small payments to stored value cards, transfers and the settlement protocols underneath, with certificate authorities and their code of practice attached as a separate topic.
What this chapter covers
- 01
The record that two strangers and a third party will all accept
- 02
Blocks, hash pointers and identical copies at every node
- 03
Transparency and incorruptibility as properties with obligations
- 04
Three technologies the arrangement is assembled from
- 05
Where a shared ledger beats a database, and where it does not
- 06
Flexibility, security, efficiency and auditability
- 07
The instruments, and the certificate authorities behind them
Choose a payment rail without defaulting to the word secure
- 1Name what the question leaves out.
- 3Score each rail against the criteria it wins and loses on.
- 2State what has to be decided before a rail can be chosen.
Key terms
- Distributed Ledger
- A decentralised database stored on multiple nodes as identical copies, holding a continuously growing linked list of records maintained with cryptographic techniques.
- Block
- A batch of transactions that have been validated and then hashed, carrying a pointer back to the block before it so that the batches form a chain.
- Flexibility
- One of the four criteria for a payment system, defined by the course as how convenient the instrument is to use.
- Auditability
- One of the four criteria for a payment system, defined as the traceability of its operations. It is the criterion that survives a dispute.
- Electronic Cash
- One of the named types of electronic payment system, alongside online card payment, electronic cheques and small payments.
- Stored Value Card
- A payment instrument holding value committed in advance of purchase. The syllabus lists it among the payment infrastructure topics.
Distributed Ledgers and Electronic Payment Systems FAQ
When is a shared ledger the right answer rather than an expensive database?
When several parties need one record that none of them controls and are already paying to reconcile separate copies of it. The application list the session gives, covering supply chain checks, identity, title registration and customer verification, shares exactly that shape. Where only one party needs the record, the replication buys nothing and the cost of maintaining identical copies on many nodes is pure overhead.
Does the permanence of a shared ledger conflict with data protection duties?
It can, and saying so is the strongest available objection in a project. The arrangement is described as transparent by definition and as effectively impossible to alter, while the local data protection regime gives an individual a right of access and correction and limits how long identifying data may be retained. A design that cannot honour a correction request has a legal problem that no amount of cryptography addresses.
Is security the main criterion for judging a payment system in this course?
No, it is one of four and the course weights none of them above the others. Flexibility, efficiency and auditability each decide real cases: an inconvenient rail loses customers, a slow one consumes working capital, and an untraceable one cannot resolve a dispute. An answer that treats robustness as the whole judgement has used a quarter of the framework the session supplies.
How much does payment infrastructure matter for the examination?
More than its share of teaching time suggests. The published course aim names both the electronic payment infrastructure and the transactional security infrastructure, and one of the five intended learning outcomes, carrying a fifth of the weighting assigned across them, is specifically about evaluating the security of payment infrastructure for electronic commerce.
That is a judgement outcome, so prepare to argue rather than to describe.
Exam move
Take one purchase you made this week and describe its rail against all four criteria in four sentences, one each, then say which criterion the merchant was optimising for. Next, draw three blocks with the hash pointer between them and explain, without using the word secure, why altering the middle one is expensive.
Finish by naming one process in an organisation you know where several parties reconcile separate records, because that is the only case the ledger argument fits.
Working through Distributed Ledgers and Electronic Payment Systems in IS6523? Sia is AskSia’s AI Information Technology tutor — ask any IS6523 Distributed Ledgers and Electronic Payment Systems question and get a clear, step-by-step explanation grounded in how IS6523 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
