docs(payment): update CreditCall progress streaming behavior
This commit is contained in:
+15
-19
@@ -117,31 +117,27 @@ SALE confirmation continues through the existing, separate XML endpoint.
|
||||
for progress delivery. No additional delivery timer or whole-operation deadline
|
||||
shortens the existing HTTP call bounds.
|
||||
- Native SDK 3.17 updates use `UPDATE`; card notifications use `NOTIFICATION`,
|
||||
retained as `CARD_STATUS` on the internal wire. Normal progress does not require
|
||||
a reference: it is accepted only inside the existing serial transaction's active
|
||||
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.
|
||||
retained as `CARD_STATUS` on the internal wire. Supported progress is forwarded
|
||||
directly to the active stream, regardless of its reference. The request registers
|
||||
its listener around the existing transaction execution and removes it in `finally`
|
||||
before queuing the final frame. Finalization never waits for card removal.
|
||||
- `CardRemovalRequested` and `CardRemovalEnforced` follow the same active-window
|
||||
rule as other progress, including when no reference is supplied. Real Miura
|
||||
rule as other progress, regardless of the supplied reference. 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 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.
|
||||
- After timeout, an ambiguous start error, an asynchronous SDK error during an
|
||||
active window, or reference reuse/overlap, progress remains suppressed for that
|
||||
`Client` lifetime across SALE and PREAUTH. New transactions, elapsed time, callbacks and automatic
|
||||
reconnect do not reset the guard. Payments remain enabled.
|
||||
- Only the exact synchronous `ClientNotConnectedToServer` error safely clears an
|
||||
unsuppressed window and releases its unused reference: SDK 3.17 `StartCommand`
|
||||
returns it before `SendRequest`. Validation errors, mixed errors and all other
|
||||
unproven errors suppress observation. Safe pre-dispatch rejection never clears
|
||||
an existing suppression latch.
|
||||
queued callback, including removal, has drained before another transaction starts.
|
||||
References are not used to correlate progress. A late callback may briefly display
|
||||
stale progress in a later active stream. This accepted limitation must never affect
|
||||
success, decline, cancellation, timeout outcomes, confirmation, retry, receipts,
|
||||
PMS posting, or business state.
|
||||
- Every stream request creates a fresh writer and empty bounded progress queue.
|
||||
Timeout and exception cleanup removes only that request's listener; SDK errors
|
||||
and repeated references do not disable progress for later SALE or PREAUTH requests.
|
||||
The Client-wide SDK subscriptions remain unchanged. Slow or disconnected consumers
|
||||
cannot block SDK callbacks on socket I/O; a full queue may drop progress hints.
|
||||
- Progress cannot approve, decline, confirm, cancel, or retry a transaction.
|
||||
`OnlineAuthCompleted` means waiting; `Removed` and unknown events are omitted.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user