← ClaudeAtlas

alternative-payments-customerslisted

Alternative Payments customers and their users: customer fields and status, the customer/user relationship, MSP client onboarding, and the destructive archive operation that requires confirmation.
WYRE-AI/msp-claude-plugins · ★ 46 · AI & Automation · score 81
Install: claude install-skill WYRE-AI/msp-claude-plugins
# 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. ## Anti-triggers - **The same client in the accounting ledger** — an Alternative Payments customer is a billing target on the payment rail with no GL contact record; use `xero-contacts` or `qbo-customers`. - **The same client in the CRM** — use `hubspot-companies` or `salesbuildr-companies-contacts`. - **Billing that customer** — use `alternative-payments-invoicing`. ## 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