All ResourcesBanking • ZIP: CSV pack + checklist + guide

Banking API Test-Case Pack

Payments idempotency, open banking consent, strong customer authentication, accounts, cards and ISO 20022 messaging

What's inside:

Payments: idempotency, limits, cut-off, status and ownership checks
Open banking consent and strong customer authentication cases
Accounts, cards (PAN masking) and ISO 20022 message validation
Self-hosted deployment and audit checklist included

For: QA and platform teams at banks and payment providers

Get your free copy

Enter your email and we'll send the download link to your inbox.

No spam. Unsubscribe anytime. We respect your privacy.

Preview: Banking API Test-Case Pack

This page shows roughly the first 20% of the pack so you can judge it before you download. The full ZIP contains 5 files: banking-api-test-cases.csv, banking-api-test-cases-guide.pdf, banking-api-test-cases-guide.md, deployment-audit-checklist.csv, self-hosted-api-testing-deployment-checklist.pdf.

About this pack

Banking APIs fail in ways generic test suites miss: a retried payment that debits twice, a consent that keeps working after it was revoked, an amount that changes after the customer approved it. These cases target those failure modes.

banking-api-test-cases.csv has 34 cases. Each names the domain area, the request, the expected result, a type, a priority and the public standard or document it was written against. Replace placeholders in {braces} with your own paths, identifiers and data.

Areas covered

Domain areaCases
Payments17
Open banking consent7
Strong customer authentication3
Accounts2
Cards2
ISO 20022 messaging2
Notifications1

Banking API test cases

banking-api-test-cases.csv · showing 7 of 34 rows. Payments, open banking consent, SCA, accounts, cards and ISO 20022.

  1. BNK-001

    Domestic credit transfer is accepted

    Domain Area
    Payments
    Preconditions
    Funded debtor account; valid creditor account
    Input / Request
    POST /payments {debtorAccount, creditorAccount, amount:{value:"125.50",currency:"EUR"}} with Idempotency-Key K1
    Expected Result
    201; payment id; status in an initial state (e.g. received/pending); amount and currency echoed exactly
    Type
    Positive
    Priority
    P1
    Reference
    Your payments API spec

  2. BNK-002

    Same Idempotency-Key and body returns the original payment

    Domain Area
    Payments
    Preconditions
    Payment created with K1
    Input / Request
    Repeat the identical POST /payments with K1
    Expected Result
    Same payment id and status; no second debit; ledger shows one entry
    Type
    Positive
    Priority
    P1
    Reference
    IETF Idempotency-Key HTTP header draft

  3. BNK-003

    Same Idempotency-Key with a different body is refused

    Domain Area
    Payments
    Preconditions
    Payment created with K1
    Input / Request
    POST /payments with K1 and amount 999.00
    Expected Result
    409 or 422; original payment unchanged; no new payment
    Type
    Negative
    Priority
    P1
    Reference
    IETF Idempotency-Key HTTP header draft

  4. BNK-004

    Concurrent duplicate submissions create one payment

    Domain Area
    Payments
    Preconditions
    Funded account
    Input / Request
    Send 5 identical POST /payments with the same Idempotency-Key concurrently
    Expected Result
    Exactly one payment created; other responses return it or 409
    Type
    Security
    Priority
    P1
    Reference
    OWASP API6:2023

  5. BNK-005

    Currency code is validated

    Domain Area
    Payments
    Preconditions
    -
    Input / Request
    amount.currency "EURO" and "XXX"
    Expected Result
    400 or 422; only active ISO 4217 codes accepted
    Type
    Negative
    Priority
    P2
    Reference
    ISO 4217

  6. BNK-006

    Amount precision follows the currency's minor units

    Domain Area
    Payments
    Preconditions
    -
    Input / Request
    EUR amount "10.123"; JPY amount "100.5"
    Expected Result
    400 or 422 for both (EUR has 2 decimals, JPY has 0)
    Type
    Boundary
    Priority
    P1
    Reference
    ISO 4217 minor units

  7. BNK-007

    Zero and negative amounts are refused

    Domain Area
    Payments
    Preconditions
    -
    Input / Request
    amount "0.00" and "-10.00"
    Expected Result
    400 or 422
    Type
    Negative
    Priority
    P1
    Reference
    Your payments API spec

The rest of the pack

74 rows across 2 CSV files, and all 6 sections of the guide as PDF and Markdown. Enter your work email above and we will send the download link.

Related reading

Want to automate your API testing?

Generate tests from OpenAPI specs, run in CI/CD, and scale quality across teams.

Start TrialBook Demo