feat: add new partyIdType MERCHANT_PAYINTOID

seeds/partyIdType.js

@@ -52,6 +52,10 @@ const partyIdTypes = [
     name: 'IBAN',
     description: 'A bank account number or FSP account ID is used as reference to a participant. The IBAN identifier can consist of up to 34 alphanumeric characters and should be entered without whitespace.'
   },
+  {
+    name: 'MERCHANT_PAYINTOID',
+    description: 'An alias value is used to reference to a checkout counter of a particular merchant. The MERCHANT_PAYINTOID identifier value can be a sequence of code.'
+  },
   {
     name: 'ALIAS',
     description: 'An alias is used as reference to a participant. The alias should be created in the FSP as an alternative reference to an account owner. Another example of an alias is a username in the FSP system. The ALIAS identifier can be in any format. It is also possible to use the PartySubIdOrType element for identifying an account under an Alias defined by the PartyIdentifier.'

src/interface/admin-swagger.yaml

@@ -534,7 +534,9 @@ components:
         can greatly differ depending on country and FSP. - IBAN A bank account number
         or FSP account ID is used as reference to a participant. The IBAN identifier
         can consist of up to 34 alphanumeric characters and should be entered without
-        whitespace. - ALIAS An alias is used as reference to a participant. The alias
+        whitespace. - MERCHANT_PAYINTOID An alias value is used to reference to a checkout counter 
+        of a particular merchant. MERCHANT_PAYINTOID value can be a sequence of code. 
+        - ALIAS An alias is used as reference to a participant. The alias
         should be created in the FSP as an alternative reference to an account owner.
         Another example of an alias is a username in the FSP system. The ALIAS identifier
         can be in any format. It is also possible to use the PartySubIdOrType element
@@ -547,6 +549,7 @@ components:
         - DEVICE
         - ACCOUNT_ID
         - IBAN
+        - MERCHANT_PAYINTOID
         - ALIAS
     Status:
       title: Status

src/interface/admin_swagger.json

@@ -707,9 +707,10 @@
         "DEVICE",
         "ACCOUNT_ID",
         "IBAN",
+        "MERCHANT_PAYINTOID",
         "ALIAS"
       ],
-      "description": "Below are the allowed values for the enumeration - MSISDN An MSISDN (Mobile Station International Subscriber Directory Number, that is, the phone number) is used as reference to a participant. The MSISDN identifier should be in international format according to the ITU-T E.164 standard. Optionally, the MSISDN may be prefixed by a single plus sign, indicating the international prefix. - EMAIL An email is used as reference to a participant. The format of the email should be according to the informational RFC 3696. - PERSONAL_ID A personal identifier is used as reference to a participant. Examples of personal identification are passport number, birth certificate number, and national registration number. The identifier number is added in the PartyIdentifier element. The personal identifier type is added in the PartySubIdOrType element. - BUSINESS A specific Business (for example, an organization or a company) is used as reference to a participant. The BUSINESS identifier can be in any format. To make a transaction connected to a specific username or bill number in a Business, the PartySubIdOrType element should be used. - DEVICE A specific device (for example, a POS or ATM) ID connected to a specific business or organization is used as reference to a Party. For referencing a specific device under a specific business or organization, use the PartySubIdOrType element. - ACCOUNT_ID A bank account number or FSP account ID should be used as reference to a participant. The ACCOUNT_ID identifier can be in any format, as formats can greatly differ depending on country and FSP. - IBAN A bank account number or FSP account ID is used as reference to a participant. The IBAN identifier can consist of up to 34 alphanumeric characters and should be entered without whitespace. - ALIAS An alias is used as reference to a participant. The alias should be created in the FSP as an alternative reference to an account owner. Another example of an alias is a username in the FSP system. The ALIAS identifier can be in any format. It is also possible to use the PartySubIdOrType element for identifying an account under an Alias defined by the PartyIdentifier."
+      "description": "Below are the allowed values for the enumeration - MSISDN An MSISDN (Mobile Station International Subscriber Directory Number, that is, the phone number) is used as reference to a participant. The MSISDN identifier should be in international format according to the ITU-T E.164 standard. Optionally, the MSISDN may be prefixed by a single plus sign, indicating the international prefix. - EMAIL An email is used as reference to a participant. The format of the email should be according to the informational RFC 3696. - PERSONAL_ID A personal identifier is used as reference to a participant. Examples of personal identification are passport number, birth certificate number, and national registration number. The identifier number is added in the PartyIdentifier element. The personal identifier type is added in the PartySubIdOrType element. - BUSINESS A specific Business (for example, an organization or a company) is used as reference to a participant. The BUSINESS identifier can be in any format. To make a transaction connected to a specific username or bill number in a Business, the PartySubIdOrType element should be used. - DEVICE A specific device (for example, a POS or ATM) ID connected to a specific business or organization is used as reference to a Party. For referencing a specific device under a specific business or organization, use the PartySubIdOrType element. - ACCOUNT_ID A bank account number or FSP account ID should be used as reference to a participant. The ACCOUNT_ID identifier can be in any format, as formats can greatly differ depending on country and FSP. - IBAN A bank account number or FSP account ID is used as reference to a participant. The IBAN identifier can consist of up to 34 alphanumeric characters and should be entered without whitespace. - MERCHANT_PAYINTOID An alias value is used to reference to a checkout counter of a particular merchant. MERCHANT_PAYINTOID value can be a sequence of code. - ALIAS An alias is used as reference to a participant. The alias should be created in the FSP as an alternative reference to an account owner. Another example of an alias is a username in the FSP system. The ALIAS identifier can be in any format. It is also possible to use the PartySubIdOrType element for identifying an account under an Alias defined by the PartyIdentifier."
     },
     "Status": {
       "title": "Status",

src/interface/api-swagger.yaml

@@ -1170,6 +1170,7 @@ components:
         - DEVICE
         - ACCOUNT_ID
         - IBAN
+        - MERCHANT_PAYINTOID
         - ALIAS
     ErrorInformation:
       title: ErrorInformation
@@ -1724,6 +1725,7 @@ components:
           - DEVICE
           - ACCOUNT_ID
           - IBAN
+          - MERCHANT_PAYINTOID
           - ALIAS
     SubId:
       name: SubId

src/interface/api_swagger.json

@@ -2392,9 +2392,10 @@
         "DEVICE",
         "ACCOUNT_ID",
         "IBAN",
+        "MERCHANT_PAYINTOID",
         "ALIAS"
       ],
-      "description": "Below are the allowed values for the enumeration - MSISDN An MSISDN (Mobile Station International Subscriber Directory Number, that is, the phone number) is used as reference to a participant. The MSISDN identifier should be in international format according to the ITU-T E.164 standard. Optionally, the MSISDN may be prefixed by a single plus sign, indicating the international prefix. - EMAIL An email is used as reference to a participant. The format of the email should be according to the informational RFC 3696. - PERSONAL_ID A personal identifier is used as reference to a participant. Examples of personal identification are passport number, birth certificate number, and national registration number. The identifier number is added in the PartyIdentifier element. The personal identifier type is added in the PartySubIdOrType element. - BUSINESS A specific Business (for example, an organization or a company) is used as reference to a participant. The BUSINESS identifier can be in any format. To make a transaction connected to a specific username or bill number in a Business, the PartySubIdOrType element should be used. - DEVICE A specific device (for example, a POS or ATM) ID connected to a specific business or organization is used as reference to a Party. For referencing a specific device under a specific business or organization, use the PartySubIdOrType element. - ACCOUNT_ID A bank account number or FSP account ID should be used as reference to a participant. The ACCOUNT_ID identifier can be in any format, as formats can greatly differ depending on country and FSP. - IBAN A bank account number or FSP account ID is used as reference to a participant. The IBAN identifier can consist of up to 34 alphanumeric characters and should be entered without whitespace. - ALIAS An alias is used as reference to a participant. The alias should be created in the FSP as an alternative reference to an account owner. Another example of an alias is a username in the FSP system. The ALIAS identifier can be in any format. It is also possible to use the PartySubIdOrType element for identifying an account under an Alias defined by the PartyIdentifier."
+      "description": "Below are the allowed values for the enumeration - MSISDN An MSISDN (Mobile Station International Subscriber Directory Number, that is, the phone number) is used as reference to a participant. The MSISDN identifier should be in international format according to the ITU-T E.164 standard. Optionally, the MSISDN may be prefixed by a single plus sign, indicating the international prefix. - EMAIL An email is used as reference to a participant. The format of the email should be according to the informational RFC 3696. - PERSONAL_ID A personal identifier is used as reference to a participant. Examples of personal identification are passport number, birth certificate number, and national registration number. The identifier number is added in the PartyIdentifier element. The personal identifier type is added in the PartySubIdOrType element. - BUSINESS A specific Business (for example, an organization or a company) is used as reference to a participant. The BUSINESS identifier can be in any format. To make a transaction connected to a specific username or bill number in a Business, the PartySubIdOrType element should be used. - DEVICE A specific device (for example, a POS or ATM) ID connected to a specific business or organization is used as reference to a Party. For referencing a specific device under a specific business or organization, use the PartySubIdOrType element. - ACCOUNT_ID A bank account number or FSP account ID should be used as reference to a participant. The ACCOUNT_ID identifier can be in any format, as formats can greatly differ depending on country and FSP. - IBAN A bank account number or FSP account ID is used as reference to a participant. The IBAN identifier can consist of up to 34 alphanumeric characters and should be entered without whitespace. - MERCHANT_PAYINTOID An alias value is used to reference to a checkout counter of a particular merchant. MERCHANT_PAYINTOID value can be a sequence of code. - ALIAS An alias is used as reference to a participant. The alias should be created in the FSP as an alternative reference to an account owner. Another example of an alias is a username in the FSP system. The ALIAS identifier can be in any format. It is also possible to use the PartySubIdOrType element for identifying an account under an Alias defined by the PartyIdentifier."
     },
     "ErrorInformation": {
       "title": "ErrorInformation",
@@ -3033,6 +3034,7 @@
         "DEVICE",
         "ACCOUNT_ID",
         "IBAN",
+        "MERCHANT_PAYINTOID",
         "ALIAS"
       ]
     },

src/interface/thirdparty/admin-swagger.yaml

@@ -534,7 +534,9 @@ components:
         can greatly differ depending on country and FSP. - IBAN A bank account number
         or FSP account ID is used as reference to a participant. The IBAN identifier
         can consist of up to 34 alphanumeric characters and should be entered without
-        whitespace. - ALIAS An alias is used as reference to a participant. The alias
+        whitespace. - MERCHANT_PAYINTOID An alias value is used to reference to a checkout counter 
+        of a particular merchant. MERCHANT_PAYINTOID value can be a sequence of code. 
+        - ALIAS An alias is used as reference to a participant. The alias
         should be created in the FSP as an alternative reference to an account owner.
         Another example of an alias is a username in the FSP system. The ALIAS identifier
         can be in any format. It is also possible to use the PartySubIdOrType element
@@ -549,6 +551,7 @@ components:
         - DEVICE
         - ACCOUNT_ID
         - IBAN
+        - MERCHANT_PAYINTOID
         - ALIAS
         - CONSENT
         - THIRD_PARTY_LINK

src/interface/thirdparty/admin_swagger.json

@@ -707,11 +707,12 @@
         "DEVICE",
         "ACCOUNT_ID",
         "IBAN",
+        "MERCHANT_PAYINTOID",
         "ALIAS",
         "CONSENT",
         "THIRD_PARTY_LINK"
       ],
-      "description": "Below are the allowed values for the enumeration - MSISDN An MSISDN (Mobile Station International Subscriber Directory Number, that is, the phone number) is used as reference to a participant. The MSISDN identifier should be in international format according to the ITU-T E.164 standard. Optionally, the MSISDN may be prefixed by a single plus sign, indicating the international prefix. - EMAIL An email is used as reference to a participant. The format of the email should be according to the informational RFC 3696. - PERSONAL_ID A personal identifier is used as reference to a participant. Examples of personal identification are passport number, birth certificate number, and national registration number. The identifier number is added in the PartyIdentifier element. The personal identifier type is added in the PartySubIdOrType element. - BUSINESS A specific Business (for example, an organization or a company) is used as reference to a participant. The BUSINESS identifier can be in any format. To make a transaction connected to a specific username or bill number in a Business, the PartySubIdOrType element should be used. - DEVICE A specific device (for example, a POS or ATM) ID connected to a specific business or organization is used as reference to a Party. For referencing a specific device under a specific business or organization, use the PartySubIdOrType element. - ACCOUNT_ID A bank account number or FSP account ID should be used as reference to a participant. The ACCOUNT_ID identifier can be in any format, as formats can greatly differ depending on country and FSP. - IBAN A bank account number or FSP account ID is used as reference to a participant. The IBAN identifier can consist of up to 34 alphanumeric characters and should be entered without whitespace. - ALIAS An alias is used as reference to a participant. The alias should be created in the FSP as an alternative reference to an account owner. Another example of an alias is a username in the FSP system. The ALIAS identifier can be in any format. It is also possible to use the PartySubIdOrType element for identifying an account under an Alias defined by the PartyIdentifier."
+      "description": "Below are the allowed values for the enumeration - MSISDN An MSISDN (Mobile Station International Subscriber Directory Number, that is, the phone number) is used as reference to a participant. The MSISDN identifier should be in international format according to the ITU-T E.164 standard. Optionally, the MSISDN may be prefixed by a single plus sign, indicating the international prefix. - EMAIL An email is used as reference to a participant. The format of the email should be according to the informational RFC 3696. - PERSONAL_ID A personal identifier is used as reference to a participant. Examples of personal identification are passport number, birth certificate number, and national registration number. The identifier number is added in the PartyIdentifier element. The personal identifier type is added in the PartySubIdOrType element. - BUSINESS A specific Business (for example, an organization or a company) is used as reference to a participant. The BUSINESS identifier can be in any format. To make a transaction connected to a specific username or bill number in a Business, the PartySubIdOrType element should be used. - DEVICE A specific device (for example, a POS or ATM) ID connected to a specific business or organization is used as reference to a Party. For referencing a specific device under a specific business or organization, use the PartySubIdOrType element. - ACCOUNT_ID A bank account number or FSP account ID should be used as reference to a participant. The ACCOUNT_ID identifier can be in any format, as formats can greatly differ depending on country and FSP. - IBAN A bank account number or FSP account ID is used as reference to a participant. The IBAN identifier can consist of up to 34 alphanumeric characters and should be entered without whitespace. - MERCHANT_PAYINTOID An alias value is used to reference to a checkout counter of a particular merchant. MERCHANT_PAYINTOID value can be a sequence of code. - ALIAS An alias is used as reference to a participant. The alias should be created in the FSP as an alternative reference to an account owner. Another example of an alias is a username in the FSP system. The ALIAS identifier can be in any format. It is also possible to use the PartySubIdOrType element for identifying an account under an Alias defined by the PartyIdentifier."
     },
     "Status": {
       "title": "Status",

src/interface/thirdparty/api-swagger.yaml

@@ -1172,6 +1172,7 @@ components:
         - DEVICE
         - ACCOUNT_ID
         - IBAN
+        - MERCHANT_PAYINTOID
         - ALIAS
         - CONSENT
         - THIRD_PARTY_LINK
@@ -1728,6 +1729,7 @@ components:
           - DEVICE
           - ACCOUNT_ID
           - IBAN
+          - MERCHANT_PAYINTOID
           - ALIAS
           - CONSENT
           - THIRD_PARTY_LINK