a "borderless" job market that still checks your papers

Problem statement

Because most refugees are blocked from the formal local labor market — work permits are hard to get, host-country unemployment is high, and credentials don't transfer — humanitarian and donor strategies increasingly pitch digital platform work (freelancing on Upwork, microtasking, e-commerce on Jumia, delivery, etc.) as a route to self-reliance that "doesn't care where you are." In practice the platforms care a great deal. Onboarding requires identity verification, a phone number, and a bank or mobile-money account; payouts route through services (e.g., PayPal, certain banks) that are unavailable, restricted, or distrust refugee documentation in many host countries. A refugee with skills, a phone, and a connection can still be unable to open the account or pass the verification step that turns work into paid work.

Why this matters

Forced displacement now exceeds 120 million people, the majority hosted in low- and middle-income countries where local jobs are scarce and legally restricted for refugees. The digital-livelihoods pitch is being scaled by major agencies and donors, so getting it wrong wastes scarce funding and, worse, trains people for work they then can't get paid for. The access gap is concrete: globally 93% of refugees are covered by at least a 2G network, yet they are about 50% less likely than the surrounding population to own an internet-enabled phone. Layer on documentation and payment exclusion, and a "borderless" opportunity reproduces the very barriers it was meant to bypass — and can entrench precarious, sub-minimum "decent-work deficits" for those who do break in.

What’s been tried and why it hasn’t worked

Digital-livelihoods programs have largely invested in the visible, easy layer — skills training and connectivity/device access — while leaving the transactional infrastructure (identity verification, KYC, and getting paid) unsolved. The ILO's three-country study (Kenya, Uganda, Egypt) found young refugees do turn to platforms in the absence of local work, but stall on a stack of barriers: no accepted ID/work permit, no access to digital payment mechanisms, unreliable electricity and internet, insufficient digital skills, and language gaps for global-market gigs. Even when training and a phone are provided, the platform's own sign-up and payout requirements — built for citizens of high-income markets — become the binding constraint. Some platforms also geo-restrict or down-rank accounts from certain countries, and global clients distrust unfamiliar locations. The result, the report warns, is that "without coordinated action, the digital economy can reinforce deeply rooted social and economic inequalities" rather than relieve them.

What would unlock progress

The unlock is in the plumbing between a refugee's verified identity and a platform payout, not more coding bootcamps. Refugees often do hold credentials — UNHCR registration, biometric IDs, mobile-money wallets — that platforms simply don't recognize. A bridge that lets a refugee's existing, verifiable identity and a low-barrier payout channel satisfy a platform's KYC/payment requirements would convert latent skills into actual income. Adjacent precedents to mine: humanitarian cash-transfer rails (which already move money to documented refugees at scale), mobile-money interoperability, and "verifiable credential" approaches. The 2024 UNHCR–ILO joint report catalogs emerging practices to build on.

Entry points for student teams

A team could map, end to end, exactly where a refugee in one host country gets stuck onboarding to one specific platform — then prototype the single missing connector (e.g., a verification/payout intermediary that translates UNHCR registration + mobile money into a platform-acceptable identity and payment method), or design an agency-side "platform-readiness" service that pairs payout access with skills. Relevant disciplines: service design, fintech/payments, digital identity, development economics, and law/policy (KYC, work-permit rules). A realistic semester deliverable: a validated user-journey map plus a working prototype or partnership concept for the verification-and-payout bottleneck for one platform in one host context.