Compare · PayJoy

Lockia vs PayJoy

PayJoy and Lockia both serve device financing operators. They sit at different layers of the stack with different sovereignty postures, different bypass-resistance models, and different commercial profiles. This page lays out the architectural facts.

Kevin Fernandez

Co-Founder & CTO, Lockia Technologies

Published May 14, 20267 min read

01 · Why this comparison exists

Different layers of the device-financing stack

PayJoy and Lockia both come up in Latin American device-financing conversations, but the companies sit at different layers of the stack. PayJoy is a direct-to-merchant lender — they originate financing, manage collections, and operate the device control as part of their lending product. Lockia is an infrastructure platform for the operators, retailers, and OEMs who run their own financing programs.

A buyer evaluating both is usually doing one of two things: (a) choosing between operating their own financing program on Lockia versus referring customers to PayJoy as the lender, or (b) considering Lockia as the device-control substrate underneath a financing operation that previously rode PayJoy's consumer product.

The architectural facts below are sourced from PayJoy's public-facing product materials and from Lockia's own documentation. This page does not characterize PayJoy's business or strategy — only what each platform builds and how each operates.

02 · Architecture

Where each platform actually runs

Competitor

PayJoy

PayJoy operates a direct-to-consumer financing product. Devices financed through PayJoy run a PayJoy-built Device Policy Controller installed as Device Owner on Android. The DPC enforces a graduated lock state tied to the customer's payment status with PayJoy as the lender of record.

The device control is software-layer enforcement at the DPC level. Public device-financing forums and well-documented bypass research demonstrate that the standard recovery-mode and factory-reset bypass paths can defeat software-only DPC enforcement on devices where the bypass-resistance layer is not anchored to hardware-attested checkpoints.

PayJoy operates the cloud infrastructure (US-hosted SaaS) that the DPC reports to. The customer relationship is between PayJoy and the end consumer; merchant integration is a referral or co-branded financing offering rather than a multi-tenant platform license.

iOS device control is not PayJoy's primary architectural focus.

Lockia

Lockia is infrastructure for operators, retailers, and OEMs running their own financing programs. The customer of Lockia is not the end consumer — it is the financing operator who licenses Lockia's policy plane, embeds Lockia's Cipher DPC on financed devices, and runs collections inside their own commercial relationship with the borrower.

Cipher DPC enforces lock state with hardware-anchored device identity from Cipher Protocol (USPTO provisional 63/940,826, "Bypass-Resistant Device Locking", December 2025). Standard recovery-mode and factory-reset bypass paths are blocked at hardware-attested checkpoints.

For iOS, Lockia operates Cipher MDM in your deployment region — no third-party MDM SaaS in your data path. Your Apple Business Manager tenant federates with the Lockia-operated MDM via Apple's published MDM protocol. Mixed Android + iOS portfolios run on one operational workflow rather than two separate financing programs per OS.

Lockia operates multi-region infrastructure across the Americas, expanding globally; customer-region deployment is available for contracts that require sovereignty over the data path.

03 · Side-by-side

Architectural facts

Each row is sourced from public vendor materials and the device-management protocols Apple and Google publish. The comparison reflects what each platform builds and how each platform serves financing operators.

Capability	Lockia	PayJoy
Commercial layer	Platform for operators, retailers, and OEMs running their own financing programs	Direct-to-consumer lender; financing originated and serviced by PayJoy
Customer relationship	Lockia → operator; operator → borrower	PayJoy → borrower direct; merchant via referral
Android control mechanism	Public AOSP DevicePolicyManager APIs (Cipher DPC, Device Owner mode)	PayJoy-built DPC, Device Owner mode
iOS control mechanism	Lockia-operated Cipher MDM, in your deployment region, via Apple Business Manager	Not the primary architectural focus
Bypass-resistance posture	Multi-layer AOSP + TEE-anchored identity (USPTO 63/940,826)	Software-layer DPC enforcement; recovery-mode bypass paths publicly documented
Hardware anchor	TEE-backed device identity	Software identity at the DPC layer
Hosting model	Lockia-operated, in your deployment region — multi-region infrastructure across the Americas, expanding globally; customer-region available	PayJoy cloud (US-hosted SaaS)
Sovereignty posture	Customer-region deployment available for sovereignty-bound contracts	US-hosted SaaS
Customer data path	Lockia-operated, in your deployment region	PayJoy cloud

04 · Sovereignty

Where the data sits matters for LATAM regulatory regimes

PayJoy's consumer-product model routes device telemetry and customer payment data through PayJoy's US cloud SaaS. For most consumer-financing contexts in markets without strict data-residency requirements, that's an architecturally acceptable trade.

For operators in markets with explicit data-residency mandates — LGPD in Brazil, Mexico's Federal Data Protection Law, public-sector procurement contracts in Chile and Colombia, regulated finance contexts across the region — US SaaS in the data path is a procurement disqualifier. The financing operator cannot use PayJoy as their substrate and remain compliant with the contracts their downstream customers require.

Lockia's customer-region deployment option exists for exactly this case. The financing operator licenses the platform and runs it in the jurisdiction their contracts require; Lockia operates the infrastructure under terms the operator's data-handling agreements can govern. Sovereignty is the architectural property; the operator's compliance posture is the contractual outcome. See the public sector solutions page for the full procurement framework.

05 · When PayJoy is the right answer

Two patterns where PayJoy's direct-lending model fits

PayJoy serves real consumer-financing scenarios well. The comparison is unhelpful if it does not name them.

Single-region small retailers without an in-house collections operation. A merchant who wants to offer financing without building or licensing the lending and collections infrastructure can refer customers to PayJoy. The merchant gets a transactional payment at the point of sale; PayJoy carries the underwriting risk and operates the device control as part of its own product.
End consumers in markets where PayJoy operates as a direct lender. Customers in PayJoy's served markets can finance devices through PayJoy as the originating lender without going through a merchant program.

06 · When Lockia is the right answer

Four patterns where Sovereign UEM is the architectural fit

Lockia is the right choice when the buyer is an operator, retailer, or OEM running their own financing program rather than referring customers to a third-party lender.

Multi-region financing operators. Operators deploying across multiple LATAM markets cannot rely on a US-SaaS substrate that doesn't satisfy LGPD, Mexico FDPL, or per-country data-residency requirements. Lockia's customer-region deployment option lets the operator standardize on one platform across regions.
In-house collections operations. Operators with their own collections workflow and billing systems integrate Lockia's policy plane via webhook or REST API — Lockia drives lock state from the operator's billing system, not the other way around.
Apple parity required. Mixed Android + iOS portfolios on one operational workflow — Cipher MDM via ABM on iPhone, Cipher DPC via AOSP on Android, one policy plane.
Reset-resistant device control as a contractual requirement. Operators whose underwriting models depend on real device recovery on defaults — see why reset-resistant device control changes device financing economics for the unit-economics framework.

Next Step

Talk to Lockia engineering about your financing program

If you operate or are launching a device financing program and want to evaluate Lockia as the infrastructure platform, the most useful next step is a technical call. We will walk through your billing-system integration, your collections workflow, your geographic footprint, and how Lockia's architecture maps to the deployment contract your operation requires.

PayJoy is a registered trademark of PayJoy, Inc. Apple and Apple Business Manager are trademarks of Apple Inc. Google and AOSP are trademarks of Google LLC. This comparison reflects publicly available information published by each company about its own product, and is provided for evaluation purposes only.