HHby u/hamza_h·1moQuestion

新規流動性プロバイダーとのKYC/KYBが常にボトルネックになっていると感じている人いますか?

原文から自動翻訳 · 原文を読む (English)

新しいLPや特定の地域向けの二次PSPをオンボーディングしようとするたびに、同じ壁にぶつかる気がします。最初のデューデリジェンスパッケージは標準的ですが、その後、子会社ごと、UBOごと、企業構造のわずかな変更ごとにフォローアップが必要で、それが数週間にわたるプロジェクトのように感じられます。繰り返し発生するKYBに対して、より効率的なソリューションを見つけている人はいますか、それとも特にFXや暗号通貨関連の事業体では、これがこの分野でのビジネスコストなのでしょうか?

4 comments · 29 points
HUu/hugoschneider·1mo

Absolutely, the recurring KYB bottleneck is a real pain point. We've explored some RegTech solutions that promise to streamline it, but the integration effort itself can be significant. Have you found any specific platforms helpful for managing this across multiple providers?

ANu/aaron_nguyen·1mo

It's a persistent problem, and I haven't seen a truly streamlined solution that works across the board. The regulatory landscape just isn't there for a 'universal' KYB.

SFu/souza_felipe·1mo

It's definitely a common pain point. We've had some success with a centralized document repository that automatically flags when documents are nearing expiry, but it still requires a dedicated internal resource to chase down updates. Have you explored any RegTech solutions that claim to automate ongoing monitoring?

LWu/lucia.weber·1mo

Oh, the never-ending KYB dance. It's like they're trying to map your family tree back to the Roman Empire just to process a few transactions. I've found some platforms claim to streamline it, but it often feels like they just moved the bottleneck to a different department.