Bulwark screening only ever sees a canonical, ISO 20022-shaped party. Everything source-specific — the file format, the transport, the field mapping — lives in a thin adapter. That means the formats and channels your bank already produces are how you onboard: upload a sample, watch it parse, map the columns, and go live.
Each adapter is a pure parser with fixtures and unit tests, built against public specifications. No partner enrollment required to start — these are the no-partner wedge.
94-character fixed-record ACH files; entries mapped to transactions with originator + receiver parties and addenda narrative.
Cash-management statements; type-16 detail records become transactions, text fields preserved as remittance.
SWIFT statement / interim statement messages; :61: lines with :86: narrative kept verbatim.
ISO 20022 bank-to-customer statement; entries and transaction details mapped to structured Debtor / Creditor parties.
Single-message parsing for the MT set (MT103, …), pacs.008 and related ISO 20022 payment messages into the canonical party shape.
Any core's nightly extract — driven entirely by a field mapping, for subjects (roster) or transactions.
Batch SFTP still dominates core banking, so it is a first-class path — alongside upload, HTTPS, S3, API pull, and a push API with per-source keys.
Drop a sample or a batch straight into the console; auto-detect the adapter and preview the mapped rows before anything is screened.
Scheduled pull from your SFTP endpoint with host allowlisting and change detection.
Scheduled fetch from an HTTPS URL; JSON, CSV, or XML bodies reuse the same parsers.
Pull the latest object by key or prefix; conditional skip on unchanged ETags.
Configurable auth (bearer / header / basic / none) with optional pagination, host allowlist, and retry semantics.
Send records to us with per-source keys — shown once, hashed at rest, scoped, and rotatable.
For teams that want to call screening directly, a partner API returns the interdiction verdict contract every payments team knows — pass / hit / needs_review, with scores and matched entities, hits parked in a hold queue for maker-checker disposition, a batch re-screen path, and a documented fail-closed default. Outbound webhooks (HMAC-signed, reference-only payloads) let you write results back into your systems.
This surface is in design-partner preview — it is being built and hardened now, not generally available. We onboard design partners against realistic fixtures and a conformance kit before switching it on for production traffic.
POST a canonical transaction, get a verdict with score and matched entities. Client-side timeout guidance and instant-rail (FedNow / RTP) mapping notes are documented.
Submit a file or a batch, get a job id, poll for the result summary. Dry-run first to preview parsed rows and mapped fields before anything is screened.
Decision, alert, monitoring, and batch-completed events delivered with an HMAC-SHA256 signature and a fetch-back URL — references and counts, never party names.
Certified, turnkey connectors to the major cores are in our design-partner program, not shipped certifications today. Each core certification is a dedicated partnership project on top of the framework above — which is precisely why the framework exists: every new core becomes one adapter plus one certification, not a rebuild. If you run one of these cores and want to be a design partner, we want to talk.
Tell us what your core emits and how it travels. We'll map it to the canonical model and — for design partners — turn on the screening API and webhooks against your fixtures.