Automating Polish UBO Checks: How to Query CRBR Without an Official API If you build AML/KYC pipelines for European markets, you've probably hit this wall: Poland's Central Register of Beneficial Owners (CRBR) has no public API. No REST endpoint. No SOAP service. Not even an FTP dump. Yet Polish law requires obligated institutions - banks, fintechs, law firms, crypto exchanges - to verify beneficial owners for every business relationship. And with the EU's 6th Anti-Money Laundering Directive tightening UBO verification requirements across all member states, manual lookups don't scale. Here's how to automate CRBR queries programmatically. CRBR (Centralny Rejestr Beneficjentow Rzeczywistych), operated by Poland's Ministry of Finance at crbr.podatki.gov.pl, holds structured UBO data for Polish-registered entities: Beneficial owner names (natural persons with >25% ownership or control) Citizenship and country of residence Nature of control (direct shareholding, indirect control, senior management) Ownership percentage range Company identifiers (NIP, KRS number, legal form) Declaration compliance status The registry covers general partnerships, limited partnerships, limited joint-stock partnerships, joint-stock companies, and limited liability companies. Civil law partnerships and sole proprietorships are exempt. Filing is mandatory within 7 days of company registration, with penalties up to 1 million PLN (~220,000 EUR) for non-compliance. The official portal lets you search by NIP (Polish tax ID) or KRS number. You type in an identifier, solve a CAPTCHA, and get one result. For a single due diligence check, that's fine. For a fintech onboarding 50 businesses per day? That's two hours of manual lookups. For a bank running periodic reviews on 5,000 corporate accounts? That's a team of people doing nothing but CRBR searches. And under AMLD6, obligated institutions must update UBO data actively - not just at onboarding but continuously throughout the business relationship. MGBI is Poland's dominant legal information provider. Their subscription gives you access to CRBR alongside other registries (KRS, KRZ, MSiG). The downside: you're paying a flat monthly fee regardless of query volume. If you only need 20 UBO checks per month, you're overpaying. If you need 5,000, the subscription tiers get expensive fast. CRBR's web portal uses standard HTTP with some session management (CSRF tokens, ASP.NET viewstate). Technically, you could build a scraper that: Requests the search page, extracts the CSRF/verification token POSTs a search with NIP/KRS Parses the HTML result table for UBO data The challenge: CRBR's anti-automation measures, CAPTCHA requirements, and the Ministry's willingness to change the portal structure without notice. Maintaining a scraper against a government portal that can change its HTML structure at any time is an ongoing engineering cost. CRBR Beneficial Owners Scraper on Apify Store provides a maintained, API-accessible wrapper around the CRBR portal: Pricing: $0.03 per result on the Free plan $0.02 per result on GOLD+ $0.025 actor start fee For context: 100 UBO checks cost $3.00-$3.25. 1,000 checks cost $20-$30. No subscription, no minimum. Input format: { "searchQueries": [ { "nip": "5252002340" }, { "krs": "0000016702" } ], "proxyConfiguration": { "useApifyProxy": false } } Output for a single company: { "query": { "nip": "5252002340" }, "company": { "name": "EXAMPLE SP Z O O", "nip": "5252002340", "krs": "0000016702", "legalForm": "SP Z O O", "declarationStatus": "Zgloszono" }, "beneficialOwners": [ { "fullName": "JAN KOWALSKI", "citizenship": "Polska", "residenceCountry": "Polska", "controlNature": "Wlasciciel bezposredni", "ownershipPercentage": "Powyzej 50%", "isAlsoSeniorManagement": false } ] } Integration via Apify API: import requests APIFY_TOKEN = "your-token-here" ACTOR_ID = "wOcPC7vYzfCkB62pG" # Start a run resp = requests.post( f"https://api.apify.com/v2/acts/{ACTOR_ID}/runs", params={"token": APIFY_TOKEN}, json={ "searchQueries": [ {"nip": "5252002340"}, {"nip": "5272520115"} ] } ) run_id = resp.json()["data"]["id"] # Poll for results import time while True: status = requests.get( f"https://api.apify.com/v2/acts/{ACTOR_ID}/runs/{run_id}", params={"token": APIFY_TOKEN} ).json()["data"]["status"] if status == "SUCCEEDED": break time.sleep(5) # Fetch results results = requests.get( f"https://api.apify.com/v2/acts/{ACTOR_ID}/runs/{run_id}/dataset/items", params={"token": APIFY_TOKEN} ).json() for r in results: for bo in r.get("beneficialOwners", []): print(f"{r['company']['name']}: {bo['fullName']} ({bo['controlNature']})") Factor Manual Portal MGBI Apify CRBR Actor Cost Free 200-500 PLN/mo $0.03/result Scale 1 at a time Bulk (subscription) API-driven, any volume Integration None Limited REST API, webhooks, datasets UBO detail Full Full Full Maintenance None Vendor-managed Actor-maintained Fintech KYC pipeline: A payment institution in Warsaw runs CRBR checks automatically during onboarding. New company applies -> system queries CRBR by NIP -> UBO data feeds into the risk scoring model. Zero manual intervention. Periodic review automation: A bank's compliance team runs batch CRBR checks quarterly on its entire corporate portfolio. Any change in UBO structure triggers a review workflow. The alternative - assigning analysts to manually re-check every account - doesn't scale past a few hundred entities. Cross-border due diligence: An international M&A advisory firm needs UBO data on Polish acquisition targets. Instead of relying on self-reported ownership structures, they pull CRBR data directly for verification. Important caveat: under AMLD5/6, institutions cannot rely solely on beneficial ownership registers. CRBR shows registered UBOs, but: Registration gaps exist (not all entities file on time) Complex multi-tier ownership structures may obscure true UBOs CRBR data reflects declarations, not verified facts CRBR automation should feed into - not replace - your broader risk-based KYC approach. Corroborate register data with client-provided information, and flag discrepancies. Poland's CRBR is an essential data source for any AML/KYC pipeline covering Polish entities. The lack of an official API is a real obstacle - but not an insurmountable one. Whether you build your own scraper (engineering cost), subscribe to MGBI (fixed monthly cost), or use pay-per-result automation (variable cost), the key decision factor is your query volume and integration requirements. For most teams building compliance automation: start with pay-per-result, measure your actual volume for 2-3 months, then decide if a subscription makes more financial sense. The CRBR Beneficial Owners Scraper is part of the European Business Data Suite - 14 actors covering Polish, Spanish, Austrian, and French government registries, all pay-per-result with no subscription.