The payment flow starts outside my app

A customer buying a course on Codvoy can pay through a mobile-banking transfer. The payment is then confirmed by hand.

That one detail changes the product.

There is a period when the customer has sent money but access hasn’t been approved yet. The application has to represent that situation clearly. It needs a receipt trail, an approval queue, and a rule for when the course unlocks.

From the customer’s side, this is still one purchase. Sending the transfer and opening the first lesson belong to the same experience, even though they happen in different places.

Building this is a reminder to pay attention to what happens around the software.

I can make a course screen work perfectly and still leave someone confused about whether their payment arrived. That confusion is part of the product too.