Compliant Stablecoin On-Ramps: AML Screening for EURR, USDC, EURC

TL;DR — Regulated stablecoin rollouts like Revolut's EURR force you to screen deposits at credit time, not after. This guide shows how to combine Verify Address AML screening with real-time Blockchain Events webhooks to check every EURR, USDC, and EURC deposit against sanctions and risk data before you credit an account, across the chains those assets settle on.

The problem

Revolut has started rolling out EURR, a euro stablecoin issued through Bridge as a regulated issuer, per The Defiant. When a regulated fintech adds a euro or dollar stablecoin on-ramp, the compliance obligation lands on the platform team, not the issuer. Under the EU's Markets in Crypto-Assets (MiCA) regulation and the Financial Action Task Force (FATF) Travel Rule, a crypto-asset service provider must screen incoming funds against sanctions and money-laundering risk before crediting a user.

That is a build problem for the backend engineer running the deposit pipeline. A user sends EURR on Ethereum, USDC on Solana, or EURC on Base. Your service detects the transfer, then has seconds to decide: credit the balance, hold for review, or reject. Screening the sender address after the deposit is already spendable defeats the purpose. The screening call has to sit inline with deposit detection. This is the layer the stablecoin news never covers.

What you need

• A Crypto APIs account and an API key. The free crypto api tier requires no credit card.
• A registered webhook endpoint that can accept POST callbacks and respond fast. Slow acknowledgement causes retries.
• The token contract addresses you accept: USDC and EURC on Ethereum, Base, and Solana; EURR on the chains your issuer supports. Verify each contract before trusting a transfer.
• A decision matrix for AML results. You must define what risk level triggers a hold and who reviews it. This is the hard part, and it is a policy question before it is a code question.

Two products carry the workload: blockchain events for real-time token transfer detection, and the AML endpoint for address screening. Screening across chains means you standardise one workflow rather than one per network. We covered the per-chain trap in AML address screening across 17 chains before you credit a deposit.

How it works

Register a token transfer webhook for each address that receives stablecoin deposits. The callbackUrl receives a POST the moment a confirmed token transfer touches the address. Create the subscription with a POST to the confirmed token transactions endpoint:

POST https://rest.cryptoapis.io/blockchain-events/ethereum/mainnet/address-tokens-transactions-confirmed
Content-Type: application/json
x-api-key: YOUR_API_KEY

{
  "context": "eurr-deposit-monitor",
  "data": {
    "item": {
      "address": "0xYourDepositAddress",
      "allowDuplicates": false,
      "callbackSecretKey": "your-shared-secret",
      "callbackUrl": "https://your-service.example/webhooks/deposits"
    }
  }
}

When a deposit arrives, the callback carries the sender address and the token contract. Take the sender address and screen it before crediting. The AML screening call is a single GET:

GET https://rest.cryptoapis.io/aml/addresses/0xSenderAddress
x-api-key: YOUR_API_KEY

The response returns risk assessment data for the address. Read the risk indicators, apply your decision matrix, and only then credit the balance. If the address exceeds your risk threshold, route the deposit to manual review instead of releasing funds. For a full walkthrough of the webhook side, see monitoring blockchain addresses with webhooks.

The same pattern applies to USDC and EURC on Solana. Swap the path to the Solana network and screen the counterparty address returned in the transfer callback. Screening runs against the address, so the workflow stays identical regardless of which regulated stablecoin the user sends.

You can also screen a specific transaction hash rather than an address using GET /aml/transactions/{blockchain}/{transactionHash}, which is useful when you want to assess the transfer that funded a deposit rather than the sender's full history.

What to watch for

Verify the token contract on every callback. A webhook fires on any token transfer to the watched address, so a scammer can send a lookalike token and trigger your credit logic. Match the contract address in the payload against your allowlist for EURR, USDC, and EURC before you treat the deposit as real. Use GET /contracts/evm/{blockchain}/{network}/{contractAddress}/token-details to confirm symbol and decimals.

Respond to the webhook fast and screen asynchronously. Acknowledge the callback, then run the AML check in your job queue. Blocking the HTTP response on a screening call risks retries and duplicate processing. Set allowDuplicates to false and key your credit logic on the transaction hash so a redelivered callback does not double-credit.

Confirmations matter for finality. Screening a sender before the deposit transaction has enough confirmations exposes you to reorg risk on some chains. Use the confirmed event, and for high-value deposits consider the each-confirmation variant to track depth before release.

Screening is a snapshot, not a guarantee. Sanctions lists and risk data change. A sender that clears today can be flagged tomorrow. Log every screening result with a timestamp so you can prove what you knew at credit time under a MiCA or FATF audit. Privacy layers complicate this further, as we noted for shielded transfers in the Starknet STRK20 privacy layer analysis.

Regulated stablecoin on-ramps push the compliance work onto your deposit pipeline, and screening has to happen inline. Pair Verify Address AML screening with Blockchain Events webhooks to check every EURR, USDC, and EURC deposit across chains before you credit a balance. Start on the free tier and review the pricing once your volume grows.