paypreflight
Validates payment batches against SEPA rules, including character-set compliance, amount notation, zero/negative/oversized amount checks, EUR requirements for euro credit transfers, and SEPA-scope hints.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@paypreflightcheck suppliers.csv for IBAN and SEPA issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
paypreflight
Pre-flight checks for an EU payment run. Audit a CSV, JSON or ISO 20022 pain.001 batch before it goes to the bank — while a wrong IBAN is still a spreadsheet problem and not a payment recall. IBAN checksums (116 countries), SEPA character set and amount rules, VAT number structure (28 areas), duplicate end-to-end references, declared-versus-actual control sums.
Runs entirely on your machine. No account, no upload, no telemetry — the package has no network code at all. The file being checked is a creditor list; being able to check it without sending a copy to a third party is the point.
npm i -g paypreflight
paypreflight check suppliers.csv
paypreflight fix suppliers.csv --out suppliers-fixed.csv --licence PPF1.…
paypreflight iban GB82WEST12345698765433
paypreflight vat DE136695976What it checks
Area | Examples |
IBAN | ISO 7064 MOD 97-10 checksum, country length and structure (116 registry countries), bank-code extraction, repair suggestion when only the check digits are wrong |
SEPA | EPC character-set offences ( |
Run level | duplicate end-to-end references, declared control sum vs. computed sum, number of transactions vs. header |
VAT | structure per country (28 areas) — offline only; live registration is VIES's job and the tool says so |
pain.001 | the same rules against XML batches, plus GrpHdr control-sum verification |
Exit codes are the CI contract: 0 clean, 1 findings at/above --fail-on,
2 usage/limit error (a row cap is a refusal, never a silent truncation), 3
a paid feature without a licence.
Related MCP server: Fintom8 E-Invoice MCP Server
The fix command (Pro)
check is free and stays free. fix goes further: it rewrites the run —
repaired check digits (re-verified before writing), canonical amounts, names
stripped to the EPC character set — and emits a change log alongside the
corrected file. Anything a machine should not guess (missing IBAN, zero amount)
is left for a person and listed.
paypreflight fix run.csv --out run-fixed.csv # free: full diff, exit 3
paypreflight fix run.csv --out run-fixed.csv --licence PPF1.xxx.yyyGet a Pro licence (€49/year): buy on Stripe — the offline key is emailed to you within 24 hours.
Licensing (offline)
A licence is verified offline with an HMAC over its payload: the key carries its entitlement, so the tool never phones home. Free tier: 5,000 rows, full diagnostics. Pro: unlimited rows + corrected-file output. The secret lives only with the issuer:
PAYPREFLIGHT_LICENCE_SECRET=… node tools/mint-licence.mjs \
--tier pro --expires 2027-09-17 --seats 5 --holder "ACME GmbH"Honest limits, stated in lib/licence.js: keys can't be revoked before expiry,
and a determined user can patch the check out — this is a fair-use mechanism
for businesses that want to pay for what they rely on, not copy protection.
MCP server
The same engine speaks MCP over stdio, so AI agents (Claude Desktop, Cursor, Cline…) can run the checks:
paypreflight mcp # prints the config snippetBrowser tool
node tools/build-site.mjs builds site/ — a fully client-side page that
audits and fixes files in the browser. Same privacy promise: no upload path
exists. Deploy site/ to any static host.
Development
npm test # node --test, zero dependencies
npm run lint:fixtures
npm run port # regenerate data/ from the registry sources
npm run siteEngine MIT-licensed. Data files derived from the SWIFT IBAN Registry (ISO 13616) and EPC/EC documentation.
This server cannot be deployed
Maintenance
Related MCP Connectors
EU compliance checks for AI agents: sanctions, company, VAT ID, IBAN, email. Pay per call.
Pre-payout IBAN screening for AI agents: validation, sanctions, Swiss clearing, risk scoring
Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.
Validate EU, UK, AU VAT numbers for AI agents. EU ViDA e-invoicing compliance.
Related MCP Servers
- AlicenseAqualityAmaintenanceIBAN validation across 89 countries, BIC/SWIFT and Swiss clearing lookup, batch validation, payment-reference, postal-address and Swiss QR-bill checks for AI agents. Connect via MCP or the REST API. Includes free quotas, paid credits and a Pro subscription. SEPA and country-risk indicators support payment-data checks; they do not confirm account ownership or replace beneficiary AML/KYC screening.13123 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables autonomous agents to validate, audit, and correct e-invoices against European standards (EN16931) and Peppol regulations.1MIT
- AlicenseAqualityDmaintenanceVerified validation of structured identifiers — IBAN, payment cards, ISBN-13 and VIN — for AI agents. Runs the real checksum algorithms (mod-97, Luhn, mod-10, ISO 3779) instead of letting the model guess, and returns structured results with clear errors.425 npmApache 2.0

Qinisoofficial
AlicenseAqualityDmaintenanceThe deterministic fact-verification layer for AI agents. Validates the structured facts an agent emits — IBANs, payment cards, VAT and national tax IDs, crypto and bank addresses, domains, emails, phone numbers, securities and academic identifiers, plus dates, currencies and holidays — against checksums and curated authoritative data, not guesses.561Apache 2.0