Refuse the wrong money before it lands.
Every inbound credit is checked against the account holder, screened, and scored. Clean funds post in seconds; third-party and high-risk payments are returned to source with a full audit trail.
Available to verified businesses only.
Shield decision
Sample dataMost recalls start with money that should never have been accepted.
- Third-party deposits are the leading cause of recalls, disputes and banking-partner escalations.
- Manual screening does not scale and leaves gaps.
- Banks want evidence of controls, not assurances.
The decision pipeline
Received
The credit arrives at the pooled account.
Attribute
It is matched to the virtual account by IBAN.
Name check
Payer name vs account holder; result exact, close, no_match or unavailable.
Screening
Sanctions, PEP and adverse-media screening on the payer.
Rules
Amount limits, velocity, payer country, first-party rule, custom client rules.
Decision
accept → settled · review → held for analyst · return → sent back to source.
Everything you need, nothing you have to build.
Payer-name verification
Fuzzy matching tolerant of legal suffixes (B.V., GmbH, Ltd), accents and word order.
First-party-only mode
Return any credit whose payer isn't the account holder. On by default.
Sanctions & PEP screening
Screening on every payer against global sanctions, PEP and adverse-media lists, refreshed daily.
Velocity & limit rules
Per-account and per-payer limits over time windows.
Country controls
Block or review payments from chosen payer countries.
Review queue
Analyst queue with evidence, notes and one-click accept/return.
Recall workflow
Inbound recall requests open a case; NEO's team contacts the end user and responds within the bank's stated timeline.
Partner reporting pack
Monthly volumes, return rate, recall ratio and corridor breakdown, signed off by NEO's MLRO.
Name-match examples
| Payer name | Account holder | Result |
|---|---|---|
| Kestrel Logistics GmbH | Kestrel Logistics GmbH | Exact |
| Alder and Finch S.A.R.L. | Alder & Finch SARL | Close (96%) |
| J. Marsh | Orchard Retail SAS | No match → returned |
Read your Shield rules
Idempotent POST, synchronous response, signed webhook. Full details in the API reference.
Shield supports your AML programme; it does not replace it. You remain responsible for your own regulatory obligations, and our compliance team works alongside yours.
curl https://api.neofin.tech/v1/shield/rules \
-H "Authorization: Bearer $NEO_API_KEY"{
"object": "shield_rules",
"first_party_only": true,
"name_match": {
"auto_accept_threshold": 0.92,
"review_threshold": 0.70
},
"screening": { "sanctions": true, "pep": true, "adverse_media": true },
"limits": {
"max_credit_amount": 5000000,
"daily_per_payer": 20000000
},
"payer_countries": { "mode": "allow", "list": ["EEA", "GB", "CH", "CA"] },
"updated_at": "2026-11-01T09:30:00Z"
}{
"id": "ev_5Tq94",
"type": "credit.returned",
"created_at": "2026-11-05T15:41:07Z",
"data": {
"id": "cr_7Pq1nW",
"collection_account": "ca_4Rt8KpL",
"external_ref": "mch_2A7D55",
"amount": 480000,
"currency": "EUR",
"rail": "sepa",
"payer": { "name": "J. Marsh", "iban": "FR14 •••• •••• •••• 0606 10", "country": "FR" },
"shield": {
"name_match": "no_match",
"score": 0.08,
"screening": "clear",
"decision": "return"
},
"return_reason": "third_party_funds",
"returned_at": "2026-11-05T15:41:07Z"
}
}Questions we get about Shield.
Is Shield an extra cost?
No. It is included on every plan.
Can I turn off first-party-only?
Only for approved use cases with documented justification, reviewed and signed off by our compliance team.
How are false positives handled?
Close matches can be auto-accepted above a threshold you set, or routed to review.
Who handles recalls?
NEO's recall team, with your input where needed.
Does this replace my own AML programme?
No. It supports it. You remain responsible for your own obligations.
Issue your first virtual IBAN this week.
Sandbox access is immediate. Live accounts follow KYB review of your business.