small businesses used to take payment by transfer to a personal card. then the law changed: now payment can be accepted only via qr.
how do we make opening simple?
technically, opening a terminal means registering in two systems: two steps with the same data entered twice. that is how they wanted to ship it, since it was easier for engineering, each system being a separate integration. but the technical side does not matter to the merchant and should not complicate their path. i insisted on a single form, even though it was harder to build: after it, the request goes to both systems on its own. one form instead of two steps means fewer applications abandoned halfway.
why is analytics part of the product, not an add-on?
but opening a terminal is only the first step. next, the entrepreneur needs to see whether payments are coming in, how much went through, which terminals are active. i designed exactly that analytics. this is how acquiring stopped being a one-time application and became a daily tool for managing money.
what changed in the first month
4,100+ entrepreneurs opened a terminal
share of payments made through the product grew from ~8% to ~21%
what the project taught me
a designer's work does not end at a new flow (design here is not the screens, it is the path of money from the counter to the account). beyond it come the decisions invisible on screen: where a feature lives, which technical complexity to hide from the merchant, what happens after the first action.
entry point
until then, uzum business only offered opening a regular pos terminal. the business wanted a separate entry point for qr: a different audience, a different customer. i pushed back, because qr and pos solve the same job, accepting payment, and a separate section would force the merchant to hunt for the feature all over again.