You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,15 @@ dotnet build
17
17
## PrivateCircle demo UI
18
18
- Run `Gateway.Api` and browse to [http://localhost:5023](http://localhost:5023) to use the built-in PrivateCircle-branded page. It can derive idempotency keys for fiat and crypto payloads, submit payments, and show canonical payloads used by the middleware.
19
19
20
+
### Online demo: worker updates for fiat + crypto
21
+
Use the built-in UI at http://localhost:5023 to show the background worker updating payment records after the simulated PSP/chain responds.
22
+
23
+
1. Start **PspStub.Api**, **Gateway.Api**, and **Gateway.Worker** (see steps below). Keep the demo UI open in a browser.
24
+
2. In the **Card / Fiat** card, click **Derive key** to populate the derived key and canonical payload, then click **Submit payment**. The UI displays the initial `Pending` response and fills the **Payment ID** field.
25
+
3. Click **Fetch /payments/{paymentId}** to query the API from inside the demo. As the worker authorizes the payment, repeat the fetch to watch the status move to `Authorized` with an `authCode` from the PSP stub.
26
+
4. Repeat the flow in the **Crypto** card. After **Submit crypto**, use **Fetch /payments/{paymentId}** and **Fetch /payments/{paymentId}/crypto** to watch the worker mark the transaction with confirmations and authorize the payment using the simulated `txHash`.
27
+
5. Call either submit button with the same derived key to highlight that the stored response is replayed (idempotent behavior still works after the worker updates records).
0 commit comments