Event Catalog
The Business Wallet emits a small, deliberately focused set of domain events to integration channels. Every event:
- Is wrapped in a CloudEvents 1.0 envelope.
- Has a
typeending in.v<major>- backwards-compatible additions reuse the same major version, breaking changes mint a new one. - Has a public JSON Schema at
${WALLET_BASE_URL}/api/public/schemas/integration/<slug>/v1.json(no authentication required) which is also pinned in the envelope'sdataschemaattribute.
What events does the wallet publish?
The Business Wallet publishes domain events covering wallet creation and public profile updates, identifier creation, wallet domain registration and verification, credential issuance and revocation, credential receipt, requests to approve a credential issuance, presentation verification, and the audit trail. Each event carries a stable type ending in .v1 and a public JSON Schema link. No event ever carries a credential document or the subject claims inside it; most carry business identifiers only, and the ones that carry more than that — contact details on wallet.created.v1 and publicprofile.updated.v1, the DNS verification token on walletdomain.created.v1, user activity on audit.recorded.v1 — say so in their own section below.
The catalog covers the wallet itself and the profile it publishes, the identifiers it signs with, the custom domain it is served on, the credentials it issues or holds and the approvals they wait for, the verifications it runs, and the trail of what its users did. Each event's subject, data fields and JSON Schema are documented in its own section below.
| Event type | What it tells you | What you would use it for |
|---|---|---|
com.credenco.businesswallet.wallet.created.v1 | A Business Wallet now exists, with the contact details given when it was created. | Provision the tenant in your own systems the moment it appears — open the CRM or ERP record, start onboarding, create the support channel — keyed on walletExternalKey. |
com.credenco.businesswallet.identifier.created.v1 | The wallet gained a new signing identity: a DID, an X509 certificate, or a JWK. | Keep your own trust registry or issuer allow-list current, and start whatever internal approval has to happen before a new identifier is used in production. |
com.credenco.businesswallet.walletdomain.created.v1 | Someone registered a hostname of their own to serve their wallet on. It starts unverified — DNS ownership has not been proven yet. | Pick the registration up when it happens rather than at the first verification result half an hour later. The payload carries the DNS verification token, so you can show the customer the exact TXT record they have to create. |
com.credenco.businesswallet.walletdomain.statuschanged.v1 | A registered hostname moved to another state: ownership proven, in service, or no longer verifying. | Hand a PENDING → VERIFIED to operations so the ingress can be arranged. Read previousStatus before acting on anything else: ACTIVE → VERIFIED is a hostname that stopped answering, not a new request, and a FAILED out of PENDING is only DNS that has not landed yet, while one out of VERIFIED or ACTIVE means a published record was removed. |
com.credenco.businesswallet.walletdomain.deleted.v1 | A registered hostname was removed. The payload is a snapshot taken at deletion; the record itself is already gone. | Retire the DNS records and the monitoring for that hostname, and flag every did:web identifier published on it — none of them resolve any more. |
com.credenco.businesswallet.credential.issued.v1 | Your wallet issued a credential to a holder. | Reconcile the issuance against whatever asked for it, count issuance for reporting, and keep revocationUuid so you can revoke the credential later. |
com.credenco.businesswallet.credential.revoked.v1 | A credential your wallet issued is no longer valid. | Mirror the revocation in your own records, notify the holder, and close whatever entitlement the credential stood for. |
com.credenco.businesswallet.credential.received.v1 | Your wallet is now holding a credential that somebody else issued to it. | Continue a process that was waiting on that document — a supplier that counts as onboarded once their certificate arrives, say — instead of polling the credential list. |
com.credenco.businesswallet.credential.issuance.approval-requested.v1 | A request to issue a credential is waiting for someone in the wallet to approve or refuse it. | Notify the approver or open a task in your own workflow the moment a request arrives, keyed on correlationId, instead of polling the pending-approval list. |
com.credenco.businesswallet.presentation.verified.v1 | A verify session you started reached a verdict, and the payload says what the verdict was. | Release whatever the check was gating — admission, a contract step, a checkout — keyed on the sessionKey you opened the session with. Read verified before acting: a finished session is not the same as an accepted one. |
com.credenco.businesswallet.publicprofile.updated.v1 | The details a wallet shows to the outside world changed. The payload is the complete current profile, not only the fields that moved. | Keep the name, logo and contact details you display for that organisation in step with what they publish, without re-reading the profile API. |
com.credenco.businesswallet.audit.recorded.v1 | One line of the wallet's holder-side history log: which user did what, when, and with which counterparty. | Stream the trail into a SIEM or a compliance archive. This is the busiest event in the catalog and the only one reporting user activity as it happens, so subscribe to it deliberately rather than through a wildcard — see its own section for what it does and does not carry. |
All event types follow the naming convention com.credenco.businesswallet.<aggregate>.<verb>.v<major>. The trailing .v<major> segment is the major version. Backward-compatible additions (new optional fields) ship as the same .v1 type; breaking changes ship as a new type (.v2) so existing consumers keep working.
JSON Schemas are served at ${WALLET_BASE_URL}/api/public/schemas/integration/<slug>/v1.json (no authentication required) and are pinned per-event via the dataschema envelope attribute.
com.credenco.businesswallet.wallet.created.v1
Trigger. Fired exactly once when a Business Wallet is created - either via the UI, the public API, or onboarding. The event is published atomically with the wallet itself, so consumers will never observe a wallet that the wallet itself does not yet know about.
Subject. wallets/{walletExternalKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | Stable external identifier of the wallet. Match this against your own records. |
displayName | string | Human-readable name shown in the wallet UI. |
email | string | null | Primary contact email, if provided during creation. |
website | string | null | Primary website URL, if provided. |
phoneNumber | string | null | Primary phone number, if provided. |
address | object | null | Postal address with street, postalCode, city, country. Any inner field may be null. |
createdAt | string (RFC 3339) | UTC timestamp of wallet creation. |
createdBy | string | Subject (sub) of the principal that created the wallet - a human user ID or an OAuth2 client ID. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.wallet.created.v1
ce-source: /credenco/wallets
ce-id: 9c7d6b1f-1d17-4c2c-8a5d-2e0f6b1a4f10
ce-time: 2026-05-01T09:42:17.812Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/wallet-created/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1746094937,v1=2c1f8e30…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"displayName": "Acme Healthcare B.V.",
"email": "ops@acme-healthcare.example",
"website": "https://acme-healthcare.example",
"phoneNumber": "+31 20 555 0100",
"address": {
"street": "Tolnasingel 3",
"postalCode": "2411 PV",
"city": "Bodegraven",
"country": "NL"
},
"createdAt": "2026-05-01T09:42:17.812Z",
"createdBy": "auth0|admin@acme-healthcare.example"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/wallet-created/v1.json
com.credenco.businesswallet.identifier.created.v1
Trigger. Fired exactly once when a wallet identifier (DID, X509 certificate, or JWK) is created. Like wallet.created.v1, the event is published atomically with the underlying change so it is never lost.
Subject. wallets/{walletExternalKey}/identifiers/{identifierExternalKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the owning wallet. |
identifierExternalKey | string (UUID) | Stable external identifier of the identifier itself. |
identifierType | enum | One of DID, X509, JWK. |
identifier | string | The actual identifier value - a DID URI, an X509 subject, or a JWK thumbprint. |
displayName | string | Human-readable label set by the operator. |
didType | string | null | Populated only when identifierType = DID (e.g. did:web, did:key, did:ebsi). null for X509 and JWK. |
didEnvironment | string | null | Populated only when identifierType = DID and the DID method has environments (e.g. pilot, production for did:ebsi). null otherwise. |
createdAt | string (RFC 3339) | UTC timestamp of identifier creation. |
createdBy | string | Subject of the principal that created the identifier. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.identifier.created.v1
ce-source: /credenco/wallets
ce-id: 7e2b1a86-9c1e-4d2e-b6a4-1f8db4a90f22
ce-time: 2026-05-01T09:43:02.401Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/identifiers/c4a4e34b-1d6d-4b9a-9e6f-3a7d6f8b1e02
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/identifier-created/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1746094982,v1=8d4a91c2…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"identifierExternalKey": "c4a4e34b-1d6d-4b9a-9e6f-3a7d6f8b1e02",
"identifierType": "DID",
"identifier": "did:web:acme-healthcare.example",
"displayName": "Primary issuer DID",
"didType": "did:web",
"didEnvironment": null,
"createdAt": "2026-05-01T09:43:02.401Z",
"createdBy": "auth0|admin@acme-healthcare.example"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/identifier-created/v1.json
com.credenco.businesswallet.walletdomain.created.v1
Trigger. Fired exactly once when a wallet domain is registered - a hostname of the customer's own that the wallet will be served on. The domain is born PENDING, and registering it is not a status change, so walletdomain.statuschanged.v1 does not also fire here. Without this event the first thing you would hear about a domain is the automatic re-check moving it to VERIFIED or FAILED up to half an hour later, and you would not know which hostname was requested, or by whom, until then.
verificationToken is the value the customer publishes in the _credenco-wallet.<hostname> TXT record to prove they own the hostname. It is not a credential - it is meant to end up in public DNS, and it is worthless to anyone who does not already control that hostname - so you can safely put it in front of the person who has to create the record. Use it to show them the exact TXT entry rather than making them open the wallet UI for it.
Subject. wallets/{walletExternalKey}/domains/{domainExternalKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the owning wallet. |
domainExternalKey | string (UUID) | Stable external identifier of the domain registration. |
hostname | string | The registered hostname, normalised. |
verificationToken | string | The DNS TXT value proving ownership of the hostname. |
createdAt | string (ISO-8601 date-time) | Timestamp of the registration. |
createdBy | string | Principal that registered the domain. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.walletdomain.created.v1
ce-source: /credenco/wallets
ce-id: 5a3b2c1d-0e9f-4a8b-9c7d-6e5f4a3b2c1d
ce-time: 2026-08-07T12:00:00.000Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/domains/22222222-2222-2222-2222-222222222222
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/wallet-domain-created/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1754568000,v1=6f7a8b9c…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"domainExternalKey": "22222222-2222-2222-2222-222222222222",
"hostname": "wallet.acme-healthcare.example",
"verificationToken": "9f2c1b7a4d3e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60",
"createdAt": "2026-08-07T12:00:00",
"createdBy": "auth0|admin@acme-healthcare.example"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/wallet-domain-created/v1.json
com.credenco.businesswallet.walletdomain.statuschanged.v1
Trigger. Fired when a registered wallet domain moves to a different status, whether that was a manual Verify DNS or one of the automatic re-checks. Only an actual transition fires the event, so a re-check that confirms the current status is silent, and so is a verify attempt whose DNS lookup could not be reached - the status is deliberately left alone rather than demoted on an inconclusive answer.
The four statuses are:
| Status | Means | Appears as |
|---|---|---|
PENDING | Registered, DNS ownership not proven yet. Every domain is born in this status. | previousStatus only - a domain is never moved into PENDING, and registering it does not fire this event. |
VERIFIED | The DNS records check out. Out of PENDING the hostname still has to be put into service by Credenco Operations; out of ACTIVE it is a demotion, because the hostname stopped answering. | both |
ACTIVE | The hostname actually serves the wallet. | both |
FAILED | The DNS records do not verify - they were never created, or they changed or disappeared. | both |
Read previousStatus before deciding what a transition means, because the same newStatus can arrive for opposite reasons.
A FAILED out of PENDING is an ordinary registration whose DNS is not in place yet. The automatic re-check runs every 30 minutes over domains registered in the last 48 hours, so this is the normal first transition for a new domain and the response is to chase the customer, not to raise an incident.
A FAILED out of VERIFIED or ACTIVE means a record that was published has been removed, and that is the one to alert on. Look at which record: the ownership TXT record is checked independently of the CNAME, so losing only the TXT demotes the domain while the hostname carries on serving, whereas losing the CNAME takes the hostname down and with it every did:web identifier published on it - credentials issued with those stop verifying until the record is restored.
Subject. wallets/{walletExternalKey}/domains/{domainExternalKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the owning wallet. |
domainExternalKey | string (UUID) | Stable external identifier of the domain registration. |
hostname | string | The registered hostname. |
previousStatus | string | null | Status before the transition. |
newStatus | string | Status after the transition - see the table above. |
statusMessage | string | Human-readable explanation, the same text the wallet UI shows. Empty when there is none. |
changedAt | string (ISO-8601 date-time) | When the transition happened. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.walletdomain.statuschanged.v1
ce-source: /credenco/wallets
ce-id: 6b4c3d2e-1f0a-4b9c-8d7e-5f4a3b2c1d0e
ce-time: 2026-08-07T12:30:00.000Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/domains/22222222-2222-2222-2222-222222222222
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/wallet-domain-status-changed/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1754569800,v1=7a8b9c0d…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"domainExternalKey": "22222222-2222-2222-2222-222222222222",
"hostname": "wallet.acme-healthcare.example",
"previousStatus": "PENDING",
"newStatus": "VERIFIED",
"statusMessage": "DNS verified.",
"changedAt": "2026-08-07T12:30:00"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/wallet-domain-status-changed/v1.json
com.credenco.businesswallet.walletdomain.deleted.v1
Trigger. Fired exactly once when a registered wallet domain is removed. The payload is a snapshot taken at deletion, including the status the domain was in: the record is already gone by the time the event is delivered, so nothing downstream can look it up again.
Removing a domain is destructive. A did:web identifier is published on its hostname, so if the removed domain carried one, that identifier can no longer be resolved and every credential issued with it stops verifying - re-registering the hostname later does not repair it. Treat a delivery on this type as an incident to confirm, not as routine bookkeeping.
Subject. wallets/{walletExternalKey}/domains/{domainExternalKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the owning wallet. |
domainExternalKey | string (UUID) | External identifier the registration had. |
hostname | string | The hostname that was removed. |
statusAtDeletion | string | null | Status the domain was in when it was deleted. |
deletedAt | string (ISO-8601 date-time) | When it was removed. |
deletedBy | string | Principal that removed it. |
createdBy | string | Principal that originally registered it. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.walletdomain.deleted.v1
ce-source: /credenco/wallets
ce-id: 7c5d4e3f-2a1b-4c0d-9e8f-6a5b4c3d2e1f
ce-time: 2026-08-09T09:30:00.000Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/domains/22222222-2222-2222-2222-222222222222
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/wallet-domain-deleted/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1754731800,v1=8b9c0d1e…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"domainExternalKey": "22222222-2222-2222-2222-222222222222",
"hostname": "wallet.acme-healthcare.example",
"statusAtDeletion": "ACTIVE",
"deletedAt": "2026-08-09T09:30:00",
"deletedBy": "auth0|admin@acme-healthcare.example",
"createdBy": "auth0|admin@acme-healthcare.example"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/wallet-domain-deleted/v1.json
com.credenco.businesswallet.credential.issued.v1
Trigger. Fired when an issuer-side credential is issued and stored by the Business Wallet. The event is published atomically with the issuance so consumers never observe an issued credential the wallet does not yet know about. The payload carries external and business identifiers only, never the credential document or any subject claims.
Subject. wallets/{walletExternalKey}/credentials/{credentialUuid}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the owning wallet. |
credentialUuid | string | Stable business identifier of the issued credential. |
credentialFormat | string | Credential format, one of JWT, SD_JWT, LDP, STATUSLIST, MDOC. |
credentialConfigurationId | string | null | Issuer credential-configuration identifier the credential was issued from, if known. |
issuanceDate | string (ISO-8601 date-time) | Timestamp the credential was issued. |
revocationUuid | string | null | Revocation list entry key, present when the credential is revocable. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.credential.issued.v1
ce-source: /credenco/wallets
ce-id: 0b8c1d2e-3f4a-4b5c-9d6e-7a8b9c0d1e2f
ce-time: 2026-05-04T09:42:17.812Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/credentials/11111111-1111-1111-1111-111111111111
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/credential-issued/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1746351737,v1=9a1b2c3d…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"credentialUuid": "11111111-1111-1111-1111-111111111111",
"credentialFormat": "SD_JWT",
"credentialConfigurationId": "DiplomaCredential",
"issuanceDate": "2026-05-04T09:42:17.812",
"revocationUuid": "22222222-2222-2222-2222-222222222222"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/credential-issued/v1.json
com.credenco.businesswallet.credential.revoked.v1
Trigger. Fired when an issued credential is revoked. The payload carries external and business identifiers only, never the credential document.
Subject. wallets/{walletExternalKey}/credentials/{credentialUuid}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the owning wallet. |
credentialUuid | string | Stable business identifier of the revoked credential. |
credentialFormat | string | Credential format, one of JWT, SD_JWT, LDP, STATUSLIST, MDOC. |
status | string | Credential status after revocation, one of VALID, INVALID, EXPIRED. A revoked credential is INVALID. |
issuanceDate | string (ISO-8601 date-time) | Timestamp the credential was originally issued. |
revocationUuid | string | null | Revocation list entry key. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.credential.revoked.v1
ce-source: /credenco/wallets
ce-id: 1c9d2e3f-4a5b-4c6d-8e7f-9a0b1c2d3e4f
ce-time: 2026-05-06T11:08:44.219Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/credentials/11111111-1111-1111-1111-111111111111
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/credential-revoked/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1746529724,v1=4d5e6f7a…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"credentialUuid": "11111111-1111-1111-1111-111111111111",
"credentialFormat": "SD_JWT",
"status": "INVALID",
"issuanceDate": "2026-05-04T09:42:17.812",
"revocationUuid": "22222222-2222-2222-2222-222222222222"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/credential-revoked/v1.json
com.credenco.businesswallet.credential.received.v1
Trigger. Fired when a holder-side credential is received and stored by the Business Wallet. The payload carries external identifiers and non-sensitive metadata only, never the credential document or any subject claims.
Subject. wallets/{walletExternalKey}/credentials/{credentialExternalKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the owning wallet. |
credentialExternalKey | string (UUID) | Stable external identifier of the received credential. |
credentialType | string | Credential type of the received credential. |
credentialFormat | string | Credential format, one of JWT, SD_JWT, LDP, STATUSLIST, MDOC. |
issuerDid | string | null | DID of the credential issuer, when available. |
issuanceDate | string (ISO-8601 date-time) | null | Issuer-asserted issuance timestamp, when present in the credential. |
createdAt | string (ISO-8601 date-time) | Timestamp the credential was stored in the wallet. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.credential.received.v1
ce-source: /credenco/wallets
ce-id: 2d0e3f4a-5b6c-4d7e-9f8a-0b1c2d3e4f5a
ce-time: 2026-05-04T09:43:01.004Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/credentials/33333333-3333-3333-3333-333333333333
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/credential-received/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1746351781,v1=7a8b9c0d…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"credentialExternalKey": "33333333-3333-3333-3333-333333333333",
"credentialType": "DiplomaCredential",
"credentialFormat": "SD_JWT",
"issuerDid": "did:web:acme-healthcare.example",
"issuanceDate": "2026-05-04T09:42:17.812",
"createdAt": "2026-05-04T09:43:01.004"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/credential-received/v1.json
com.credenco.businesswallet.credential.issuance.approval-requested.v1
Trigger. Fired when an issuer defers a credential until someone approves it: the request enters the pending-approval state and waits there for a decision. It is delivered once per issuance request. The payload carries the identifiers needed to find and decide the request, never the claims of the credential; read those from GET /api/v2/credential/issue/pending-approval, which needs the WALLET_ISSUE_CREDENTIAL_CRUD (or GLOBAL_WALLET_CRUD) role.
Subject. wallets/{walletExternalKey}/issuances/{correlationId}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the issuing wallet. |
correlationId | string | Identifier of the issuance request. Pass it to POST /api/v2/credential/issue/{correlationId}/approve or .../reject to decide it. This is the correlationId field in the data, not the ce-correlationid envelope attribute, which belongs to the originating request. |
credentialIssuerExternalKey | string | null | External key of the credential issuer the request was made against. |
credentialConfigurationId | string | null | Credential-configuration identifier that was requested. |
requestedAt | string (ISO-8601 date-time) | Timestamp the request started waiting for approval. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.credential.issuance.approval-requested.v1
ce-source: /credenco/wallets
ce-id: 4f1a5b6c-7d8e-4f90-a1b2-c3d4e5f60718
ce-time: 2026-05-04T09:44:09.318Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/issuances/6c7d8e9f-0a1b-4c2d-8e3f-4a5b6c7d8e9f
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/credential-issuance-approval-requested/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1746351849,v1=5d6e7f80…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"correlationId": "6c7d8e9f-0a1b-4c2d-8e3f-4a5b6c7d8e9f",
"credentialIssuerExternalKey": "diploma-issuer",
"credentialConfigurationId": "DiplomaCredential",
"requestedAt": "2026-05-04T09:44:09.318"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/credential-issuance-approval-requested/v1.json
com.credenco.businesswallet.presentation.verified.v1
Trigger. Fired when a verify session reaches the verified state. A verify session reaches the verified state at most once, so this event is delivered once per session. The payload carries the verify-session business key, the verdict, and the presented credential types only, never the VP tokens or the presented credential bodies.
Subject. wallets/{walletExternalKey}/verify-sessions/{sessionKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the verifying wallet. |
sessionKey | string | Verify-session business key (the external correlation id). |
verified | boolean | Verification verdict. |
presentedCredentialTypes | array of string | Credential types presented in the session. May be empty. |
verifiedAt | string (ISO-8601 date-time) | Timestamp the session reached the verified state. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.presentation.verified.v1
ce-source: /credenco/wallets
ce-id: 3e1f4a5b-6c7d-4e8f-9a0b-1c2d3e4f5a6b
ce-time: 2026-05-04T09:44:12.330Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301/verify-sessions/44444444-4444-4444-4444-444444444444
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/presentation-verified/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1746351852,v1=0d1e2f3a…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"sessionKey": "44444444-4444-4444-4444-444444444444",
"verified": true,
"presentedCredentialTypes": ["DiplomaCredential", "IdentityCredential"],
"verifiedAt": "2026-05-04T09:44:12.330"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/presentation-verified/v1.json
com.credenco.businesswallet.publicprofile.updated.v1
Trigger. Fired whenever a Business Wallet's public profile is updated, through either the full replace (PUT) or the partial update (PATCH) endpoint. Every successful update emits one event carrying a full snapshot of the current public profile plus the last-modified audit fields.
Subject. wallets/{walletExternalKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the wallet. |
displayName | string | Public display name. |
logo | string | Logo, as a URL or a data: URI. |
email | string | Public contact email. |
website | string | Public website URL. |
phoneNumber | string | Public contact phone number. |
address | object | Nested street, postalCode, city, country. |
geoLocation | object | Nested latitude, longitude (strings). |
lastModifiedAt | string (ISO-8601 date-time) | Timestamp of this update. |
lastModifiedBy | string | Principal that performed the update. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.publicprofile.updated.v1
ce-source: /credenco/wallets
ce-id: 7c9e6679-7425-40de-944b-e07fc1f90ae7
ce-time: 2026-05-04T09:45:03.120Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/public-profile-updated/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1746351903,v1=1a2b3c4d…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"displayName": "Acme Healthcare B.V.",
"logo": "https://cdn.credenco.example/logos/acme.png",
"email": "ops@acme-healthcare.example",
"website": "https://acme-healthcare.example",
"phoneNumber": "+31 20 555 0100",
"address": {
"street": "Keizersgracht 123",
"postalCode": "1015 CJ",
"city": "Amsterdam",
"country": "NL"
},
"geoLocation": {
"latitude": "52.3676",
"longitude": "4.9041"
},
"lastModifiedAt": "2026-05-04T09:45:03.120",
"lastModifiedBy": "martijn"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/public-profile-updated/v1.json
com.credenco.businesswallet.audit.recorded.v1
Trigger. Fired whenever an audit record is written to the Business Wallet history log - the same trail the wallet UI shows under a wallet's history. Subscribe a channel to it to stream that trail into a SIEM or compliance system.
The wallet writes an audit record for exactly these actions, so this is the full set of category / action pairs the event can carry today:
category | action | Written when |
|---|---|---|
CREDENTIAL | OFFER_RECEIVED | A credential offer is received from an issuer. |
CREDENTIAL | OFFER_ACCEPTED | An offered credential is accepted and stored. |
CREDENTIAL | DELETED | A stored credential is deleted. |
PRESENTATION | OFFER_RECEIVED | A presentation request is received from a verifier. |
PRESENTATION | OFFER_ACCEPTED | A presentation request is accepted and the presentation is sent. |
That is one delivery per audited action, which on a holder-side wallet makes this the busiest event in the catalog. Both category and action are open sets - new values may be introduced within v1, so do not reject unknown ones.
Note that this is the holder-side audit trail. Issuer-side activity such as issuing or revoking a credential does not write a history record, and therefore does not produce this event; use com.credenco.businesswallet.credential.issued.v1 and com.credenco.businesswallet.credential.revoked.v1 for those.
Two classes of audit record are deliberately not emitted:
- Records in the
INTEGRATIONcategory, which audit the integration pipeline's own actions (channel and delivery administration - theCHANNEL_*andDELIVERY_*actions). Emitting them would let the pipeline feed itself: on a channel subscribed to*with a dead endpoint, dismissing a failed delivery would enqueue a fresh delivery that fails in turn, and the failure queue could never be drained. Those records stay visible in the wallet's own history log. - Records that are not attributable to a wallet, because
walletExternalKeyis the partition and routing key, so there is no channel to route them to.
evidence is not in the contract. The underlying history record's free-form evidence blob - which holds credential subject claims and full OID4VP authorization requests - is deliberately not part of this event and never leaves the wallet over a channel. It stays retrievable through the authenticated history API. Should a consumer ever need it, that would be a new .v2 type with an explicit per-channel opt-in, never a silent addition to v1.
What the event does carry is a behavioural record of a named user. userName plus action plus eventDate says who did what and when. Other events in this catalog already carry personal data - wallet.created.v1 carries createdBy, email and phoneNumber - but this is the first one that describes user activity, and it fires continuously rather than at setup time.
An existing channel can start receiving it without anyone opting in. A channel whose filter is * (or a matching wildcard) matches every type in the catalog, so it will pick this event up as soon as the wallet is upgraded - see Versioning. Before rolling this out, review your existing channels and pin explicit event types on any channel that should not receive the audit trail.
Channel export is not gated on the audit-trail read permission. Reading history through the wallet API requires WALLET_AUDIT_TRAIL_READ. Configuring a channel requires WALLET_INTEGRATION_CHANNEL_CRUD. Those are different permissions, so someone who can manage channels can route the audit trail to an endpoint they control without being able to read it in the UI. Treat channel-management rights on a wallet as equivalent to audit-trail read access.
Subject. wallets/{walletExternalKey}
Data fields.
| Field | Type | Description |
|---|---|---|
walletExternalKey | string (UUID) | External identifier of the wallet the audited action belongs to. |
userName | string | null | The wallet user recorded on the audit entry. Null when the record could not be attributed to a user. |
category | string | The audited area - see the table above for the values in use. INTEGRATION never appears here. Open set. |
action | string | The audited action - see the table above. The CHANNEL_* and DELIVERY_* actions exist in the wallet but only ever on INTEGRATION records, so they never reach this event. Open set. |
party | string | null | The counterparty the action concerned - the issuer URL for a credential offer, the verifier for a presentation request. |
credentialUuids | array of string | The credentials the audited action touched. Empty when the action is not credential-scoped. These are the id claims of the credential documents, not the credentialExternalKey / credentialUuid values the other events in this catalog use, so do not expect them to join against those. |
eventDate | string (ISO-8601 date-time) | When the action was recorded. Carries no UTC offset - it is the wallet server's local time. Use the envelope's time attribute when you need an unambiguous instant. |
Sample envelope (binary CloudEvents over HTTP).
POST /webhooks/credenco HTTP/1.1
Host: receiver.example.com
Content-Type: application/json
ce-specversion: 1.0
ce-type: com.credenco.businesswallet.audit.recorded.v1
ce-source: /credenco/wallets
ce-id: 9b2c1d0e-5a4f-4c3b-8d7e-6f5a4b3c2d1e
ce-time: 2026-07-10T09:42:17.812Z
ce-subject: wallets/3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-dataschema: https://wallet.acc.credenco.com/api/public/schemas/integration/audit-recorded/v1.json
ce-datacontenttype: application/json
ce-walletexternalkey: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
ce-correlationid: 5b1e2dca-6c3a-4b9b-9f0d-7c12da3a1b88
X-Credenco-Signature: t=1752140537,v1=2b3c4d5e…
{
"walletExternalKey": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"userName": "j.jansen",
"category": "CREDENTIAL",
"action": "OFFER_ACCEPTED",
"party": "https://issuer.acme-healthcare.example",
"credentialUuids": ["urn:uuid:11111111-1111-1111-1111-111111111111"],
"eventDate": "2026-07-10T09:42:17.812"
}
JSON Schema. https://wallet.acc.credenco.com/api/public/schemas/integration/audit-recorded/v1.json
Versioning
The trailing .v1 segment in every event type is the major version. We follow these rules:
- Adding a new optional field to the
datapayload is backward compatible and ships as the samev1type. Build your receivers so that unknown fields are ignored. - Removing a field, renaming a field, or changing a field's type is breaking and ships as a new major version (
v2). The oldv1type is kept emitting in parallel for at least one major release cycle so you have time to migrate. - New event types are added freely. A channel whose event filters name specific types is never auto-subscribed to a new one. A channel configured over the API with a wildcard pattern is:
*matches every type in the catalog, and a segment wildcard such ascom.credenco.businesswallet.credential.*matches any futurecredentialevent. If you need a predictable set of deliveries, pin the types you want instead of relying on a wildcard.
Pin the schema you tested against in your receiver code by storing the dataschema attribute alongside any persisted event.