Product

AMLR Compliance Is an Identity Infrastructure Problem

Ben Cejvan

·

·

5 min read

For compliance teams, the next year is looking busy. Teams that will be in good shape at July 2027’s AMLR deadline are not the ones spending the next six months updating their AML policies. They’re the ones that recognize AMLR for what it fundamentally is: a mandate to rebuild how you verify and re-verify customer identity, at scale, across 27 EU member states, using methods that didn’t exist when your current KYC infrastructure was built.

Closing the infrastructure gap is the hard part.

The Problem Everyone Underestimates

AMLR’s identity requirements are simple when taken individually: verify customers at onboarding, apply Enhanced Due Diligence for high-risk relationships, keep CDD records current, verify beneficial owners. Compliance teams have been doing versions of these things for years.

What’s different is the standard. AMLR puts every obliged entity under one directly applicable rulebook. AMLA writes the technical standards, and from 2028 it directly supervises around 40 of the highest-risk cross-border financial groups. National supervisors keep everyone else, but they enforce the same rules. The patchwork of national AMLD4 implementations that let firms paper over gaps between jurisdictions is largely gone.

The regulation explicitly recognizes electronic identity. AMLR names eIDAS electronic identification at assurance level substantial or high, together with relevant qualified trust services, as one of two equally valid ways to verify a customer’s identity, and AMLA’s draft technical standards confirm that EUDI Wallets qualify. Enhanced Due Diligence still adds its own measures, such as source of wealth, senior-management approval, and closer monitoring. The regulation was written to align with the EUDI Wallet rollout happening right now.

That creates a practical problem for most financial institutions: your existing KYC stack was not built to receive cryptographically signed identity presentations from government-issued digital wallets. It was built around document capture, like passport photos, utility bills, manual review queues. Document checks still have a place, but under AMLA’s draft standards a remote document check becomes the fallback for customers who can’t use eID, not the default route. Building the infrastructure to accept eID at scale is not a quick project.

What Building AMLR Compliance Actually Involves

This is where most compliance roadmaps underestimate the timeline.

The EU identity landscape is not a single system. To accept electronically verified identity across your EU customer base, you need to receive presentations from each national eID scheme already in use around Europe, and from the EUDI Wallets that every member state must offer by 24 December 2026, with rollout staggered into 2027 and beyond. Each of those runs on different protocols, different attribute schemas, different certificate chains. There is no single “EU eID” integration. There’ll be 27.

Your compliance system needs consistent data, not raw provider output. A verification from MitID returns attributes differently than one from itsme. Different field names. Different formats. Different ways of signaling assurance level. If you’re building direct integrations with multiple providers, you need a normalization layer that translates all of them into a consistent data model before your compliance system can use them. Build that wrong, and your audit trail has gaps.

The audit trail needs to be designed in, not added later. AMLA will ask for evidence of each CDD event, asking what assurance level was achieved, which provider was used, what data was returned and when it was returned. If you’re assembling that logging retroactively, it has problems. A supervisory examination is not the moment to discover you’ve been storing verification metadata inconsistently across providers.

None of this is unsolvable. All of it takes longer than it looks.

The Specific Problems Worth Illustrating

PEP re-verification. For institutions with meaningful PEP exposure, like private banks, wealth managers, and international investment platforms, AMLR raises the volume and frequency of customer reviews. It caps the time between customer-information updates at one year for higher-risk customers and five years for everyone else, and a change in a customer’s circumstances triggers an update too. Every one of those events is a retention risk. Ask a customer to photograph their passport every time their file comes up for review, and a large percentage of them won’t. That’s not just friction. That’s churn, triggered by a compliance process.

A wallet-based re-verification flow, for a user who already has a EUDI wallet or national digital ID, takes seconds. Tap to share, cryptographic verification, event logged. The compliance obligation is met.

Crypto platforms and the travel rule. CASPs carry an extra layer of identity obligations. Under the Transfer of Funds Regulation, in force since 30 December 2024, every crypto transfer must carry originator and beneficiary information, whatever the amount. For transfers above €1,000 to or from a self-hosted wallet, the CASP must also check that the wallet belongs to its customer. Many platforms built their KYC before these rules existed, so a meaningful share of their existing customers may not have on-file identity that meets the AMLR standard.

That’s a retroactive verification problem. You need to identify the affected cohort, reach those customers, and complete compliant identity verification before July 2027, without rebuilding your onboarding flow from scratch, and without triggering mass customer abandonment.

Where Trinsic Fits

Trinsic’s Identity Acceptance Platform is the infrastructure layer that handles the EU identity landscape, so your compliance team doesn’t have to.

One integration connects your system to the national eID schemes your EU customers already use. Trinsic handles the EUDI-compliant protocols (OID4VP, SD-JWT, ISO 18013-5) and normalizes every verification result into a consistent data model before it reaches your system. Every verification event is logged with full metadata: provider, assurance level, attribute set, timestamp.

Assurance requirements are configurable per flow. For example, a standard CDD flow can accept eIDs at LoA Substantial or High, while an EDD flow for a PEP can be limited to LoA High. AMLR accepts either level, so where you set the bar is a policy choice. Your compliance team defines the rules; Trinsic enforces them at the point of verification.

The practical result is that your compliance infrastructure meets the AMLR standard without your engineering organization becoming a permanent maintainer of the EU eID ecosystem. That ecosystem will keep changing: new wallets will be certified, protocols will be updated, and implementing acts will clarify assurance level requirements. Trinsic maintains that coverage. You maintain the business.

The Timeline That Actually Works

Organizations that integrate before national EUDI Wallets launch have a workable path to July 2027.

Connect to Trinsic’s sandbox environment now and begin testing identity acceptance flows for your primary EU markets. Identify which customer segments require EDD treatment and configure assurance requirements accordingly. Prepare for Wallet Relying Party registration now: national registers open from 24 December 2026, and registration is the step that takes the longest.

As EUDI Wallets launch, move from sandbox to production testing in the markets where national wallets are furthest along, such as Italy (IT-Wallet), France (France Identité), and Denmark (AltID). That’s your live validation window: real users, real wallets, before the compliance deadline.

Through 2027, expand production acceptance as other member states’ wallets come online. Finland, Estonia, the Netherlands, and Sweden have published timelines that run into 2027 and beyond, and regulated businesses such as banks must accept EUDI Wallets by 24 December 2027.

By July 10, 2027, you have months of real-world operational data behind you. Your infrastructure has been tested in production, not rushed into production.

The organizations that start in Q2 2027, when the deadline is visible from where they’re standing, will get there. But they’ll spend the first year under AMLR managing what the early starters have already resolved.

To explore AMLR-compliant identity acceptance and connect with our team, visit trinsic.id or reach out at hello@trinsic.id. Sandbox access is available today.

Related from Trinsic: explore digital identity verification by country, including Austria, Belgium, Denmark, and Estonia.

Updated November 2026 to reflect AMLA’s draft technical standards, the Transfer of Funds Regulation, and current EUDI Wallet timelines.

Ben Cejvan

Marketing @ Trinsic

Ben Cejvan leads marketing and content at Trinsic, where he writes about digital identity and the shift toward a global identity acceptance network. He is focused on making the case for why businesses should start accepting digital IDs today.

Newsletter

Subscribe to weekly insights and updates in the digital ID ecosystem.

sphere background icon