@flopay/react 1.4.14 → 1.4.16
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 +11 -2
- package/dist/index.cjs +9 -9
- package/dist/index.mjs +9 -9
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -547,8 +547,17 @@ session embeds session.vault or advertises gateways.stripe.enabledPaymentMethods
|
|
|
547
547
|
are charged by the backend's auto-checkout cascade.
|
|
548
548
|
- **3DS** is handled inside the widget — there is no client-side `confirmCardPayment`.
|
|
549
549
|
|
|
550
|
-
**
|
|
551
|
-
|
|
550
|
+
**Processing feedback:** after the hosted widget emits `submitting`, the SDK's
|
|
551
|
+
full-checkout processing overlay remains visible continuously until the widget
|
|
552
|
+
reports `complete`, `decline`, or `error`. Intermediate status polling and
|
|
553
|
+
late card-field validation mutations cannot expose the completed form while a
|
|
554
|
+
charge is still in flight. A synchronous card-validation rejection still
|
|
555
|
+
returns the buyer to the form immediately, as does a `4xx` account-snapshot
|
|
556
|
+
validation failure.
|
|
557
|
+
|
|
558
|
+
**Failure modes:** `onDecline` / `onError` receive the mapped reason + message
|
|
559
|
+
so consumers can react, and the SDK leaves an inline retry message after its
|
|
560
|
+
terminal failure overlay clears.
|
|
552
561
|
|
|
553
562
|
> **Backend dependencies:** the hosted widget must emit the `flopay-vault`
|
|
554
563
|
> `postMessage` outcome the SDK listens for (otherwise it falls back to its own
|