Privacy

We do not store payment files.

Payment XML is processed in memory and discarded. It is not stored as a dataset.

Validator and public API

Uploaded pain.001, from the website or from POST /v1/validate, and camt files sent to POST /v1/camt/validate or POST /v1/camt/convert, are processed in memory for that request and discarded. They are not stored as a dataset and they are not written to disk. Server logs may keep version, byte size, pass/fail, error codes, and a hash of the client IP. The XML is not logged. Rate-limit counters are kept in process memory and are cleared on restart. They are not a copy of the file.

Report download and recent checks

The downloadable report is built in your browser. It lists the file name, message type, result, and error explanations. It does not include the payment file. Recent checks stay in this browser only (file name, message type, pass or fail, and date). They are not uploaded.

Email a report

If you ask us to email the report, and email is configured, we send a summary: file name, message type, result, and the error explanations. We do not attach the payment file and we do not send the XML. We use your address for product updates only when you check that box. If email is not configured, nothing is sent and the address is not stored.

Diagnostic waitlist

The waitlist stores work email, optional company, bank, country, and bank error text (not the payment file) so we can contact you about the diagnostic.

What we never do

No bank login, EBICS, VoP, or payment initiation. We do not rewrite your XML with a language model.

Operator

Bobook Limited, Venture Hub, 136 Capel Street, Dublin 1, D01 T2C9, Ireland · Company 785764 · info@bobook.club · +353 870385414 / +34 614892688