使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
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
methodaction captures the card and returns astoredMethodId. Card data never touches the partner's server. The EmbeddedMethod UI guide lists `paymentDetails` (and `customerData`) as required to save a method with themethodaction — withoutpaymentDetailsthe 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 asreferenceId. The partner then drives the API call for full control: convert it (POST /TokenStorage/addwithtokenId), charge it (POST /v2/MoneyIn/getpaidwithstoredMethodId), 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/addwith raw card data returns the saved method's token asresponseData.referenceId(there's nostoredMethodIdfield in the response). Pass that value asstoredMethodIdwhen you charge. ReadreferenceId, notmethodReferenceId, which can differ when you convert a temp token. Here the partner handles card data, which raises PCI responsibility (seepayabli-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