@flopay/react 1.4.13 → 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 +12 -3
- package/dist/index.cjs +9 -9
- package/dist/index.d.cts +17 -1
- package/dist/index.d.ts +17 -1
- package/dist/index.mjs +9 -9
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -60,7 +60,7 @@ function CheckoutPage() {
|
|
|
60
60
|
`FloPayCheckout` supports three checkout modes matching the billing API's `checkoutMode` field:
|
|
61
61
|
|
|
62
62
|
- **`full`** (default) — Shows the hosted card widget plus supported non-card methods.
|
|
63
|
-
- **`confirm`** — Hides the payment form and shows a "Confirm Purchase" button. Uses a saved payment method on the backend.
|
|
63
|
+
- **`confirm`** — Hides the payment form and shows a "Confirm Purchase" button. Uses a saved payment method on the backend. When the saved card needs re-authentication, the 3DS challenge runs in place and the same payment attempt completes — the button is not replaced by the card form.
|
|
64
64
|
- **`auto`** — Auto-submits with a saved payment method after the session loads. Falls back to `full` mode on failure.
|
|
65
65
|
|
|
66
66
|
```tsx
|
|
@@ -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
|