@flopay/react 1.4.4 → 1.4.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -3
- package/dist/index.cjs +9 -9
- package/dist/index.mjs +9 -9
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -487,9 +487,14 @@ best-effort **in parallel** with the widget's charge:
|
|
|
487
487
|
with the parsed `FloPayError`, and the processing overlay clears so the buyer can
|
|
488
488
|
correct and retry. The charge cannot be cancelled once submitted, so this surfaces
|
|
489
489
|
for the buyer's *next* attempt rather than stopping the in-flight one.
|
|
490
|
-
- **Transient failure (`5xx` / network)** → best-effort and silent: the
|
|
491
|
-
listener falls back to the session's baseline address while the
|
|
492
|
-
the charge.
|
|
490
|
+
- **Transient failure (`5xx` / network)** → best-effort and buyer-silent: the
|
|
491
|
+
backend listener falls back to the session's baseline address while the
|
|
492
|
+
widget completes the charge.
|
|
493
|
+
- **Internal 10-second timeout** → the same functional fallback applies, and
|
|
494
|
+
successful widget completion still reaches `onComplete`. Telemetry records
|
|
495
|
+
the privacy-safe lifecycle event `operation.fallback` with
|
|
496
|
+
`processing` / `account_snapshot` / `timeout` dimensions instead of an
|
|
497
|
+
alert-level technical error. Direct and blocking timeout paths remain errors.
|
|
493
498
|
|
|
494
499
|
### Vault PCI card form
|
|
495
500
|
|