@12-apps/payments-frontend 1.19.1 → 1.20.0

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@12-apps/payments-frontend",
3
- "version": "1.19.1",
3
+ "version": "1.20.0",
4
4
  "type": "module",
5
5
  "description": "Browser half of the vendor-agnostic payments platform: plug-and-play MUI components for the per-provider settings page (credential form from each provider's schema, masked hints, verify/enable) and the checkout page (PIX QR + polling, card tokenization, hosted-checkout redirect), plus the headless hooks and fetch clients they build on. Talks only to the host's payments HTTP surface — never to a provider directly. Microfrontend-ready: no app coupling, host injects theme and auth.",
6
6
  "exports": {
@@ -17,7 +17,7 @@
17
17
  "storybook:build": "storybook build"
18
18
  },
19
19
  "dependencies": {
20
- "@12-apps/payments-backend": "^1.22.2",
20
+ "@12-apps/payments-backend": "^1.23.0",
21
21
  "react-qr-code": "^2.2.0"
22
22
  },
23
23
  "peerDependencies": {
@@ -92,9 +92,10 @@ function anyCredentialStored(
92
92
  *
93
93
  * Two qualifications, both learned the hard way:
94
94
  *
95
- * - Only providers that CAN charge are held to having charged. Stripe and
96
- * InfinitePay have no browser tokenization written, so requiring the proof
97
- * would not make their "Ativo" honest it would make them unactivatable.
95
+ * - Only providers that CAN charge are held to having charged. Every shipped
96
+ * adapter now declares activationCharge (Stripe's tokenizer and InfinitePay's
97
+ * hosted link included FUT-689/FUT-698), so today this spares only an
98
+ * adapter that genuinely cannot obtain proof.
98
99
  * - Turning OFF is never blocked. An owner must be able to pull a provider out
99
100
  * of rotation at once, and rows enabled before this rule existed would
100
101
  * otherwise be stuck on with no way down.