Garang Mayom Malek

Writing

A Lesson I Have Changed My Mind About: Moving Money Is Not the Whole Job

A technically successful transfer can still leave the payer, the recipient and the institution without the answer they need.

One lesson has become increasingly important in the way I think about payment infrastructure: moving money is not the whole job.

It is easy to focus on the moment a transfer succeeds. That moment matters. But an institution and the person using its service may still have unanswered questions. What was the payment for? Has the receiving organisation recognised it? Which record proves that the obligation has been settled? What happens if the reference is wrong or the result is disputed?

I have come to see the work around the transfer as part of the payment itself.

A transfer and an institutional outcome are different

A bank or payment network can confirm that money moved. An institution may still need to connect that movement to a farmer, an invoice, a compliance process or another service obligation.

When that connection is missing, the transaction can be technically complete while the user's task remains unfinished. The person may have a receipt but still be asked to prove the payment. A finance team may see an amount but not know where to apply it. An operations team may wait because it cannot confirm the next step.

The lesson is that success must be defined from the user's task, not only from the transfer.

The reference is part of the service

A useful payment record needs context. It should connect the amount, the parties and the purpose in a way the relevant institution can recognise.

That does not mean placing unnecessary personal information into every record. It means designing the right reference, protecting access and retaining enough history to explain the outcome. If a correction is made, the record should show what changed through an appropriate audit trail.

This becomes especially important when several organisations contribute to one service. Each may hold a different part of the record. The design work is making those parts understandable together.

Exceptions reveal the quality of the system

My earlier instinct was to judge a system primarily by the normal path: the instruction is correct, the transfer is completed and the record is matched.

The harder cases taught me to look more closely at what happens when the normal path fails. An incorrect account detail, an unmatched reference or a duplicated instruction can require action by several people. If responsibility is unclear, the user experiences delay even when every organisation believes it has completed its own part.

A better design starts the exception route at the same time as the successful route. It identifies who can correct information, who can approve the change, how the user is informed and how the final outcome is reconciled.

Support is infrastructure too

Support is sometimes treated as something added after the product is built. I now think it should influence the product from the beginning.

If support staff cannot see the relevant history, the user has to repeat the story. If statuses are written only for technical teams, the user cannot tell whether to wait or act. If the organisations involved do not agree on the handover, a case can move between them without being resolved.

Clear language, a visible owner and an accessible record are therefore not cosmetic details. They are part of whether the system works.

What I would do differently now

I would begin a payment project by mapping the full institutional journey, including the difficult cases. I would ask what the person is ultimately trying to complete, what record each organisation needs and what evidence will establish the outcome.

I would also define the words used for each status before the service is launched. A status should tell the user what is known and what happens next. The same meaning should carry through the interface, the downloadable record and the support response.

Finally, I would ask the project team to report more than transaction volume. Completion, correction, exception handling and resolution time tell a fuller story. Their definitions and reporting periods should be clear.

The broader lesson

Technology is valuable when it helps institutions and people complete real work. For payment infrastructure, the transfer is essential, but the useful outcome includes the record, the recognition and the route to resolution.

That change in perspective affects what I ask of a project. I want to know not only whether the money moved, but whether the person and the institution can explain what happened and complete the next step with confidence.

Filed under Payments infrastructure.

Sources

More writing