As mobile credit scales across emerging markets, one question keeps surfacing: how can repayment enforcement coexist with trust and privacy—without breaking the user experience or the law? To dig in, we sat down with Victor Kirnarskiy, CEO of GetMobi, whose team has launched and scaled smartphone-financing programs across LATAM, Asia, and Africa.
In this interview, Victor speaks candidly about integration pain points, regulatory expectations, Apple coverage, time-to-integration metrics, and why a borrower-facing app changes everything. This transcript is part of our ongoing series on Device Lock & Privacy.
For a structured analysis with frameworks and case studies, read our main article: From Locks to Loyalty: Field Notes on How GetMobi Actually Ships Device Finance
Q: Where does GetMobi sit in the global device-finance ecosystem, and what truly differentiates you from “classical” locking providers?
Victor Kirnarskiy: Most providers sell device locking as a standalone control. We go further. Two big differences: broader brand coverage—including Apple—and a customer-facing module that ships with the control. The borrower gets a clear interface to understand status, next steps, and instant unlock after payment. It’s not just APIs; it’s a complete experience.
Q: What market gaps do you see, and how do you close them in practice?
Victor: The gap is integration. Device finance touches the full journey—merchant, lender, payments, CX, legal. Many teams underestimate the work of aligning those layers. We close it by delivering test devices, near-production tenants, and hands-on, on-site support. Partners can literally lock/unlock real devices in their own office before launch. That tangibility accelerates decisions and reduces surprises.
Q: You’ve argued the tech is similar across vendors—that the edge is in process. What processes matter most?
Victor: Exactly. Mobile OS capabilities are known. The edge is our integration playbook—a knowledge base distilled from many launches. We run a big checklist per project and assign people who can dive into each client’s unique systems. It’s not “here are the docs, good luck.” It’s “let’s make minimal changes to your stack and ship safely.”
Q: How do you maintain speed without compromising compliance and security?
Victor: Preparation. Because we’ve seen the edge cases, we capture them in the playbook—consent artifacts, role-based access, audit trails, escalation rules. That lets us move fast and safely. We know which “basic hygiene” items must be right from day one.
Q: What specific UX elements change outcomes for borrowers and operators?
Victor: Start with the end state. During pilots, partners see exactly how it will look at scale: the borrower app, the notifications, the unlock flow, even the draft legal text. Real devices + real tenant access = shared mental model across legal, product, and CX. When users clearly understand the rules and the resolution path, complaints drop and repayments rise.
Q: Can you share a concrete example where deep support made the difference?
Victor: A Mexican neobank hit a scaling phase with lots of data and edge cases. Our engineers spent hours investigating flows—at no extra charge—so they could optimize without rewriting their systems. That’s typical for us: we dive deep so clients can keep their architecture and still ship a high-quality program.
Q: What KPI best captures GetMobi’s value?
Victor: Time-to-Integration (TTI). We’ve had partners reach first sales in 2–4 weeks. In enterprise contexts that often take 12–24 months, this is huge. Shorter TTI means revenue earlier—and less integration fatigue.
Q: How does brand coverage, especially Apple, show up in real deals?
Victor: It’s common for partners to supplement their existing vendor with us to close coverage gaps—Apple being the big one—without ripping out what works. Interoperability beats ideology. We fit into their stack and unify policy across fleets.
Q: Beyond locking, you speak about lifetime value. What else do you bring to the table?
Victor: We operate across the device-finance stack: trade-in and diagnostics for fair pricing, fleet management, and even loan-management layers. Increasingly, we’re building monetization into the borrower app—merchant-funded tasks or offers that offset payments. It flips the story from “punitive control” to loyalty and rewards.
Q: What regions do you see as most promising over the next 2–3 years?
Victor: Asia and Latin America are our current focus—huge smartphone demand, strong BNPL tailwinds, and room for responsible programs. The tech is location-agnostic, but execution depends on local regulation, time zones, and go-to-market realities.
Q: Where does compliance meet UX? What’s non-negotiable in your designs?
Victor: Informed consent, proportional enforcement, and transparent off-ramps. Practically: a plain-language pre-contract explainer (~2 minutes), stored consent artifacts, graded steps (reminders → soft restrictions → temporary lock), and instant unlock after payment. Borrowers must see what happened and why—right in the app.
Q: What common mistakes should fintechs and telcos avoid?
Victor: Treating device locking like a black box. In some markets, we’ve seen misuse—trying to piggyback spyware behaviors. That’s not a mistake; it’s a red line. Device locking is only for repayment discipline and loan-related communications. Anything else destroys trust and invites enforcement.
Q: What safeguards do you recommend against abuse or error?
Victor:
Role-based access and least privilege
Maker–checker for mass actions and overrides
Immutable audit logs (who/what/when/why)
Encryption and key rotation
Automated guardrails (e.g., no lock if a dispute/hardship case is open)
Periodic audits and stress tests
These answer the regulator’s “fairness and necessity” questions before they’re asked.
Q: What’s your outlook on competition—and GetMobi’s role—in the next wave?
Victor: We see vendors competing for favored relationships with OS and OEM ecosystems—an oligopoly risk. Our counter is focusing on the end customer’s value: locking + rewards/monetization + UX. If borrowers can earn offsets, the incentive flips from dodging payment to playing to win—and everyone’s risk model improves.
Q: A short checklist for responsible implementation?
Victor:
Be explicit with customers from day one—show the lock and the path to unlock.
Align internally: locking is for repayment, not data extraction.
Invest in security: clear roles, access hygiene, and an owner for cybersecurity.
Q: Final advice for founders building in this space?
Victor: Think 10–15 years out. Envision the relationship you want with customers and build for that future now. Radical transparency wins: show your “ingredients”—what the control does, what data is processed, and why. If you play fair, you stay safe.
The through-line is simple: trust is the product. When consent is vivid, governance is auditable, and the borrower experience is first-class, enforcement becomes a transparent safety rail—not a threat. That’s how programs launch in weeks, not quarters, and why customers come back for the upgrade, not the complaint form.
Dive deeper—regulatory mapping, playbooks, and case studies—in the main article: From Locks to Loyalty: Field Notes on How GetMobi Actually Ships Device Finance