Case study · Multiple workflows and regional scenarios

Managed operations for payments platforms

Company-reported case study

Actigy BPO supplied one operating team for Sable Pay’s merchant onboarding, first-line support and partner reconciliation. Each workflow retained its own service, cost and quality measures.

Actigy BPO confirms the engagement and supporting records. Results apply to the stated scope and measurement windows.

Cost per onboarded merchant

Result

£118

Baseline: £212

Window: 6 months

Supporting record: Finance system report

Onboarding time

Result

5 hours

Baseline: 31 hours

Window: 6 months

Supporting record: Onboarding portal export

Support first response

Result

41 minutes

Baseline: 6 hours

Window: 6 months

Supporting record: Zendesk analytics

Client profile

Sable Pay, a UK embedded payments platform with 240 staff.

Challenge and scope

Three vendors use different quality processes. The platform cannot easily connect a pending onboarding case, a support contact, and a partner settlement issue.

A merchant can open a support case while an application is still in review, then raise a payout issue after onboarding. Different vendors can report all three events with separate identifiers and clocks. The platform needs enough shared case context for the next team to resolve the issue without exposing more data than it needs.

Delivery workflow

Coordinate 1,100 monthly merchant applications, 7,400 support contacts, and 2,200 partner transactions under one delivery lead and three workflow owners. Define each handoff and report the measures in one operating review.

Use a stable merchant reference to connect records across the approved onboarding, support, and reconciliation tools. Define which status and evidence each team needs before accepting a handoff. Keep specialist queues and service measures for document review, customer contacts, and exceptions in partner settlements.

Have each workflow owner reconcile open items at regular operating reviews. Trace cross-queue cases through the original reference and record who owns the next action. Escalate conflicting priorities, partner discrepancies, and risk decisions to the platform with the status and relevant approved evidence.

Delivery team

Poland and Bulgaria, about 23 FTE. 1 engagement lead, 3 service leads (KYC, support, finance), 6 onboarding associates, 9 support associates and 4 reconciliation specialists.

Systems and tools

Persona, Zendesk, NetSuite, client onboarding portal.

Client decision rights

The platform owns risk acceptance, pricing, merchant termination, and service priorities for each queue.

Early milestone

At week 4, onboarding takes 19 hours and first support response takes under two hours.

Outcomes

Company-reported results, with the baseline, measurement window and supporting record described for each measure.

Reported results: Managed operations for payments platforms
MeasureBaselineResultWindowSupporting record
Cost per onboarded merchant£212£1186 monthsFinance system report
Onboarding time31 hours5 hours6 monthsOnboarding portal export
Support first response6 hours41 minutes6 monthsZendesk analytics
Reconciliation close9 days3 days6 monthsNetSuite report
Merchant CSAT after 30 days3.9/54.6/56 monthsZendesk analytics

Interpreting the results

The cost per onboarded merchant falls from £212 to £118 while onboarding, replies, and reconciliation each take less time. Agree which labor and shared costs are included and calculate each workflow’s measure on its own denominator. Review handoff return rates and merchant satisfaction to explain cross-queue effects.

Recommendations for new clients

For fintech teams with at least three outsourced queues, pilot a handoff between functions and reconcile the definitions before aggregating metrics. Report onboarding, response, and close times at the workflow level.

Bring a set of journeys that span two or more queues and the baseline records that describe each one. Define data access by role and agree which lead routes disputes about ownership. Start with one handoff where waiting creates visible rework, and verify the tracking record before adding other transfers.

Scope this workflow for your operation

Use the documented workflow, client-held decisions and operational checks to outline a pilot for your own workload.