@flopay/react 1.1.5 → 1.2.0

package/README.md

@@ -170,21 +170,49 @@ function UpsellButton() {
 
 `children` render inside the button, so you can treat them as slot content. If omitted, the default buttons-layout card content is used.
 
-#### Wallet Buttons
+#### Wallet Buttons & alternative payment methods
 
-Apple Pay, Google Pay, and PayPal are enabled by default. Toggle them with props:
+The payment-method list is now **gateway-driven**: the billing API ships
+`gateways.stripe.enabledPaymentMethods` per session, derived from the Stripe
+Payment Method Configurations enabled on the merchant account. The SDK
+partitions that list into two regions inside `SplitCardForm`:
+
+- `ExpressCheckoutElement` — `apple_pay`, `google_pay`, `paypal`, `link`,
+  `amazon_pay`, `klarna` (everything supported as a native big button).
+- `PaymentElement` (accordion) — every other enabled method, e.g. `cashapp`,
+  `affirm`, `ideal`, `bancontact`, `sepa_debit`.
+
+Enabling Cash App Pay (or any future Stripe method) in the Stripe dashboard is
+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).
+
+Toggle the whole Stripe region or the PayPal region independently with the
+two gateway-level props:
 
 ```tsx
 <FloPayCheckout
   sessionId="sess_abc123"
-  showApplePay={true}   // default: true
-  showGooglePay={true}  // default: true
-  showPayPal={true}     // default: true
+  showStripe={true}  // default: true — card + ECE + PaymentElement
+  showPayPal={true}  // default: true — DirectPayPal when gateway present,
+                     //                  Stripe-rendered PayPal otherwise
   onComplete={handleSuccess}
 />
 ```
 
-Apple Pay and Google Pay only render on supported devices (Apple Pay on Safari/macOS/iOS, Google Pay on Chrome).
+Setting both to `false` (with no PayPal gateway configured) is treated as a
+bootstrap-time validation error — `onError` fires with a
+`FloPayError({ type: 'validation_error' })` so the misconfiguration surfaces
+during integration instead of silently rendering an empty form.
+
+##### Deprecated props
+
+`showApplePay`, `showGooglePay`, and `directPaypal` are still accepted but
+emit a one-time `console.warn` when supplied alongside the new
+`enabledPaymentMethods` payload. They are no-ops once the backend ships the
+field — Apple Pay / Google Pay are dashboard-controlled at Stripe, and direct
+PayPal is auto-resolved from `gateways.paypal` on the session response. The
+legacy props will be removed in `2.0`.
 
 #### Theming
 
@@ -565,11 +593,14 @@ Shares most props with `CheckoutFormProps`, plus:
 
 | Prop | Type | Description |
 |------|------|-------------|
-| `showPayPal` | `boolean` | Show PayPal button (default: `true`) |
-| `showApplePay` | `boolean` | Show Apple Pay button (default: `true`) |
-| `showGooglePay` | `boolean` | Show Google Pay button (default: `true`) |
-| `totalAmount` | `number` | Amount in dollars for PayPal config |
-| `currency` | `string` | Currency code for PayPal config (default: `'usd'`) |
+| `showStripe` | `boolean` | Show the whole Stripe surface (card + ECE + PaymentElement). Default: `true`. Setting `showStripe={false}` together with `showPayPal={false}` (or no PayPal gateway) emits a `FloPayError({ type: 'validation_error' })` via `onError`. |
+| `showPayPal` | `boolean` | Show PayPal. Renderer chosen by `gateways.paypal` presence (DirectPayPal JS SDK when present; Stripe-rendered PayPal otherwise). Default: `true`. |
+| `enabledPaymentMethods` | `string[]?` | Per-session list of Stripe method type identifiers (`apple_pay`, `google_pay`, `cashapp`, `klarna`, `link`, `amazon_pay`, `sepa_debit`, `affirm`, `ideal`, …). Normally threaded automatically from `gateways.stripe.enabledPaymentMethods` by `FloPayCheckout`. The SDK partitions it into the ExpressCheckoutElement big-button row (intersected with `STRIPE_EXPRESS_METHODS`) and the accordion PaymentElement region (everything else; `card` is always dropped because the split fields render the card path). |
+| `showApplePay` | `boolean` | *Deprecated.* Apple Pay availability is dashboard-controlled at Stripe and surfaces through `enabledPaymentMethods`. Emits a one-time `console.warn` when supplied alongside `enabledPaymentMethods` and is otherwise ignored. Removed in `2.0`. |
+| `showGooglePay` | `boolean` | *Deprecated.* See `showApplePay`. |
+| `directPaypal` | `{ clientId: string; environment?: GatewayEnvironment }?` | *Deprecated input on `FloPayCheckout`* — auto-resolved from `gateways.paypal` on the session response. Still accepted on `SplitCardForm` for advanced consumers wiring providers manually. |
+| `totalAmount` | `number` | Amount in cents for PayPal / wallet config |
+| `currency` | `string` | Currency code for PayPal / wallet config (default: `'usd'`) |
 | `onFirstNameChange` | `(value: string) => void` | First name change callback |
 | `onLastNameChange` | `(value: string) => void` | Last name change callback |
 | `submitLabel` | `string` | Button text (default: `'CONFIRM PAYMENT'`) |