Introduction

Build, deploy, operate.

Architecture references, deployment guides, API specs, and operator runbooks. Every module ships with a docset matched to its release.

AppDevs is an infrastructure platform for regulated payment businesses. The platform layer covers wallets, remittance, card issuing, banking, and commerce — every module shares a ledger, a permission model, and a deployment topology. This documentation walks through deploying, integrating, and operating.

Quick start

Most operators are running their first transaction in under thirty minutes. The quick start uses Docker Compose to spin up a Wallet Core instance with the ledger, mobile app backend, and operator console pre-configured against test data.

bash · quickstart

# 1. Clone the wallet-core starter
git clone https://github.com/appdevs/wallet-core-starter
cd wallet-core-starter

# 2. Boot the local stack
docker compose up -d

# 3. Run database migrations
./bin/migrate up

# 4. Seed sandbox data
./bin/seed --env sandbox

# 5. Visit the operator console
open http://localhost:8080

Architecture overview

Every AppDevs module follows the same four-layer topology: edge surfaces (mobile apps, partner consoles, embedded SDKs), core services (business logic, validation, orchestration), data plane (double-entry ledger plus event stream), and partner rails (banks, KYC, payment processors). Modules compose through shared events on the data plane.

Edge

Mobile apps, hosted pages, embedded SDKs

Service

Business logic, validation, orchestration

Data

Double-entry ledger + event stream

Integration

Banks, KYC, processors

Authentication

AppDevs APIs authenticate with rotating API keys issued from the operator console. Every key carries a scope, an environment, and an expiry. Production keys require approval from a second operator with admin scope.

bash · authenticated request

# Issue an API key from the operator console
curl https://api.appdevs.local/v1/wallets \
  -H "Authorization: Bearer ${APPDEVS_KEY}" \
  -H "Content-Type: application/json"

First transaction

With the Wallet Core sandbox running, create a customer through the onboarding endpoint, run the simulated KYC flow, top up the wallet with a sandbox transfer, and post a transfer between two customers. Every step writes a posting to the ledger you can inspect through the operator console.

bash · POST /v1/transfers

# Post a wallet-to-wallet transfer
curl https://api.appdevs.local/v1/transfers \
  -X POST \
  -H "Authorization: Bearer ${APPDEVS_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "from_wallet": "wallet_8201",
    "to_wallet":   "wallet_8294",
    "amount":      4250,
    "currency":    "USD",
    "memo":        "Coffee + tip"
  }'

Going to production

Production deployment follows a documented checklist: sponsor bank contracts signed, KYC provider configured, production keys rotated, observability wired to your APM, on-call schedule defined, and the production runbook reviewed with your solutions architect.

01Sponsor bank contracts signed
02KYC provider configured · production tier
03Production API keys rotated
04Observability wired to your APM
05On-call schedule defined
06Production runbook reviewed with solutions architect

Explore product references →