UZINFOCOM

BACKGROUND

Please describe your company and position.

I am an executive at Pingy

Describe what your company does in a single sentence.

PINGY is a Tashkent-based technology company building everyday apps for Uzbekistan: Pingy Tasks, a marketplace where people hire verified local pros and pay only for accepted work, and Pingy Calls, a platform that analyses sales calls to help businesses sell more.

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire UZINFOCOM to accomplish?

• We engaged UZINFOCOM to integrate MyID, the national biometric identity verification service, into our Pingy Tasks mobile app. Our goals were to verify the real identity of every user who posts a task or offers services, to reduce fraud and fake accounts on the marketplace, and to meet local requirements for handling personal data, with the check running on the state side so we never store biometric data ourselves.

SOLUTION

How did you find UZINFOCOM?

• Online Search
• Referral

Why did you select UZINFOCOM over others?

• High ratings
• Close to my geographic location
• Pricing fit our budget
• Great culture fit
• Good value for cost
• Referred to me
• Company values aligned

How many teammates from UZINFOCOM were assigned to this project?

2-5 Employees

Describe the scope of work in detail. Please include a summary of key deliverables.

UZINFOCOM provided MyID, the national biometric identity verification service, which we integrated into Pingy Tasks, our marketplace for everyday services in Uzbekistan. The project ran from sandbox testing to a signed production contract in July 2026.

Key deliverables from UZINFOCOM:
- Sandbox access: test API host and backend credentials, so we could build and test the full verification flow before going live.
- Mobile SDKs: native SDKs for iOS and Android with face liveness detection, plus their official React Native bridge, which fit our app stack.
- API documentation: endpoints for access tokens, verification sessions and retrieving the verified result.
- Production credentials and service contract: a monthly package of 1,000 verifications, with per-check pricing above that.
- Biometric verification against the state registry: it returns the person's confirmed name, document details and PINFL. Biometric data stays on MyID's side, so we never store face images.
- Technical support during integration: guidance on SDK setup, platform choice and session parameters.

Result: every user who posts a task or offers services now completes a one-tap face scan. Their identity is confirmed by the state registry, with no manual document checks on our side. Our first production verification passed with a 0.91 face-match score.

RESULTS & FEEDBACK

What were the measurable outcomes from the project that demonstrate progress or success?

- Went from sandbox access to live production in 2 days (July 2026).
- 100% of production verifications so far matched the state registry with a face-match score above 0.89 (average 0.906), with no false rejections of legitimate users.
- Replaced manual operator checks, which had no registry cross-check, with an automated flow: zero fields for the user to fill in, one face scan, identity confirmed by the state registry.
- No biometric data stored on our side. Verified identity details are kept encrypted.
- One MyID verification is reused across our Pingy apps, so a user verified once is not charged a second paid scan in another app.

Describe their project management. Did they deliver items on time? How did they respond to your needs?

The UZINFOCOM team was responsive and easy to work with. Sandbox credentials arrived quickly after we applied, and production access followed within two days, once the contract was signed. They asked about our technology stack early on, and when they learned we build with React Native, they pointed us to their official React Native SDK. That saved us from maintaining our own native bridge. Questions during integration were answered promptly, and the path from testing to live verifications had no delays on their side.

One area to improve: the documentation could cover a few edge cases more clearly. For example, the iOS SDK requires a delegate method that wasn't in their React Native guide, and passport-based lookup fails for users whose document was reissued, while PINFL-based lookup always works. We figured these out ourselves, but noting them in the docs would save other teams time.

What was your primary form of communication with UZINFOCOM?

• Virtual Meeting
• Email or Messaging App

What did you find most impressive or unique about this company?

What sets UZINFOCOM apart is that MyID confirms identity directly against the state registry, not just a photo of a document. For a marketplace where strangers let each other into their homes, that matters: we get a name, document details and PINFL confirmed by an official source, not whatever a user types in.

A few things stood out:
- Privacy by design. The face comparison happens on MyID's side, and we only receive the result, so we never have to store biometric data ourselves.
- Almost no friction for users. The flow can start with zero fields: MyID's own screen collects the document, and one face scan finishes the check.
- Easy to start. The SDKs are publicly available, so we could build and compile the integration before the contract was signed, then switch to production just by changing credentials.
- An official React Native SDK. For a local provider this is rare, and it made MyID a natural fit for a modern mobile stack.

Are there any areas for improvement or something UZINFOCOM could have done differently?

A few suggestions that would make MyID easier to adopt:

- Make the official React Native SDK easy to find. We had already written our own native bridge before learning that an official SDK existed. A clear link from the main documentation would have saved us several days.
- Document edge cases. The iOS SDK requires a delegate method that wasn't mentioned in the React Native guide, so the build failed until we found it. Sessions created with passport data also need a birth date, otherwise the API returns an error. And passport-based lookup fails for users whose document was reissued, while PINFL-based lookup always works. Knowing this upfront would have saved debugging time and helped us guide users.
- Offer a startup-friendly tariff. The minimum monthly package is significant for an early-stage product with only a handful of verifications in its first months. A pay-as-you-go or reduced starter tier would lower the barrier for new companies.
- Publish a changelog for SDK updates, so integrators know when a new version requires code changes.