light-mode-image
Learn
API ReferenceWallet providers

Delete a wallet provider

Roles

adminverifier

Analytics Events

PRESENTATION_WALLET_PROVIDER_DELETE_STARTPRESENTATION_WALLET_PROVIDER_DELETE_SUCCESSPRESENTATION_WALLET_PROVIDER_DELETE_FAIL
DELETE/v2/presentations/wallet-providers/{walletProviderId}

Deletes an existing wallet provider that can present mDocs for online verification.

Analytic events

  • PRESENTATION_WALLET_PROVIDER_DELETE_START
  • PRESENTATION_WALLET_PROVIDER_DELETE_SUCCESS
  • PRESENTATION_WALLET_PROVIDER_DELETE_FAIL

Authorization

bearerAuth
AuthorizationBearer <token>

In: header

Path Parameters

walletProviderId*string

Unique identifier for the wallet provider.

Formatuuid

Response Body

application/json

curl -X DELETE "https://example.vii.au01.mattr.global/v2/presentations/wallet-providers/281d20b3-42a3-40dd-b29a-115ff32b02b7"
Empty
{
  "code": "string",
  "message": "string",
  "details": [
    {
      "value": "string",
      "msg": "Invalid value",
      "param": "id",
      "location": "body"
    }
  ]
}

How would you rate this page?

Update a wallet provider PUT

Updates an existing wallet provider that can present mDocs for online verification. ### **Analytic events** * CREDENTIAL_PRESENTATION_WALLET_PROVIDER_UPDATE_START * CREDENTIAL_PRESENTATION_WALLET_PROVIDER_UPDATE_SUCCESS * CREDENTIAL_PRESENTATION_WALLET_PROVIDER_UPDATE_FAIL

Retrieve presentation session result GET

Retrieves the result of an online presentation session by providing the session's ID. When a holder responds to a verification request, the result indicates whether the presentation succeeded and whether the credentials were verified. The response can be a `PresentationSuccessResult` (holder completed the presentation workflow) or a `PresentationFailureResult` (holder was unable to complete the workflow). A successful presentation may include verified credentials, credential errors (requested credentials not provided), claim errors (specific claims that failed verification), or a combination of these outcomes. Your backend should validate that the returned `challenge` matches the challenge generated before starting the session to protect against session replay attacks. For detailed information about result structures, error types, and complete examples, see the [handling verification results guide](https://learn.mattr.global/docs/verification/remote-web-verifiers/guides/handling-verification-results). ### **Analytic events** * CREDENTIAL_PRESENTATION_SESSION_RESULT_RETRIEVE_START * CREDENTIAL_PRESENTATION_SESSION_RESULT_RETRIEVE_SUCCESS * CREDENTIAL_PRESENTATION_SESSION_RESULT_RETRIEVE_FAIL