How NESVRA screens every transfer without slowing you down

Compliance and speed are usually framed as opposites: the more you check, the slower you get. We don't think that's actually true if the screening is designed well — it's true if screening is bolted on as an afterthought. Here's what actually happens in the roughly 400 milliseconds between you pressing send and your transfer being cleared.

Screening happens in parallel, not in sequence

Sanctions list screening, transaction pattern analysis and device/behavioral fraud checks all run at the same time against a transfer, not one after another. Most transfers clear all three simultaneously well within a second. The transfers that get held aren't slowed down by a queue — they're the small minority that trip a specific rule and need a human or an additional document.

What actually triggers a hold

• A name or entity partially matching a sanctions or watchlist entry, pending manual review
• A transaction pattern meaningfully different from a customer's typical sending behavior
• A first-time high-value transfer to a new recipient in a higher-risk corridor
• Device or account signals consistent with known fraud patterns

When a hold happens, we tell you clearly on the tracking page rather than leaving a transfer in silent limbo — that's deliberate. An unexplained delay erodes trust faster than an honest "we need one more document from you."

Why this matters for operators too

Every operator building on NESVRA's rails inherits this same screening pipeline automatically — you don't build your own AML program from scratch, and you don't get to skip it either. That consistency is what lets us run both our direct consumer product and Remittance-as-a-Service on the same compliance backbone without weakening either one.