@wirexapp/card-topup-web 1.1.0-beta.4 → 1.1.0

package/CHANGELOG.md

@@ -1,5 +1,119 @@
 # @wirexapp/card-topup-web
 
+## 1.1.0
+
+### Minor Changes
+
+- 8097859: CVV entry masking — show / hide what was typed into the top-up CVV field. The
+  CVV has always been masked as it is typed (a password input); this adds the
+  reveal element's masking model to that input, for both collect variants
+  (`createCardTopUpFields`, `createCardTopUpForm`). The card number is not
+  affected, and with no option passed nothing changes.
+
+  - `masked` (boolean, default `true`) — the state at mount; `false` starts the
+    field shown.
+  - `maskToggle: 'button' | 'text' | 'none'` (default `'none'`) — an in-frame
+    control at the field's right edge: the reveal's eye / eye-off icon, or a
+    text button from the new collect strings `show` / `hide`. It is the same
+    control the reveal rows draw (one module in the frames), themed by the same
+    `copyIconSize` / `colorCopyIcon` / `colorCopyIconHover` tokens. No `'row'`
+    mode: a tap on an input has to focus it. The toggle never takes the focus
+    from the field; the value and the caret stay.
+  - `maskAfter` (ms, default never) — shown digits re-mask from the frame,
+    counted from the moment they are visible.
+  - `setMasked(boolean)` on `PciCollectElement` and `PciCollectGroup` (the group
+    forwards to its `cvv` field) — host control in place, safe before `mount()`
+    resolves and after `destroy()`. Host→frame event `collect-set-masked`, sent
+    with the reply-less `PciFrameChannel.post()`.
+  - `onMaskedChange({ masked, reason })` — the state the frame applied, once at
+    mount (`'init'`) and after every change (`'user'`, `'host'`, `'timeout'`).
+    Frame→host event `collect-masked-changed`: a boolean and a reason, never
+    the value.
+  - `PciCollectGroup.field(name, options?)` takes the same masking options for
+    the `cvv` field (they win over the group config's).
+  - React: `CardCvvField` takes `masked` (live — forwarded in place, never a
+    remount), `maskToggle`, `maskAfter` and `onMaskedChange`. Mirroring
+    `onMaskedChange` into the state `masked` is rendered from is safe — the rule
+    is "when in doubt, mask": a hide is always sent, a show is not sent when it
+    is the echo of the frame's own "shown" report.
+
+  No reveal gate (`onRevealRequested`) on the input — the digits are the user's
+  own typing — and no `maskedPlaceholder`: the masked rendering is the browser's
+  password bullet. Microsoft Edge's built-in reveal button is now hidden in the
+  CVV field (it showed the digits behind the frame's state); the SDK's toggle
+  and `setMasked()` are the only ways to show them, in every browser alike.
+  The OCT package's surface is unchanged (its profile has no CVV). Additive
+  within protocol v1: frames that predate this ignore the three options and
+  `collect-set-masked`, keep the CVV masked and never send
+  `collect-masked-changed`; ship the frames first.
+
+- 901cddf: Collect failures. `PciFrameRequestError` gains `code`,
+  `retryable` and `reason`: the mobile SDK's failure payload
+  (`WirexCollectErrorPayload`), with the same values classified by the same rules.
+
+  - `code` is one of a frozen set: `unauthorized`, `actionRequired`,
+    `updateRequired`, `invalidInput`, `temporary`, `failed`. It is typed as the
+    `PciFrameErrorCode` union, so a `switch` over it checks exhaustively.
+  - `retryable` says whether sending the request again is safe.
+  - `reason` is present where one `code` has two remedies: `invalidInput` with
+    `cardAlreadyLinked` (enter another card) or `cardLimitReached` (remove one
+    first). The set grows; handle an unknown value.
+
+  The frame classifies a tokenize failure by the backend's business code on a 400
+  (`0243`, `0366`), otherwise by the HTTP status. A request without an answer is
+  `temporary`; a `Validation failed — …` reply is `invalidInput`. Messages are
+  unchanged. Older frames send none of the fields (`code` and `reason` undefined,
+  `retryable` false): ship the frames first.
+
+- 731da3e: Wallet checkout TOKEN MODE (WPAY-4431): pass the backend's short-lived top-up
+  token as `auth.checkoutToken` and the hosted checkout executes the top-up
+  itself, reporting `onExecuted` / `onExecuteFailed` (`wallet-executed` /
+  `wallet-execute-failed` on the wire) — the wallet payment token never leaves
+  the frame. Legacy tokenize-and-return (`onToken`) is unchanged without `auth`.
+
+  Token mode also brings Google Pay to desktop (`googlePayHandoff: 'qr' | 'none'`,
+  probe flag `googlePayHandoff`): the frame draws a QR that carries the checkout
+  itself — the token, the quote and the estimate's `provider` name (new init /
+  `arm()` / `update()` field) — and an Android phone opens the same checkout
+  top-level, pays and executes. Nothing is stored on the frames service and the
+  desktop never learns the outcome: hosts reconcile by their own status reads
+  after `wallet-state: handoff-pending`. `arm(quote, config, auth?, provider?)` /
+  `update(quote, config?, auth?, provider?)`; `wallet-update` carries `auth` and
+  `provider`; new `wallet-state` values `executing`, `handoff-pending`.
+
+  `buildWalletLaunchFragment` / `buildWalletLaunchUrl` (core) build the same
+  compact fragment for a Chrome Custom Tab launch (`#t=&e=&s=&p=[&r=]`); the page
+  resolves the provider block from the public BaaS config by name.
+
+### Patch Changes
+
+- 274c69f: Fixed: the frames rendered as solid white rectangles in host pages that declare
+  `<meta name="color-scheme" content="dark">` (or `light dark` with dark
+  preferred) — typical of hybrid-app shells and dark-themed sites. The SDK set
+  `color-scheme: normal` on the iframe element; Chromium resolves `normal` from
+  the host's meta, so under a dark host the element became dark while the frame
+  document is light, and on that mismatch the browser paints the frame's canvas
+  opaque (CSS Color Adjust). The iframe element is now explicitly
+  `color-scheme: light`, matching the frame documents, which now declare
+  `:root { color-scheme: light }` as well — the frames stay transparent under any
+  host scheme. Hosts that set their dark theme through CSS alone were never
+  affected. The SDK change alone removes the mismatch for an updated host; the
+  frame-document change makes the pair explicit and independent of any meta.
+- Updated dependencies [8097859]
+- Updated dependencies [901cddf]
+- Updated dependencies [cc46627]
+- Updated dependencies [390c416]
+- Updated dependencies [274c69f]
+- Updated dependencies [b43affc]
+- Updated dependencies [d4654e9]
+- Updated dependencies [417ab29]
+- Updated dependencies [1d89a12]
+- Updated dependencies [5f67be4]
+- Updated dependencies [33b4595]
+- Updated dependencies [a629a98]
+- Updated dependencies [731da3e]
+  - @wirexapp/card-sdk-core@1.1.0
+
 ## 1.1.0-beta.4
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wirexapp/card-topup-web",
-  "version": "1.1.0-beta.4",
+  "version": "1.1.0",
   "type": "module",
   "description": "Collect an external card for top-up inside Wirex-served PCI iframes; the host receives only a token. CHD-free loader.",
   "license": "UNLICENSED",
@@ -37,6 +37,6 @@
     "prepublishOnly": "yarn clean && yarn build"
   },
   "dependencies": {
-    "@wirexapp/card-sdk-core": "1.1.0-beta.4"
+    "@wirexapp/card-sdk-core": "1.1.0"
   }
 }