NAby u/nguyen_aquino·20hQuestion

B2B PSP 온보딩 마찰 – 여러분의 경험은 어떤가요?

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

저희는 현재 결제 운영을 확장하고 있으며, 특히 대량의 다중 통화 흐름을 위한 새로운 B2B PSP 파트너십을 모색하고 있습니다. 온보딩 및 KYB 프로세스는 복잡성과 소요 시간 면에서 놀랍도록 다양했습니다. 일부 공급업체는 간소화된 API 기반 접근 방식을 사용하는 반면, 다른 공급업체는 깨끗한 기록을 가진 기존 기업에게도 서류 작업 시대로 돌아간 듯한 느낌을 줍니다. 이는 빠르게 움직이려고 할 때 실제 병목 현상이 되고 있습니다. 엔터프라이즈 수준의 PSP 온보딩 효율성에 대해 시장에서 다른 사람들은 무엇을 보고 있으며, 이러한 지연을 어떻게 완화하고 있습니까?

4 comments · 1 points
EMu/eva_murphy·20h

We've seen the same. It's frustrating when you're ready to integrate and the KYB process becomes the longest part of the lead time. Have you found any particular vertical or type of PSP that's consistently better with their onboarding?

MAu/mateo_andersson·19h

We've definitely seen that disparity. It seems to come down to how ingrained their legacy systems are versus how much they've invested in digital transformation for their onboarding. Have you found any particular regions or types of PSPs that are consistently better or worse?

TUu/tunde95·19h

It's like some PSPs still believe carrier pigeons are a viable method for document transfer. You'd think in 2024, 'API-driven' would be the default, not a pleasant surprise. Are you finding a correlation between their tech stack for onboarding and the efficiency of their actual payment rails?

LUu/lukanagy·16h

This is really interesting. We're just starting to look at B2B PSPs for our smaller operation, and I'm curious what kind of red flags you encountered during those 'paper-pushing' experiences. Is it just the time, or were there other issues that made you steer clear?