payabli/integration-skills

payabli-disputes

Use when handling chargebacks or transaction returns on Payabli — responding to disputes, submitting evidence, processing ACH return codes, or recovering from a failed refund.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/payabli/integration-skills --skill payabli-disputes

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

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

Payabli disputes (chargebacks & returns)

Handle money coming back out after the fact: chargebacks, ACH returns, and failed refunds.

Disputes and returns originate externally — a cardholder or bank starts a chargeback, the processor returns an ACH debit. Through the API you can only read and respond, never create them. Read both through GET /Query/chargebacks (a record's Method and status distinguish a card chargeback from an ACH return). To exercise this flow in sandbox, simulate a chargeback or ACH return first — see payabli-testing.

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 ## SDK value.

Chargebacks

When a cardholder disputes a charge, the funds are debited immediately and a fee applies. You have a limited window (about 10 days) to respond with evidence via POST /ChargeBacks/response/{Id} — transaction receipt, customer communication, terms accepted, and transaction-specific proof. You cannot refund a transaction once its chargeback is initiated. https://docs.payabli.com/guides/pay-ops-disputes-chargebacks-returns-overview.md

ACH returns

Returned ACH debits carry return codes (for example R01 insufficient funds, R02 account closed, R10 unauthorized). Monitor your return rates — exceeding network thresholds risks suspension. https://docs.payabli.com/guides/pay-ops-transfers-ach-returns.md

Failed refunds

A failed refund — especially ACH — usually surfaces later as an ACH return, not an immediate error. If a refund fails, confirm it was initiated correctly for the right transaction, then make the customer whole another way (store credit, check, or another method). Card refunds rarely fail. https://docs.payabli.com/guides/pay-in-refunds-failures-overview.md

Boundary

Voiding or refunding a healthy transaction (the normal reversal decision) is not this skill — that's payabli-accept-payments. This skill is for chargebacks, returns, and recovering from a refund that failed.

같은 저장소의 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일