The version that was signed is the version that stands.
Loan agreements, account mandates and settlement confirmations are sealed at execution. When a dispute surfaces years later, the bank proves exactly which version was signed, and that nobody has touched it since.
What gets sealed
Sealed at execution, so the signed terms are fixed the moment ink dries, including every annex and rate schedule.
Who may instruct on an account, sealed when the mandate is accepted, provable when an instruction is challenged.
Trade and payment confirmations anchored at issuance, so back offices reconcile against records nobody can restate.
How it runs day to day
Your document system calls POST /v1/seal when a contract is executed.
The digest is batched, MPC-signed and anchored on RoxChain within the normal pipeline.
The proof is filed alongside the loan in your DMS, a few kilobytes.
In any later dispute, the file plus proof verifies against the chain in front of the counterparty.
A borrower claims the rate schedule was different at signing. The bank produces the sealed agreement and its proof; verification shows the file is byte-for-byte the one anchored on execution day. The conversation ends there.
Without an independent seal, the same dispute becomes forensics on backup tapes, email trails and testimony about internal controls, months of cost to establish what one verification shows in seconds.