On Friday morning, Juma and Halima arrived at Kelvin’s small office before the other people began coming in. The office was behind a phone-accessories shop, with one table, three chairs, and a printer crowded with paper. Kelvin stood near the window holding his phone like a man prepared to give a brief explanation.
Halima placed the printout on the table and read aloud.
“Selected withdrawals delayed. Do not encourage additional deposits until liquidity review.”
Kelvin said, “I received that message.”
“When?” Juma asked.
“Around the time we told people to stay calm.”
Halima showed him the email header. “The timestamp says Wednesday at noon. The group received your message that ‘everything was proceeding normally’ after midday.”
Kelvin sat down. “I didn’t know how large the problem was.”
“You didn’t need to know its size before stopping the encouragement of deposits,” Juma said.
Kelvin looked at his hands. “My account is locked too.”
“And you still told people to continue?” Halima asked.
“I thought it was a temporary delay.”
“You had been given a liquidity-review warning.”
“I thought the team would finish.”
Juma opened the group-chat folder. “You wrote that the earlier withdrawals proved the system. You didn’t say support had warned about new deposits.”
Kelvin stood angrily. “And what did you say? You brought people in using your withdrawals as proof.”
“Yes. That is why I came with your records, not to pretend I have no responsibility.”
Kelvin sat again. Halima asked him to open the complete email and show whether it had an attachment. Kelvin refused at first, saying it was company information. Halima did not argue.
“Then we will record that you were asked and refused,” she said.
Kelvin opened his phone. One attachment was called liquidity stabilization. It was dated the day before Juma joined the platform. The first page said withdrawals from selected accounts could be delayed while new inflows were matched. Beneath it was a notice that referral communication must not promise profit or withdrawal speed.
Juma read the line twice. It did not contain a sentence separating Kelvin from blame, but it contained an instruction that would have prevented the group message.
“Did you read it?” Juma asked.
Kelvin nodded. “I opened it.”
“And you continued telling people the system was safe.”
“I wanted to stop them from panicking.”
“Being a victim does not give you permission to create other victims.”
Kelvin closed his eyes. “I had money in it too. If I told everyone everything, they would all try to withdraw at once. I thought if I bought two days, liquidity would return.”
“You needed time,” Halima said.
“Yes.”
Juma felt anger and pity collide. Kelvin was not explaining the actions of a man who had calmly planned everything. He was a man who had entered, received signs of danger, and then chosen to look away because his own money was inside. That did not remove his responsibility.
Halima asked for an export of the entire thread, not a screenshot of the first page. Kelvin asked where it would be used.
“In the evidence bundle. We will separate fact from inference. We will not write that you stole unless we have a record of it.”
“And you will write that I kept reassuring people?”
“Yes. That is in your messages.”
Kelvin looked at Juma. “Will you say I hid it from you?”
“I will say what I knew and what I discovered. You will say it too.”
After several minutes, Kelvin sent the export to Halima’s email. She opened it immediately and checked the dates. In the thread was his reply to support: Understood, will keep users calm. The reply came several hours after the warning, not before it.
“I wrote that because I wanted time to ask for clarification,” Kelvin said.
“Did you tell people not to make new deposits?” Juma asked.
“No.”
“Why not?”
“Because I was afraid the group would collapse.”
“The group was not more important than the people.”
Kelvin fell silent. Halima asked him to write a short statement: when he received the warning, what he did after receiving it, and what messages he sent to users. Kelvin wrote by hand, got the date wrong, and began again. Juma did not correct him until Kelvin asked.
Before they left, Kelvin asked Juma whether he still told people his withdrawals were proof.
“No,” Juma said. “Now they are transactions I received. They do not prove the source of the payout, the safety of the system, or anyone else’s future.”
Kelvin looked at him as if he had heard something new. “So you don’t believe anymore?”
“I believe records more than stories.”
Halima closed the laptop. “We’ll place your statement beside the email. You will review it before we attach it to the complaint. If you refuse to sign, we will record that you were given the chance and did not sign.”
Kelvin lifted his eyes. “I’ll sign.”
Juma did not feel victorious. Kelvin had changed from a man who rejected them into a witness with interests and his own weakness. That made the record heavier, not easier.
Outside, Halima sent Juma a copy of the attachment. Its heading said liquidity stabilization, but its date was before Juma joined. Juma wrote in his notebook: warning existed before my referral; Kelvin continued reassuring people; personal lock did not erase public responsibility.
Halima asked Kelvin not to sign under pressure, but only after reading every line. “If you believe one part is wrong, write it in the margin,” she said. Kelvin did so beside the sentence saying users had been told to stay calm.
“What did you mean by stay calm?” Juma asked.
“Don’t make all the withdrawals at once.”
“And new deposits?”
Kelvin shook his head. “I should not have left that out of the conversation.”
Juma wrote those words into the chronology, then asked Halima to read them exactly as written. He did not want a forced confession; he wanted a record Kelvin could confirm the next day without saying anger had trapped him. Kelvin corrected one date, signed, and said he could not apologize for every loss, but he could accept responsibility for the message he had sent.
At the bottom of the page, he added: The “liquidity stabilization” attachment was dated before I joined.
---