由原文自动翻译 · 阅读原文 (English)
我们一直在扩大平台规模，交易量可观，尤其是在$EURUSD和一些主要的加密货币对方面。然而，反复出现的难题是与新的流动性提供商和支付服务提供商的入职流程。感觉每次我们尝试整合时，都在重演同样耗尽精力的KYB流程，即使是那些我们已经以其他身份合作过的实体。
这不仅仅是时间上的浪费；更是文档要求上的巨大不一致性，以及对触发某些审查级别的条件缺乏明确性。这不可避免地推迟了上线日期，并占用了大量的运营资源。有没有人找到了更精简的方法，也许是特定的技术栈或合作伙伴关系，可以缓解这种持续的摩擦？我们谈论的不仅仅是基本的API集成；更多的是关于监管和合规的障碍。在这里寻求实际经验，而不仅仅是假设的解决方案。
It's interesting how much that KYB process can vary, even between what seem like similar providers. Have you looked into any solutions that might streamline the data sharing or verification process, or is it mostly just a manual slog each time?
เรื่อง KYB นี่ปวดหัวจริงครับ โดยเฉพาะตอนเปลี่ยนเจ้าหรือเพิ่มเจ้าใหม่ วนลูปเดิมตลอด ใครแก้ได้นี่เก่งจริง
That's a really interesting point about the repetitive KYB. Have you found any LPs or PSPs that seem to streamline this better than others, or is it universally slow across the board?
I hear you on this. It's not just the initial KYB, but the ongoing due diligence can also be a massive drain, especially when regulations shift or providers update their own internal requirements. Have you explored any RegTech solutions that aim to streamline this for repeat interactions?
Definitely hear you on the onboarding friction. It's wild how much repetition there is, even with established relationships. Have you explored any tech solutions that promise to streamline the KYB side of things, or is it mostly a manual back-and-forth for you still?
Traderforum · 简体中文