@flopay/react 1.3.3 → 1.4.0

package/README.md

@@ -187,6 +187,17 @@ the entire integration change — no SDK redeploy or consumer code update is
 required. Wallets only render on supported devices regardless of dashboard
 state (Apple Pay on Safari/macOS/iOS, Google Pay on Chrome).
 
+In `layout="buttons"`, the **Credit / Debit Card** button always opens the
+inline card form. External wallets and PayPal keep their own lifecycle:
+buyer cancellation silently returns to the payment-method chooser with all
+eligible options available, while post-click technical failures, popup
+blocking, or a provider surface returning focus without a terminal callback
+restore the chooser, focus a visible retry control for the failed method, show safe method-specific copy such as
+`We couldn't open Google Pay. Try again or choose another payment method.`, and
+call `onError` with a structured `FloPayError`. Passive pre-click load or
+eligibility failures still collapse only the unavailable method and do not show
+a checkout error.
+
 Toggle the whole Stripe region or the PayPal region independently with the
 two gateway-level props:
 
@@ -698,6 +709,24 @@ function PaymentStatus() {
 | `options.currency` | `string?` | ISO 4217 currency code (used when no `clientSecret`) |
 | `options.paymentMethodCreation` | `'manual' \| 'auto'` | How payment methods are created |
 
+### Privacy-safe operational telemetry
+
+`FloPayCheckout` emits the same closed Flo-owned lifecycle/error/performance
+contract as `@flopay/js`, including React render/interactivity and provider
+readiness milestones. Collection is best-effort; merchant callbacks remain
+available with their existing arguments and invocation order. Synchronous
+throws and rejected callback promises are contained and logged only to the
+merchant console; they are not uploaded as `CALLBACK_FAILED`. Set the single
+`telemetry={false}` prop to opt out:
+
+```tsx
+<FloPayCheckout sessionId={sessionId} nonce={nonce} telemetry={false} />
+```
+
+No endpoint, custom tag, user context, message, stack, or metadata can be
+configured. See [`docs/TELEMETRY.md`](../../docs/TELEMETRY.md) for the complete
+privacy and retention contract.
+
 ### CheckoutFormProps
 
 | Prop | Type | Description |