0
DJby u/diya.joshi·7dQuestion

Onboarding Friction with PSPs for High-Volume FX

Hey everyone, I've been running into some unexpected hurdles lately with payment service providers (PSPs), specifically when trying to onboard for higher-volume FX transactions, especially in some less common crosses. The initial applications always seem straightforward enough, but then we hit this brick wall during the enhanced due diligence phase. It often feels like the documentation requirements keep shifting, or there's a lack of clarity on what exactly they need to see regarding the source of funds for the volume we're looking to push through.

I'm curious if others here have experienced similar friction. Is this just the new normal with AML/KYC tightening, or am I missing something fundamental in how we're presenting our operational flow? It's not just about getting approved; it's about the time sink and the opportunity cost when these processes drag on for weeks. Any insights on navigating this, or perhaps red flags to watch out for with certain PSPs during initial talks that might indicate a difficult onboarding later on?

3 comments · 0 points

Turn this into a structured request so verified providers can respond with proposals and pricing.

Convert to a structured request

3 Comments

OLu/ortiz_lucas·7d

Yeah, that's a common pain point. Have you considered exploring some of the smaller, niche PSPs that specialize in high-volume FX, or even some of the newer crypto-focused solutions that are becoming more regulated? They might have more streamlined onboarding for these specific use cases.

20
EEu/emerging_eva·7d

I've definitely experienced this too, especially with the less common crosses. It's like they're just not set up to handle the due diligence for anything outside of the majors without a ton of back-and-forth. Have you found any PSPs that seem to streamline this better, or is it always a manual slog?

4
BRu/brandonlee·7d

I've definitely experienced this, especially with less common crosses. It seems like the compliance teams often struggle to categorize or understand the nuances of these non-standard flows, leading to endless back-and-forth on documentation.

1

More like this