payabli/integration-skills

payabli-testing

Use when testing a Payabli integration — sandbox usage, test cards and bank data, simulating events, or preparing a sandbox-to-production cutover.

ソースを見る

使い方

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

開始前の確認

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

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

Payabli testing

Exercise an integration in sandbox before going live.

Load fundamentals first

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

On load

If payabli-integration.md exists at the repo root, read it; honor its ## Environment value (default sandbox until certified).

Sandbox

Sandbox uses its own base URL, https://api-sandbox.payabli.com/api. Partners receive a sandbox account at integration kickoff. Sandbox transactions auto-settle daily (default 9 PM UTC; adjustable by your Payabli contact). https://docs.payabli.com/developers/platform-developer-testing-guide.md

Test cards and bank data

Use Payabli's published test cards and test bank accounts — including cards that force a decline — rather than inventing values. https://docs.payabli.com/guides/test-accounts-reference.md

For ACH payouts, the account-holder name (achHolder) accepts letters and spaces only — a value carrying digits or hyphens (for instance a tagged identifier reused as a name) fails with 400 "Account holder name cannot contain special characters". Use a plain name.

What needs Payabli to trigger in sandbox

Most of sandbox is self-serve, but a few things can't be triggered on your own — you have to ask your Payabli contact to fire them. This trips up integrators constantly, so plan for it: build and verify everything self-serve first, then batch the Payabli-side triggers with your contact rather than getting blocked mid-test.

  • Some webhook events — payment-event webhooks (for example ApprovedPayment) fire when you run the transaction, but some events won't fire on their own.
  • ACH returns — not self-service. Send your Payabli Solution Engineer the ACH transaction IDs you want turned into returns.
  • Some transaction-status transitions — a transaction won't always advance through its lifecycle on its own.
  • Funding triggers — advancing to settled/funded. This gates anything settlement-dependent, most commonly refunds (which need a settled transaction).

Card chargebacks, by contrast, are self-service: settle a card transaction first, then import it as a dispute from the Payabli Portal (Pay In reports). The import moves the transaction into a chargeback and fires the chargeback-received webhook; handle the dispute after that with payabli-disputes.

https://docs.payabli.com/developers/platform-developer-testing-guide.md

Keep responses small when you run calls

When you run calls and read the responses back — exercising a flow, debugging, or verifying a result — query narrowly: request the specific record, and filter or paginate list endpoints instead of pulling whole collections. Payabli responses are large and vary per endpoint, so a broad query returns far more than you need and floods context. This only matters when an agent is executing and interpreting output; integration code you write for the app to run at runtime isn't affected.

Prepare for production cutover

Production access requires Payabli certification and underwriting — this is not self-serve; it's coordinated with the Payabli team. Prepare by exercising every flow your integration uses in sandbox first, so the review goes smoothly.

Boundary

Configuring and handling webhook events → payabli-webhooks.

同じリポジトリから

関連する 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日