# Igrantio Dcql Multiple Statements

> DCQL pattern: request several instances of the SAME credential type in one OpenID4VP verification using multiple: true on the iGrant.io Organisation Wallet Suite - a loan provider collecting six recent BankStatement SD-JWT credentials (period, account number, holder name) in a single flow. Loan applications, income checks, and any multi-instance evidence gathering with EUDI Wallet (EUDIW) under eIDAS 2.0.

- Skill: `l3-igrant/igrantio-dcql-multiple-statements` (Agent Skill)
- Install (CLI): `npx skillmds@latest add l3-igrant/igrantio-dcql-multiple-statements`
- Raw SKILL.md: https://api.skillmd.com/api/skills/l3-igrant/igrantio-dcql-multiple-statements/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: Apache-2.0
- Author: L3-iGrant (https://skillmd.com/u/l3-igrant)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/l3-igrant/igrantio-dcql-multiple-statements

---


# DCQL: multiple instances of one credential (bank statements)

## Scenario
A loan provider assesses an application and needs six recent
`BankStatement` credentials. `multiple: true` lets the wallet return
several instances of the same credential type in one presentation.

**Before you build**: run the integrator intake in `igrantio-ows-overview` - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each.

## The DCQL query
```json
{
  "credentials": [
    {
      "id": "bank_statement",
      "format": "dc+sd-jwt",
      "multiple": true,
      "meta": {
        "vct_values": [
          "https://credentials.bank.com/bank_statement"
        ]
      },
      "claims": [
        { "id": "statement_period", "path": ["period"] },
        { "id": "account_number", "path": ["account_number"] },
        { "id": "account_holder_name", "path": ["account_holder_name"] }
      ],
      "claim_sets": [
        ["statement_period", "account_number", "account_holder_name"]
      ]
    }
  ]
}
```

## Run it on OWS
1. Store as a presentation definition; send the verification request (v3).
2. On `presentation_acked` + `verified === true`, `vpTokenResponse` /
   `presentation` carry SEVERAL entries for the one query id - iterate all
   of them, do not read only `presentation[0]`.
3. Validate business rules server-side: count received, contiguous
   `period` values, same `account_number` across instances.

## Adjust for your deployment
- `vct_values`: your bank-statement credential VCT.
- DCQL's `multiple` does not fix a COUNT - enforce "six recent months" in
  your verification logic and re-prompt if short.
- Combine with `trusted_authorities` to only accept statements issued by
  regulated banks.

## Cross-references
- `igrantio-dcql-kyc` - single bank statement as address proof.
- The TS12 e-mandate transaction data (`igrantio-ows-overview`
  api-reference §2.1) often follows this check in a loan flow.

## Source of truth
This workflow mirrors
<https://docs.igrant.io/docs/dcql-2-4-6-loan-application-multiple-bank-statements/>
(query detailed in
<https://docs.igrant.io/concepts/eudi-wallet-dcql-openid4vp-business-wallet-payments/>,
§2.4.6). Before implementing, fetch the doc page; if it disagrees with this
skill, the documentation wins - follow it and report the drift so the skill
can be updated.