CNby u/cerny_natalia·4dQuestion

대량 암호화폐 결제 온보딩 마찰

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

다른 분들도 암호화폐 결제를 위한 새로운 결제 레일 온보딩에 비슷한 어려움을 겪고 계신지 궁금합니다. 저희는 기존에 설립된 법인으로, 상당한 거래량과 깨끗한 규정 준수 이력을 가지고 있음에도 불구하고, 몇몇 새로운 암호화폐 결제 제공업체의 KYB(Know Your Business) 프로세스가 예상외로 길어졌습니다. 특히, 초기 문서 검토를 통과하는 데 상당한 지연을 겪었으며, 기존 규제 프레임워크를 고려할 때 중복되는 정보 요청이 뒤따르는 경우가 많았습니다.

일부 제공업체는 프론트엔드에서 훌륭한 기술을 제공하지만, 기업 고객을 위한 확장 가능한 백오피스 운영에 여전히 어려움을 겪고 있는 것 같습니다. 규제된 법정화폐 PSP에 일반적으로 요구되는 것 이상의 맞춤형 정보 요청은 상당한 지연을 초래합니다. 대량 운영을 하는 분들은 이 문제를 어떻게 해결하고 계신가요? 특정 유형의 제공업체(예: 순수 암호화폐 vs. 하이브리드)가 대규모에서 더 원활하고 효율적인 KYB 프로세스를 가지고 있는 것 같습니까? 어떤 요인이 특정 제공업체를 더 빠르거나 느리게 만드는지에 대한 통찰력이 있다면 도움이 될 것입니다.

4 comments · -1 points
KSu/korn_saetang·4d

เป็นปัญหาที่เจอเหมือนกันเลยครับ โดยเฉพาะกับแพลตฟอร์มที่เพิ่งเข้ามาใหม่ๆ บางทีเอกสารพร้อมหมดแล้วแต่ก็ยังติดอยู่นาน อยากรู้เหมือนกันว่ามีใครเจอแบบที่เข้มงวดเกินจำเป็นจนแปลกๆ บ้างไหมครับ

STu/stefanivanov·4d

Yeah, it's definitely a common complaint. Many of these newer providers are still figuring out their KYB processes, and it often feels like they're not set up to handle established entities as smoothly as they should be. Are you finding it's specific types of documents that cause the most hangups, or just the overall review speed?

AAu/aaron50·4d

We've seen this too. It's frustrating how many of these "innovative" crypto payment providers still have KYC/KYB processes stuck in the stone age. They claim to handle large volumes, but can't onboard a legitimate entity efficiently.

MSu/mller_sara·4d

We've seen this too. It's not just the new providers; even some established players are struggling to scale their KYB teams with the increased demand. Feels like they're still playing catch-up.