payabli/integration-skills

payabli-getting-started

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).

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/payabli/integration-skills --skill payabli-getting-started

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Payabli getting started

The entry point for adding a Payabli-powered capability to an existing application. Translate the developer's stated goal into concrete Payabli pieces, confirm the architecture, and write an optional payabli-integration.md plan that downstream skills read.

Load fundamentals first

If payabli-fundamentals is not already loaded, load it now, then continue.

Step 1 — Listen

Read the developer's stated capability goal as given ("add card payments," "pay our vendors," "add bill OCR"). Do not recommend a product. Map what they said to Payabli pieces.

Step 2 — Map the capability to components

Match the goal to the rows below. Fetch the linked .md page for depth, and hand off to the named skill when the developer starts building that piece.

CapabilityPayabli piecesUsually alsoDepth
Accept card or ACH paymentsPay In — embedded components or hosted pagewebhooks; tokenization if saving methodspayabli-accept-payments · https://docs.payabli.com/guides/pay-in-overview.md
Save payment methods for reuseTokenization (customer-scoped)Pay Inpayabli-tokenization · https://docs.payabli.com/guides/platform-tokenization-overview.md
Recurring billing / subscriptionsSubscription APItokenization, webhookspayabli-subscriptions · https://docs.payabli.com/guides/pay-in-developer-subscriptions-manage.md
Send invoices / payment linksInvoices and payment linkswebhookspayabli-invoices · https://docs.payabli.com/guides/pay-in-developer-invoices-manage.md
Embedded checkoutEmbedded components vs. hosted page (see Step 3)tokenizationpayabli-accept-payments · https://docs.payabli.com/guides/pay-in-components-overview.md
Pay vendors / payoutsPay Out (/MoneyOut)vendors, webhookspayabli-send-payments · https://docs.payabli.com/guides/pay-out-overview.md
Automate bill pay / AP (incl. bill OCR)Bills — bill capture (manual entry or OCR)Pay Out to pay thempayabli-bills · https://docs.payabli.com/guides/pay-out-developer-bills-manage.md
Real-time status updatesWebhooks (weigh against polling)—payabli-webhooks · https://docs.payabli.com/guides/pay-ops-notifications-webhooks-vs-polling.md
Reports / reconciliationPay Ops reporting—payabli-reporting · https://docs.payabli.com/guides/pay-ops-overview.md
Onboard merchants through the APIIntelligent boarding (beta, opt-in) — business, paypoint, people, bank accounts, applicationwebhooks and polling for statuspayabli-boarding · https://docs.payabli.com/guides/pay-ops-boarding-object-model-overview.md
Move an integration off legacy boardingIntelligent boarding migration—payabli-boarding-migration · https://docs.payabli.com/guides/pay-ops-developer-boarding-legacy-migrate.md

Step 3 — Recommend best practice; stay neutral on genuine choices

  • Recommend where there is a technical best practice: idempotency for money-moving calls, and embedded components as the default Pay In surface (lowest PCI scope).
  • Enumerate neutrally where the choice is genuinely the partner's: which products to integrate, and how to collect payments — embedded components (recommended, in-app, Payabli handles card data; can be extended with the temporary token flow for API control), a hosted payment page (no-code, redirects off-site), or direct API where the partner handles card data (raising their PCI responsibility). PCI guidance is engineering best practice, not legal advice — point them at it and send specific PCI scope questions to the Payabli team. See https://docs.payabli.com/guides/pay-in-components-overview.md, https://docs.payabli.com/guides/pay-in-payment-page-overview.md, and https://docs.payabli.com/guides/platform-pci-best-practices-overview.md.
  • Never nudge toward a choice on Payabli's business interest (margin, upsell).

Step 4 — If payouts are in scope, ask the right decision

The partner's decision is managed vs. on-demand payables — ask that. The payment method (vCard, ACH, check) is the vendor's, set on the recipient side; under managed payables, Payabli's team handles vendor outreach (vCard → ACH → check). Do not ask the partner to pick a method, and do not lead with one. See https://docs.payabli.com/guides/pay-out-managed-payables-overview.md.

Step 5 — Infer the paypoint model, then confirm

Listen for cues, propose the model, and confirm — do not ask cold.

  • "my customers," "the merchants we serve," "each location" → multi (ISV managing many paypoints).
  • One business taking its own payments → single.

Entities reference: https://docs.payabli.com/guides/platform-entities-overview.md

Step 6 — Detect the language; suggest the SDK if it fits

Detect the project's language from its manifest files. Direct API and the SDKs are both fully supported — don't assume an SDK. If the project is in a supported language and nothing requires raw HTTP, suggest the matching SDK as an option (it handles auth, typing, and serialization); don't push it. Use the mapping in payabli-fundamentals → references/sdk-and-language-detection.md. Record what the integration uses in the plan under ## SDK (raw-http for direct API).

Step 7 — Offer the plan artifact

Offer to write payabli-integration.md at the repo root, capturing the decisions above. Use the format and controlled vocabulary in references/integration-plan-template.md. Downstream Payabli skills read this file on load for architecture-aware guidance.

If payabli-integration.md already exists, ask whether to update it or archive it (rename to payabli-integration.<date>.md) and start fresh.

Step 8 — Recommend the Docs MCP

Recommend installing the official Payabli Docs MCP server for ongoing Q&A during the build. To install it, point the developer to the payabli-mcp-setup skill.

同じリポジトリから

関連する Skills

すべての Skills
payabli
コミュニティ

payabli-accept-payments

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: payabli-invoices; disputes and refund-failure recovery: payabli-disputes. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-bills

Use when building accounts-payable automation on Payabli — capturing vendor bills (manual entry or OCR) and paying them through Pay Out. Distinct from raw payouts (payabli-send-payments): a bill is a captured vendor invoice that you then pay. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-boarding

Use when onboarding merchants to Payabli through the API — creating the business, its people, paypoints, and bank accounts, opening a boarding application, validating and submitting it, answering underwriting requests, or tracking an application's status and enablement. Moving an existing integration off the legacy /Boarding/ endpoints lives in payabli-boarding-migration. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日
payabli
コミュニティ

payabli-boarding-migration

Use when moving an existing integration off Payabli's legacy boarding endpoints (/Boarding/app, /Boarding/read, boarding links) to intelligent boarding — converting legacy application payloads to the new records, mapping fields, values, and statuses, or planning the cutover before the legacy sunset. Building boarding from scratch lives in payabli-boarding. Reads payabli-integration.md on load if present.

1時間の導入数
1
GitHub Stars
0
更新日
10月23日