Como usar
- Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
- Consulte no original as ferramentas, credenciais e ambientes necessários.
- Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/payabli/integration-skills --skill payabli-certification-prepAntes de começar
- A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
- Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.
Payabli certification prep
Rehearse the certification test scenarios in sandbox so the partner walks into their Payabli certification call confident. This preps for the call — it does not certify; certification happens with a Payabli SE.
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 and run only the recipes for the products in scope (## Pay In, ## Pay Out, ## Webhooks, ## Tokenization). Don't walk a partner through Pay Out cases if they only integrated Pay In.
How to use
- Pick the areas in scope (from the plan, or ask).
- Load the matching reference(s) and run each recipe in sandbox, recording the reference ID and result.
- Most recipes are self-serve. A few need a Payabli-side trigger (a settled/funded state, or certain webhook events) — those are marked. Note them and raise them on the cert call rather than getting blocked.
- When the self-serve set passes, the partner is ready for the certification call.
Recipes by area
- Pay In — cards, ACH, auth/capture, void/refund:
references/pay-in.md - Stored methods / tokenization:
references/tokenization.md - Subscriptions:
references/subscriptions.md - Webhooks:
references/webhooks.md - Pay Out — payouts, vendors, bills:
references/pay-out.md
Results scorecard
Record each recipe's outcome in a table like this and bring it to the cert call:
| Area | Recipe | Expected | Actual (code · ref ID) | Pass? |
|---|---|---|---|---|
| Pay In | Sale | A0000 approved | ||
| Pay In | Decline | D0100 decline | ||
| Pay In | Void (pre-settlement) | A0003 canceled | ||
| Pay In | Over-amount / early refund | E7002 rejected | ||
| Tokenization | Token not found | 7007 | ||
| Webhooks | ApprovedPayment delivery | HTTP 200 ack |
Add a row per recipe you run. For anything that needs a Payabli-side trigger, mark it "raise on call" instead of pass/fail.
What needs a Payabli-side trigger (flag, don't get stuck)
Successful refunds (need a settled transaction → funding), cancel-after-settled, and chargeback/return webhook events require Payabli to trigger them in sandbox. Subscription execution is self-serve but time-based — schedule near-term and wait. See payabli-testing.
Boundary
Sandbox mechanics (test cards, environments, what needs a trigger) → payabli-testing. This skill is the certification rehearsal specifically.