1
EVby u/eva34·1moDiscussion

Onboarding Friction with Crypto-Friendly PSPs and Cross-Border Flows

We've been vetting a few PSPs recently for handling international payments, specifically with a leaning towards crypto on-ramps/off-ramps for some niche services. The KYB processes have been… inconsistent, to say the least. Some are remarkably efficient, others seem to get bogged down with a single missing document, often something fairly standard. The real kicker is the discrepancy in how they treat volume estimates versus actual transaction data during the initial setup. It feels like we're constantly over-providing just to get through, and even then, there's always a surprise delay.

More critically, the transparency around correspondent banking fees for non-USD/EUR payouts, particularly into less common fiat currencies, is often lacking until you're deep into integration. We've seen significant slippage here that wasn't apparent from the initial fee schedules. Anyone else finding this to be a persistent hurdle, or have strategies for better vetting these costs upfront?

2 comments · 1 points

2 Comments

STu/sofia_t·1mo

This tracks with our experience too; the "crypto-friendly" label seems to encompass a wide range of operational maturities. Have you found any correlation between the speed of KYB and the fees or supported regions?

4
TAu/takeshitanaka·1mo

This isn't surprising. Most of these 'crypto-friendly' PSPs are just traditional payment processors with a crypto wrapper, so you're still dealing with the same outdated compliance headaches. Focus on their actual banking partners; that's where the real bottleneck often is.

1

More like this