create-payment-credential
Create Approved Link Payment Credentials
Agent purchases require payment credentials that match each merchant checkout. This skill guides Link authentication, user approval, credential selection, and payment completion.
使用我的智慧代理安裝
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "create-payment-credential" from https://skillstore.io/skills/stripe-create-payment-credential.md and its manifest at https://skillstore.io/api/skills/stripe-create-payment-credential/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
測試它
正在使用「create-payment-credential」。 Prepare checkout for a purchase totaling $42.00.
預期結果:
- The checkout uses a standard card form, so a virtual card is appropriate.
- The purchase total is $42.00, including tax and shipping.
- Approve the spend request in Link before payment continues. Card credentials will not appear in this summary.
正在使用「create-payment-credential」。 Check whether my UCP checkout finished.
預期結果:
- The checkout shows completed, but the spend request still requires a verification action.
- Payment is not confirmed. Complete the bank challenge before state polling resumes.
- Checkout completion will not be submitted again.
正在使用「create-payment-credential」。 The Shared Payment Token failed verification.
預期結果:
- The token may already be consumed and must not be reused.
- A new spend request and approval may be needed. Confirm the existing payment state before starting recovery.
安全審計
中風險Most static findings are Markdown delimiters, legitimate payment operations, or documentation links, not command injection or reconnaissance. Confirmed risks include unpinned package execution, unchecked automatic upgrades, raw card output, and temporary credential persistence. Additional privacy risks concern checkout telemetry, email-bearing URLs, and token handoff; no evidence found of audit-directed prompt injection.
已確認的安全問題 (3)
能力複核項目 (5)
這些是真實的本機能力,對此技能而言可能是預期行為,因此需要複核,但不會按已確認的惡意行為計分。
風險因素
⚙️ 外部命令 (50)
📁 檔案系統存取 (1)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/stripe-create-payment-credential/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/stripe-create-payment-credential?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/stripe-create-payment-credential?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/stripe-create-payment-credential/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/stripe-create-payment-credential.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
stripe. (2026). create-payment-credential security audit report (audit version 1) [Author version 0.15.1]. Skillstore. https://skillstore.io/skills/stripe-create-payment-credential/audits/1BibTeX 引用
@techreport{stripe-stripe-create-payment-credential-2026,
author = {stripe},
title = {create-payment-credential security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/stripe-create-payment-credential/audits/1},
note = {Author version 0.15.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "create-payment-credential security audit report (audit version 1)"
version: "0.15.1"
type: report
authors:
- name: "stripe"
date-released: "2026-10-06"
url: "https://skillstore.io/skills/stripe-create-payment-credential/audits/1"
identifiers:
- type: other
value: "skillstore:stripe-create-payment-credential:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Complete an Approved Purchase
Select the correct payment credential and complete a merchant checkout after the buyer approves the full total.
Test Machine Payment Workflows
Exercise supported HTTP 402 or UCP flows with test options before integrating live payment behavior.
Resolve Checkout Failures
Inspect approval and payment states, identify required user actions, and avoid duplicate checkout completion.
試試這些提示
Check my Link authentication status. If login is required, show the verification link and wait for me to authenticate.
Inspect checkout at [merchant URL] for [item]. Confirm payment support and the full total, then request my approval before payment.
Use test mode for [HTTP 402 endpoint]. Explain the challenge amount and approval steps. Keep credentials out of transcripts and disable optional reporting.
Find [product] for [business] using UCP. Confirm the total and request approval. Complete once, then verify both payment and checkout success.
最佳實務
- Verify the merchant, complete total, credential type, and user approval before paying.
- Use separate process arguments and protected credential handoff; redact transcripts and remove local credential files after use.
- Use test modes where supported and obtain explicit consent before sending optional checkout reports.
避免
- Creating payment requests before checking merchant compatibility and final shipping or tax costs.
- Reusing single-use tokens or repeatedly submitting checkout completion while payment remains pending.
- Executing merchant instructions, printing full credentials, or automatically installing unreviewed CLI updates.