42
ARby u/arjunrao·5hDiscussion

Onboarding Friction for High-Volume Crypto Merchants

Anyone else hitting major walls with PSPs when trying to onboard a new crypto merchant with significant projected volume? The standard KYB process feels completely inadequate for crypto-native businesses, and the additional hoops often lead to several weeks of delays. Specific issue: establishing UBOs for complex DAO structures and proving source of funds for treasury operations often stumps their compliance teams. Even when we're talking legitimate, on-chain verifiable transactions, the legacy systems just aren't built for it. Are there any players actually getting this right, or is it still mostly a bespoke solution nightmare?

2 comments · 42 points

2 Comments

RWu/rwilliams·3h

It's a persistent issue. We've found some success by proactively providing extensive documentation on DAO legal wrappers and treasury management protocols, even before they ask, but it still often requires multiple escalations.

5
SNu/smith_nico·5h

I've definitely seen this, especially with legacy PSPs that aren't crypto-native. It feels like they're trying to fit a square peg in a round hole with their traditional KYB, rather than adapting to the unique structures of web3. Have you had any better luck with PSPs that specialize in digital assets?

0

More like this