@flopay/react 1.3.4 → 1.4.1
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 +25 -0
- package/dist/index.cjs +1508 -788
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +7 -10
- package/dist/index.d.ts +7 -10
- package/dist/index.mjs +1349 -630
- package/dist/index.mjs.map +1 -1
- package/dist/payment-logos/alipay.svg +1 -0
- package/dist/payment-logos/bancontact.svg +1 -0
- package/dist/payment-logos/blik.svg +1 -0
- package/dist/payment-logos/eps.svg +1 -0
- package/dist/payment-logos/giropay.svg +1 -0
- package/dist/payment-logos/ideal.svg +1 -0
- package/dist/payment-logos/klarna.svg +1 -0
- package/dist/payment-logos/p24.svg +1 -0
- package/dist/payment-logos/sepa_debit.svg +1 -0
- package/dist/payment-logos/wechat_pay.svg +1 -0
- package/package.json +4 -3
package/README.md
CHANGED
|
@@ -187,6 +187,13 @@ the entire integration change — no SDK redeploy or consumer code update is
|
|
|
187
187
|
required. Wallets only render on supported devices regardless of dashboard
|
|
188
188
|
state (Apple Pay on Safari/macOS/iOS, Google Pay on Chrome).
|
|
189
189
|
|
|
190
|
+
> **Bundler note:** the vendored APM brand logos ship as sibling `.svg` assets
|
|
191
|
+
> under `dist/payment-logos/`, referenced with `new URL('./…', import.meta.url)`
|
|
192
|
+
> so their bytes stay out of the JS bundle (a card-only checkout ships none of
|
|
193
|
+
> them). Your bundler must support asset URLs — Vite, webpack 5, Rollup, Next,
|
|
194
|
+
> and esbuild all do out of the box. Card-only and vault checkouts never render
|
|
195
|
+
> a method tile, so they never request a logo.
|
|
196
|
+
|
|
190
197
|
In `layout="buttons"`, the **Credit / Debit Card** button always opens the
|
|
191
198
|
inline card form. External wallets and PayPal keep their own lifecycle:
|
|
192
199
|
buyer cancellation silently returns to the payment-method chooser with all
|
|
@@ -709,6 +716,24 @@ function PaymentStatus() {
|
|
|
709
716
|
| `options.currency` | `string?` | ISO 4217 currency code (used when no `clientSecret`) |
|
|
710
717
|
| `options.paymentMethodCreation` | `'manual' \| 'auto'` | How payment methods are created |
|
|
711
718
|
|
|
719
|
+
### Privacy-safe operational telemetry
|
|
720
|
+
|
|
721
|
+
`FloPayCheckout` emits the same closed Flo-owned lifecycle/error/performance
|
|
722
|
+
contract as `@flopay/js`, including React render/interactivity and provider
|
|
723
|
+
readiness milestones. Collection is best-effort; merchant callbacks remain
|
|
724
|
+
available with their existing arguments and invocation order. Synchronous
|
|
725
|
+
throws and rejected callback promises are contained and logged only to the
|
|
726
|
+
merchant console; they are not uploaded as `CALLBACK_FAILED`. Set the single
|
|
727
|
+
`telemetry={false}` prop to opt out:
|
|
728
|
+
|
|
729
|
+
```tsx
|
|
730
|
+
<FloPayCheckout sessionId={sessionId} nonce={nonce} telemetry={false} />
|
|
731
|
+
```
|
|
732
|
+
|
|
733
|
+
No endpoint, custom tag, user context, message, stack, or metadata can be
|
|
734
|
+
configured. See [`docs/TELEMETRY.md`](../../docs/TELEMETRY.md) for the complete
|
|
735
|
+
privacy and retention contract.
|
|
736
|
+
|
|
712
737
|
### CheckoutFormProps
|
|
713
738
|
|
|
714
739
|
| Prop | Type | Description |
|