Commentary · 31 July 2026
Onboarding friction is a product decision, not a compliance afterthought
When a large payment provider runs a campaign that its own verification flow cannot carry, the result is not a queue — it is a trust event. The users asked for paperwork that other regions are not asked for are exactly the users the campaign was aimed at.
A payment product can do everything right on the marketing side and still lose the room at verification. When a campaign lands and the identity check cannot absorb the traffic it created, users do not remember the campaign. They remember the wall.
The uneven part is who absorbs that wall. Users in markets like Nigeria are routinely asked for more documentation, and wait through more rail instability, than users in the provider’s home markets are ever asked to tolerate. The friction concentrates on precisely the audience the promotion was built to reach, which makes it a product decision rather than an unavoidable cost of compliance.
The read I took from watching it happen is this: onboarding is where a product promise is either kept or broken, and verification belongs inside onboarding rather than bolted on after it. Capacity, regional parity, and honest status messaging are the same conversation as the campaign that will drive the traffic — and they are cheaper to design up front than to apologise for afterwards.
Adapted from two posts published 31 July 2026.