@phis/contracts 0.5.0 → 0.7.0

package/README.md

@@ -6,6 +6,7 @@ and change at different moments.
 
 ```
 @phis/contracts/addon                what phis and a separately shipped Add-on promise each other
+@phis/contracts/payments             the approved Payment consumer, Provider and merchant-profile types
 @phis/contracts/access               the authorization vocabulary phis and @phis/ui both evaluate
 @phis/contracts/signals              the signal vocabulary and address grammar the UI declares in and phis validates
 @phis/contracts/catalog              the Module categories an Add-on declares, the UI groups by and a market filters on
@@ -45,7 +46,7 @@ The types and constants an Add-on declares or implements. Types and constants on
 `server-only`, no React, no Next.
 
 An Add-on is compiled to a single ESM artifact and installed into a running phis through the `phis` CLI;
-it is never built into the server. This subpath is the only thing an Add-on compiles against, and it must
+it is never built into the server. This subpath is the shared Add-on entrypoint it compiles against, and it must
 not depend on phis itself. For an Add-on author it is a build-time dependency: everything it exports is
 erased at compile time apart from a handful of constants.
 
@@ -61,10 +62,10 @@ What it covers:
   (`PhisMediaStorageAdapter`, upload plans, object I/O) and Directory. `PHIS_SERVICE_KINDS` names them
   and `PHIS_SERVICE_INTERFACE_DIGESTS` holds the digest of each kind's current interface; Core refuses an
   Add-on built against a different digest at install.
-- **Core capabilities** -- `PHIS_CORE_CAPABILITIES`, the capability ids an Add-on may require. Declare
-  against these constants rather than spelling the ids out. The list is the vocabulary and may reserve a
-  name before Core delivers it (`resource-links`, `support`); an Add-on that requires a capability this
-  release does not deliver is refused rather than handed a missing object.
+- **Core capabilities** -- `PHIS_CORE_CAPABILITIES`, the catalogue ids an Add-on may require. Declare
+  against these constants rather than spelling the ids out. Core separately validates delivery to
+  Add-ons; a catalogue id such as `authentication` may serve Site Modules without a corresponding
+  Add-on context field. Payment ids accompany the implemented Core capability/service/event catalogue.
 
 `PHIS_ADDON_ABI_VERSION` is the single number phis checks an Add-on against.
 
@@ -72,6 +73,23 @@ How an Add-on is laid out, compiled, installed, activated and upgraded is descri
 [`ADDON_HOWTO.md`](https://github.com/phis-dev/phis-server/blob/main/ADDON_HOWTO.md); the rules behind it
 are in [`SERVER_ADDONS.md`](https://github.com/phis-dev/phis-server/blob/main/SERVER_ADDONS.md).
 
+## `/payments`
+
+The approved v1 consumer capability, Provider adapter, checkout plans, normalized money,
+payment/operation/refund records, merchant profile/grant types and owning-consumer event facts.
+All exports are types; there is no secret accessor implementation, checkout SDK, exchange-rate
+conversion or Payment engine here. The same types are re-exported by `/addon`.
+
+Consumers own their prices in CHF, EUR, USD or another supported currency. Every payment uses one
+currency; capture and refunds inherit it. Core never infers conversion or settlement currency.
+
+Core implements Payment execution separately. Its catalogue exports `payments`, `paymentNotifications`,
+the Payment service kind/interface digest and `payment.changed`. Notification ingress is available
+only in a bound hook context. The Add-on event context discriminates thread and Payment subjects;
+thread producers remain explicitly typed as thread events.
+See the normative [Payment contract](https://github.com/phis-dev/phis-server/blob/main/PAYMENTS.md)
+and [Stripe/profile contract](https://github.com/phis-dev/phis-server/blob/main/PAYMENTS_STRIPE.md).
+
 ## `/access`
 
 Claim shapes, policy shapes, and the evaluator that decides them. Unlike `/addon`, this is runtime code

package/dist/addon-index.d.ts

@@ -3,6 +3,7 @@ export * from "./assets.js";
 export * from "./capabilities.js";
 export * from "./core.js";
 export * from "./media-storage.js";
+export * from "./payments.js";
 export * from "./queries.js";
 export * from "./resource-links.js";
 export * from "./schema.js";

package/dist/addon-index.js

@@ -3,6 +3,7 @@ export * from "./assets.js";
 export * from "./capabilities.js";
 export * from "./core.js";
 export * from "./media-storage.js";
+export * from "./payments.js";
 export * from "./queries.js";
 export * from "./resource-links.js";
 export * from "./schema.js";

package/dist/addon.d.ts

@@ -65,7 +65,9 @@ export type PhisAddonHookDescriptor = {
      *
      * Absent is not a lesser variant of present: an unverified hook writes nothing at all -- not through
      * `data:v1`, not by opening a thread -- because nothing distinguishes its caller from anybody who
-     * found the address. A hook that needs to write declares how it can be believed.
+     * found the address. A hook that needs ambient write authority declares how it can be believed.
+     * Target v1 Payment notification ingress instead verifies through its bound Core capability and
+     * reconciles Core-owned payment state without granting ambient hook write authority.
      */
     verification?: PhisAddonHookVerificationDescriptor;
     /**
@@ -197,6 +199,46 @@ export type PhisAddonEventHandlerDescriptor = {
     event: PhisAddonEventId;
     handler: string;
 };
+/**
+ * One sentence of an occasion, with the parameters it takes in order.
+ *
+ * `%1`, `%2`, ... in `text` stand for the named parameters, the way Core's own templates are written,
+ * so the sentence translates as one unit and the values are put in afterwards. A text parameter is
+ * escaped where it lands; a path parameter arrives as a link on the Site's own public address.
+ */
+export type PhisAddonOccasionLine = {
+    text: string;
+    parameters?: string[];
+};
+/**
+ * One kind of message this Add-on may ask Core to write to a person.
+ *
+ * Declared rather than composed at the call: the words are part of the manifest and therefore of the
+ * digest, so what a Site can say in an Add-on's name is readable at install and cannot change under a
+ * running Site. Core renders the lines through its own layout, salutation and translation, and adds
+ * what the class owes -- which is why an Add-on cannot produce a mail without Core's frame.
+ *
+ * `class` is `asked-for` and nothing else this release: the person's own action is the reason for the
+ * message (an order they placed, a request they made), no consent bit applies and no unsubscribe link
+ * is offered. The sent class -- a message somebody decided to send to people who did not ask today --
+ * is Core's own bulk case and is not declarable here until it is.
+ */
+export type PhisAddonOccasionDescriptor = {
+    /** `^[a-z][a-z0-9-]{0,63}$`; the name a `notify` call and the outbox row carry. */
+    name: string;
+    class: "asked-for";
+    description?: string;
+    subject: PhisAddonOccasionLine;
+    lines: PhisAddonOccasionLine[];
+    /**
+     * What a call must bring, by name. `text` is inserted as written; `path` is a Site-relative path
+     * (`/shop/order/1234`) that Core turns into an absolute link on the Site's public address.
+     */
+    parameters: {
+        name: string;
+        type: "text" | "path";
+    }[];
+};
 export type PhisAddonManifestV1 = {
     manifestVersion: typeof PHIS_ADDON_MANIFEST_VERSION;
     addonId: string;
@@ -258,6 +300,13 @@ export type PhisAddonManifestV1 = {
      * provider, and every write here refuses a group carrying anybody else's.
      */
     groupWriter?: PhisAddonGroupWriterDescriptor;
+    /**
+     * The occasions this Add-on may write to a person about. Absent means none, and `notify` then has
+     * nothing it could be asked for.
+     *
+     * Optional for the reason `settings` is: it arrived after the manifest version was in the wild.
+     */
+    occasions?: PhisAddonOccasionDescriptor[];
     /**
      * The Modules this package's other half contributes. Absent means it has no Module half.
      *

package/dist/capabilities.d.ts

@@ -12,7 +12,8 @@
  * at the point where it made the mistake.
  */
 import type { PhisAssetsCapabilityV1 } from "./assets.js";
-import type { PhisAddonEventId } from "./core.js";
+import type { PhisAddonThreadEventId } from "./core.js";
+import type { PhisPaymentChangedEventFacts, PhisPaymentNotificationsCapabilityV1, PhisPaymentsCapabilityV1 } from "./payments.js";
 import type { PhisDataCapabilityV1 } from "./queries.js";
 import type { PhisResourceLinksCapabilityV1 } from "./resource-links.js";
 import type { PhisSupportCapabilityV1 } from "./support.js";
@@ -102,6 +103,12 @@ export type PhisAddonCapabilities = {
     support?: PhisSupportCapabilityV1;
     settings?: PhisSettingsCapabilityV1;
     roles?: PhisRolesCapabilityV1;
+    /** Bound to the declaring consumer and Site when required. */
+    payments?: PhisPaymentsCapabilityV1;
+    /** Supplied only to an original, bound Payment Provider hook request. */
+    paymentNotifications?: PhisPaymentNotificationsCapabilityV1;
+    /** Writing to a person about an occasion this Add-on declared; Core owns the frame and the sending. */
+    notifications?: PhisNotificationsCapabilityV1;
 };
 /**
  * The roles capability: `@phis/server/roles:v1`.
@@ -206,8 +213,67 @@ export type PhisStorageCapabilityV1 = {
  * own would be a package that could plant one.
  */
 export type PhisSecretsCapabilityV1 = {
-    /** The value, or null when the operator has not configured it. */
-    read(name: string): Promise<string | null>;
+    /**
+     * The value, or null when the operator has not configured it.
+     *
+     * `scope` says which of the two an operator can set: `"site"` (the default) is the one set with
+     * `--site` for the Site this call runs on; `"addon"` is the one set without `--site`, shared by every
+     * Site the Add-on runs on -- one credential for one external account, such as a single app
+     * registration. The two are never substituted for each other: a Site secret that is missing is
+     * `null`, not the shared one.
+     */
+    read(name: string, scope?: PhisSecretScope): Promise<string | null>;
+};
+/** Which secret `PhisSecretsCapabilityV1.read` names: the Site's own, or the one shared by all Sites. */
+export type PhisSecretScope = "site" | "addon";
+/**
+ * The notifications capability: `@phis/server/notifications:v1`.
+ *
+ * `notify` names **who** and **what happened**, and nothing about how. The occasion is one this Add-on
+ * declared in its manifest (`occasions`), so its words are sealed by the digest; Core resolves the
+ * address, picks the language, writes the salutation, renders the lines through its own layout and
+ * translation, chooses the sender, and sends -- through the outbox, with retry and a record. There is no
+ * subject, body, `from`, header or attachment on the call, because every one of those is a decision
+ * about how a Site speaks, and a Site speaks with one voice.
+ *
+ * Two recipients. A `user` is a member of this Site, named by id: the address is resolved when the
+ * message is sent, so a corrected address is used and a membership that is gone is not written to.
+ * A `contact` is a person who has no account here and gave this Add-on their address for exactly this
+ * purpose -- a guest who placed an order, somebody who filled in a form. It is the one place an Add-on
+ * hands Core an address, and it is admitted on two conditions Core enforces: the occasion is one the
+ * person's own action asked for (every declared occasion is, this release), and the locale is stated,
+ * because there is no profile to ask.
+ *
+ * `params` are values about the event, never about the person: a `text` parameter is inserted as
+ * written, a `path` parameter is a Site-relative path Core turns into an absolute link on the Site's own
+ * public address. An occasion cannot put an arbitrary URL into a Site's outgoing mail.
+ *
+ * Answers the outbox row's id, or `null` when `dedupeKey` named a message already written -- which is
+ * what makes a repeated run safe. Refused outright: an undeclared occasion, a parameter the occasion
+ * did not declare or lacks, a `user` who is not a member of this Site, and any call from an
+ * unverified hook, which may change nothing.
+ */
+export type PhisNotificationsCapabilityV1 = {
+    notify(input: PhisNotificationInput): Promise<{
+        notificationId: string | null;
+    }>;
+};
+export type PhisNotificationRecipient = {
+    kind: "user";
+    userId: number;
+    locale?: string | null;
+} | {
+    kind: "contact";
+    address: string;
+    locale: string;
+    name?: string | null;
+};
+export type PhisNotificationInput = {
+    occasion: string;
+    recipient: PhisNotificationRecipient;
+    params: Readonly<Record<string, string>>;
+    /** Unique within the Site; a second call with the same key writes nothing and answers `null`. */
+    dedupeKey?: string | null;
 };
 /**
  * What an Add-on may learn about a person.
@@ -357,24 +423,26 @@ export type PhisAddonJobContext = {
  * this Site something, an event is this Site telling an Add-on something, and both run as the Add-on
  * rather than as a person.
  *
- * Delivery is bounded by the same link. An Add-on is told about a thread it is synced with and about no
- * other, because a Site-wide feed of everything anybody writes is the listing `threads:v1` refuses,
- * arriving by push instead of by pull.
+ * Thread delivery is bounded by a synced link. The Payment event reaches only its stored
+ * consuming Add-on. The subject kind and event discriminate those two ownership models; approved
+ * Payment facts are delivered through Core's durable owner-directed outbox.
  */
-export type PhisAddonEventContext = {
+export type PhisAddonEventFacts = {
+    event: PhisAddonThreadEventId;
+    subject: {
+        kind: "thread";
+        threadId: number;
+        messageId: number | null;
+    };
+} | PhisPaymentChangedEventFacts;
+export type PhisAddonEventContext = PhisAddonEventFacts & {
     addonId: string;
-    event: PhisAddonEventId;
     /** This delivery, stable across retries, so a handler can recognise one it already settled. */
     deliveryId: string;
     site: {
         id: number;
         key: string;
     };
-    /** The thread the event happened in, and the message where the event is about one. */
-    subject: {
-        threadId: number;
-        messageId: number | null;
-    };
     capabilities: PhisAddonCapabilities;
     signal: AbortSignal;
 };

package/dist/cms.d.ts

@@ -73,7 +73,9 @@ export declare const PhiCmsVisibilityContext: {
  * The flags a CMS row carries, in the one numbering both sides read them from.
  *
  * Not every flag reaches every kind of row -- `Collapsed` is a Region's answer and `MobileOnly` a
- * renderable's -- but they share one space, because a row is stored as a row whatever it holds.
+ * renderable's -- but they share one space, because a row is stored as a row whatever it holds. The
+ * same numbering serves a config's own `flags`, where a Region's and an Overlay's behaviour live
+ * (`Sticky`, `NoCloseButton`, ...): a yes-or-no answer in a stored record is a bit, never a boolean.
  *
  * `NoIndex` is a Page's, and it is the Site's answer rather than the preset's: a Module states what a
  * Page it ships starts out as, and the Builder's switch is what decides from then on. That is why it
@@ -88,6 +90,26 @@ export declare const PhiCmsFlags: {
     readonly Collapsed: number;
     readonly NoTranslate: number;
     readonly NoIndex: number;
+    /** Stays in view while the page scrolls (Header and Sider families). */
+    readonly Sticky: number;
+    /** A Sider that takes the viewport height below its offset. */
+    readonly FullHeight: number;
+    /** A Sider the viewer can fold to its collapsed width. */
+    readonly Collapsible: number;
+    /** The Header chrome renders no close button. */
+    readonly NoCloseButton: number;
+    /** Escape does not request dismissal. */
+    readonly NoEscapeClose: number;
+    /** A Modal centred in the viewport. */
+    readonly Centered: number;
+    /** A Drawer the viewer can resize. */
+    readonly Resizable: number;
+    /** A Drawer that pushes a nested Drawer aside (`pushDistance` states how far). */
+    readonly Push: number;
+    /** Pointer input reaches the page behind the Overlay. */
+    readonly MaskPassesPointer: number;
+    /** An outside pointer action does not request dismissal. */
+    readonly MaskKeepsOpen: number;
 };
 export declare const PhiCmsRevisionFlags: {
     readonly Draft: number;

package/dist/cms.js

@@ -81,7 +81,9 @@ export const PhiCmsVisibilityContext = {
  * The flags a CMS row carries, in the one numbering both sides read them from.
  *
  * Not every flag reaches every kind of row -- `Collapsed` is a Region's answer and `MobileOnly` a
- * renderable's -- but they share one space, because a row is stored as a row whatever it holds.
+ * renderable's -- but they share one space, because a row is stored as a row whatever it holds. The
+ * same numbering serves a config's own `flags`, where a Region's and an Overlay's behaviour live
+ * (`Sticky`, `NoCloseButton`, ...): a yes-or-no answer in a stored record is a bit, never a boolean.
  *
  * `NoIndex` is a Page's, and it is the Site's answer rather than the preset's: a Module states what a
  * Page it ships starts out as, and the Builder's switch is what decides from then on. That is why it
@@ -96,6 +98,35 @@ export const PhiCmsFlags = {
     Collapsed: 1 << 4,
     NoTranslate: 1 << 5,
     NoIndex: 1 << 6,
+    /*
+     * A Region's behaviour, carried in its config's `flags`: a Region stored on a Page is a config under
+     * the Page's `layoutConfig` and has no row of its own, so the config is the one place both kinds have.
+     */
+    /** Stays in view while the page scrolls (Header and Sider families). */
+    Sticky: 1 << 7,
+    /** A Sider that takes the viewport height below its offset. */
+    FullHeight: 1 << 8,
+    /** A Sider the viewer can fold to its collapsed width. */
+    Collapsible: 1 << 9,
+    /*
+     * An Overlay's behaviour, carried in its config's `flags` the same way. The bits name the departure
+     * from the Overlay's defaults, so an unset flag set is the plain Overlay: a close button, Escape
+     * closes, the mask stops the pointer and closes on a click.
+     */
+    /** The Header chrome renders no close button. */
+    NoCloseButton: 1 << 10,
+    /** Escape does not request dismissal. */
+    NoEscapeClose: 1 << 11,
+    /** A Modal centred in the viewport. */
+    Centered: 1 << 12,
+    /** A Drawer the viewer can resize. */
+    Resizable: 1 << 13,
+    /** A Drawer that pushes a nested Drawer aside (`pushDistance` states how far). */
+    Push: 1 << 14,
+    /** Pointer input reaches the page behind the Overlay. */
+    MaskPassesPointer: 1 << 15,
+    /** An outside pointer action does not request dismissal. */
+    MaskKeepsOpen: 1 << 16,
 };
 export const PhiCmsRevisionFlags = {
     Draft: 1 << 0,

package/dist/controls.d.ts

@@ -26,7 +26,15 @@ export type PhiControlOption<TValue extends string | number = string> = {
      * come, so the order has to make sense without the headings.
      */
     group?: string;
+    /**
+     * A line drawn between this option and the one before or after it, where the Control can draw one --
+     * a Select does, in its menu. It sets an option apart from the rest without a heading to name it: the
+     * Button's "Custom" above the actions it is not one of. A Control that cannot draw it lists the
+     * options as they come.
+     */
+    separator?: PhiControlOptionSeparator;
 };
+export type PhiControlOptionSeparator = "before" | "after";
 export type PhiControlOptionPreview = PhiControlOptionBackgroundPreview | PhiControlOptionFontPreview;
 /**
  * The option's label set in the typeface it names, so a list of fonts shows the fonts.

package/dist/controls.js

@@ -125,6 +125,7 @@ export function readPhiControlOptions(value) {
                 icon: readString(record.icon),
                 preview: readOptionPreview(record.preview),
                 group: readString(record.group),
+                separator: record.separator === "before" || record.separator === "after" ? record.separator : undefined,
             };
         })
             .filter((item) => item != null);

package/dist/core.d.ts

@@ -1,3 +1,4 @@
+import type { PhisPaymentChangedEventFacts } from "./payments.js";
 /**
  * What Core offers, named once so both sides can spell it the same way.
  *
@@ -45,6 +46,10 @@ export declare const PHIS_CORE_CAPABILITIES: {
     readonly settings: "@phis/server/settings:v1";
     /** Whether the acting user holds one of this Add-on's own declared roles. */
     readonly roles: "@phis/server/roles:v1";
+    readonly payments: "@phis/server/payments:v1";
+    readonly paymentNotifications: "@phis/server/payment-notifications:v1";
+    /** Writing to a person about an occasion the Add-on declared, with Core owning frame and transport. */
+    readonly notifications: "@phis/server/notifications:v1";
 };
 export type PhisCoreCapabilityId = (typeof PHIS_CORE_CAPABILITIES)[keyof typeof PHIS_CORE_CAPABILITIES];
 /**
@@ -67,8 +72,11 @@ export declare const PHIS_ADDON_EVENTS: {
     readonly threadStatusChanged: "thread.status.changed";
     /** The link itself is gone; what follows from that is the Add-on's own business. */
     readonly threadLinkRemoved: "thread.link.removed";
+    readonly paymentChanged: "payment.changed";
 };
-export type PhisAddonEventId = (typeof PHIS_ADDON_EVENTS)[keyof typeof PHIS_ADDON_EVENTS];
+export type PhisAddonThreadEventId = Exclude<(typeof PHIS_ADDON_EVENTS)[keyof typeof PHIS_ADDON_EVENTS], "payment.changed">;
+/** Delivered v1 event vocabulary, discriminated by its owned subject. */
+export type PhisAddonEventId = PhisAddonThreadEventId | PhisPaymentChangedEventFacts["event"];
 /**
  * The Core-owned service kinds an Add-on may implement.
  *
@@ -78,6 +86,7 @@ export type PhisAddonEventId = (typeof PHIS_ADDON_EVENTS)[keyof typeof PHIS_ADDO
  */
 export declare const PHIS_SERVICE_KINDS: {
     readonly mediaStorage: "@phis/server/service/media-storage";
+    readonly payments: "@phis/server/service/payments";
     readonly directory: "@phis/server/service/directory";
     /**
      * Turning text in one language into text in another.
@@ -88,6 +97,15 @@ export declare const PHIS_SERVICE_KINDS: {
      * operator selects which one an installation uses.
      */
     readonly translation: "@phis/server/service/translation";
+    /**
+     * Handing a Support ticket's work to a system outside the Site -- an issue tracker, a ticket desk.
+     *
+     * A kind because Core owns the question: which ticket, which task, what may leave and what comes back.
+     * What the implementation talks to is its own business, and several may be installed at once; a
+     * Supporter chooses one per forward. The interface is `PhisSupportForwardingAdapterV1` in
+     * `@phis/contracts/support`.
+     */
+    readonly supportForwarding: "@phis/server/service/support-forwarding";
 };
 export type PhisServiceKind = (typeof PHIS_SERVICE_KINDS)[keyof typeof PHIS_SERVICE_KINDS];
 /**

package/dist/core.js

@@ -45,6 +45,10 @@ export const PHIS_CORE_CAPABILITIES = {
     settings: "@phis/server/settings:v1",
     /** Whether the acting user holds one of this Add-on's own declared roles. */
     roles: "@phis/server/roles:v1",
+    payments: "@phis/server/payments:v1",
+    paymentNotifications: "@phis/server/payment-notifications:v1",
+    /** Writing to a person about an occasion the Add-on declared, with Core owning frame and transport. */
+    notifications: "@phis/server/notifications:v1",
 };
 /**
  * What Core tells an Add-on about after the fact.
@@ -66,6 +70,7 @@ export const PHIS_ADDON_EVENTS = {
     threadStatusChanged: "thread.status.changed",
     /** The link itself is gone; what follows from that is the Add-on's own business. */
     threadLinkRemoved: "thread.link.removed",
+    paymentChanged: "payment.changed",
 };
 /**
  * The Core-owned service kinds an Add-on may implement.
@@ -76,6 +81,7 @@ export const PHIS_ADDON_EVENTS = {
  */
 export const PHIS_SERVICE_KINDS = {
     mediaStorage: "@phis/server/service/media-storage",
+    payments: "@phis/server/service/payments",
     directory: "@phis/server/service/directory",
     /**
      * Turning text in one language into text in another.
@@ -86,6 +92,15 @@ export const PHIS_SERVICE_KINDS = {
      * operator selects which one an installation uses.
      */
     translation: "@phis/server/service/translation",
+    /**
+     * Handing a Support ticket's work to a system outside the Site -- an issue tracker, a ticket desk.
+     *
+     * A kind because Core owns the question: which ticket, which task, what may leave and what comes back.
+     * What the implementation talks to is its own business, and several may be installed at once; a
+     * Supporter chooses one per forward. The interface is `PhisSupportForwardingAdapterV1` in
+     * `@phis/contracts/support`.
+     */
+    supportForwarding: "@phis/server/service/support-forwarding",
 };
 /**
  * The digest of the interface each service kind currently has.
@@ -107,11 +122,15 @@ export const PHIS_SERVICE_KINDS = {
  */
 export const PHIS_SERVICE_INTERFACE_VERSIONS = {
     [PHIS_SERVICE_KINDS.mediaStorage]: 1,
+    [PHIS_SERVICE_KINDS.payments]: 1,
     [PHIS_SERVICE_KINDS.directory]: 1,
     [PHIS_SERVICE_KINDS.translation]: 1,
+    [PHIS_SERVICE_KINDS.supportForwarding]: 1,
 };
 export const PHIS_SERVICE_INTERFACE_DIGESTS = {
+    [PHIS_SERVICE_KINDS.payments]: "6b106818d5edbfeddd484e9f571509695a1a8dbb5b82435338a094216410fcf7",
     [PHIS_SERVICE_KINDS.mediaStorage]: "45a871522511f7d77841ca8dd0113b423b3cfd4cb921f143cd1d3d116cab6952",
     [PHIS_SERVICE_KINDS.directory]: "2cac7397c7beb1b8e71fc67f5cae3be89182dddf096895570a15deafa1adbfc9",
     [PHIS_SERVICE_KINDS.translation]: "9bae2e7b92ded5cdde9321939a3bb8cd589f6e1ef8bca7bc5f65608313b3207d",
+    [PHIS_SERVICE_KINDS.supportForwarding]: "e9d01711a5ebdfa37ea4c6828952c87935b6e755b98ab8e69cc397933dfbed6f",
 };