資本市場における分散型台帳

プロセス

Distributed ledgers in capital markets: Payment from instruction to finality

RTGS システムは支払いを確認し、資金が不足していれば待ち行列に入れ、即時にグロスで決済し、最終的な決済を与えます。

1. 01 受付

   1. 01Payment instructionSource · ParticipantThe system should use, or at least accommodate, relevant internationally accepted communication procedures and standards.
   2. 04Validity and conditionality checksStep · System operator支払いは、資金や与信などの有効性と条件の確認を通過すると受け付けられます。無効な支払いは通常拒否されます。

2. 02 決済

   1. 02流動性データセット · 参加者Participants need liquidity for outgoing payments: central or commercial bank balances, incoming payments and intraday credit.
   2. 05QueueModel · System operator有効であっても条件の確認を通過しない支払いは、待ち行列に入れられるか拒否されます。待ち行列やその他の流動性節約の手段は、必要な流動性を削減できます。
   3. 06Settle in real time, grossStep · System operatorRTGS settles payments continuously, without deferral, usually one by one. Money settlements should use central bank money where practical.

3. 03 ファイナリティ

   1. 07最終決済Record · System operatorThe system gives clear, certain final settlement by the end of the value date at least, intraday or real time where needed.
   2. 08ReconciliationStep · System operatorReconciliation checks that records issued by two different entities match. The pages read state no timing for payment システム.

4. 04 レジリエンス

   1. 03Business continuity and secondary site演習 · システム運営者The plan uses a secondary site and aims to resume critical IT within two hours and settle by end of day. Arrangements are regularly tested.

Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval. The source is the CPMI-IOSCO Principles for financial market infrastructures. A business continuity plan covers disruption.