@flopay/react 1.9.21 → 1.9.22

package/README.md

@@ -626,6 +626,13 @@ Checkout errors reach `onError` (and the `error` render prop) as `FloPayError` v
 | `stored_payment_method_unsupported` | `api_error` | The backend-selected saved method cannot be used for this transaction. Show the supplied buyer-safe instruction and let the buyer choose another method. |
 | `InvalidPaymentProcessResponse` | `api_error` | Saved-payment processing returned a response the SDK could not use. |
 
+Every `external_payment_method_failed` keeps that code and the existing buyer
+message. Its optional `details` object contains only bounded support fields:
+`providerCode`, `popupBlocked`, `inAppBrowser`, `appFamily`, `popupCapability`,
+and optional `presentationMode`. `providerCode` is sanitized and falls back to
+`external_payment_method_failed`; raw provider messages, URLs, user agents,
+credentials, payment identifiers, and customer data are never exposed.
+
 A `validation_error` is also reported when both `showStripe` and `showPayPal` are false with no PayPal gateway, or when a session advertises no supported gateway. When saving the AVS billing address is rejected with a `4xx`, `onError` receives the parsed billing API error while the message shows inline; the buyer corrects it for the next attempt.
 
 `FloPayCardSetup` reports failures to `onError` as `FloPayCardSetupError`, which adds `retryable`. Network, rate-limit, `5xx`, card-form timeout, and unexpected failures are retryable; validation failures are not.