Privacy-first financial protocol tools
Bite Apps builds utilities for trading-support engineers, FIX onboarding teams, treasury and finance ops who can't paste production logs or bank statements into cloud tools. Every tool runs entirely in your browser — nothing is uploaded, and you can prove it in DevTools.
Small, focused, and built from years of reading other people's FIX logs at 3 a.m.
Client-side FIX protocol log analyzer, custom dictionary validator and log anonymizer.
Client-side ISO 20022 and SWIFT MT bank-statement converter and payment-file validator, for the move from MT940 to camt.053.
camt.053 / camt.052 / camt.054, MT940 and BAI2 → Excel / CSVBAI2 control totals and record counts checked and recalculatedpain.001 from an Excel / CSV payment list (checked against the official XSD)pain.001 and pain.008 checks: counts, control sums, IBAN/BIC, decimals, SEPA rules, mandates, creditor identifierpain.002 reject reports decoded and matched to your payments; fix & anonymize payment files with recalculated control sumsClient-side NACHA ACH file viewer, validator and anonymizer for payments, payroll and fintech support teams.
Client-side validator for the DORA Register of Information — the annual register of ICT third-party arrangements that EU financial entities file with their competent authority.
.zip packageThe specs we keep open while building the tools — one page each, no sign-up.
Check digits for IBANs, BICs, LEIs, ABA routing numbers, SEPA creditor IDs, RF references, ISINs, CUSIPs and SEDOLs — paste a whole column; nothing is sent.
Nacha rule dates, Swift's camt/MT9xx and E&I milestones, Instant Payments Regulation, DORA and EBA reporting — each with its source.
All FIX 4.2 / 4.4 tags with types and values, and every MsgType with its required fields.
SessionRejectReason (373), BusinessRejectReason (380), OrdRejReason (103), CxlRejReason (102) — meanings and causes.
Logon failures, “MsgSeqNum too low”, ResendRequest and SequenceReset gap fill, heartbeats — symptoms, causes and fixes.
Portal, accepted format, ZIP file name and window at BaFin, the Central Bank of Ireland, CSSF, AFM, DNB and FMA — with sources.
Every MT940 field, the :61: statement line subfield by subfield, and the German and slash-coded :86: formats.
Where every MT940 field lands in camt.053.001.08 — balances, :61: with reversals, :86: parties and remittance — plus BAI2 to camt.053.
The status codes and 147 reason codes from AC01 to UPAY: what the bank means and what to check in your pain.001 or pain.008.
Every BAI2 record field by field, how the 49 / 98 / 99 control totals and record counts are calculated, and all 469 type codes.
All purpose and category purpose codes for pain.001 and pacs.008, with the official definitions.
Every permitted domain / family / sub-family combination of the camt.053 BkTxCd, such as PMNT-RCDT-ESCT.
All external code lists — reasons, local instruments, service levels, clearing systems — from the latest quarterly publication.
Exact positions of every field in the 94-character ACH records, plus entry hash and blocking rules.
R01–R85 and C01–C69 with meanings, return windows and the Nacha return-rate thresholds.
Your Nacha unauthorized (0.5%), administrative (3%) and overall (15%) return rates from a debit count and pasted return codes.
All 15 register of information templates, every field code, key, reference and allowed value.
Why registers get rejected: package checks, empty keys (805), broken references (807, R1–R22), formats and EBA rules — with fixes.
Synthetic FIX logs, MT940, camt.053 and BAI2 statements, pain.001, pain.008 and pain.002 files, NACHA ACH files and DORA registers — clean versions and versions with documented mistakes. CC0.
Execution logs and bank files carry account numbers, CompIDs, credentials and client positions. Most NDAs and compliance policies forbid sending them to third-party servers — including AI chat tools.
Parsing, validation and conversion run in JavaScript inside your browser tab. Files never touch a server, and the tools keep working offline once loaded.
No analytics, no telemetry, no cookies, no accounts. A Pro license is checked against Polar only when you activate it — your data is never part of that request.
Open DevTools → Network and process a 10 MB log: zero requests. Each tool ships a strict Content-Security-Policy that blocks every other destination.
When a tool is not enough, hire the engineer who built it — one person, fixed scope, no agency overhead.
Stuck on a FIX onboarding, a bank-format migration or a DORA register that keeps getting rejected? I'm the engineer behind SafeFIX, SafeCAMT, SafeACH and SafeDORA, and I take on small, well-defined projects in the same areas. Tell me what you need at support@biteapps.cc and you'll get a fixed quote, usually within a day.
Describe your project