{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "AddUpdateItems",
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "description": "The action to be performed on the Digital Payment Application (DPA). The selected action will be applied to all DPAs provided in the items list.\n\nADD - Add DPA\n\nUPDATE - Update DPA\n\nDELETE - Delete DPA\n\nNote:\n* A limited number of DPA fields can be changed using the __UPDATE__ action. These are `dpaPresentationName`, `programName`, `dpaLogoUri`, `debitTokenRequested`, `merchantCategoryCode`, and `threeDSDefaultData`. Please refer to the example for a minimal use case.\n* All DPA data from the original request (including non-updatable fields) will also need to be provided unchanged in the __PUT__ request for the operation to process successfully.\n"
    },
    "customerId": {
      "type": "string",
      "description": "Conditional: The Customer Identifier (CID) must be passed when the Integrator is acting On-Behalf-Of (OBO) a client, registering through the Mastercard Connect (MC Connect) portal, or participating in the Secure Card on File (SCOF) program.\n\nThis field should be populated with the CID of the Integrator's client (e.g., a Payment Service Provider (PSP) would pass the CID of the client they are integrating, i.e. DASP model).\n"
    },
    "programType": {
      "type": "string",
      "description": "The Mastercard program that the Integrator would like to add their client(s) to. The Integrator must be enrolled in the program prior to enrolling their client(s). Integrators may view their active programs in the Mastercard Connect (MC Connect) portal.\n\n`SECURE_COF_MERCHANT` -  Integrating Merchant managing network tokenization. Tokens generated are unique for each merchant.\n\n`SECURE_COF_MERCHANT_OBO` - Integrating Payment Service Provider (PSP) managing network tokenization for their Merchant(s). Tokens generated are unique for each merchant.\n\n`SECURE_COF_COMMERCE_PLATFORM` - Integrating Commerce Platform managing network tokenization. Tokens are generated unique for each Commerce Platform (tokens will be shared among their marketplace).\n\n`SECURE_COF_COMMERCE_PLATFORM_OBO` - Integrating PSPs managing network tokenization for their Commerce Platform(s). Tokens are generated unique for each Commerce Platform (tokens will be shared among their marketplace).\n\n`SECURE_COF_MERCHANT_OBO_SHARED` - Integrating PSPs managing network tokenization for their sub-Merchants. Tokens generated are unique for each Merchant Group.\n\n`SRC` - Integrating Merchants and PSPs participating in or offering the Click to Pay (C2P) program.\n\n`GUEST_CHECKOUT_TOKENIZATION` - A checkout solution that uses an alternative identifier to Account PANs, generated by the issuing network for guest checkout tokenization.\n\nNote: Other programTypes (e.g., AUTOFILL, SQR_DEVICE etc.) may be available to select regions. Please contact your Mastercard representative for more details.\n"
    },
    "trid": {
      "type": "string",
      "description": "The Token Requestor Identifier (TRID) should be passed by MDES for Merchants (M4M) Integrators who would like to onboard their M4M TRIDs to be used on Secure Card on File (SCOF)."
    },
    "serviceId": {
      "type": "string",
      "description": "A unique identifier assigned by Mastercard for which tokens are created uniquely for the entity onboarded."
    },
    "category": {
      "type": "string",
      "description": "Assign a category to the sub-merchant group identified in the request. For example, sub-merchants can be grouped by common attributes such as merchant category code (MCC), volume of transactions, or geography. Required for the SECURE_COF_MERCHANT_OBO_SHARED program type. Examples: \"discount stores\" and \"bakeries\""
    },
    "programName": {
      "type": "string",
      "description": "The Cardholder facing name of the Merchant.\n\nConditional: Must be supplied when adding Merchants to all Secure Card On File (SECURE_COF) programs.\n"
    },
    "dpas": {
      "type": "array",
      "description": "Dpas\n\nObject for Integrator to provide a list of Digital Processing Application (DPA) objects. Each DPA object is used to create a corresponding DPA. A minimum of 1 DPA object (to a maximum of 80 DPA objects) must be provided in the request.\n"
    }
  }
}