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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「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)
🌐 ネットワークアクセス (7)
📁 ファイルシステムへのアクセス (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.