@mojaloop/api-snippets 18.3.1 → 18.4.0

package/thirdparty/v2_0/openapi3/components/schemas/FIDOPublicKeyCredentialAssertion.yaml

@@ -0,0 +1,71 @@
+title: FIDOPublicKeyCredentialAssertion
+type: object
+description: |
+  A data model representing a FIDO Assertion result.
+  Derived from PublicKeyCredential Interface in WebAuthN.
+
+  The PublicKeyCredential interface represents the below fields with a Type of
+  Javascript ArrayBuffer.
+  For this API, we represent ArrayBuffers as base64 encoded utf-8 strings.
+
+  https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v2.0.0/api/thirdparty/data-models.md#32128-fidopublickeycredentialassertion
+properties:
+  id:
+    type: string
+    description: |
+      credential id: identifier of pair of keys, base64 encoded
+      https://w3c.github.io/webauthn/#ref-for-dom-credential-id
+    minLength: 20
+    maxLength: 118
+  rawId:
+    type: string
+    description: |
+      raw credential id: identifier of pair of keys, base64 encoded.
+    minLength: 20
+    maxLength: 118
+  response:
+    type: object
+    description: |
+      AuthenticatorAssertionResponse
+    properties:
+      authenticatorData:
+        type: string
+        description: |
+          Authenticator data object.
+        minLength: 49
+        maxLength: 256
+      clientDataJSON:
+        type: string
+        description: |
+          JSON string with client data.
+        minLength: 121
+        maxLength: 512
+      signature:
+        type: string
+        description: |
+          The signature generated by the private key associated with this credential.
+        minLength: 59
+        maxLength: 256
+      userHandle:
+        type: string
+        description: |
+          This field is optionally provided by the authenticator, and
+          represents the user.id that was supplied during registration.
+        minLength: 1
+        maxLength: 88
+    required:
+      - authenticatorData
+      - clientDataJSON
+      - signature
+    additionalProperties: false
+  type:
+    type: string
+    description: response type, we need only the type of public-key
+    enum:
+      - 'public-key'
+required:
+  - id
+  - rawId
+  - response
+  - type
+additionalProperties: false

package/thirdparty/v2_0/openapi3/components/schemas/FIDOPublicKeyCredentialAttestation.yaml

@@ -0,0 +1,54 @@
+title: FIDOPublicKeyCredentialAttestation
+type: object
+description: |
+  A data model representing a FIDO Attestation result. Derived from 
+  [`PublicKeyCredential` Interface](https://w3c.github.io/webauthn/#iface-pkcredential).
+
+  The `PublicKeyCredential` interface represents the below fields with
+  a Type of Javascript [ArrayBuffer](https://heycam.github.io/webidl/#idl-ArrayBuffer).
+  For this API, we represent ArrayBuffers as base64 encoded utf-8 strings.
+properties:
+  id:
+    type: string
+    description: |
+      credential id: identifier of pair of keys, base64 encoded
+      https://w3c.github.io/webauthn/#ref-for-dom-credential-id
+    minLength: 20
+    maxLength: 118
+  rawId:
+    type: string
+    description: |
+      raw credential id: identifier of pair of keys, base64 encoded
+    minLength: 20
+    maxLength: 118
+  response:
+    type: object
+    description: |
+      AuthenticatorAttestationResponse
+    properties:
+      clientDataJSON:
+        type: string
+        description: |
+          JSON string with client data
+        minLength: 121
+        maxLength: 512
+      attestationObject:
+        type: string
+        description: |
+          CBOR.encoded attestation object
+        minLength: 306
+        maxLength: 2048
+    required:
+      - clientDataJSON
+      - attestationObject
+    additionalProperties: false
+  type:
+    type: string
+    description: response type, we need only the type of public-key
+    enum:
+      - 'public-key'
+required:
+  - id
+  - response
+  - type
+additionalProperties: false

package/thirdparty/v2_0/openapi3/components/schemas/FirstName.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/FirstName.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/FspId.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/FspId.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/GenericCredential.yaml

@@ -0,0 +1,13 @@
+title: GenericCredential
+type: object
+description: |
+  A publicKey + signature of a challenge for a generic public/private keypair.
+properties:
+  publicKey:
+    $ref: ./BinaryString.yaml
+  signature:
+    $ref: ./BinaryString.yaml
+required:
+  - publicKey
+  - signature
+additionalProperties: false

package/thirdparty/v2_0/openapi3/components/schemas/GeoCode.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/GeoCode.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/IlpCondition.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/IlpCondition.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/IlpFulfilment.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/IlpFulfilment.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/IlpPacket.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/IlpPacket.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/Integer.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/Integer.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/LastName.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/LastName.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/Latitude.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/Latitude.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/Longitude.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/Longitude.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/MerchantClassificationCode.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/MerchantClassificationCode.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/MiddleName.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/MiddleName.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/Money.yaml

@@ -0,0 +1 @@
+$ref: ../../../../../fspiop/v2_0/openapi3/components/schemas/Money.yaml

package/thirdparty/v2_0/openapi3/components/schemas/Name.yaml

@@ -0,0 +1,2 @@
+$ref: ../../../../../fspiop/v2_0/openapi3/components/schemas/Name.yaml
+     

package/thirdparty/v2_0/openapi3/components/schemas/Note.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/Note.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/ParticipantsIDPutResponse.yaml

@@ -0,0 +1,17 @@
+title: ParticipantsIDPutResponse
+type: object
+description: 'The object sent in the PUT /participants/{ID} callback.'
+properties:
+  partyList:
+    type: array
+    items:
+      $ref: ./PartyResult.yaml
+    minItems: 1
+    maxItems: 10000
+    description: >-
+      List of PartyResult elements that were either created or failed to be
+      created.
+  currency:
+    $ref: ./Currency.yaml
+required:
+  - partyList

package/thirdparty/v2_0/openapi3/components/schemas/ParticipantsPostRequest.yaml

@@ -0,0 +1,20 @@
+title: ParticipantsPostRequest
+type: object
+description: The object sent in the POST /participants request.
+properties:
+  requestId:
+    $ref: ./CorrelationId.yaml
+  partyList:
+    type: array
+    items:
+      $ref: ./PartyIdInfo.yaml
+    minItems: 1
+    maxItems: 10000
+    description: |
+      List of PartyIdInfo elements that the client would like to update
+      or create FSP information about.
+  currency:
+    $ref: ./Currency.yaml
+required:
+  - requestId
+  - partyList

package/thirdparty/v2_0/openapi3/components/schemas/ParticipantsTypeIDPutResponse.yaml

@@ -0,0 +1,8 @@
+title: ParticipantsTypeIDPutResponse
+type: object
+description: >-
+  The object sent in the PUT /participants/{Type}/{ID}/{SubId} and
+  /participants/{Type}/{ID} callbacks.
+properties:
+  fspId:
+    $ref: ./FspId.yaml

package/thirdparty/v2_0/openapi3/components/schemas/ParticipantsTypeIDSubIDPostRequest.yaml

@@ -0,0 +1,15 @@
+title: ParticipantsTypeIDSubIDPostRequest
+type: object
+description: >-
+  The object sent in the POST /participants/{Type}/{ID}/{SubId} and
+  /participants/{Type}/{ID} requests. An additional optional ExtensionList
+  element has been added as part of v1.1 changes.
+properties:
+  fspId:
+    $ref: ./FspId.yaml
+  currency:
+    $ref: ./Currency.yaml
+  extensionList:
+    $ref: ./ExtensionList.yaml
+required:
+  - fspId

package/thirdparty/v2_0/openapi3/components/schemas/PartiesTypeIDPutResponse.yaml

@@ -0,0 +1,13 @@
+title: PartiesTypeIDPutResponse
+type: object
+description: |
+  The object sent in the PUT /parties/{Type}/{ID} callback.
+
+  This is a variant based on FSPIOP `PartiesTypeIDPutResponse` specification.
+  Main difference being that it returns a `Party` with the newly added
+  `accounts` property.
+properties:
+  party:
+    $ref: ./Party.yaml
+required:
+  - party

package/thirdparty/v2_0/openapi3/components/schemas/Party.yaml

@@ -0,0 +1,15 @@
+title: Party
+type: object
+description: Data model for the complex type Party.
+properties:
+  partyIdInfo:
+    $ref: ./PartyIdInfo.yaml
+  merchantClassificationCode:
+    $ref: ./MerchantClassificationCode.yaml
+  name:
+    $ref: ./PartyName.yaml
+  personalInfo:
+    $ref: ./PartyPersonalInfo.yaml
+required:
+  - partyIdInfo
+  

package/thirdparty/v2_0/openapi3/components/schemas/PartyComplexName.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v1_1/openapi3/components/schemas/PartyComplexName.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/PartyIdInfo.yaml

@@ -0,0 +1,17 @@
+title: PartyIdInfo
+type: object
+description: Data model for the complex type PartyIdInfo.
+properties:
+  partyIdType:
+    $ref: ./PartyIdType.yaml
+  partyIdentifier:
+    $ref: ./PartyIdentifier.yaml
+  partySubIdOrType:
+    $ref: ./PartySubIdOrType.yaml
+  fspId:
+    $ref: ./FspId.yaml
+  extensionList:
+    $ref: ./ExtensionList.yaml
+required:
+  - partyIdType
+  - partyIdentifier

package/thirdparty/v2_0/openapi3/components/schemas/PartyIdInfoTPLink.yaml

@@ -0,0 +1,17 @@
+title: PartyIdInfo
+type: object
+description: Data model for the complex type PartyIdInfo.
+properties:
+  partyIdType:
+    $ref: ./PartyIdTypeTPLink.yaml
+  partyIdentifier:
+    $ref: ./PartyIdentifier.yaml
+  partySubIdOrType:
+    $ref: ./PartySubIdOrType.yaml
+  fspId:
+    $ref: ./FspId.yaml
+  extensionList:
+    $ref: ./ExtensionList.yaml
+required:
+  - partyIdType
+  - partyIdentifier

package/thirdparty/v2_0/openapi3/components/schemas/PartyIdType.yaml

@@ -0,0 +1,58 @@
+title: PartyIdType
+type: string
+enum:
+  - MSISDN
+  - EMAIL
+  - PERSONAL_ID
+  - BUSINESS
+  - DEVICE
+  - ACCOUNT_ID
+  - IBAN
+  - 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](https://www.itu.int/rec/T-REC-E.164/en).
+  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](https://tools.ietf.org/html/rfc3696).
+  - 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.
+  - CONSENT - A Consent represents an agreement between a PISP, a Customer and
+  a DFSP which allows the PISP permission to perform actions on behalf of the 
+  customer. A Consent has an authoritative source: either the DFSP who issued 
+  the Consent, or an Auth Service which administers the Consent.
+  - THIRD_PARTY_LINK - A Third Party Link represents an agreement between a PISP,
+  a DFSP, and a specific Customer's account at the DFSP. The content of the link 
+  is created by the DFSP at the time when it gives permission to the PISP for 
+  specific access to a given account.
+example: PERSONAL_ID

package/thirdparty/v2_0/openapi3/components/schemas/PartyIdTypeTPLink.yaml

@@ -0,0 +1,7 @@
+title: PartyIdTypeTPLink
+type: string
+enum:
+  - THIRD_PARTY_LINK
+description: |
+  - THIRD_PARTY_LINK - is the DFSP's internal reference which allows DFSP to find out the corresponding consent
+example: PERSONAL_ID

package/thirdparty/v2_0/openapi3/components/schemas/PartyIdentifier.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/PartyIdentifier.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/PartyName.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/PartyName.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/PartyPersonalInfo.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/PartyPersonalInfo.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/PartyResult.yaml

@@ -0,0 +1,10 @@
+title: PartyResult
+type: object
+description: Data model for the complex type PartyResult.
+properties:
+  partyId:
+    $ref: ./PartyIdInfo.yaml
+  errorInformation:
+    $ref: ./ErrorInformation.yaml
+required:
+  - partyId

package/thirdparty/v2_0/openapi3/components/schemas/PartySubIdOrType.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/PartySubIdOrType.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/PartyTPLink.yaml

@@ -0,0 +1,14 @@
+title: Party
+type: object
+description: Data model for the complex type Party.
+properties:
+  partyIdInfo:
+    $ref: ./PartyIdInfoTPLink.yaml
+  merchantClassificationCode:
+    $ref: ./MerchantClassificationCode.yaml
+  name:
+    $ref: ./PartyName.yaml
+  personalInfo:
+    $ref: ./PartyPersonalInfo.yaml
+required:
+  - partyIdInfo

package/thirdparty/v2_0/openapi3/components/schemas/QuotesIDPutResponse.yaml

@@ -0,0 +1 @@
+$ref: '../../../../../fspiop/v2_0/openapi3/components/schemas/QuotesIDPutResponse.yaml'

package/thirdparty/v2_0/openapi3/components/schemas/QuotesPostRequest.yaml

@@ -0,0 +1,79 @@
+title: QuotesPostRequest
+type: object
+description: The object sent in the POST /quotes request.
+properties:
+  quoteId:
+    $ref: ./CorrelationId.yaml
+    description: >-
+      Common ID between the FSPs for the quote object, decided by the Payer FSP.
+      The ID should be reused for resends of the same quote for a transaction. A
+      new ID should be generated for each new quote for a transaction.
+    example: b51ec534-ee48-4575-b6a9-ead2955b8069
+  transactionId:
+    $ref: ./CorrelationId.yaml
+    description: >-
+      Common ID (decided by the Payer FSP) between the FSPs for the future
+      transaction object. The actual transaction will be created as part of a
+      successful transfer process. The ID should be reused for resends of the
+      same quote for a transaction. A new ID should be generated for each new
+      quote for a transaction.
+    example: a8323bc6-c228-4df2-ae82-e5a997baf899
+  transactionRequestId:
+    $ref: ./CorrelationId.yaml
+    description: Identifies an optional previously-sent transaction request.
+    example: a8323bc6-c228-4df2-ae82-e5a997baf890
+  payee:
+    $ref: ./Party.yaml
+    description: Information about the Payee in the proposed financial transaction.
+  payer:
+    $ref: ./Party.yaml
+    description: Information about the Payer in the proposed financial transaction.
+  amountType:
+    $ref: ./AmountType.yaml
+    description: 'SEND for send amount, RECEIVE for receive amount.'
+    example: SEND
+  amount:
+    $ref: ./Money.yaml
+    description: >-
+      Depending on amountType - If SEND - The amount the Payer would like to
+      send, that is, the amount that should be withdrawn from the Payer account
+      including any fees. The amount is updated by each participating entity in
+      the transaction. If RECEIVE - The amount the Payee should receive, that
+      is, the amount that should be sent to the receiver exclusive any fees. The
+      amount is not updated by any of the participating entities.
+  fees:
+    $ref: ./Money.yaml
+    description: >-
+      The fees in the transaction. The fees element should be empty if fees
+      should be non-disclosed. The fees element should be non-empty if fees
+      should be disclosed.
+  transactionType:
+    $ref: ./TransactionType.yaml
+    description: Type of transaction for which the quote is requested.
+  geoCode:
+    $ref: ./GeoCode.yaml
+    description: >-
+      Longitude and Latitude of the initiating Party. Can be used to detect
+      fraud.
+  note:
+    $ref: ./Note.yaml
+    description: A memo that will be attached to the transaction.
+    example: Free-text memo.
+  expiration:
+    $ref: ./DateTime.yaml
+    description: >-
+      Expiration is optional. It can be set to get a quick failure in case the
+      peer FSP takes too long to respond. Also, it may be beneficial for
+      Consumer, Agent, and Merchant to know that their request has a time limit.
+    example: '2016-05-24T08:38:08.699-04:00'
+  extensionList:
+    $ref: ./ExtensionList.yaml
+    description: 'Optional extension, specific to deployment.'
+required:
+  - quoteId
+  - transactionId
+  - payee
+  - payer
+  - amountType
+  - amount
+  - transactionType

package/thirdparty/v2_0/openapi3/components/schemas/Scope.yaml

@@ -0,0 +1,20 @@
+title: Scope
+type: object
+description: >-
+  The Scope element contains an identifier defining, in the terms of a DFSP,
+  an account on which access types can be requested or granted.
+  It also defines the access types which are requested or granted.
+
+  https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v2.0.0/api/thirdparty/data-models.md#32121-scope
+properties:
+  address:
+    $ref: ./AccountAddress.yaml
+  actions:
+    type: array
+    minItems: 1
+    maxItems: 32
+    items:
+      $ref: ./ScopeAction.yaml
+required:
+  - address
+  - actions

package/thirdparty/v2_0/openapi3/components/schemas/ScopeAction.yaml

@@ -0,0 +1,14 @@
+title: ScopeAction
+type: string
+description: |
+  The ScopeAction element contains an access type which a PISP can request
+  from a DFSP, or which a DFSP can grant to a PISP.
+  It must be a member of the appropriate enumeration.
+
+  - ACCOUNTS_GET_BALANCE: PISP can request a balance for the linked account
+  - ACCOUNTS_TRANSFER: PISP can request a transfer of funds from the linked account in the DFSP
+  - ACCOUNTS_STATEMENT: PISP can request a statement of individual transactions on a user's account
+enum:
+  - ACCOUNTS_GET_BALANCE
+  - ACCOUNTS_TRANSFER
+  - ACCOUNTS_STATEMENT

package/thirdparty/v2_0/openapi3/components/schemas/ServiceType.yaml

@@ -0,0 +1,15 @@
+title: ServiceType
+type: string
+description: >-
+  The ServiceType enumeration describes the types of role for which a DFSP may query using the /services resource.
+
+  Below are the allowed values for the enumeration ServiceType
+  - THIRD_PARTY_DFSP - Enum used to query for DFSPs that have thirdparty features enabled.
+  - PISP - Enum used to query for PISPs.
+  - AUTH_SERVICE - Participants which provide Authentication Services.
+
+  https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v2.0.0/api/thirdparty/data-models.md#3229-servicetype
+enum:
+  - THIRD_PARTY_DFSP
+  - PISP
+  - AUTH_SERVICE

package/thirdparty/v2_0/openapi3/components/schemas/ServicesServiceTypePutResponse.yaml

@@ -0,0 +1,26 @@
+title: ServicesServiceTypePutResponse
+type: object
+description: >-
+  Used by: Switch
+
+  The callback PUT /services/{ServiceType} is used to inform the client of a
+  successful result of the service information lookup.
+
+  Callback and data model information for GET /services/{ServiceType}:
+
+  Callback - PUT /services/{ServiceType}
+  Error Callback - PUT /services/{ServiceType}/error
+  Data Model - Empty body
+
+  https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v2.0.0/api/thirdparty/data-models.md#31531-put-servicesservicetype
+properties:
+  providers:
+    type: array
+    minLength: 0
+    maxLength: 256
+    items:
+      $ref: ./FspId.yaml
+  extensionList:
+    $ref: ./ExtensionList.yaml
+required:
+  - providers

package/thirdparty/v2_0/openapi3/components/schemas/SignedCredential.yaml

@@ -0,0 +1,23 @@
+title: SignedCredential
+type: object
+description: |
+  A credential used to allow a user to prove their identity and access
+  to an account with a DFSP.
+
+  SignedCredential is a special formatting of the credential to allow us to be
+  more explicit about the `status` field - it should only ever be PENDING when
+  updating a credential.
+properties:
+  credentialType:
+    $ref: ./CredentialType.yaml
+  # The challenge has signed but not yet verified.
+  status:
+    $ref: ./CredentialStatusPending.yaml
+  genericPayload:
+    $ref: ./GenericCredential.yaml
+  fidoPayload:
+    $ref: ./FIDOPublicKeyCredentialAttestation.yaml
+required:
+  - credentialType
+  - status
+additionalProperties: false

package/thirdparty/v2_0/openapi3/components/schemas/SignedPayloadFIDO.yaml

@@ -0,0 +1,11 @@
+title: SignedPayloadFIDO
+type: object
+properties:
+  signedPayloadType:
+    $ref: ./SignedPayloadTypeFIDO.yaml
+  fidoSignedPayload:
+    $ref: ./FIDOPublicKeyCredentialAssertion.yaml
+required:
+  - signedPayloadType
+  - fidoSignedPayload
+additionalProperties: false

package/thirdparty/v2_0/openapi3/components/schemas/SignedPayloadGeneric.yaml

@@ -0,0 +1,11 @@
+title: SignedPayloadGeneric
+type: object
+properties:
+  signedPayloadType:
+    $ref: ./SignedPayloadTypeGeneric.yaml
+  genericSignedPayload:
+    $ref: ./BinaryString.yaml
+required:
+  - signedPayloadType
+  - genericSignedPayload
+additionalProperties: false