@vaam-apps/vpay-sdk 0.13.0 → 0.14.1

package/dist/index.d.ts

@@ -11,5 +11,5 @@ export { verifyWebhook, type VerifyWebhookOptions } from "./webhooks.js";
 /** This package's own version, as sent in the `vpay-sdk-node/<version>` User-Agent. */
 export { SDK_VERSION } from "./version.js";
 export { VpayError, VpayApiError, VpayAuthError, VpayUnexpectedResponseError, VpayTransportError, VpayConfigError, VpayInvalidParamsError, WebhookSignatureError, } from "./errors.js";
-export type { AccountHolder, RetrieveAccountHolderParams, CheckoutSession, CheckoutSessionStatus, CheckoutSessionUiMode, CheckoutPaymentStatus, CreateCheckoutSessionParams, ListCheckoutSessionsParams, Customer, DeletedCustomer, Address, AddressParams, CreateCustomerParams, UpdateCustomerParams, ListCustomersParams, Invoice, InvoiceLine, InvoiceStatus, InvoiceStatusTransitions, DeletedInvoice, DeletedInvoiceItem, CreateInvoiceParams, UpdateInvoiceParams, ListInvoicesParams, PayInvoiceParams, HostedPayInvoiceParams, OutOfBandPayInvoiceParams, OutOfBandParams, OutOfBandMethod, OutOfBandPayment, CreateInvoiceItemParams, UpdateInvoiceItemParams, PaymentIntent, PaymentIntentStatus, PaymentMethodType, NextAction, LastPaymentError, FailureCode, Refund, RefundStatus, Event, KnownEventType, Balance, BalanceAmount, List, ListParams, ListPaymentIntentsParams, ListEventsParams, CreatePaymentIntentParams, ConfirmPaymentIntentParams, MtnMomoPaymentMethodData, OrangeMoneyPaymentMethodData, CreateRefundParams, RefundDestination, UpdateRefundParams, ListRefundsParams, RequestOptions, } from "./types.js";
+export type { AccountHolder, RetrieveAccountHolderParams, CheckoutSession, CheckoutSessionStatus, CheckoutSessionUiMode, CheckoutPaymentStatus, CreateCheckoutSessionParams, ListCheckoutSessionsParams, Customer, DeletedCustomer, Address, AddressParams, CreateCustomerParams, UpdateCustomerParams, ListCustomersParams, Invoice, InvoiceLine, InvoiceStatus, InvoiceStatusTransitions, DeletedInvoice, DeletedInvoiceItem, CreateInvoiceParams, UpdateInvoiceParams, ListInvoicesParams, PayInvoiceParams, HostedPayInvoiceParams, OutOfBandPayInvoiceParams, OutOfBandParams, OutOfBandMethod, OutOfBandPayment, CreateInvoiceItemParams, UpdateInvoiceItemParams, PaymentIntent, PaymentIntentStatus, PaymentMethodDetails, PaymentMethodType, NextAction, LastPaymentError, FailureCode, Refund, RefundStatus, Event, KnownEventType, Balance, BalanceAmount, List, ListParams, ListPaymentIntentsParams, ListEventsParams, CreatePaymentIntentParams, ConfirmPaymentIntentParams, MtnMomoPaymentMethodData, OrangeMoneyPaymentMethodData, CreateRefundParams, RefundDestination, UpdateRefundParams, ListRefundsParams, RequestOptions, } from "./types.js";
 export { isCheckoutSessionEvent, isInvoiceEvent, isPaymentIntentEvent, isRefundEvent, } from "./types.js";

package/dist/types.d.ts

@@ -54,6 +54,23 @@ export interface LastPaymentError {
     code: FailureCode;
     message: string;
 }
+/**
+ * What a {@link PaymentIntent}'s one charge was made with (vpay since
+ * 2026-10-24): the payment-method type the payer used and the rail vpay
+ * charged it on. The outcome of routing; why that rail won is not on the API.
+ */
+export interface PaymentMethodDetails {
+    /**
+     * The charge's payment-method type (`"mtn_wallet"`, `"orange_wallet"`), or
+     * `null` where the charge records none: one confirmed by the code of a rail
+     * serving several types (`notchpay`), or made before vpay recorded types.
+     * A `string` rather than a closed union, so a type this SDK predates still
+     * type-checks.
+     */
+    type: string | null;
+    /** The code of the rail the charge was made on (`"mtn_momo"`, `"notchpay"`, …). */
+    rail: string;
+}
 export interface PaymentIntent {
     id: string;
     object: "payment_intent";
@@ -63,6 +80,14 @@ export interface PaymentIntent {
     currency: string;
     status: PaymentIntentStatus;
     payment_method_types: string[];
+    /**
+     * What the intent's one charge was made with, or `null` while it has none.
+     *
+     * `?` because a vpay predating 2026-10-24 omits the key entirely, for
+     * {@link PaymentIntent.customer}'s reason: `undefined` and `null` both mean
+     * "no charge to describe".
+     */
+    payment_method_details?: PaymentMethodDetails | null;
     next_action: NextAction | null;
     last_payment_error: LastPaymentError | null;
     metadata: Record<string, string>;
@@ -1341,8 +1366,9 @@ export type RefundDestination = {
      * A **rail code** (`"mtn_momo"`, `"orange_money"`, `"notchpay"`), or the
      * payment-method type the charge records (`"mtn_wallet"`, `"orange_wallet"`):
      * a server since 2026-10-24 accepts the type for a charge routed by it, which
-     * is how to refund one without knowing the rail it went to (no `/v1` object
-     * names that rail yet). Another type, or a type on an older server, is
+     * is how to refund one without knowing the rail it went to. (Since v0.14.0
+     * the intent names that rail too, as `payment_method_details.rail`, so the
+     * rail code is also at hand.) Another type, or a type on an older server, is
      * refused with a `400` naming `destination`.
      */
     payment_method_type: PaymentMethodType;

package/dist/version.d.ts

@@ -9,4 +9,4 @@
  * releases. A hand-written constant has no such landmine — it just needs to
  * be bumped alongside `package.json`'s own `version` field.
  */
-export declare const SDK_VERSION = "0.13.0";
+export declare const SDK_VERSION = "0.14.1";

package/dist/version.js

@@ -9,4 +9,4 @@
  * releases. A hand-written constant has no such landmine — it just needs to
  * be bumped alongside `package.json`'s own `version` field.
  */
-export const SDK_VERSION = "0.13.0"; // x-release-please-version
+export const SDK_VERSION = "0.14.1"; // x-release-please-version

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vaam-apps/vpay-sdk",
-  "version": "0.13.0",
+  "version": "0.14.1",
   "description": "The Node.js merchant SDK for vpay's /v1 API: OAuth2 private_key_jwt, payment intents, checkout sessions, refunds, events and webhook verification.",
   "license": "Apache-2.0",
   "publishConfig": {