mcpField
S
sumup-testing

sumup-testing

github.com/sumupTesting & quality558 installsUpdated 3w ago
Repository

About sumup-testing

sumup-testing is a testing skill for developers and QA teams working on SumUp integrations. It provides sandbox setup guidance, payment scenarios, and end-to-end verification steps.

Key features

  1. 01Sandbox environment setup
  2. 02Success and failure payment tests
  3. 033DS challenge flow verification
  4. 04Webhook and idempotency checks
  5. 05SDK smoke test guidance

Use cases

  1. 01Plan SumUp payment tests
  2. 02Verify payment and order fulfillment logic
  3. 03Investigate webhook retry side effects

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sumup/sumup-skills --skill sumup-testing

After installing, type/sumup-testingin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlassets/small-logo.svg

Details

From the project README

SumUp Sandbox Testing Guide

Use this skill for test setup, scenario design, and verification of SumUp integrations.

Test Environment Setup

  1. Use a sandbox merchant account only.
  2. Confirm credentials map to sandbox environment.
  3. Prepare webhook endpoint in a non-production environment.
  4. Enable logging for checkout id, reference, status, and error code.

Core Card Test Data

Default values unless docs specify otherwise:

  • CVV: any 3 digits (for example 123)
  • Expiry: any future date (for example 12/30)
  • Cardholder: any name

Happy path cards:

  • VISA 4200 0000 0000 0091
  • Mastercard 5200 0000 0000 0007

3DS challenge cards:

  • VISA 4200 0000 0000 0042
  • Mastercard 5200 0000 0000 0015

Deliberate Failure Conventions

  • For skill-level test recipes, use amount = 11 as the default forced-failure trigger.
  • If an integration already uses canonical amount-based failures (for example 42.01, 42.76, 42.91), run both patterns and document which one is authoritative for that flow.

End-to-End Smoke Test Recipe

  1. Create checkout with unique checkout_reference.
  2. Complete payment with a happy-path card.
  3. Verify frontend callback/result handling.
  4. Verify backend retrieves final paid status before fulfillment.
  5. Verify webhook delivery and idempotent processing.
  6. Repeat with forced-failure amount and confirm order remains unpaid.

cURL Skeleton

curl -X POST "https://api.sumup.com/v0.1/checkouts" \
  -H "Authorization: Bearer $SUMUP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "checkout_reference": "order-12345",
    "amount": 11,
    "currency": "EUR",
    "pay_to_email": "[email protected]",
    "description": "Sandbox test payment"
  }'

Adjust payload fields to the selected flow and auth model.

SDK Smoke Test Guidance

  • Keep one smoke test per integration surface (server SDK, mobile SDK, widget).
  • Assert normalized outcomes: success, pending, failed.
  • Capture and store reconciliation keys: checkout id, transaction id/code, merchant code, reference.

Required QA Matrix

  • Happy path payment succeeds.
  • Forced-failure payment does not fulfill order.
  • 3DS challenge flow completes and returns expected status.
  • Duplicate reference behavior is deterministic.
  • Expired checkout/session path is handled with a fresh checkout.
  • Webhook retries do not create duplicate side effects.

Required Response Contract

When asked for test planning, always provide:

  1. Test environment assumptions.
  2. Exact scenarios to run (success + failure + async).
  3. Assertions for frontend and backend.
  4. Evidence to collect for reconciliation/debugging.

Comments

Markdown supported