From afb8bb0e9e997119a4670668ff5151622d7527d0 Mon Sep 17 00:00:00 2001 From: yurii Date: Tue, 8 Sep 2026 15:38:21 +0100 Subject: [PATCH] fix: stream in-transaction card removal prompts --- CREDITCALL_STREAMING.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/CREDITCALL_STREAMING.md b/CREDITCALL_STREAMING.md index 9c3a8d2..cf73b90 100644 --- a/CREDITCALL_STREAMING.md +++ b/CREDITCALL_STREAMING.md @@ -55,11 +55,14 @@ Confirmation continues through the existing, separate XML endpoint. observational window. A supplied nonempty reference must match. The window opens immediately before the SDK start call and closes immediately at `TransactionFinished`; finalization never waits for card removal. -- Unidentified `CardRemovalRequested` and `CardRemovalEnforced` updates are omitted - because they can arrive after financial completion. They require a matching - explicit reference. `Removed` remains omitted even with a reference. +- `CardRemovalRequested` and `CardRemovalEnforced` follow the same active-window + rule as other progress, including when no reference is supplied. Real Miura + insertion-recovery sequences can repeat present-card and remove-card prompts + within one transaction; these repeated prompts are not deduplicated. Outside + the active window they are discarded. `Removed` remains omitted even with a + reference, and the existing `Inserted` mapping is unchanged. - Ownership is best-effort UI observation. SDK 3.17 does not establish that every - queued reference-less non-removal callback has drained before another transaction + queued reference-less callback, including removal, has drained before another transaction starts. Such a callback may briefly display stale progress in a later active window. This accepted limitation must never affect success, decline, cancellation, timeout outcomes, confirmation, retry, receipts, PMS posting, or business state.