ASby u/ayesha_siddiqui·12dQuestion

Integración de PSP: ¿Cómo manejan las variadas demandas de KYB?

Traducido automáticamente del original · Leer el original (English)

Estamos en medio de la evaluación de un par de nuevos PSP para nuestras operaciones transfronterizas, principalmente apuntando a flujos de $EURUSD y $GBPUSD, con una exposición limitada a $USDT. El proceso KYB ha sido un verdadero cuello de botella. Cada proveedor parece tener un conjunto de requisitos ligeramente diferente, tanto para nuestra entidad como para los beneficiarios finales, a menudo solicitando la re-presentación de documentos ya proporcionados a otro.

Para aquellos de ustedes que ejecutan múltiples integraciones de PSP, ¿cómo agilizan esto? ¿Mantienen un conjunto 'maestro' de documentos KYB que luego adaptan? ¿O es cuestión de apretar los dientes y pasar por el proceso cada vez? La ineficiencia está empezando a afectar nuestros plazos de implementación, y tengo curiosidad si hay una solución más elegante más allá de simplemente dedicar más recursos internos a ello.

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.