← ClaudeAtlas

alternative-payments-payments--payoutslisted

Alternative Payments transactions and payouts: transaction types, statuses, and the customer/invoice/payment-method filters; payout objects and the transactions that compose them for reconciliation. A read-only surface -- there is no create-payment or direct-charge operation.
WYRE-AI/msp-claude-plugins · ★ 46 · DevOps & Infrastructure · score 81
Install: claude install-skill WYRE-AI/msp-claude-plugins
# Alternative Payments Payments & Payouts ## Overview This skill covers the **read-only** money-visibility surface in Alternative Payments: transactions (individual payment records) and payouts (settled batches of funds deposited to your account). It is used for reporting and reconciliation — matching transactions to invoices and customers, and tracing which transactions make up a given payout. There is **no create-payment tool here.** This integration never charges a card or moves money (`POST /payments`, the direct charge, is excluded by design). To collect from a customer, generate a hosted payment link or payment request — see [Alternative Payments Invoicing](../invoicing/SKILL.md). ## Anti-triggers - **Collecting money rather than reporting on it** — this surface is read-only; hosted payment links and payment requests are `alternative-payments-invoicing`. - **Recording a receipt against an invoice in the books** — use `xero-payments` or `qbo-payments`. - **A payment captured against a Quote Manager sales order** — use `kaseya-quote-manager-quotes`. ## Core Concepts ### Transactions A transaction is a single payment event against an invoice or payment request. Note that the transactions resource lives at `GET /payments` — but only the read (list/get) verbs are exposed. | Field | Type | Description | |-------|------|-------------| | `id` | string | Transaction identifier | | `type` | string | Transaction type (e.g. `payment`, `refund`) | | `status` | strin