Protocol Security Compliance Anti-Fraud AML Whitepaper API Reference ghostpaymesh.com
v2.0 — Protocol Documentation

GhostPay Mesh
Protocol Documentation

Everything you need to understand, implement, and integrate with the GhostPay Mesh cryptographic offline-first payment protocol.

Protocol Specification

PLC structure, lifecycle states, offline transfer protocol, settlement flow, and replay protection mechanisms.

Read specification →

Security Model

Threat model, cryptographic primitives, device-bound keys, transfer security, and privacy-by-design architecture.

View security model →

Whitepaper

Academic-grade analysis of the protocol design, security proofs, use cases, and the roadmap for the GhostPay Mesh network.

Read whitepaper →
{}

API Reference

REST API endpoints for PLC management, settlement, device registration, and merchant integration.

Open API docs →

Compliance & Regulatory

AML/KYC tiered identity, transaction limits, BACEN compatibility, audit trails, and privacy-preserving traceability.

View compliance →

Anti-Fraud System

Device fingerprinting, risk scoring, double-spend prevention, chain integrity verification, and circuit breakers.

View anti-fraud →

Anti Money Laundering

Transaction monitoring, suspicious pattern detection, COAF reporting, sanctions screening, and Brazilian regulation compliance.

View AML docs →

Quick Start

Create a PLC
// Issue a Cryptographic Liquidity Promise (PLC)
POST /api/v1/plcs

{
  "amount": 150.00,
  "currency": "BRL",
  "issuer_pubkey": "ed25519:abc123...",
  "expires_in": 86400
}

// Response
{
  "id": "plc_7f3a...",
  "status": "ISSUED",
  "commitment_hash": "sha256:e3b0c44...",
  "signature": "sig_ed25519:..."
}

Offline-First

PLCs can be created, transferred, and verified entirely offline using BLE, NFC, or QR codes. Settlement occurs when connectivity returns.

Cryptographically Secure

Ed25519 signatures, XChaCha20-Poly1305 encryption, SHA-256 commitments, and Argon2id key derivation protect every transaction.

Privacy by Design

Zero personal data required. No KYC. Device-bound keys never leave the device. Compliant with BACEN regulations.