@flopay/react 1.4.18 → 1.4.19
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -0
- package/dist/index.cjs +9 -9
- package/dist/index.mjs +9 -9
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -785,6 +785,16 @@ Stripe and PayPal SDK load/runtime failures emit `provider_runtime`. Inline
|
|
|
785
785
|
`validation_rejected` / `payment_declined` outcomes and never carry
|
|
786
786
|
`failureCategory`.
|
|
787
787
|
|
|
788
|
+
The same classification applies to React-owned saved-payment processing in
|
|
789
|
+
`auto` and `confirm` modes. An ordinary saved-payment `400` decline, a
|
|
790
|
+
structured-field `400`, or a `422` still falls back to the usable full checkout
|
|
791
|
+
and emits `operation.fallback`, but reports only the matching
|
|
792
|
+
`payment_declined` or `validation_rejected` outcome. Genuine server,
|
|
793
|
+
transport, malformed-response, and provider-runtime failures remain
|
|
794
|
+
categorized technical errors. This does not change fallback rendering or
|
|
795
|
+
merchant callback behavior, and no response body, provider payload, session
|
|
796
|
+
value, payment data, or raw error message is added to telemetry.
|
|
797
|
+
|
|
788
798
|
### SplitCardFormProps
|
|
789
799
|
|
|
790
800
|
Key payment-surface props include:
|