generated: '2026-07-20'
method: searched
source: https://github.com/payabli/integration-skills
notes: Provider-published Agent Skills (Payabli integration-skills repo, MIT). Also distributed as a Claude
  plugin marketplace. Saved verbatim; AGENTS.md is the top-level guide.
api: openapi/payabli-api-reference-openapi.json
agents_md: skills/payabli-AGENTS.md
skills:
- file: payabli-accept-payments.md
  name: payabli-accept-payments
  description: 'Use when writing code that accepts payments through Payabli: charging cards or ACH, integrating
    embedded payment components or a hosted payment page, handling Apple Pay or Google Pay, or processing
    voids and refunds. Boundaries — subscriptions: payabli-subscriptions; invoices and payment links:
    paya'
- file: payabli-bills.md
  name: payabli-bills
  description: 'Use when building accounts-payable automation on Payabli — capturing vendor bills (manual
    entry or OCR), routing them through approval, and paying them through Pay Out. Distinct from raw payouts
    (payabli-send-payments): a bill starts with a vendor invoice that may need approval before payment.
    Reads'
- file: payabli-certification-prep.md
  name: payabli-certification-prep
  description: Use when a partner wants to rehearse the Payabli certification test scenarios in sandbox
    before their certification call — running the checks they can self-serve and confirming expected results.
    This is prep for the call, not self-certification (certification happens with a Payabli SE). Reads
    payabl
- file: payabli-customers.md
  name: payabli-customers
  description: Use when working with Payabli customer records — creating, reading, listing or searching,
    updating, or deleting customers, or showing a customer's transaction history (any CRM or customer
    portal). Covers the Customer API and customer queries. Money movement lives in payabli-accept-payments,
    saved pa
- file: payabli-disputes.md
  name: payabli-disputes
  description: Use when handling chargebacks or transaction returns on Payabli — responding to disputes,
    submitting evidence, processing ACH return codes, or recovering from a failed refund. Routine voids/refunds
    of healthy transactions are NOT here — those live in payabli-accept-payments. Reads payabli-integratio
- file: payabli-fundamentals.md
  name: payabli-fundamentals
  description: Foundation reference for any Payabli integration work. Use it for authentication, environment
    selection (sandbox vs. production), the org/paypoint/entrypoint ID hierarchy, paypoint scoping, idempotency,
    and error handling. Other Payabli skills load it first. Reads payabli-integration.md on load if p
- file: payabli-getting-started.md
  name: payabli-getting-started
  description: Use at the start of a Payabli integration, when a developer wants to add payments to an
    existing app (accept payments, save payment methods, subscriptions, invoices, payouts, or bill pay).
    Interviews for the use-case shape, maps it to the right Payabli components and paypoint architecture,
    detects t
- file: payabli-invoices.md
  name: payabli-invoices
  description: Use when sending invoices and collecting payment from customers — invoice creation and
    delivery (email, SMS, or link), customer-facing payment links, or Pay By SMS. Taking the payment itself
    lives in payabli-accept-payments; paying vendors lives in payabli-bills. Reads payabli-integration.md
    on load
- file: payabli-mcp-setup.md
  name: payabli-mcp-setup
  description: Use when the developer wants to install or configure the official Payabli Docs MCP server
    in their coding agent (Claude Code, Cursor, Codex, Gemini, Copilot CLI). Triggers on "install the
    Payabli Docs MCP," "set up Payabli Docs MCP," or "add the Docs MCP server." Reads payabli-integration.md
    on load
- file: payabli-reporting.md
  name: payabli-reporting
  description: Use when an agent needs the Query API — to build reports and exports, reconcile batches,
    track settlement, or back a list/detail data UI such as a customer's transaction history. Explains
    the filter syntax, pagination, and the response envelope. Reads payabli-integration.md on load if
    present.
- file: payabli-send-payments.md
  name: payabli-send-payments
  description: Use when the developer is sending money out through Payabli — paying vendors via payout.
    Covers the MoneyOut flow, managed vs. on-demand payables, vendors and vendor enrichment, reissue,
    ghost cards, and Positive Pay. AP automation (bills and OCR) lives in payabli-bills. Reads payabli-integration.md
- file: payabli-subscriptions.md
  name: payabli-subscriptions
  description: Use when building recurring billing on Payabli — subscriptions, autopay, scheduled charges,
    retry/dunning logic, or moving one-time charges to recurring. Covers the Subscription API, CIT/MIT
    indicators, and lapse handling. One-time charges live in payabli-accept-payments. Reads payabli-integration.m
- file: payabli-testing.md
  name: payabli-testing
  description: Use when testing a Payabli integration — sandbox usage, test cards and bank data, simulating
    events, or preparing a sandbox-to-production cutover. Reads payabli-integration.md on load if present.
- file: payabli-tokenization.md
  name: payabli-tokenization
  description: 'Use when working with stored payment methods in Payabli — saving a customer''s card or
    bank account for repeat billing, saving a vendor''s method for payouts, sharing tokens across paypoints,
    or using temporary tokens for one-time captures. Cross-product: Pay In is customer-scoped, Pay Out
    is vendor-s'
- file: payabli-vendors.md
  name: payabli-vendors
  description: Use when working with Payabli vendor records — creating, reading, listing or searching,
    updating, or deleting vendors, or showing a vendor's payment history (an AP directory, vendor portal,
    or supplier management screen). Covers the Vendor API and vendor queries. Sending payouts lives in
    payabli-sen
- file: payabli-webhooks.md
  name: payabli-webhooks
  description: Use when writing or modifying a webhook handler for Payabli events — receiving and processing
    event payloads, acknowledging delivery, authenticating incoming webhooks, handling retries idempotently,
    configuring event subscriptions, routing events across multiple paypoints, or weighing the webhooks-v