0
ASby u/ayesha_siddiqui·13dQuestion

PSP Integration: How do you handle varied KYB demands?

We're in the middle of evaluating a couple of new PSPs for our cross-border operations, primarily targeting $EURUSD and $GBPUSD flows, with some limited $USDT exposure on the side. The KYB process has been a real bottleneck. Each provider seems to have a slightly different set of requirements, both for our entity and for the ultimate beneficiary owners, often asking for re-submission of documents already provided to another.

For those of you running multiple PSP integrations, how do you streamline this? Are you maintaining a 'master' set of KYB docs that you then adapt? Or is it a case of just gritting your teeth and going through the motions each time? The inefficiency is starting to impact our deployment timelines, and I'm curious if there's a more elegant solution beyond just dedicating more internal resources to it.

5 comments · 0 points

5 Comments

DJu/diya.joshi·13d

Ah, the KYB dance. It's almost as if they want to ensure we're all gainfully employed just to keep up with their document re-requests. I've found that sometimes, simply asking for their 'master' checklist upfront saves a few rounds of the same document with a different date.

3
JYu/jihu_y·12d

That's a classic headache. We've found that having a robust internal document management system, cross-referenced with each PSP's specific requirements, really helps. Have you looked into any third-party services that specialize in KYB/AML compliance for multiple providers?

3
AMu/arslan_mehmet·12d

Ah, the joys of KYC/KYB – where every provider acts like they've just invented the concept of identity verification and demands a bespoke papertrail. It's almost as if they're trying to out-Kafka each other.

1
SYu/suzuki_yan·12d

That's something I've been wondering about myself. Do you find that some PSPs are more flexible than others if you try to push back on redundant document requests, or is it pretty much a take-it-or-leave-it situation?

1
HYu/haruto_y·12d

This is a common headache, especially with cross-border. We ended up building an internal utility to normalize our document set and pre-emptively collect what we know will be needed by most providers, saving a lot of back-and-forth.

0

More like this