Verifiable Credentials - Pricing

Pay-as-you-go pricing

MATTR uses a pay-as-you-go pricing model.

Each chargeable activity is represented by a SKU. A SKU will be charged on one of the following bases:

1. Usage-based charges are determined by the volume of an activity x price per activity – SKUs charged on this basis may or may not be the direct result of your invocation of an API

2. Variable recurring charges are calculated based on the quantity of a particular entity managed across time (such as the number of credentials stored in a given month x price per each credential stored)

3. Fixed recurring charges are charged as a fixed monthly fee (often as a result of provisioning an Add-On)

MATTR pricing is tiered based on the volume of use of each SKU. If your usage volumes are likely to fall outside the published tiers, please contact us to discuss our high-volume discounts.

All prices presented are exclusive of any taxes that may apply.

Pricing for Verifiable Credentials

SKU: Generate Verifiable Credential

A Generate Verifiable Credential SKU is charged for each successful request to create a Verifiable Credential and through user-initiated issuance flows as supported by the OIDC Credential Issuer.

The specific SKU that will be charged depends upon the key type of the DID specified as the issuer in the request to the Create a Verifiable Credential API endpoint or as configured in the OIDC Credential Issuer.

SKU: Store Verifiable Credential

If, when creating a Verifiable Credential, the persist attribute is set to true then the content of the Verifiable Credential will be stored perpetually until such time as it is explicitly removed. Each month in which a credential has been stored (for all / or a portion of the month) a Store Verifiable Credential SKU shall be charged.

The specific Store Verifiable Credential SKU that will be charged depends upon the total size of the stored data within the credential and/or metadata; whether it is < 1KB or < 10KB.

Any Verifiable Credential may be subsequently removed in order to cease further charges related to the continued persistence of the Verifiable Credential. You should always satisfy yourself that the Verifiable Credential is not in use before removing it; such as could be the case where the credential data contains credential status information potentially used by future verifiers of the credential.

One of the below SKUs shall be charged in accordance with the total size of the data stored.

SKU: Store Credential Status

A credential status record is created whenever a request is made to the Create a Verifiable Credential API endpoint to create a Verifiable Credential with the revocable attribute set to true. The credential status record is used by verifiers to ascertain if the issuer has marked the credential as being revoked.

Each month in which a credential status record is stored (for all / or a portion of the month) a Store Credential Status SKU shall be charged.

A credential status record (along with any credential data) may be subsequently removed in order to cease further charges related to the continued persistence of the credential status record. You should always satisfy yourself that the Verifiable Credential and its credential status record is not in use before removing it. Future verifiers of the credential will not be able to ascertain the status of the credential once the credential status record has been removed and could reasonably view the credential to be revoked in such a case.

SKU: Retrieve Verifiable Credential

A Retrieve Verifiable Credential SKU is charged for each request to the Retrieve Credential Data API endpoint.

SKU: Verify Verifiable Credential

When presenting a Verifiable Credential to the Verify a Credential API endpoint for verification, the signature contained in the proof of the Verifiable Credential will be verified (in addition to other verification criteria) and a Verify Verifiable Credential SKU will be charged.

Additionally, a Verify Verifiable Credential SKU wil be charged when credential verifiaction occurs as a result of a user-initiated verification flow as supported by the OIDC Credential Verifier and by way of the verification of a credential using a callback flow.

The specific SKU that will be charged depends upon the proof type within the Verifiable Credential specified in the input payload.

N.B. Verification has taken place, and a Verify SKU will be charged, regardless of if the Verifiable Credential is deemed to be verified or not.