Informally documented financial arrangements
An informal loan between individuals
Goal: organize the terms and payments of a loan already agreed. If your material is older, keep in mind that a timestamp obtained today covers the hash submitted today. Documents from the time have their own dates and their own sources of proof; the Record does not certify the date of the event or the capture.
The problem
This use is limited to documenting a significant loan already agreed by message, without a formal contract.
Prefer a written contract and proper formalization. A chat export may leave out context, and a bank transfer receipt on its own shows a transfer, not that it was a loan or what all the terms were.
Between friends and family, it's common to lend money without anything signed. The amount, the deadline and how it will be repaid sit in a message thread, and the payments appear here and there on bank statements. Over time, conversations get deleted, phones get replaced and the history is lost. When a question comes up about how much is still owed, each person has their own version.
A contract is still the best route. This use case is for documenting what already exists when the agreement was made by message.
What to preserve
A chat export or screenshots of the conversation, and receipts for the transfer and the repayments.
Goal: organize the terms and payments of a loan already agreed.
Main file: the chat export and the bank receipts.
When to capture: at the milestones of the agreement and at each payment.
Supporting sources: a contract and confirmation from both parties.
Limit of this scenario: on its own, the Record does not establish the legal nature of the money, interest or an obligation to repay.
Collect only what you need, through access you are lawfully entitled to. Use neutral file names and descriptions, store files securely and share them only with people who need them. Where it is lawful to make a redacted copy, keep it as a separate file from the preserved original and note which version's hash you registered. See the Privacy Policy.
A chat export, when the app offers one, can keep part of the available sequence, without guaranteeing it is complete. If you use screenshots, show the contact's name, the dates and the passage where the terms were agreed, without cropping. Keep the receipt for the initial transfer and for each payment made or received.
How Provenia documents this scenario
Your browser calculates the SHA-256 hash of the file you select. The file itself stays on your device: Provenia receives only the hash and metadata, meaning the file name, its size and the context fields you fill in. Provenia stores the hash and the Record data. Keep the exact file you used and the exported Dossier, because they are what make a byte-for-byte check possible later.
Three different times are involved. The time the Record was created on Provenia comes from Provenia's server and is not certified. The date of the event or capture is something you declare in the context, in the description or in the file itself, and it depends on other sources. The externally certified UTC date and time ties the hash you submitted to the timestamp authority's response; it does not certify when the event happened.
Provenia sends the hash, never the file, to FreeTSA, an external timestamp authority, which issues an RFC 3161 timestamp. Provenia validates that timestamp before the Record is completed. If FreeTSA is unavailable, or the timestamp cannot be obtained or does not validate, the Record is not created and no credit is used. Older Records created before this feature was active may have no external timestamp. A timestamp obtained today covers the hash submitted today; it is never issued later or backdated.
Each Record's timestamp is separate from the signatures on the exported Dossier: Provenia's digital signature on the PDF and the Ed25519 signature on Dossier.json. Those signatures cover the exported documents and do not certify the date of the event. See Trust and Verifiability.
In this scenario, use the chat export and the bank receipts as your reference material and check it against a contract and confirmation from both parties. The timestamp on a hash does not confirm the legal nature of the money, interest or an obligation to repay.
Step by step
- Define your goal and check that your access is legitimate, which permissions apply and whether any deadlines are running before you collect anything.
- Prefer a written contract and proper formalization. A chat export may leave out context, and a bank transfer receipt on its own shows a transfer, not that it was a loan or what all the terms were.
- Preserve the chat export and the bank receipts exactly as it is; don't edit the file you register.
- Link the material to a contract and confirmation from both parties; describe its origin and when it was captured as declared information.
- Group the milestones in a Project and register each relevant file separately. Keep the files untouched and the exported Dossier, with a secure backup.
What the Record shows and what it does not
A Record is a private electronic document that can form part of a wider body of evidence, assessed according to its context and origin. On its own, it does not establish the legal nature of the money, interest or an obligation to repay. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
What can this Record be used to check?
Whether the file you kept matches the registered hash and, where there is a valid timestamp, that the hash is tied to the UTC date and time shown. On its own, it does not establish the legal nature of the money, interest or an obligation to repay.
How should I organize the files for this case?
Use one Project per loan. Register the passage where the terms were agreed, then the initial transfer receipt, then each repayment in date order, and say in each description what the transfer was for. If you later sign a contract, add it to the same Project.
Which date is certified?
Only the UTC date and time in a valid external RFC 3161 response tied to that Record's hash. The time on Provenia's server and the event or capture date you declare are separate pieces of information. The timestamp does not certify when the event happened.
Official references
Technical reference for context only. It is not legal advice or a conclusion about any case. Provenia is not affiliated with, integrated with or endorsed by the organization listed.
- RFC 3161 — Time-Stamp Protocol (IETF)https://datatracker.ietf.org/doc/html/rfc3161
Start with three free credits
Each Record covers one file. Each completed Record uses one credit, including the first one, which creates the Project. A new account includes three free Document Credits and one Project, with no payment and no card, so the starter credits cover three single-file Records. For prices and conditions, see Pricing.
Already have an account? Log in.