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 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

모든 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일