GCLE study materials
GCLE study resources

Meridian Pay: A 91% Sanctions Hit, a Held Payment, and Fourteen Round-Number Transfers

GCLE · Put your knowledge to work in context.

All case studies

Meridian Pay: A 91% Sanctions Hit, a Held Payment, and Fourteen Round-Number Transfers

Meridian Pay is a UK payment institution settling for online merchants. The compliance analyst escalates a merchant, Al-Rashid Trading FZE, registered in Sharjah. Automated screening against the consolidated list returns a 91% name similarity to a designated individual; the date of birth differs by three years and the listed person is an individual, not a company. Over the last 60 days the merchant received 14 incoming transfers, each USD 9,650, from 11 different originators, converted them to cryptocurrency within 48 hours, and sent funds to a wallet in a jurisdiction with no virtual-asset regime. A payment of USD 9,650 is currently held. The relationship manager calls it a 'good client' and asks compliance to release it. The board wants to know the firm's exposure.

1. Should Meridian release the held payment? Set out how the screening hit should be resolved and what legal basis, if any, supports refusing or delaying the payment.

Read the worked answer

Separate two questions that are being blurred: sanctions and suspicion.

1. Sanctions hit. A 91% name score is a candidate match, not a designation. Resolution means testing identifiers, not the score:

  • Entity type mismatch (a designated individual versus an FZE company) is strong disconfirming evidence.
  • DOB off by three years is not a match criterion here because there is no individual customer to compare.
  • Document the disposition, who approved it, and on what identifiers. An undocumented 'clear' is itself the finding.

Conclusion: no legal freeze obligation arises on these facts. The firm must not label the hold a sanctions block, because an indefinite hold without legal basis exposes Meridian to a claim from the merchant under its terms of service.

2. Suspicion, which is the real driver. The pattern is independent of the sanctions question and is worse:

  • 14 deposits clustered just below a round reporting threshold;
  • multiple unrelated originators paying the same merchant;
  • immediate conversion to crypto within 48 hours;
  • onward transfer to an unregulated jurisdiction.

That is textbook layering. The firm may refuse or delay under its own contractual terms and its AML risk appetite, with MLRO sign-off.

3. Do not release on the RM's assurance. The RM's view is not a control. Decision must sit with the MLRO, be minuted, and be reviewable.

2. What reporting obligations arise, and what may and may not be communicated to the merchant and to the relationship manager?

Read the worked answer

Reporting. The MLRO should file a suspicious activity report with the FIU promptly; the deadline is short (commonly 24–48 hours) and is triggered by suspicion, not proof. Consider simultaneously seeking a defence against money-laundering so the held funds can be lawfully frozen pending consent.

Tipping off. No disclosure to the merchant or the RM of the fact of, or content of, the report, or of anything likely to prejudice an investigation. Internally, information is on a need-to-know basis - the RM may be told 'the payment is under compliance review', nothing more.

Standard customer communications. The firm can request source-of-funds and KYC for all 11 originators, explain that verification is required, and use normal contractual notice. Asking for documents is not tipping off; naming the reason is.

Records. Retain the screening disposition, the SAR reference, the decision log and correspondence for the statutory retention period (typically five years after the relationship ends). Record-keeping is the evidence of a defensible control environment if the regulator asks later.

If the customer becomes evasive or refuses to identify the originators, that is itself further suspicion and supports exit.

3. What should Meridian do at the governance level before the board meeting?

Read the worked answer

Treat this as a systems finding, not a one-off.

  • Back-file the merchant portfolio against the same typology: sub-threshold clustering, rapid crypto conversion, high-risk corridors. Report volumes and hits.
  • Confirm the screening tool is actually tuned: 91% on a company-versus-individual comparison suggests the matching logic is not discriminating on entity type. A false-positive rate that high is a tuning defect.
  • Report to the board with a clear distinction between sanctions exposure (low on these facts) and AML control weakness (present), because the board will otherwise conflate them.
  • Confirm the MLRO has unfettered escalation and that the RM's commercial pressure is not able to override a hold. If it can, that is the headline risk.
  • Consider exit and de-risking, documented with reasons; note that de-risking decisions should not be made on protected characteristics.
  • Remediation plan with owners and dates; a regulator will ask what changed.