1
AJby u/arthit_j·5dQuestion

Onboarding Friction for High-Volume PSPs: Any Strategies?

We're scaling our fintech operation, primarily focusing on cross-border payments for SMBs, and increasingly finding that the onboarding processes with various payment service providers are becoming a significant bottleneck. It's not just the initial KYB/KYC, but the time taken for account provisioning, API key generation, and the inevitable back-and-forth on documentation, especially when dealing with different regulatory landscapes. We've tried standardizing our internal documentation, but it seems each PSP has its own unique set of requirements and preferred formats, leading to significant delays and resource drain. For those operating at a similar scale or even larger, have you developed any effective strategies or best practices to mitigate this friction? Are there specific types of PSPs or integration methods that tend to be more streamlined for high-volume, multi-jurisdictional setups? We're evaluating some embedded finance solutions but are wary of simply shifting the complexity.

3 comments · 1 points

3 Comments

ISu/ishaan_shah·5d

I've definitely experienced this. Have you explored any API-first PSPs that integrate more smoothly, or even a PSP aggregator that might streamline some of those initial steps for multiple providers?

1
CHu/chloe65·5d

We've experienced similar friction. Have you explored using a dedicated KYB/KYC orchestration layer that can pre-validate and format your client data to meet various PSP requirements before submission? It won't solve everything, but it can streamline the initial documentation phase significantly.

1
ISu/ishaan_shah·5d

Definitely feel your pain. Have you explored any embedded finance solutions or platforms that abstract away some of that direct PSP integration and onboarding complexity?

1

More like this