@flopay/react 1.8.2 → 1.8.3

package/README.md

@@ -55,6 +55,25 @@ function CheckoutPage() {
 
 `FloPayCheckout` automatically fetches the session, initializes the correct payment providers, and renders a `SplitCardForm` with the hosted vault card widget plus the session's supported wallets, APMs, and PayPal. Customer data (email, userId, name) is injected from the session.
 
+#### Buyer identity collection
+
+For inline checkout creation, `createSession.account.userId` remains required,
+but `email`, `firstName`, and `lastName` may be omitted. `FloPayCheckout`
+creates a mountable session shell first, then collects and attaches the missing
+identity before payment can continue:
+
+- Hosted card checkout renders a required email field first, above name, AVS,
+  and the hosted card widget. Submit stays gated until the email passes the
+  shared `isValidEmail()` validator and a name is present.
+- Apple Pay, Google Pay, other Stripe wallets, and PayPal use provider-returned
+  email/name automatically when available.
+- A wallet, PayPal, or APM that does not return the missing fields opens a
+  required second pane for email/name before the SDK creates an intent or
+  processes payment.
+
+The SDK never attaches a blank email. The merchant-supplied `userId` is not
+replaced by provider data.
+
 #### Merchant instrument feed
 
 Use `onInstrument` on `FloPayCheckout` or `FloPayProvider` to forward a stable,
@@ -443,7 +462,7 @@ Skip the backend API route — create the session directly in the component:
     clientId: 'your-client-id',
     currency: 'EUR',
     items: [{ providerItemId: 'product-1', providerItemName: 'Widget', totalAmount: 29.99 }],
-    account: { userId: 'user_1', email: 'user@example.com', firstName: 'Jane', lastName: 'Doe' },
+    account: { userId: 'user_1' }, // email and name are collected in checkout
     successUrl: '/success',
     cancelUrl: '/cancel',
   }}
@@ -451,7 +470,8 @@ Skip the backend API route — create the session directly in the component:
 />
 ```
 
-The component POSTs to the billing API, gets the full session back, and renders the form — zero backend code needed.
+The component creates a lightweight shell, renders the form, and claims the
+session after buyer identity is available — zero merchant backend code needed.
 
 #### Authorisation-only checkout