By Appbay Technologies
A partnership makes the headline. Onboarding at speed, without weakening controls, is the work that follows.
A Saudi bank recently set out to be the partner of choice for international digital payments, through a strategic partnership meant to accelerate digital commerce growth. A named partnership like that signals ambition, and it also creates a queue: every international merchant still has to be onboarded, screened, and approved.
This piece is a candid one. The fit is a good one with some configuration work, and we’ll be specific about which parts are which.
The Priority: Becoming the Partner of Choice for International Digital Payments
Accelerating digital commerce growth and reinforcing a position in international payments is a clear and worthwhile priority. It is also a competitive one, where speed matters.
That creates a real operational question: can a bank onboard international merchants quickly without weakening its AML and KYC controls?
The Hidden Problem: Review Capacity That Doesn’t Scale
Here’s where the operational gap can show up, inside a bank onboarding international merchants:
- Foreign merchant files chased – documents arrive in varied formats from different jurisdictions
- Sanctions screening re-checked – the same checks repeated file by file
- Analysts triaging by hand – review depth set case by case
- Merchants waiting to go live – each new merchant queued behind manual review
Why does this exist? Competitive speed pressure meets cross-border risk review. Demand scales with the partnership, but KYB and sanctions review scale with analysts. Cross-border exposure also raises the cost of getting screening and risk evidence wrong, so shortcuts aren’t an option.
Why This Matters Now
The partnership was announced. When does it show up in revenue?
The board approved the partner. It now wants time-to-revenue and cost per merchant on the next quarterly pack. The question that follows isn’t rhetorical:
“How quickly does a new merchant go live, and what does each one cost to onboard?”
For the COO, CDO, and CCO, this plays out across four measures:
- Time-to-revenue per merchant – how long between signing and first transaction
- Cost per onboarded merchant – the real cost of each onboarding
- Partnership revenue versus plan – how the partnership is tracking against its promise
- Partnership benefit realization – whether the board’s approval is paying back
Without that visibility, partnership growth is capped by the compliance queue.
An Honest Look at the Fit
We want to say this plainly: this is a good fit, but not a complete one. Merchant (KYB) onboarding with cross-border screening is close to Appbay’s core strength in KYC and AML workflows.
What transfers directly:
- Document intelligence for corporate and merchant files
- Risk-tiered routing so low-risk merchants move quickly and complex ones reach the right officer
- Audit IQ-style auditable reporting for every decision
What is configuration work, not a ready product:
- Merchant-specific risk rules that reflect the bank’s own appetite
- Integration with the payments partner’s data
Risk appetite and screening decisions stay with the bank’s compliance function. AI supports the analysis and does not make the call.
Here’s what that would actually involve:
Ingest Merchant Documents
Corporate and merchant files brought into one governed workflow.
AI Classification and Extraction
Documents that arrive in different formats structured into a consistent view.
Auto-Route by Risk Tier
Low-risk merchants move through quickly. Complex ones reach the right officer with the evidence already assembled.
Compliance Officer Approval
Every approval remains with a person.
Full Audit Trail
Every step and decision on record.
The practical starting point is a scoped 8-12 week proof of concept on one merchant segment, for example cross-border e-commerce merchants. It would show whether risk-tiered onboarding shortens time-to-live without loosening screening.
Why We’re Saying This Plainly
Being specific matters more than a broad claim would. This problem sits close to what Appbay already builds, so the honest message is that we can scope it clearly, and that two parts need configuration. Naming that up front is more useful than overstating it.
This Pattern Isn’t Unique to One Bank
Any institution building a payments partnership for international merchants will face the same constraint: demand scales with the partnership, but review scales with analysts. The banks getting ahead of this are treating risk-tiered onboarding as part of the partnership design from the start, not as a clean-up exercise after launch.
Let’s Compare Notes
We’re curious how other banks are onboarding international merchants faster without loosening screening. If your organization is working through the same challenge, we’d welcome the conversation.
Send us a message. This one’s genuinely about comparing notes, not a pitch.
