Screening for BNPL.

BNPL sits in a tightening regulatory window. The EU's Consumer Credit Directive II (CCD2) brings most BNPL products fully into the credit-institution perimeter from late 2026, and supervisors are already treating BNPL as in-scope for AMLD where credit is extended. The practical consequence: every BNPL onboarding now needs PEP and sanctions screening — and the answer has to come back fast enough not to dent conversion.

The BNPL screening problem

• Volume. Mass-market BNPL routinely processes tens of thousands of new customers a day at peak retail periods.
• Latency budget. Checkout pages target sub-second response. A screening call sitting in the critical path must respond in under 200 ms p95.
• False-positive cost. Every analyst review is a delayed approval, which directly translates to abandoned carts.
• Returning customers. Many BNPL buyers are repeat users — re-screening every order would be wasteful, but blindly reusing a 12-month-old screening result is non-compliant.

Recommended pattern

1. Screen at first onboarding, with full identity payload (name, DoB, country, optional document number). Pass any threshold-clear customer instantly.
2. Skip per-transaction screening on subsequent purchases — instead, rely on continuous monitoring of the existing profile.
3. Enable ongoing monitoring for the entire active customer base. New PEP designations and sanctions adds fire a webhook within minutes; your system queues a review job and pauses risk-elevated accounts pending analyst decision.
4. Tune thresholds permissively at checkout, strictly on monitoring. The cost of a false review at checkout is high (lost conversion); the cost on a background monitoring queue is low (analyst time).
5. Capture full audit trail. Every screen, list version, decision and reviewer action — exportable for the regulator.

Sizing the cost

For a BNPL with 250,000 new customers a year, ScreeningHub's Growth plan covers all onboarding screens plus continuous monitoring of the active book at €399/month. That is <€0.02 per customer — typically two orders of magnitude below customer-acquisition cost.

How ScreeningHub fits

• Sub-200 ms p95 latency on the hot path.
• Fuzzy + transliteration matching handles the diverse-name reality of European retail customer bases.
• Webhook-driven monitoring on Growth and Enterprise.
• Configurable thresholds per API key, so checkout and back-office can run different decision strictness on the same data.

For deeper background see what is PEP screening and sanctions screening explained. Compare us with ComplyAdvantage and Sumsub.