Client: SafeBet · iGaming & Betting · Maltese iGaming compliance provider

Engineering Support for a KYC Review Workflow

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team supported SafeBet’s Python and AWS Lambda identity verification workflow ahead of an iGaming audit. Over four months, the client’s Zendesk records show manual know-your-customer reviews falling from 2,100 to 820 per week.

Client and engagement facts

Client
SafeBet
Industry
iGaming & Betting
Business context
Maltese iGaming compliance provider
Delivery model
Identity verification workflow support
Application
KYC and compliance review workflow
Supplied geography
Maltese

Application stack and tools

Application stack

  • Python
  • PostgreSQL
  • AWS Lambda
  • KYC vendor APIs

Tools used

  • Zendesk
  • Jira Service Management
  • KYC vendor logs

Why Support Was Needed

Three client analysts were working through manual reviews while preparing for an audit in 90 days. The engineering scope covered queue routing, evidence capture and data from eight upstream systems. The client handled regulator correspondence.

Technical Work

  • Mapped the client’s audit evidence needs against vendor logs in the first two weeks.
  • Added routing for audit-relevant cases in the review queue.
  • Automated data mapping from eight source systems into the KYC workflow.

Representative Incident

The team initially implemented one retention requirement incorrectly and redid two weeks of work. The corrected workflow gave the remaining rules a pattern for capturing the necessary evidence.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSample / populationSource and scope
Manual reviews/week2,1008204 monthsClient Zendesk
Verification time4.5 h38 minBaseline: h; Result: min4 monthsVendor logs; Scope: One identity-verification vendor outage was excluded from timing.
Internal audit findings604 monthsClient internal audit; regulator correspondence remained with the client.Internal audit

Evidence and Limitations

One identity-verification vendor outage was excluded from timing. The finding count is from the client’s internal audit, and the client owned regulator correspondence.

Audit Evidence and Correspondence

SafeBet handled regulatory correspondence. TechSupport Team supplied the application evidence trail in Jira Service Management.

Scope a Similar Engagement

Share the verification systems, manual handoffs and the evidence your application needs to capture. Request a support plan or explore application support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.