Compare commits

...
1 Commits
Author SHA1 Message Date
Yurii cf84caecc8 docs(payment): update CreditCall progress streaming behavior 2026-11-16 14:34:05 +00:00
5 changed files with 21 additions and 20 deletions
+1 -1
View File
@@ -33,7 +33,7 @@ import (
) )
const ( const (
buildVersion = "v2.2.4" buildVersion = "v2.2.5"
serviceName = "hardlink" serviceName = "hardlink"
pollingFrequency = 8 * time.Second pollingFrequency = 8 * time.Second
) )
+15 -19
View File
@@ -117,31 +117,27 @@ SALE confirmation continues through the existing, separate XML endpoint.
for progress delivery. No additional delivery timer or whole-operation deadline for progress delivery. No additional delivery timer or whole-operation deadline
shortens the existing HTTP call bounds. shortens the existing HTTP call bounds.
- Native SDK 3.17 updates use `UPDATE`; card notifications use `NOTIFICATION`, - Native SDK 3.17 updates use `UPDATE`; card notifications use `NOTIFICATION`,
retained as `CARD_STATUS` on the internal wire. Normal progress does not require retained as `CARD_STATUS` on the internal wire. Supported progress is forwarded
a reference: it is accepted only inside the existing serial transaction's active directly to the active stream, regardless of its reference. The request registers
observational window. A supplied nonempty reference must match. The window opens its listener around the existing transaction execution and removes it in `finally`
immediately before the SDK start call and closes immediately at before queuing the final frame. Finalization never waits for card removal.
`TransactionFinished`; finalization never waits for card removal.
- `CardRemovalRequested` and `CardRemovalEnforced` follow the same active-window - `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 insertion-recovery sequences can repeat present-card and remove-card prompts
within one transaction; these repeated prompts are not deduplicated. Outside within one transaction; these repeated prompts are not deduplicated. Outside
the active window they are discarded. `Removed` remains omitted even with a the active window they are discarded. `Removed` remains omitted even with a
reference, and the existing `Inserted` mapping is unchanged. reference, and the existing `Inserted` mapping is unchanged.
- Ownership is best-effort UI observation. SDK 3.17 does not establish that every - 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 queued callback, including removal, has drained before another transaction starts.
starts. Such a callback may briefly display stale progress in a later active References are not used to correlate progress. A late callback may briefly display
window. This accepted limitation must never affect success, decline, cancellation, stale progress in a later active stream. This accepted limitation must never affect
timeout outcomes, confirmation, retry, receipts, PMS posting, or business state. success, decline, cancellation, timeout outcomes, confirmation, retry, receipts,
- After timeout, an ambiguous start error, an asynchronous SDK error during an PMS posting, or business state.
active window, or reference reuse/overlap, progress remains suppressed for that - Every stream request creates a fresh writer and empty bounded progress queue.
`Client` lifetime across SALE and PREAUTH. New transactions, elapsed time, callbacks and automatic Timeout and exception cleanup removes only that request's listener; SDK errors
reconnect do not reset the guard. Payments remain enabled. and repeated references do not disable progress for later SALE or PREAUTH requests.
- Only the exact synchronous `ClientNotConnectedToServer` error safely clears an The Client-wide SDK subscriptions remain unchanged. Slow or disconnected consumers
unsuppressed window and releases its unused reference: SDK 3.17 `StartCommand` cannot block SDK callbacks on socket I/O; a full queue may drop progress hints.
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.
- Progress cannot approve, decline, confirm, cancel, or retry a transaction. - Progress cannot approve, decline, confirm, cancel, or retry a transaction.
`OnlineAuthCompleted` means waiting; `Removed` and unknown events are omitted. `OnlineAuthCompleted` means waiting; `Removed` and unknown events are omitted.
+1
View File
@@ -12,6 +12,7 @@ import (
) )
func (app *App) preauthPayment(w http.ResponseWriter, r *http.Request) { func (app *App) preauthPayment(w http.ResponseWriter, r *http.Request) {
log.Printf("preauthPayment called")
app.streamPayment(w, r, true) app.streamPayment(w, r, true)
} }
+1
View File
@@ -16,6 +16,7 @@ import (
) )
func (app *App) salePayment(w http.ResponseWriter, r *http.Request) { func (app *App) salePayment(w http.ResponseWriter, r *http.Request) {
log.Printf("salePayment called")
app.streamPayment(w, r, false) app.streamPayment(w, r, false)
} }
+3
View File
@@ -2,6 +2,9 @@
`buildVersion` is a const in `cmd/hardlink/main.go`. `buildVersion` is a const in `cmd/hardlink/main.go`.
#### v2.2.5 - 16 November 2026
docs(payment): update CreditCall progress streaming behavior
#### v2.2.4 - 05 November 2026 #### v2.2.4 - 05 November 2026
fix(creditcall): require fresh confirmation approval for sale fix(creditcall): require fresh confirmation approval for sale