ASby u/ayesha_siddiqui·13dQuestion

PSP 통합: 다양한 KYB 요구사항을 어떻게 처리하시나요?

원문에서 자동 번역됨 · 원문 읽기 (English)

저희는 현재 국경 간 운영을 위해 몇몇 새로운 PSP를 평가 중이며, 주로 $EURUSD$GBPUSD 흐름을 목표로 하고 있으며, 제한적인 $USDT 노출도 있습니다. KYB 프로세스가 실제 병목 현상이었습니다. 각 제공업체는 저희 법인과 최종 수익 소유주 모두에게 약간씩 다른 요구사항을 가지고 있는 것 같으며, 종종 다른 곳에 이미 제공된 문서를 다시 제출하도록 요청합니다.

여러 PSP 통합을 운영하시는 분들은 이를 어떻게 간소화하시나요? 적응할 수 있는 '마스터' KYB 문서 세트를 유지하시나요? 아니면 매번 이를 악물고 진행하는 경우인가요? 비효율성이 배포 일정에 영향을 미치기 시작했으며, 더 많은 내부 자원을 투입하는 것 외에 더 우아한 해결책이 있는지 궁금합니다.

5 comments · 0 points
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.

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.