# Engineering Support for a KYC Review Workflow

> 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.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/igaming-kyc-workflow-engineering/
- Updated: 2026-11-16

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

## 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

Related services: [Application support](https://techsupport-team.com/services/application-support/)

## 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

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Sample / population | Source and scope |
| --- | --- | --- | --- | --- | --- | --- |
| Manual reviews/week | 2,100 | 820 |  | 4 months |  | Client Zendesk |
| Verification time | 4.5 h | 38 min | Baseline: h; Result: min | 4 months |  | Vendor logs; Scope: One identity-verification vendor outage was excluded from timing. |
| Internal audit findings | 6 | 0 |  | 4 months | Client 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](https://techsupport-team.com/contact/) or explore [application support](https://techsupport-team.com/services/application-support/).

## Related pages

- [Application support](https://techsupport-team.com/services/application-support/): The related service for this engagement.

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
