sumup/sumup-skills

sumup-best-practices

Choose a SumUp integration and credential model, or review its payment security.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sumup/sumup-skills --skill sumup-best-practices

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Choose a SumUp Integration

Start with the user's constraints and existing stack. Recommend the simplest supported path that meets them; preserve an explicit integration choice unless evidence shows it cannot satisfy the requirement. Use the current documentation index to verify availability and product-specific requirements.

Choose by requirement

RequirementDefault choice and deciding constraint
Online checkout with redirect UXHosted Checkout; the backend creates the checkout and redirects to its hosted URL.
Embedded website payment collectionCard Widget; SumUp provides the payment interface and authentication flow.
Website wallet buttonsSwift Checkout JavaScript SDK; verify browser/wallet and merchant-domain requirements.
React Native payment sheetReact Native Checkout; check the current alpha API and use a public merchant key in the app.
Save cards and charge laterCustomers plus tokenization; the stored token belongs to its customer and each later charge is a separate attempt.
Native mobile app controls a readeriOS Terminal or Android Reader SDK; check supported devices and platform permissions.
Contactless payment on the phoneTap to Pay on iPhone or the separate Android Tap-to-Pay SDK; verify device eligibility and access requirements.
POS or backend controls SoloCloud API; design around asynchronous transaction results.
Existing app must hand off to the SumUp appPayment Switch; retain it when that handoff is a requirement.

A custom backend may still use hosted, widget, or SDK payment collection. Do not introduce direct card-data handling just because the application needs custom order logic.

Choose credentials and verify payment state

  • Use a secret API key on the server for its owning merchant. Use OAuth when other merchants authorize the application. Check endpoint permissions and any required OAuth scope verification in the authorization guide.
  • Public sup_pk_ merchant keys belong in supported checkout clients; secret sup_sk_ keys and OAuth client secrets do not. Sandbox behavior follows the authenticated merchant, not an assumed key-prefix tier.
  • Terminal integrations need the Affiliate Key and matching app identifiers required by that SDK or API.
  • Match the checkout/transaction to the expected merchant, order reference, amount, and currency. Retrieve final payment state before fulfillment; callback delivery and HTTP success are not enough.
  • Resolve an uncertain payment or refund before repeating it. A unique reference helps reconciliation but is not a guarantee of server-enforced idempotency.
  • Make repeated notifications and status reads safe for order updates. Follow the selected callback protocol rather than assuming every SumUp webhook is signed.

For a selection question, explain the deciding constraint and credential requirements. For a security review, lead with concrete findings and evidence, and describe validation for the affected behavior. Add alternatives or a launch checklist only when they help the requested decision.

For implementation, use the sumup skill if installed, or continue with the selected flow's current documentation. General account reporting and MCP setup do not require an integration-selection exercise.

同じリポジトリから

関連する Skills

すべての Skills