alternative-payments-customers

# Alternative Payments Customers Management ## Overview Customers are the foundational entity in Alternative Payments — every invoice, payment request, transaction, and payout traces back to a customer. For MSPs, a customer is typically a managed services client (a business you bill on a recurring or project basis). Each customer can have one or more **users** — the individual contacts at that business who receive invoices and pay them. This skill covers the read + safe-write customer surface: listing, retrieving, and creating customers, adding users, and archiving (a destructive operation). There is no direct money-movement operation here. ## Core Concepts ### Customers and Users | Entity | Description | MSP Example | |--------|-------------|-------------| | Customer | A business you bill | "Acme Corp" | | User | A contact at that business | "billing@acme.com" | A customer is created first; users are then attached under `/customers/{id}/users`. Invoices and payment requests reference the customer. ### Customer Status | Status | Description | |--------|-------------| | `active` | Normal, billable customer (default) | | `archived` | Hidden from default lists; preserved for history | Archiving is performed with `DELETE /customers/{id}` — it does **not** hard-delete the record. Treat it as destructive and confirm before running it. ## Field Reference ### Customer Fields | Field | Type | Required | Description | |-------|------|----------|-------------| | `id` | stri...