@flopay/react 1.11.4 → 1.11.6

package/dist/index.d.cts

@@ -844,6 +844,13 @@ interface VaultCardFieldsProps {
      * gate; omitted to skip it.
      */
     expectedOrigin?: string;
+    /**
+     * The form sits behind the backend's production human check (the vault
+     * block's `verification.required`). Forwarded to the adapter so a pre-submit
+     * frame `error` (check failed, expired or unavailable) is not reported as a
+     * vault load failure; it still reaches {@link VaultCardFieldsProps.onError}.
+     */
+    verificationRequired?: boolean;
     /**
      * Merchant theme colors pushed into the hosted widget so the card form
      * matches the surrounding checkout. Applied live on change (no remount).
@@ -893,6 +900,6 @@ interface VaultCardFieldsProps {
  * {@link CardCaptureAdapter} and bridges its `ready` / `error` lifecycle events
  * back to the surrounding card form.
  */
-declare function VaultCardFields({ capture, html, messageToken, expectedOrigin, theme, submitLabel, containerStyle, onReady, onError, onValidation, }: VaultCardFieldsProps): React.ReactElement;
+declare function VaultCardFields({ capture, html, messageToken, expectedOrigin, verificationRequired, theme, submitLabel, containerStyle, onReady, onError, onValidation, }: VaultCardFieldsProps): React.ReactElement;
 
 export { type CheckoutState, DirectPayPalButton, type DirectPayPalButtonProps, type DirectPayPalInitializationState, FloPayAutomaticPaymentButton, type FloPayAutomaticPaymentButtonProps, type FloPayAutomaticPaymentSuccessEvent, FloPayCheckout, type FloPayCheckoutProps, FloPayPaymentMethodSetup, FloPayPaymentMethodSetupProps, FloPayProvider, type FloPayProviderProps, SplitCardForm, type SplitCardFormProps, VaultCardFields, type VaultCardFieldsProps, useCheckout, useFloPay, usePayPalFloPay };

package/dist/index.d.ts

@@ -844,6 +844,13 @@ interface VaultCardFieldsProps {
      * gate; omitted to skip it.
      */
     expectedOrigin?: string;
+    /**
+     * The form sits behind the backend's production human check (the vault
+     * block's `verification.required`). Forwarded to the adapter so a pre-submit
+     * frame `error` (check failed, expired or unavailable) is not reported as a
+     * vault load failure; it still reaches {@link VaultCardFieldsProps.onError}.
+     */
+    verificationRequired?: boolean;
     /**
      * Merchant theme colors pushed into the hosted widget so the card form
      * matches the surrounding checkout. Applied live on change (no remount).
@@ -893,6 +900,6 @@ interface VaultCardFieldsProps {
  * {@link CardCaptureAdapter} and bridges its `ready` / `error` lifecycle events
  * back to the surrounding card form.
  */
-declare function VaultCardFields({ capture, html, messageToken, expectedOrigin, theme, submitLabel, containerStyle, onReady, onError, onValidation, }: VaultCardFieldsProps): React.ReactElement;
+declare function VaultCardFields({ capture, html, messageToken, expectedOrigin, verificationRequired, theme, submitLabel, containerStyle, onReady, onError, onValidation, }: VaultCardFieldsProps): React.ReactElement;
 
 export { type CheckoutState, DirectPayPalButton, type DirectPayPalButtonProps, type DirectPayPalInitializationState, FloPayAutomaticPaymentButton, type FloPayAutomaticPaymentButtonProps, type FloPayAutomaticPaymentSuccessEvent, FloPayCheckout, type FloPayCheckoutProps, FloPayPaymentMethodSetup, FloPayPaymentMethodSetupProps, FloPayProvider, type FloPayProviderProps, SplitCardForm, type SplitCardFormProps, VaultCardFields, type VaultCardFieldsProps, useCheckout, useFloPay, usePayPalFloPay };