Skip to content
Skills Library
Finance & accounting · Testing

sumup-testing

/sumup-testing

Set up and run SumUp sandbox tests. Use when configuring a SumUp test merchant, picking test cards, triggering deliberate failure (`amount = 11`), or building a SumUp end-to-end test harness.

Author
sumup ↗
Licence
Apache-2.0
Last repository change
07.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 07.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Set up and run SumUp sandbox tests. Use when configuring a SumUp test merchant, picking test cards, triggering deliberate failure (`amount = 11`), or building a SumUp end-to-end test harness.

Original author description

Set up and run SumUp sandbox tests. Use when configuring a SumUp test merchant, picking test cards, triggering deliberate failure (`amount = 11`), or building a SumUp end-to-end test harness.

How it works

  1. Test Environment Setup
  2. Core Card Test Data
  3. Deliberate Failure Conventions
  4. End-to-End Smoke Test Recipe
  5. cURL Skeleton
  6. SDK Smoke Test Guidance
  7. Required QA Matrix
  8. Required Response Contract
Original SKILL.md headings · 85 lines, 390 words
SKILL.md preview
---
name: sumup-testing
description: Set up and run SumUp sandbox tests. Use when configuring a SumUp test merchant, picking test cards, triggering deliberate failure (`amount = 11`), or building a SumUp end-to-end test harness.
license: Apache-2.0
---

# 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

```bash
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": "merchant@example.com",
    "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.
Files in this package (4)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB
  • assets/large-logo.png 4 KB
  • assets/small-logo.svg 1 KB

Versions

The database has no other skills named sumup-testing.

Database snapshot: 13.11.2026 · package version b2c53ed3815a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100sumup-mcp
    Use the SumUp MCP server (https://mcp.sumup.com/mcp) from Cursor, Claude Code, Codex, or any MCP-capable client. Use when the user mentions SumUp MCP, needs to wire mcp.sumup.com, or wants tool-based access to SumUp APIs.
  • 90upgrade-sumup
    Guide for upgrading SumUp API versions and server/mobile SDKs (@sumup/sdk, sumup-go, sumup Python, PHP, Java, Rust, .NET, iOS Terminal, Android Reader, Swift Checkout, React Native). Use when bumping SumUp SDK versions or migrating off deprecated endpoints.
  • 95sumup
    Guide for building SumUp payment integrations that cover both terminal (card-present) and online (card-not-present) checkout flows using SumUp SDKs and APIs. Use when implementing or debugging SumUp checkout creation, payment processing, reader pairing, Card Widget integrations,…
  • 90payment-testing
    How to test a Sri Lankan payment gateway integration before going live - sandbox hosts, test cards, what is and is not simulable, a scenario checklist (success, failure, cancel, duplicate callback, tampered amount, bad signature, lost callback), and tunnelling callbacks to…
  • 100payment-gateway-sandboxes
    Wraps the vendor-generic payment-gateway sandbox pattern - test credentials, sandbox base URLs / environment switches, deterministic test-card matrices, and gateway-native webhook simulators - with per-gateway references for Adyen test mode, PayPal Sandbox, and Braintree…
  • 100v1-e2e-testing
    Use when implementing or debugging browser end-to-end tests, especially Playwright or flaky tests. Triggers on "E2E test", "Playwright", or "flaky browser test".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.