Custody, on the record.
How the house verifies, isolates and — when it must — restricts. Filed as clauses, kept as practice.
Verification before volume
Identity, formation and address documents are filed before a desk opens. Approvals create the login; nothing operates on trust alone.
Registration applications carry their own reference numbers, and documents are reviewed by administrators — never auto-approved.
One ledger per customer
Customer data is isolated at the desk: accounts, cards, transfers, bills and tickets are served per customer session and never mixed across entities.
Sessions expire on their own clock; an expired desk returns to the sign-in sheet rather than a stale screen.
Passwords with a spine
Desk passwords require ten characters across upper case, lower case, numerals and symbols, confirmed twice at enrollment and stored only as salted scrypt digests.
Drafts saved during application exclude passwords and files — those exist only in the open page until submission.
Documents, gated at upload
Verification files are accepted as PDF, JPG or PNG only, capped at ten megabytes each, checked before they ever leave the browser.
Restriction, stated plainly
When a compliance review opens, a desk is restricted: functions suspend, the notice is shown before anything else, and the review team completes its assessment before service resumes.
Failed amounts follow the same honesty — struck through in the day-book, excluded from every total, still visible for the record.
Controls you can point at
Card budgets, single-purchase limits and region rules are printed on each card record. Wire instructions and daily limits are printed on each account record. Security settings carry their current value and an action — no hidden defaults.
Filed by the Solvanepay controls desk. Questions on any clause may be directed to the correspondence desk.
Write to the desk