@vaam-apps/vpay-sdk 0.14.0 → 0.14.2
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 +2 -1
- package/dist/types.d.ts +3 -2
- package/dist/version.d.ts +1 -1
- package/dist/version.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -764,7 +764,8 @@ been checked against the real OP verifier by hand.** An assertion minted by
|
|
|
764
764
|
this SDK was fed directly to
|
|
765
765
|
`authkestra_op::client_assertion::verify_client_assertion` at the pinned
|
|
766
766
|
`authkestra-op = "=0.7.1"`, against a `ClientRegistration` holding the
|
|
767
|
-
corresponding public JWK, and was accepted.
|
|
767
|
+
corresponding public JWK, and was accepted — and again at `=0.13.1` on
|
|
768
|
+
2026-10-26, when the pin moved. `just sdk-conformance-node`
|
|
768
769
|
reproduces it: the recipe mints an assertion via `scripts/mint-assertion.mjs`
|
|
769
770
|
and pipes it into `cargo run -p vpay-sdk --example verify_assertion`. It is a
|
|
770
771
|
manual check, run on demand — it needs a Rust toolchain, it is not part of
|
package/dist/types.d.ts
CHANGED
|
@@ -1366,8 +1366,9 @@ export type RefundDestination = {
|
|
|
1366
1366
|
* A **rail code** (`"mtn_momo"`, `"orange_money"`, `"notchpay"`), or the
|
|
1367
1367
|
* payment-method type the charge records (`"mtn_wallet"`, `"orange_wallet"`):
|
|
1368
1368
|
* a server since 2026-10-24 accepts the type for a charge routed by it, which
|
|
1369
|
-
* is how to refund one without knowing the rail it went to (
|
|
1370
|
-
* names that rail
|
|
1369
|
+
* is how to refund one without knowing the rail it went to. (Since v0.14.0
|
|
1370
|
+
* the intent names that rail too, as `payment_method_details.rail`, so the
|
|
1371
|
+
* rail code is also at hand.) Another type, or a type on an older server, is
|
|
1371
1372
|
* refused with a `400` naming `destination`.
|
|
1372
1373
|
*/
|
|
1373
1374
|
payment_method_type: PaymentMethodType;
|
package/dist/version.d.ts
CHANGED
package/dist/version.js
CHANGED
|
@@ -9,4 +9,4 @@
|
|
|
9
9
|
* releases. A hand-written constant has no such landmine — it just needs to
|
|
10
10
|
* be bumped alongside `package.json`'s own `version` field.
|
|
11
11
|
*/
|
|
12
|
-
export const SDK_VERSION = "0.14.
|
|
12
|
+
export const SDK_VERSION = "0.14.2"; // x-release-please-version
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vaam-apps/vpay-sdk",
|
|
3
|
-
"version": "0.14.
|
|
3
|
+
"version": "0.14.2",
|
|
4
4
|
"description": "The Node.js merchant SDK for vpay's /v1 API: OAuth2 private_key_jwt, payment intents, checkout sessions, refunds, events and webhook verification.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"publishConfig": {
|