GITBOOK-1201: No subject

SUMMARY.md

@@ -328,7 +328,6 @@
   * [Roadmap](spar/roadmap.md)
 * [G2P Bridge](g2p-bridge/README.md)
   * [Features](g2p-bridge/features/README.md)
-    * [Digital Cash Transfer](g2p-bridge/features/digital-cash-transfer.md)
     * [Extensibility - Connect to Sponsor Banks](g2p-bridge/features/extensibility-connect-to-sponsor-banks.md)
     * [Account Mapper Resolution](g2p-bridge/features/account-mapper-resolution.md)
     * [Reconciliation with Sponsor Bank](g2p-bridge/features/reconciliation-with-sponsor-bank.md)

g2p-bridge/README.md

@@ -6,13 +6,17 @@ Being a G2P system (not a P2G, P2P, P2M, etc), the platform does not desire to o
 
 The following figure shows how the G2P Bridge subsystem fits into the overall G2P landscape
 
-<figure><img src="../.gitbook/assets/Gitbook-G2PB-Landscape.jpg" alt=""><figcaption><p>G2P Bridge in the G2P landscape</p></figcaption></figure>
 
 
-
-## Functional overview
+{% embed url="https://miro.com/app/board/uXjVKX-8Zq0=/" %}
+G2P Bridge in the G2P landscape
+{% endembed %}
 
 ## Technical overview
 
-<figure><img src="../.gitbook/assets/Gitbook-G2PB-Tech-Architecture.jpg" alt=""><figcaption><p>G2P Bridge - Technical Architecture</p></figcaption></figure>
+
+
+{% embed url="https://miro.com/app/board/uXjVKWoMWx0=/" %}
+Technial Architecture of G2P Bridge
+{% endembed %}
 

g2p-bridge/features/account-mapper-resolution.md

@@ -20,7 +20,11 @@ Based on this, the G2P Bridge is designed to receive Beneficiary IDs from the up
 
 The following figure illustrates this flow
 
-<figure><img src="../../.gitbook/assets/Account-Mapper-Resolution.jpg" alt=""><figcaption><p>G2P Bridge - resolving financial address using beneficiary IDs</p></figcaption></figure>
+
+
+{% embed url="https://miro.com/app/board/uXjVLOFA-qw=/" %}
+G2P Bridge - interface with ID-Account Mapper
+{% endembed %}
 
 The G2P Bridge then passes this resolved financial address to the downstream Sponsor Bank for further processing by the Banking Network.&#x20;
 

g2p-bridge/features/extensibility-connect-to-sponsor-banks.md

@@ -16,6 +16,10 @@ layout:
 
 Different benefit programs across various government departments can connect to different sponsor banks (treasury banks & commercial banks) to effect their respective disbursements. The following figure represents this
 
-<figure><img src="../../.gitbook/assets/Bank-Connectors.jpg" alt=""><figcaption><p>Connecting to Sponsor Banks - extending the Bank Connector Library</p></figcaption></figure>
+
+
+{% embed url="https://miro.com/app/board/uXjVLOCIexM=/" %}
+Connecting G2P Bridge to Sponsor Banks
+{% endembed %}
 
 For details on the methods defined by the BankConnectorInterface and the payload definitions, refer to the [design specification for the Bank Connector](https://docs.openg2p.org/g2p-bridge/development/design-specifications/interfaces).

g2p-bridge/features/privacy-and-security.md

@@ -14,5 +14,8 @@ layout:
 
 # Privacy & Security
 
-<figure><img src="../../.gitbook/assets/Gitbook-G2PB-Security-Architecture.jpg" alt=""><figcaption><p>JWT Security (for g2p-bridge as sender and receiver)</p></figcaption></figure>
 
+
+{% embed url="https://miro.com/app/board/uXjVLX90SPo=/" %}
+G2P Bridge - Security Architecture
+{% endembed %}

g2p-bridge/features/reconciliation-with-sponsor-bank.md

@@ -2,6 +2,8 @@
 
 The reconciliation of disbursement transactions between the G2P Bridge and the Sponsor Bank is explained by the following diagrams.
 
-<figure><img src="../../.gitbook/assets/Reconciliation-with-Sponsor-Bank-1 (1).jpg" alt=""><figcaption></figcaption></figure>
 
-<figure><img src="../../.gitbook/assets/Reconciliation-with-Sponsor-Bank-2.jpg" alt=""><figcaption><p>MT940 Account Statement for the Program Account - from Sponsor Bank </p></figcaption></figure>
+
+{% embed url="https://miro.com/app/board/uXjVLOLxLfM=/" %}
+G2P Bridge - Reconciliation with Sponsor Bank
+{% endembed %}

g2p-bridge/features/scaling-for-high-volumes.md

@@ -18,6 +18,8 @@ The G2P Bridge is designed to perform in high volume disbursement scenarios. To
 
 The disbursement instructions from the upstream Program MIS / PBMS systems are received by the G2P Bridge via. a REST API. The "create\_disbursements" API is designed to receive multiple API invocations for a single "program-disbursement-cycle". Each invocation of the API brings a payload that contains a list of disbursements.
 
-<figure><img src="../../.gitbook/assets/Scaling-for-Volumes-1.jpg" alt=""><figcaption><p>create_disbursements in G2P Bridge (from upstream Program MIS systems)</p></figcaption></figure>
 
-<figure><img src="../../.gitbook/assets/Scaling-for-Volumes-2.jpg" alt=""><figcaption><p>Scaling the Worker PODs for volume</p></figcaption></figure>
+
+{% embed url="https://miro.com/app/board/uXjVLNhY0o8=/" %}
+G2P Bridge - Scale out the Workers for high volumes
+{% endembed %}