Kura Technologies

The core flow is a chain of real-world state: a sponsor or NGO funds USDC, a beneficiary directs spending, a merchant accepts at the point of sale, and value either pays out or continues circulating merchant-to-merchant.

That requires fiat-to-stablecoin on-ramp orchestration, transaction state machines, webhook handling, idempotency, retries, asynchronous provisioning, ledger consistency, and recovery when an external provider and internal state disagree.

The merchant platform has moved toward a non-custodial wallet and POS experience: one wallet per business, background provisioning after KYB, merchant-controlled signing, Stellar account activation, USDC trustlines, and optional external wallet registration.

Around that sit the product surfaces merchants actually need—business and location models, store and cashier permissions, QR acceptance, history, recovery, analytics, and supplier payments.

Activation is a lifecycle, not a form. Authentication, Google SSO, email and phone OTP, business KYB, owner KYC, location verification, hosted verification, and webhooks all have to resolve into a policy: when is a merchant live, and what gets provisioned automatically after approval.

The strongest engineering stories are operational: idempotent APIs, asynchronous jobs, webhook ordering, atomic state transitions, and reconciling internal ledgers with external financial systems. Production work includes AWS monitoring and tracing failures through providers rather than treating the API as a closed box.

Security work follows the money: separating authentication from transaction signing, thinking through wallet and key lifecycle, payment authorization, webhook verification, and compliance-aware design for non-custodial wallets.

The role is not only backend implementation. It includes merchant onboarding design, NGO workflows, demos, customer feedback, provider evaluation, and translating field constraints—feature phones, cash, uneven bank access—into architecture.