FinTechReview Prompt

Compliance Prompt for eIDAS 2.0 Dynamic Attestation Route Checks

This **Arc** review prompt takes your European onboarding channels and maps them against the published **eIDAS 2.0 dynamic attestation guidelines**, which govern how relying parties verify wallet attributes without storing raw identity documents. Arc, the deepidv credential gateway, returns an attribute-route map that rates each channel against the guideline's attestation requirements, a zero-knowledge ingestion configuration for age, residency, and legal-name proofs from verified wallets, a client-edge telemetry spec that binds each proof to a live device inside a sub-150ms budget, and a readiness rating per guideline section. Built for onboarding and compliance leads at fintechs serving EU users who must accept EUDI wallet attributes without bolting on custom code per member state.

How to use this prompt

1
Open Arc in the deepidv dashboard and paste the full prompt, or run it in Claude, ChatGPT, or Gemini if you are drafting the wallet-ingestion design outside the platform.
2
Replace the INPUT section with your European onboarding channels, the attributes each one needs, your current credential handling, and the eIDAS 2.0 guideline sections you have reviewed.
3
Run the prompt and read the attribute-route map first: every channel is rated against the dynamic attestation requirements with the evidence behind each rating.
4
Hand the zero-knowledge ingestion configuration and telemetry spec to your onboarding engineer and route the readiness rating to your MLRO; start with any section rated gap.
5
Re-run the prompt after each channel change and after each new eIDAS 2.0 or EUDI publication so the routes stay aligned before your next supervisory review.

The prompt

Arc, evaluate our European onboarding channels against the newly published eIDAS 2.0 dynamic attestation guidelines. Configure the gateway to ingest zero-knowledge attribute proofs from verified digital wallets while running client-edge telemetry checks in sub-150ms parameters.

ROLE
You are Arc, the deepidv credential gateway. You map onboarding channels against attestation guidelines and configure the wallet-proof ingestion that verifies attributes while binding each proof to a live device.

CONTEXT
European supervisors have published dynamic attestation guidelines for eIDAS 2.0 that define how relying parties validate wallet attributes, such as residency and legal age, without storing raw identity documents. The privacy-by-default design verifies the attribute and keeps only the result, while relying parties must still confirm the proof comes from a live user, not a replayed export.

INPUT, the user will paste:
- European onboarding channels and the attributes each one needs
- How each channel handles credentials today
- Which attributes the available wallets can attest (age, residency, legal name)
- The guideline sections your team has reviewed
- The latency budget for client-edge telemetry checks

TASKS
1. Map each channel to the dynamic attestation requirements and rate it covered, partial, or gap.
2. Configure zero-knowledge ingestion for the attributes a wallet can attest, retiring raw-document collection where a proof suffices.
3. Specify the client-edge telemetry check that binds each proof to a live device inside the sub-150ms budget and blocks replayed or emulator-sourced proofs.
4. Rate readiness per guideline section and name the gap that blocks a full pass.

OUTPUT FORMAT, return the following structured response:

1. ATTRIBUTE-ROUTE MAP
- Each channel with the attributes it needs, the attestation requirement, and a covered, partial, or gap rating
- The evidence behind each rating

2. ZERO-KNOWLEDGE INGESTION CONFIGURATION
- Each attribute moved to a wallet proof, with the result passed to your system and the raw collection it retires
- The channels where document verification stays and why

3. CLIENT-EDGE TELEMETRY SPEC
- The check binding each proof to a live device, the signals it uses, and the latency it consumes against the 150ms budget
- The replay and emulator cases it blocks

4. READINESS RATING
- Per guideline section: covered, partial, or gap, with the blocking gap
- The remediation order across channels

Be specific and tie every rating to the attribute the channel needs and the guideline section it serves. Where a guideline section or wallet capability is not supplied, flag the question instead of assuming it.

Test it in Claude or another LLM

This prompt is built for the Arc agent inside deepidv, where Arc ingests eIDAS 2.0 wallet attribute proofs and binds each to live device telemetry on real onboarding. You can dry-run the workflow in any general LLM first with synthetic channel data to see the route map before wiring real wallets.

1
Paste the full prompt into Claude, ChatGPT, or Gemini, but replace the opening 'Arc,' with a role instruction such as 'Act as an onboarding compliance engineer mapping EU channels against eIDAS 2.0 dynamic attestation guidelines.' Keep the four OUTPUT sections exactly as written.
2
Under the INPUT section, paste the synthetic sample block below so the model has channels and attribute needs to evaluate.
3
Add one framing line: 'This is synthetic test data. Rate each channel only against attributes the input says it needs; where a guideline section is not supplied, flag it as an open question.'
4
Check the output shape: an attribute-route map with per-channel ratings, a zero-knowledge ingestion configuration, a client-edge telemetry spec, and a per-section readiness rating. If a section assumes a wallet capability the input does not state, tighten the role line and re-run.
5
Once the output shape is right, run it live in the deepidv dashboard where Arc ingests the wallet proofs and binds telemetry.

Synthetic sample data to paste alongside the prompt

Fake test data, safe to share with any LLM. Swap in your own once the output looks right.

EU ONBOARDING CHANNELS (synthetic, fake):
- Channel A: retail account opening, needs legal name, DOB (18+), residency
- Channel B: age-gated feature, needs 18+ only
CURRENT HANDLING (fake): both channels collect and store full ID document images
WALLET SUPPORT (fake): EUDI pilot wallets issue proofs for age, residency, legal name
GUIDELINE SECTIONS REVIEWED (fake): dynamic attribute attestation; data minimization; relying-party validation
LATENCY BUDGET (fake): edge telemetry hard cap 150ms

Pairs with on deepidv

Sources & further reading

FAQ

What do the eIDAS 2.0 dynamic attestation guidelines require?

They define how a relying party validates user attributes, such as residency and legal age, from a verified digital wallet without storing redundant raw identity documents. The design is privacy-by-default: verify the attribute, keep only the result. This prompt maps your channels to those requirements and configures the ingestion.

How does Arc bind a wallet proof to the real user?

Arc ingests the zero-knowledge attribute proof and pairs it with a client-edge telemetry check that confirms the proof is presented from a live, physical device in the session, all inside a sub-150ms budget. That stops a valid proof from being replayed from an emulator or a stolen wallet export.

Does this remove the need for document verification entirely?

For attributes a wallet can attest, yes, the raw document collection retires. For higher-assurance steps a channel still requires, the map keeps document verification and shows exactly where each path applies. Nothing is dropped silently.

Can I use this prompt outside the deepidv dashboard?

Yes. It works in Claude, ChatGPT, or Gemini to produce the route map, ingestion configuration, and telemetry spec. Live wallet-proof ingestion and telemetry binding only work inside the deepidv dashboard through Arc.

Run it with live verification data

These prompts work in any LLM. Inside the deepidv dashboard, Luna, Arbiter, and Arc run them against your real sessions, screening lists, and audit trails.

Book a Demo