How are onboarding documents protected?
Every document is encrypted under a managed key, in transit and at rest, and each merchant's files sit in storage reserved for that merchant rather than a shared pool. The data read out of a document carries the same encryption as the document.
In detail
Onboarding handles some of the most sensitive data a payment operator touches: identity documents, ownership structures and bank details. Every document is encrypted under a managed key, in transit and at rest. The platform applies the encryption by default, so no reviewer or merchant has to switch it on.
Each merchant's files sit in storage reserved for that merchant rather than in a shared pool. The separation comes from how storage is built, not from a permission rule layered on top. The information read out of a document carries the same encryption as the document itself, so the scan and the extracted field are protected alike.
Further controls
- Onboarding data stays on European infrastructure, a setting visible in your program configuration for due diligence questions.
- Retention is set per program, and documents are removed on schedule, with the removal logged.
- Every version of a document stays on record, with who reviewed it and when.
- Documents shared with a payment partner travel inside the platform, with a sender, a recipient and a timestamp.
NORBr is built under EU Regulation 2016/679. Keeping documents in the platform also removes the usual leaks of a KYB process, where files end up in email threads, chat apps and personal drives as soon as a partner asks a follow-up question.