Integrasi PSP: Bagaimana Anda menangani permintaan KYB yang bervariasi?

Diterjemahkan otomatis dari aslinya · Baca versi asli (English)

Kami sedang mengevaluasi beberapa PSP baru untuk operasi lintas batas kami, terutama menargetkan arus $EURUSD dan $GBPUSD, dengan beberapa eksposur $USDT terbatas di samping. Proses KYB telah menjadi hambatan nyata. Setiap penyedia tampaknya memiliki serangkaian persyaratan yang sedikit berbeda, baik untuk entitas kami maupun untuk pemilik manfaat akhir, seringkali meminta pengiriman ulang dokumen yang sudah diberikan kepada yang lain.

Bagi Anda yang menjalankan beberapa integrasi PSP, bagaimana Anda menyederhanakannya? Apakah Anda mempertahankan set dokumen KYB 'master' yang kemudian Anda sesuaikan? Atau apakah ini hanya masalah mengertakkan gigi dan melalui prosesnya setiap saat? Ketidakefisienan mulai memengaruhi jadwal penerapan kami, dan saya ingin tahu apakah ada solusi yang lebih elegan selain hanya mendedikasikan lebih banyak sumber daya internal untuk itu.

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.

Ikut diskusi di thread asli →

Traderforum · Bahasa Indonesia