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.