IBAN- and payment-instrument-level risk intelligence delivered as an API

IBAN- and payment-instrument-level risk intelligence delivered as an API. Each IBAN is scored beyond format validation across issuing country, issuing bank and behavioural risk signals to produce an onboarding risk verdict; a companion transaction-scoring API scores each payment in flight for mule patterns such as rapid multi-source inflows and fan-in/fan-out shaping. The asset behind the scores is a continuously-maintained risk profile per issuing institution and per country corridor, plus the accumulated labelled decisions: which banks and IBAN ranges produce mule accounts, which onboarding attempts were blocked, flagged or suspended, and the realised outcome of each action. Framing on the page: a FATF-documented rise in use of online-only institutions for laundering, and neobank susceptibility driven by rapid account creation, minimalist digital verification, cross-border reach and growth-driven removal of onboarding friction

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Greip and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Financial Exchanges & Data
Instruments: equitiesfx
Categories: AlternativeReference

Dataset card

Type: not stated
Format: Tabular / API (JSON risk scores and signals per IBAN and per transaction) + Text (risk rationales, mule-typology documentation, a structured fraud-term dictionary the site maintains)
Volume: Large where it matters and enumerable: the reference layer spans the SEPA and international IBAN namespace — every issuing country and bank, so millions of distinguishable IBAN prefixes — each carrying a maintained risk profile. The transaction layer scores per payment and grows with client throughput. Request further research for the count of distinct scored issuing institutions and cumulative scored transactions
Users: N/A — developer-facing API product sold on usage; customers are integrating institutions and developers, not registered consumers. Coverage is measured in API calls and integrated clients
History: 3 years
Update frequency: not stated
Growth: Active (current blog and dictionary content targeting neobank mule fraud, live API product surface, and continuous model refinement stated as part of the method)
Launched: est. 2023 (organisation record created mid-2023 — a young UK payments-risk API vendor)
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site