@invonetwork/web-sdk 3.1.0 → 3.2.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/CHANGELOG.md CHANGED
@@ -4,6 +4,64 @@ All notable changes to `@invonetwork/web-sdk` are documented here. This project
4
4
  [Semantic Versioning](https://semver.org/). Releases are managed with
5
5
  [changesets](https://github.com/changesets/changesets).
6
6
 
7
+ ## [3.2.1] - 2026-08-28
8
+
9
+ **Documentation only. No code changes, no API changes.**
10
+
11
+ Documents two things about the Steam rail that the SDK does not change but every
12
+ Steam integration has to handle:
13
+
14
+ - **Currency for a Steam-distributed title must be bought on the `steam` rail.**
15
+ Any other rail is refused with `409 STEAM_PURCHASE_LAYER_REQUIRED`. This is a
16
+ platform requirement and it applies across every storefront the title ships on,
17
+ because a player's balance is shared between them.
18
+ - **The player is charged more than the value you request.** Steam's platform
19
+ commission is priced into the charge rather than absorbed, so the Steam
20
+ init-purchase response now carries `charged_usd` alongside `value_usd`. Show
21
+ `charged_usd` in your store. The currency the player receives is unchanged, so a
22
+ pack is worth the same in-game on every rail, and the rate is configuration --
23
+ read the response rather than hard-coding a multiplier.
24
+
25
+ ## [3.2.0] — 2026-08-24
26
+
27
+ **Storefront keys.** A game that ships on more than one storefront now gets one SDK
28
+ key per storefront -- `steam`, `ios`, `android`, `web`, `console` -- all valid at the
29
+ same time, and the key determines the payment rail. Construct one client per key and
30
+ use whichever matches where the player is buying. **Additive: no behavior changes, no
31
+ API removals.** A single existing key keeps working exactly as it does today, `rail`
32
+ included, with no deadline and no migration.
33
+
34
+ Three new typed error predicates for refusals this SDK previously surfaced only as a
35
+ raw `code` string:
36
+
37
+ - `InvoError.isRailChannelMismatch` -- the `rail` you sent disagrees with the storefront key
38
+ you authenticated with (400). The fix is to stop sending `rail`; the key already
39
+ determines it. INVO refuses rather than silently overriding, because overriding
40
+ would bill a player through a route you did not ask for.
41
+ - `InvoError.isSteamRailNotEntitled` -- a Steam purchase was attempted for a title INVO has
42
+ not registered as distributed on Steam (403). Holding a `steam` storefront key does
43
+ not by itself register the title.
44
+ - `InvoError.isSteamPurchaseLayerRequired` -- a title distributed on Steam tried to sell currency
45
+ on a non-Steam rail (409). Use the dedicated Steam purchase flow.
46
+
47
+ Also in this release: the 3-D Secure completion method's documentation no longer names
48
+ a payment processor. INVO does not name processors in developer-facing surfaces, and
49
+ this line had been an exception to that for some time.
50
+
51
+ Also in 3.2.0: **provider-neutral error codes.** INVO stamps a neutral alias
52
+ (`error_code_public`) beside any machine code that carries a payment
53
+ processor's name. This SDK previously read only the raw code, so a partner
54
+ branching on `err.code` had to hard-code a vendor name INVO's own public
55
+ documentation is not allowed to print. `err.code` is now the neutral alias when
56
+ one exists (`STRIPE_ERROR` becomes `PROCESSOR_ERROR`), and the literal wire value stays reachable on
57
+ `err.rawCode` for anyone already matching it. Refund reads prefer
58
+ `processor_refund_reference` over the vendor-named field, with a fallback.
59
+
60
+
61
+ **Storefront keys are still server-side keys.** A storefront key names where the
62
+ *purchase* came from, not where the key lives. It belongs in your backend exactly like
63
+ your original key -- never in a game client, an app bundle, or browser code.
64
+
7
65
  ## [3.1.0] — 2026-08-04
8
66
 
9
67
  **Passkeys are the gold standard; the SMS-PIN path is deprecated.** This release makes INVO's