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 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

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
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日