payabli/integration-skills

payabli-tokenization

Use when working with stored payment methods in Payabli — saving a customer's card or bank account for repeat billing, saving a vendor's method for payouts, sharing tokens across paypoints, or using temporary tokens for one-time captures.

소스 보기

사용 방법

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

시작 전 확인

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

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

Payabli tokenization

Store payment methods as tokens so they can be reused without handling raw card or bank data. Cross-product: customer-scoped for Pay In, vendor-scoped for Pay Out.

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

Pick the scope

  • Customer-scoped (Pay In) — save a customer's card or bank account for repeat billing.
  • Vendor-scoped (Pay Out) — save a vendor's payout method.

Customer-scoped tokenization

Three ways to capture and store a customer method, in order of increasing control and PCI responsibility:

  • Embedded component (low-code) — EmbeddedMethod UI (or the PayMethod UI lightbox) with the method action captures the card and returns a storedMethodId. Card data never touches the partner's server. The EmbeddedMethod UI guide lists `paymentDetails` (and `customerData`) as required to save a method with the method action — without paymentDetails the save can fail with no clear error. https://docs.payabli.com/guides/pay-in-components-embeddedmethod-ui.md
  • Embedded component + temporary token flow — the same component, configured with temporaryToken: true, captures the card (so PCI scope stays low) and returns a one-time temp token as referenceId. The partner then drives the API call for full control: convert it (POST /TokenStorage/add with tokenId), charge it (POST /v2/MoneyIn/getpaid with storedMethodId), or charge-and-save (saveIfSuccess: true). Use the v2 Money In endpoints on this path. This is the bridge between low-code components and direct API — not a way to handle raw card data. https://docs.payabli.com/guides/platform-developer-tokenization-temp-flow.md
  • Direct API — POST /TokenStorage/add with raw card data returns the saved method's token as responseData.referenceId (there's no storedMethodId field in the response). Pass that value as storedMethodId when you charge. Read referenceId, not methodReferenceId, which can differ when you convert a temp token. Here the partner handles card data, which raises PCI responsibility (see payabli-fundamentals → PCI scope). https://docs.payabli.com/guides/platform-developer-tokenization-save-method.md

Field-name gotcha: a temp token is passed as tokenId to TokenStorage endpoints, but as storedMethodId to MoneyIn endpoints.

Reuse a stored method by passing its storedMethodId to a charge — see payabli-accept-payments.

To read a customer's saved methods back, GET /Customer/{customerId} and use the top-level StoredMethods[] array — there is no token-list or Query/reporting route for stored methods. Each entry's token is its IdPmethod (the value you charge as storedMethodId).

Vendor-scoped tokenization

Vendors self-enroll their payout method (ACH, vCard, or check) through a payment link; the chosen method is tokenized onto the vendor record and used in payouts via its storedMethodId. The payout flow itself lives in payabli-send-payments. https://docs.payabli.com/guides/pay-out-developer-payment-links-manage.md

Read a vendor's saved methods the same way as a customer's: GET /Vendor/{idVendor} and use the top-level StoredMethods[] array (each entry's token is its IdPmethod, the value you pay as storedMethodId). There is no token-list or Query/reporting route for stored methods.

Token types and sharing across paypoints

  • Merchant (default) — scoped to a single paypoint.
  • Universal — shareable across paypoints on the same processor.
  • Network — card-network managed.

Cross-paypoint sharing (universal/network) requires Payabli enablement, and the token must be created after enablement; the paypoints must share the same customer (customerNumber). A token created before enablement won't share. https://docs.payabli.com/guides/platform-developer-tokenization-share-tokens.md

Keep stored cards current

Card Account Updater is a paid add-on (requires Payabli enablement) that refreshes stored card tokens before they expire. When enabled, subscribe to the CardUpdaterComplete notification to act on results that need follow-up. https://docs.payabli.com/guides/platform-tokenization-card-updater.md

PCI

Embedded components and the temporary token flow keep card data off the partner's servers. Do not recommend raw card handling. PCI guidance is engineering best practice, not legal advice — see payabli-fundamentals → PCI scope. Direct questions about PCI scope to the Payabli team.

Boundaries

  • Charging a saved customer method → payabli-accept-payments
  • Paying a vendor with a saved method → payabli-send-payments
같은 저장소의 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일