Hana, the bank officer, read Maya's request twice. “I can help retrieve transaction history from an account where you were a signatory. I cannot tell you whether a transaction was lawful or unlawful.”
“Good. I want history and references, not a verdict.”
In a small glass service room, Hana showed when the account's operating instructions had changed. Two months before the first closure request, the confirmation threshold had been lowered. Maya remembered approving a “simplification” because her mother was ill and she was exhausted by calls for household payments.
“That approval doesn't mean you approved every transfer afterward,” Hana said. “But it changed how the account operated.”
Maya wrote both facts down.
The visible history showed a pattern she had missed on the app: several smaller payments preceded the large one. Contractor, supplier, delivery, then the final transfer. Individually, the amounts were small enough to disappear among family expenses.
“Can the archive show who initiated each?”
“For some transactions, maybe. Beneficiary, narrative, posting date, sometimes channel. Don't expect every field.”
Maya added those limits to the request. She also found an old email in which she had clicked `approved` on the threshold change. She did not erase her own role simply because the later use troubled her.
Hana advised her to request the complete three-month archive before settlement rather than one dramatic line. It would cost a retrieval fee and take several days. Maya signed.
She decided not to close the account until the archive arrived and the last scheduled charges were moved. Emotional closure could wait. Destroying access to a ledger before reconciliation would be foolish.
As Hana prepared the request, Maya built a chronology: app anomaly, public contractor address, physical observation, 4C invoice, archive request. The word *affair* did not appear once. Strangely, the file still felt heavy.
Omar called while Maya stood in the lobby. She let it ring out and later texted: *I'm verifying records from the old account. I'll send specific questions when I have the documents.*
Back in the service room, Hana briefly opened the detail view for the largest transfer. The ordinary statement had truncated the narrative. The internal view did not.
Maya copied the words exactly, then backed up the stamped retrieval receipt.
Hana printed a receipt for the archive request and explained that old transaction fields might arrive in several batches. Maya asked how a later reviewer could tell the data came from the bank rather than from a spreadsheet she had assembled herself. Hana showed her the request number and statement identifiers, and Maya added them to the evidence index. She also wrote down what the archive might *not* contain: a beneficiary reference was not the same thing as an explanation of authorization. The discipline was tedious, but it prevented a future argument in which Omar could dismiss her chronology as something reconstructed from screenshots without source records.
Maya also asked Hana whether keeping the account open during retrieval created any risk of new discretionary transfers. Hana checked the mandate and confirmed the account was effectively dormant except for scheduled charges Maya was already moving. Maya documented that answer. The point was practical: preserving access to history did not mean leaving a live financial channel open for either former spouse to use casually.
The transfer reference read: “deposit unit 4C.”