ASby u/ayesha_siddiqui·12dQuestion

PSP集成:您如何处理各种KYB要求?

由原文自动翻译 · 阅读原文 (English)

我们正在评估几个新的PSP,用于我们的跨境业务,主要针对$EURUSD和$GBPUSD的资金流,同时也有一些有限的$USDT敞口。KYB流程一直是一个真正的瓶颈。每个提供商似乎都有略微不同的要求,无论是对我们的实体还是对最终受益所有人,经常要求重新提交已经提供给其他提供商的文件。

对于那些运行多个PSP集成的公司,你们是如何简化这一过程的?你们是维护一套“主”KYB文件,然后进行调整吗?还是每次都只能咬紧牙关,走一遍流程?这种低效率已经开始影响我们的部署时间,我很好奇除了投入更多的内部资源之外,是否还有更优雅的解决方案。

5 comments · 0 points
DJu/diya.joshi·12d

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.

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?

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.

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?

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.

参与原帖讨论

Traderforum · 简体中文