Pick a topic from the panel to see the details.
Why a payments test playbook?
- Every level has written exit criteria
- Negative and edge cases are first-class
- Results tracked and reported each release
- Testing squeezed at the end of the project
- Only happy paths tested
- Sign-offs given without evidence
Purpose and scope
Rails covered: ACH (Nacha), wire (Fedwire, CHIPS, SWIFT MT/MX), cards (auth, capture, refund, chargeback), real-time (RTP, FedNow) and recurring/subscription payments.
Systems in scope: channels (web, mobile, API), payment hub/orchestration, fraud and sanctions screening, ledger/core banking, network gateways, notifications, reconciliation and reporting.
Out of scope unless agreed: third-party network certification (run by the network), and infrastructure DR drills owned by platform teams.
Test strategy
Test in five levels, each gating the next. Nothing reaches production without a passing end-to-end run on the network simulator and a signed-off parallel run.
| Level | Goal | Environment | Owner |
|---|---|---|---|
| Unit and component | Validation rules, fee and FX math, message mapping | Dev | Engineering |
| API and contract | Request/response schema, error codes, idempotency keys | Dev/QA with mocks | QE |
| System integration (SIT) | Hub to fraud, sanctions, ledger, gateway | QA with network simulators | QE |
| End-to-end and UAT | Full customer journeys, ops screens, reports | UAT with production-like data | Business + QE |
| Parallel run / pilot | New vs old system give the same result | Pre-prod or limited production | Ops + Product |
Test data rules
- Use synthetic or masked data only; never real PANs or account numbers outside PCI scope.
- Keep a fixed set of test accounts: funded, zero balance, closed, frozen, dormant, joint, business.
- Include sanctions test names (exact, fuzzy, alias) and high-risk countries.
- Cover cut-off times, weekends, US bank holidays and month/quarter end.
Entry criteria: requirements signed off, environment stable, test data loaded, simulators connected.
Exit criteria: 100% of critical cases passed, zero open Sev 1/Sev 2 defects, reconciliation balanced to the cent, compliance sign-off received.
Unit & Component
- Runs in CI on every pull request
- Rounding and boundary values covered
- Low coverage on money calculations
- Tests skipped to hit a deadline
API & Contract
- Duplicate requests create exactly one payment
- All error codes documented
- Breaking schema change without versioning
- Generic errors with no reason code
System Integration
- Every return and reject code tested
- Simulators match the network specification
- Mocks only, no simulators
- Sanctions screening stubbed out
End-to-End & UAT
- Business signs off on real scenarios
- Ops team trained on new screens
- UAT done by developers only
- No production-like data
Parallel Run / Pilot
- Zero unexplained differences over the agreed period
- Peak day included
- Differences waved away
- Run cut short to meet a date
Go-live Gate
- All checklist items signed
- Rollback and kill switch rehearsed
- Open Sev 1 / Sev 2 accepted “to fix later”
- Missing compliance or AML sign-off
Cloud testing
- Failover tested and measured against recovery targets
- Load test at peak volume passed
- Security scan clean before go-live
- DR plan exists only on paper
- Test environment differs from production
- Over-broad IAM roles or public storage buckets
AI Agent testing
- AI cannot release or approve a payment without a human
- Golden test set with clear pass thresholds
- Every AI decision logged and explainable
- AI-generated tests run without review
- No limits on what an agent can do in production
- Model changes deployed without re-testing
Notification testing
- Each status sent exactly once, in order
- Webhook retries and signature checks pass
- No PII or full account numbers in messages
- Notifications tested only on the happy path
- Duplicate events after retries
- Messages with no reason for a failure
Ready-made test scenarios
Each rail lists the cases that catch most production defects. Run the positive case first, then the negatives.
ACH (Nacha)
| ID | Scenario | Expected result |
|---|---|---|
| ACH-01 | Same-day credit submitted before cut-off | File built, settles same day, ledger posted |
| ACH-02 | Credit submitted after cut-off | Rolls to next business day |
| ACH-03 | Debit with insufficient funds | R01 return processed, customer notified |
| ACH-04 | Account closed / invalid account | R02 / R03 / R04 returns mapped correctly |
| ACH-05 | Unauthorized debit dispute | R10 handled within Nacha time limit |
| ACH-06 | NOC (notification of change) received | Account details updated, no duplicate post |
| ACH-07 | Prenote | Zero-dollar entry sent, live entries held as configured |
| ACH-08 | File format | Batch headers, control totals and hash valid |
Wire (Fedwire, CHIPS, SWIFT)
| ID | Scenario | Expected result |
|---|---|---|
| WIR-01 | Domestic Fedwire, valid ABA | ISO 20022 pacs.008 built, IMAD/OMAD captured |
| WIR-02 | International SWIFT MX with intermediary bank | Correct routing chain, charges (OUR/SHA/BEN) applied |
| WIR-03 | FX wire | Rate locked, quote expiry enforced, amounts match |
| WIR-04 | Sanctions hit on beneficiary | Payment held for review, not released |
| WIR-05 | Wire after Fedwire cut-off | Queued for next business day |
| WIR-06 | Recall / return (camt.056, pacs.004) | Status updated, funds returned to account |
| WIR-07 | Dual approval above limit | Single user cannot release |
| WIR-08 | Tracking (gpi / UETR) | End-to-end status visible to customer |
Cards
| ID | Scenario | Expected result |
|---|---|---|
| CRD-01 | Authorization approved | Hold placed, available balance reduced |
| CRD-02 | Decline codes (insufficient funds, expired, CVV fail) | Correct response code and customer message |
| CRD-03 | Partial and multiple captures | Captured total never exceeds auth |
| CRD-04 | Full and partial refund | Credit posted, original transaction linked |
| CRD-05 | Reversal / void before settlement | Hold released |
| CRD-06 | Chargeback and representment | Case created, deadlines tracked |
| CRD-07 | 3-D Secure challenge | Liability shift flagged |
| CRD-08 | Tokenized wallet payment (Apple Pay, Google Pay) | Token mapped to correct card |
Real-time (RTP, FedNow)
| ID | Scenario | Expected result |
|---|---|---|
| RTP-01 | Credit transfer 24/7, including weekend | Accepted or rejected within network timeout |
| RTP-02 | Amount above network or bank limit | Rejected with correct reason code |
| RTP-03 | Receiver timeout | No duplicate debit, status resolved |
| RTP-04 | Request for Payment | Payer can accept or decline |
| RTP-05 | Irrevocability | No reversal path; only a return request |
Recurring and subscription
| ID | Scenario | Expected result |
|---|---|---|
| REC-01 | Schedule on 29th, 30th or 31st | Runs on correct date in short months |
| REC-02 | Schedule falls on weekend or holiday | Moves per business rule |
| REC-03 | Failed payment retry | Retries per policy, then stops and notifies |
| REC-04 | Customer cancels or pauses | No further charges |
| REC-05 | Card expired / updated | Account updater applied, schedule continues |
| REC-06 | Amount change mid-cycle | Proration or next-cycle rule applied |
Holidays and cut-offs
Calendar and timing cases. Cut-offs are evaluated in Eastern Time unless the product says otherwise.
| ID | Scenario | Expected result |
|---|---|---|
| CAL-01 | ACH or wire dated on a US Federal Reserve holiday | Not sent that day; value date moves to next business day; customer shown the new date before confirming |
| CAL-02 | Payment initiated on a weekend | Queued and released when the next business-day window opens |
| CAL-03 | Recurring payment falls on a holiday | Moves to prior or next business day per product rule, the same way every time |
| CAL-04 | Submitted one minute after Same Day ACH cut-off | Goes to next window or next day; customer told before final confirmation |
| CAL-05 | Wire submitted after Fedwire customer cut-off | Queued for next business day, or released only with an approved ops exception |
| CAL-06 | Customer in another time zone submits near cut-off | Cut-off checked in Eastern Time; result consistent across channels |
| CAL-07 | RTP / FedNow payment on a holiday | Settles immediately (24/7/365); ledger posting and statement dates follow the bank’s rule |
| CAL-08 | Daylight saving time change day | Scheduled jobs and payments run once, not skipped or doubled |
| CAL-09 | New holiday added to the calendar | Future-dated payments re-dated and affected customers notified |
| CAL-10 | Month-end and quarter-end peak | Cut-offs honored and processing SLA met at peak volume |
System failures (FX and dependencies)
What must happen when a service the payment depends on fails. The rule: never lose, duplicate or release an unchecked payment.
| ID | Scenario | Expected result |
|---|---|---|
| FXF-01 | FX rate service down when customer starts a cross-border payment | No stale rate used; customer sees “rate unavailable, try again”; no debit taken |
| FXF-02 | FX quote expires before customer confirms | Customer must accept a new quote |
| FXF-03 | FX booking fails after account debit, before sending | Payment held in suspense and retried; if still failing, debit reversed and customer notified; never debited twice |
| FXF-04 | Rate moves beyond tolerance between quote and booking | Re-quote or reject per policy; customer never charged an unagreed rate |
| FXF-05 | Currency not supported or restricted | Rejected at validation with a clear reason |
| FXF-06 | Sanctions screening service times out | Payment held (fail closed), not released unscreened |
| FXF-07 | Core ledger unavailable | Payments queued; no partial postings; processed in order when ledger returns |
| FXF-08 | Network gateway times out after sending | Status set to “pending confirmation” and resolved by inquiry; payment not resent blindly |
| FXF-09 | Fraud scoring service down | Fallback rules applied (for example lower limits or manual review); event logged |
Internal transfers and notifications
On-us (book) transfers inside the bank and the notifications around them.
| ID | Scenario | Expected result |
|---|---|---|
| INT-01 | Transfer between the customer’s own accounts | Debit and credit posted together instantly; both balances updated; no network fee |
| INT-02 | Transfer to another customer at the same bank | Payee validated; posted on-us; payer and payee each notified |
| INT-03 | Internal transfer with insufficient funds | Rejected before posting with a clear message |
| INT-04 | Success notification content | Sent once per party; correct amount and date; account number masked |
| INT-05 | Failed transfer notification | Reason given; no “success” message ever sent |
| INT-06 | Notification service down during transfer | Transfer still completes; messages queued and sent once when service returns |
| INT-07 | Customer opted out of SMS | Only the channels the customer allows are used |
| INT-08 | Webhook to a corporate client | Signed event; retried on errors; client receives it exactly once (idempotent) |
| INT-09 | Ops alert for stuck transfer | Alert raised after SLA breach and routed to the on-call team |
High-value payments
Controls that protect large payments.
| ID | Scenario | Expected result |
|---|---|---|
| HVP-01 | Amount above the user’s single-payment limit | Needs a second approver (maker-checker) |
| HVP-02 | Amount above the company daily limit | Blocked or sent for limit-increase approval |
| HVP-03 | User tries to approve their own payment | Blocked |
| HVP-04 | High value triggers call-back verification | Held until verification is recorded |
| HVP-05 | Approval not completed before cut-off | Rolls to next day or expires per rule; initiator notified |
| HVP-06 | High value to a newly added beneficiary | Extra fraud check or cooling-off period applied |
| HVP-07 | Wire of $3,000 or more | Travel Rule originator and beneficiary details captured and sent |
| HVP-08 | Large FX amount | Priced by treasury / dealer desk, not the standard retail rate |
ACH to wire upgrade
Moving a payment from one rail to another without duplicating it.
| ID | Scenario | Expected result |
|---|---|---|
| RTE-01 | Same-day payment above the Same Day ACH per-payment limit | Customer offered a wire instead; wire fee shown before confirming |
| RTE-02 | Customer upgrades an ACH payment to wire before the ACH file is sent | ACH entry cancelled; exactly one wire sent; customer charged once |
| RTE-03 | Upgrade requested after the ACH file was already sent | Upgrade blocked; customer told to wait for the ACH result or request a reversal |
| RTE-04 | Wire fee higher than ACH fee | Customer sees and accepts the new fee before conversion |
| RTE-05 | Beneficiary bank’s wire ABA differs from its ACH routing number | Wire routing number validated separately |
| RTE-06 | Wire fails; fallback to ACH | Only with customer consent; new value date shown |
| RTE-07 | Receiving bank not enabled for RTP or FedNow | Routed to an available rail per rules; customer told of the timing change |
Account types and status
Payments from and to different account types and states.
| ID | Scenario | Expected result |
|---|---|---|
| ACC-01 | Business vs consumer account | Correct ACH SEC code (CCD vs PPD), limits and fees applied |
| ACC-02 | Savings account debit | Bank’s savings transfer-limit policy applied |
| ACC-03 | Joint account | Initiation follows the account mandate; owners notified per their preferences |
| ACC-04 | Inactive / dormant account | Outgoing payment blocked; customer asked to reactivate |
| ACC-05 | Closed account | Rejected; ACH return R02 when received |
| ACC-06 | Frozen account (legal hold or garnishment) | Debits blocked; ops alerted |
| ACC-07 | Account holder deceased | Outgoing blocked; ACH returns R14 / R15 handled |
| ACC-08 | Insufficient funds | Rejected, or overdraft used only if enabled; NSF fee per policy |
| ACC-09 | Funds on hold (uncollected deposit) | Only the available balance can be used |
| ACC-10 | High-risk account (enhanced due diligence) | Payments above threshold held for compliance review |
| ACC-11 | Custodial or minor’s account | Custodian approval rules enforced |
| ACC-12 | Foreign currency account | Debited in account currency; FX applied only when currencies differ |
Risk and compliance
Sanctions, AML and fraud cases. Customer messages stay neutral so no one is tipped off.
| ID | Scenario | Expected result |
|---|---|---|
| RSK-01 | Beneficiary in a comprehensively sanctioned country | Payment blocked or held; compliance alerted; neutral customer message |
| RSK-02 | Beneficiary in a high-risk (non-sanctioned) country | Extra review; purpose of payment required |
| RSK-03 | Fuzzy name match on the OFAC SDN list | Held; analyst clears or escalates with full audit trail |
| RSK-04 | Several payments just under a reporting threshold (structuring) | AML alert raised |
| RSK-05 | Sudden volume or amount spike vs customer profile | Alert or step-up authentication |
| RSK-06 | Money in then quickly out (mule pattern) | AML alert; outgoing held per rule |
| RSK-07 | New device + new payee + large amount | Step-up authentication or block |
| RSK-08 | Politically exposed person (PEP) as beneficiary | Enhanced due diligence review |
| RSK-09 | Cross-border payment missing purpose code or remittance info | Rejected or more information requested |
| RSK-10 | Account under compliance hold | No payments released until hold is cleared |
Special characters and data quality
Each rail allows a different character set: SWIFT MT uses the restricted FIN “X” set, ISO 20022 allows more but needs XML escaping, and Nacha files are fixed-width ASCII. Test every free-text field: names, addresses, references and remittance info.
| ID | Scenario | Expected result |
|---|---|---|
| CHR-01 | Accented letters in beneficiary name (José Muñoz, Müller) | Transliterated per scheme rule (for example Jose Munoz, Mueller) or accepted where allowed; screening runs on both forms |
| CHR-02 | Non-Latin script name (Chinese, Arabic, Cyrillic) | Rejected at entry with a clear message, or transliterated per policy; never sent garbled |
| CHR-03 | Ampersand in name (Smith & Sons LLC) | Escaped as & in ISO 20022 XML; replaced (for example “and”) for SWIFT MT |
| CHR-04 | Apostrophe or hyphen (O’Brien, Smith-Jones) | Accepted and preserved |
| CHR-05 | Characters outside the SWIFT X set (such as @ # ! _ and semicolon) in an MT field | Replaced or rejected before sending; no NAK from the network |
| CHR-06 | Reference starting or ending with “/” or containing “//” | Rejected or corrected at validation (not allowed in SWIFT reference fields) |
| CHR-07 | XML-special characters (< > “) in remittance info | Escaped correctly; message stays valid against the XSD schema |
| CHR-08 | Emoji or control characters pasted into a memo field | Stripped or rejected; no file or message corruption |
| CHR-09 | Name longer than the field limit (35 per MT line, 140 for ISO 20022 name) | Clear error at entry, or truncated only by an agreed rule; screening uses the full name |
| CHR-10 | Lowercase or mixed case in Nacha file fields | Converted to the case the bank’s Nacha spec requires; file passes validation |
| CHR-11 | Leading / trailing spaces and double spaces | Trimmed; no false sanctions mismatch |
| CHR-12 | Injection-style input (‘ OR 1=1, <script>) | Treated as plain text; no error leak; security event logged |
Address validation (ISO 20022)
Since SWIFT Standards Release 2026 (14 November 2026), CBPR+ cross-border messages accept only fully structured or hybrid postal addresses, with Town Name and Country mandatory. Fully unstructured addresses are rejected by the network.
| ID | Scenario | Expected result |
|---|---|---|
| ADR-01 | Fully structured address (street, building, postal code, town, country) | Accepted; each part in its own XML tag; no AdrLine |
| ADR-02 | Hybrid address (TwnNm + Ctry structured, rest in AdrLine) | Accepted; AdrLine within the allowed limit (max 2 lines of 70 characters) |
| ADR-03 | Fully unstructured address (AdrLine only) | Blocked before sending; customer or ops asked to complete town and country; no network rejection |
| ADR-04 | Town name missing | Validation error at entry; payment not created |
| ADR-05 | Invalid country code (USA, UK, XX) | Rejected; only ISO 3166 two-letter codes (US, GB) accepted |
| ADR-06 | Placeholder text (“NOTPROVIDED”, “N/A”, “UNKNOWN”) | Rejected; real values required |
| ADR-07 | Postal code format wrong for the country (US ZIP not 5 or 9 digits) | Warning or rejection per policy |
| ADR-08 | Postal code and country do not match | Flagged for correction |
| ADR-09 | Hybrid address where structured town differs from town in AdrLine | Structured data takes precedence; mismatch flagged for data-quality review |
| ADR-10 | Legacy beneficiary record with free-text address | Address service structures it (town + country) and asks the user to confirm before first use |
| ADR-11 | Address in a sanctioned region inside a non-sanctioned country | Screening checks town and subdivision, not just country; payment held |
| ADR-12 | SWIFT MT option 50F / 59F structured party | Line 3 carries country code and town in the correct format; maps cleanly to ISO 20022 |
| ADR-13 | PO Box only address | Accepted or rejected per policy; town and country still required |
SWIFT MT and ISO 20022 messages
Test each message type end to end and its MT-to-ISO 20022 mapping where both still exist in your flow (for example corporate MT101 in, ISO 20022 out). Fedwire and SWIFT cross-border now run on ISO 20022.
| ID | Scenario | Expected result |
|---|---|---|
| MSG-01 | MT101 request for transfer from a corporate (single and multiple transactions) | Each transaction validated and executed; maps to pain.001 / pacs.008; status returned to the corporate |
| MSG-02 | MT101 with one invalid transaction in a batch | Only that transaction rejected (or whole batch, per agreement); clear status per transaction |
| MSG-03 | MT102 multiple customer credit transfer | Each transaction split into its own single-transaction pacs.008, as CBPR+ requires; totals reconcile |
| MSG-04 | MT103 single customer credit transfer | Maps to pacs.008; fields 50 / 59 / 70 / 71A carried correctly; no data truncated |
| MSG-05 | Charges option OUR / SHA / BEN (71A, ChrgBr) | Correct fees deducted or billed; amounts on both sides match |
| MSG-06 | MT202 / MT202 COV bank-to-bank cover payment | Maps to pacs.009 / pacs.009 COV; underlying customer details travel with the cover for screening |
| MSG-07 | pacs.002 status report (accepted, rejected, pending) | Status shown to customer and ops; reason codes mapped to clear messages |
| MSG-08 | Return (pacs.004) | Funds returned to the original account; return reason shown; fees per policy |
| MSG-09 | Recall request (camt.056) and answer (camt.029) | Recall tracked to resolution; funds credited back only on positive answer |
| MSG-10 | Debit / credit confirmations (MT900 / MT910, camt.054) | Booked once; matched to the original payment |
| MSG-11 | Statements (MT940 / MT950, camt.053) | Every payment appears; balances reconcile to the ledger |
| MSG-12 | Free-format messages (MT199 / MT299) | Routed to ops queue; never auto-processed as payments |
| MSG-13 | UETR on every payment | Same UETR kept end to end, including returns and recalls; gpi tracking works |
| MSG-14 | Duplicate message received (same reference and UETR) | Detected and not booked twice |
| MSG-15 | Schema-invalid ISO 20022 message | Rejected before sending with the failing element named |
Payment files and mapping
Files and data flowing in from upstream systems (ERP, corporate clients, channels) and out to downstream systems (networks, ledger, reconciliation, reporting). Every field must map correctly and every file must be accounted for.
| ID | Scenario | Expected result |
|---|---|---|
| FIL-01 | Upstream bulk file intake (pain.001, CSV, Nacha, MT101) | File accepted, parsed and each payment created once; acknowledgement returned |
| FIL-02 | Duplicate file received (same name, hash or control totals) | Detected and rejected or held; no payment created twice |
| FIL-03 | Header / trailer and control totals mismatch | Whole file rejected per rule; clear error returned to sender |
| FIL-04 | One bad record in a valid file | Bad record rejected (or whole file, per client agreement); others processed; status per record |
| FIL-05 | Empty, truncated or corrupted file | Rejected safely; no partial processing; ops alerted |
| FIL-06 | File encoding and line endings (UTF-8 with BOM, CRLF vs LF) | Parsed correctly; special characters preserved or transliterated per rule |
| FIL-07 | File arrives after cut-off | Processed for next business day or held per rule; sender notified |
| FIL-08 | Encryption, signature and secure transfer (PGP, SFTP) | Invalid signature or key rejected; file not processed |
| FIL-09 | Large file (peak volume) | Processed within SLA; no timeouts or memory errors |
| FIL-10 | Field-by-field mapping upstream to internal to downstream | Every field lands in the right target field; mapping sheet signed off |
| FIL-11 | Code-list mapping (purpose codes, SEC codes, charge bearer, return codes) | Each source code maps to the correct target code; unknown codes go to an error queue |
| FIL-12 | Mandatory target field missing in source | Defaulted only by the documented rule, otherwise rejected; never sent blank |
| FIL-13 | References preserved end to end (EndToEndId, UETR, client reference) | Same references appear in network message, status reports, statements and ERP |
| FIL-14 | Status and reports returned upstream (pain.002, camt.054, ACK / NACK files) | Client receives status for every payment in the agreed format and time |
| FIL-15 | Downstream ledger and GL posting mapping | Correct GL accounts, debit / credit sides, fees and FX booked; ledger balances |
| FIL-16 | Downstream reconciliation and reporting files (camt.053, BAI2, data warehouse, regulatory) | All payments present; totals match the ledger and network settlement |
| FIL-17 | Mapping version change (new field or format release) | Regression suite passes; old and new versions handled during transition |
Currency logic
ISO 4217 currency codes, minor units, rounding and FX direction. US domestic rails (ACH, RTP, FedNow, Fedwire) settle in USD only.
| ID | Scenario | Expected result |
|---|---|---|
| CUR-01 | Currency with 0 decimals (JPY) and 3 decimals (KWD, BHD) | Amounts stored and sent with the correct minor units; no extra or missing decimals |
| CUR-02 | Amount with more decimals than the currency allows (USD 10.005) | Rejected at entry, or rounded only by the documented rule |
| CUR-03 | Rounding rule on FX conversion (half-up vs half-even) | Result matches the bank’s documented rounding rule at every step |
| CUR-04 | Buy vs sell rate and inverse rate | Correct side of the quote used; inverse rate gives the same result within tolerance |
| CUR-05 | Cross-currency via USD (triangulation, e.g. GBP to JPY) | Both legs use the agreed rates; final amount matches the quoted amount |
| CUR-06 | FX rate precision (6 or more decimals) | Rate not truncated in storage, messages or statements |
| CUR-07 | Payment currency differs from account currency | FX applied once; customer sees both amounts and the rate before confirming |
| CUR-08 | Non-USD amount on a USD-only rail (ACH, RTP, FedNow, Fedwire) | Rejected or routed to a cross-border rail |
| CUR-09 | Invalid or lowercase currency code (usd, US$, XXX) | Rejected; only valid upper-case ISO 4217 codes accepted |
| CUR-10 | Amount display by locale (1,234.56 vs 1.234,56) | Display follows locale; stored and sent values are unchanged |
| CUR-11 | Zero, negative or blank amount | Rejected at entry with a clear message |
| CUR-12 | Amount above the rail’s maximum field length | Rejected before sending; no truncation |
Calculation logic
Fees, totals, balances and limits must be correct to the cent, every time.
| ID | Scenario | Expected result |
|---|---|---|
| CLC-01 | Flat fee, percentage fee and tiered fee | Fee matches the fee schedule for each tier boundary |
| CLC-02 | Percentage fee with minimum and maximum cap | Fee never below the minimum or above the cap |
| CLC-03 | Fee rounding to the cent | Rounded once, by the documented rule; no sub-cent residue in the ledger |
| CLC-04 | Fee waiver (premium client, promo, internal transfer) | Fee set to zero only when the waiver rule applies |
| CLC-05 | FX margin / markup | Customer rate = market rate adjusted by the configured margin; margin booked to revenue |
| CLC-06 | Total debit = amount + fees (+ FX cost) | Customer shown and debited the same total |
| CLC-07 | Amount received under charge options OUR / SHA / BEN | Beneficiary amount = sent amount minus the right deductions |
| CLC-08 | Available balance = ledger balance – holds + overdraft line | Payment allowed only up to the available balance |
| CLC-09 | Daily limit summed across channels (web, mobile, API) | Cumulative total enforced; resets at the documented time |
| CLC-10 | Fees reversed when a payment fails or is returned | Fee refunded per policy; no fee charged twice |
| CLC-11 | Partial refunds and split payments | Sum of parts never exceeds the original; totals reconcile |
| CLC-12 | Nacha batch and file control totals | Entry count, total debits/credits and entry hash match the entries |
| CLC-13 | Large amounts and decimal precision | No floating-point error (for example 0.1 + 0.2); exact decimal arithmetic |
| CLC-14 | Interest or proration on recurring and scheduled payments | Calculated amount matches the formula and day-count rule |
Payment status
Every payment follows a defined lifecycle: Draft, Pending approval, Approved, Scheduled, Sent, Accepted, Settled / Completed, with exits to Rejected, Returned, Cancelled, Failed and On hold.
| ID | Scenario | Expected result |
|---|---|---|
| STS-01 | Happy-path lifecycle (Draft to Settled) | Each status reached in order with a timestamp and user / system actor |
| STS-02 | Invalid transition (Settled to Cancelled, Rejected to Sent) | Blocked by the system; error logged |
| STS-03 | Cancel before release | Status Cancelled; no message sent; no debit or debit reversed |
| STS-04 | Cancel after release | Cancel refused; customer offered recall where the rail allows |
| STS-05 | Network status codes mapped (pacs.002 ACCP / ACSC / RJCT / PDNG) | Each code maps to the right internal and customer status |
| STS-06 | Completed payment later returned (ACH R-code, pacs.004) | Status moves to Returned; funds and fees handled; customer notified |
| STS-07 | Compliance hold and release | Status On hold, then resumes to Sent or ends Rejected; history kept |
| STS-08 | Same status event received twice | Processed once; no duplicate notification or posting |
| STS-09 | Events arrive out of order (Settled before Accepted) | Final status is correct; older event does not overwrite a newer one |
| STS-10 | Payment stuck in one status past SLA | Alert raised to ops; customer sees an accurate pending message |
| STS-11 | Status consistent everywhere | UI, API, webhook, notification and statement show the same status |
| STS-12 | Approval expires before action | Status Expired / Cancelled per rule; initiator notified |
| STS-13 | Future-dated payment | Shows Scheduled until the value date, then follows the normal lifecycle |
| STS-14 | Customer-facing status labels | Plain-language labels with a reason for Rejected, Returned and On hold (neutral wording for compliance holds) |
Cross-cutting tests
Run these on every rail. Most costly payment incidents come from these areas, not from the happy path.
| Area | What to test | Pass condition |
|---|---|---|
| Sanctions screening (OFAC) | Exact, fuzzy and alias name matches; country and BIC hits | True hits held; false-positive rate within agreed target |
| AML monitoring | Structuring, velocity, rapid in-and-out, high-risk geography | Alerts generated with correct rule and risk score |
| Fraud | Account takeover, new payee plus large amount, device change | Step-up or block triggered |
| Idempotency and duplicates | Same request sent twice, retry after timeout | Exactly one payment, one ledger entry |
| Reconciliation | Hub vs ledger vs network settlement file | Balanced to the cent; breaks reported |
| Limits and entitlements | Per-transaction, daily and user-role limits | Over-limit rejected; maker-checker enforced |
| Security | Auth tokens, PII masking, PCI scope, API rate limits | No data leak; OWASP top 10 clean |
| Performance | Peak volume (for example payroll day, month end) | Throughput and latency meet SLA |
| Resilience | Gateway down, ledger slow, network reject storm | Payments queue safely and resume; no loss or duplicate |
| Audit trail | Every create, approve, release, cancel | User, time and before/after values logged |
| Notifications | Email, SMS, push, webhooks per status | Correct status, sent once, no PII in plain text |
Defects, metrics and go-live
Defect severity
| Severity | Payments meaning | Example |
|---|---|---|
| Sev 1 | Money lost, duplicated or sent to the wrong party; compliance breach | Duplicate wire released; sanctions hit not held |
| Sev 2 | Payment blocked or wrong amount, no workaround | FX rate applied wrongly |
| Sev 3 | Workaround exists | Status shows late in UI |
| Sev 4 | Cosmetic | Label typo |
Metrics to report
- Test cases planned, executed and passed, by rail
- Open defects by severity, and defect leakage to UAT and production
- Requirement coverage, including every return and reject code
- Reconciliation breaks found and fixed
- Automation coverage for regression
Go-live checklist
- ☐ All critical and regression cases passed
- ☐ Zero open Sev 1 / Sev 2 defects
- ☐ End-to-end run on network simulator or certification passed
- ☐ Parallel run matched, reconciliation balanced
- ☐ Compliance and AML sign-off received
- ☐ Performance test met peak-volume SLA
- ☐ Rollback plan tested and kill switch ready
- ☐ Ops runbook, monitoring alerts and support contacts in place
- ☐ Business and product owner sign-off
Automation testing
What to automate so every release is checked the same way, fast. Aim to automate stable, high-risk, repeatable checks; keep exploratory and usability testing manual.
| ID | Scenario | Expected result |
|---|---|---|
| AUT-01 | Regression suite runs in CI on every build | Build blocked when a P1 test fails; results published to the team |
| AUT-02 | API and contract tests automated (schemas, error codes, idempotency) | Breaking API change caught before merge |
| AUT-03 | Test data created and reset automatically | Each run starts from a known state; no dependency on leftover data |
| AUT-04 | Network simulators / service virtualization for ACH, Fedwire, SWIFT, RTP | Tests run without real networks; every return and reject code can be triggered |
| AUT-05 | File-based tests automated (generate, submit, compare output) | Generated Nacha / pain.001 files and resulting messages compared field by field to expected |
| AUT-06 | Smoke test after every deployment | Core flows (create, approve, send, status) pass in each environment within minutes |
| AUT-07 | Automated reconciliation check | Nightly job compares hub, ledger and settlement totals and flags breaks |
| AUT-08 | Flaky test tracking | Flaky tests quarantined and fixed; flake rate reported |
| AUT-09 | Results linked to test management and defects | Each automated run updates test case status and links failures to defect IDs |
| AUT-10 | Automation coverage measured | Coverage of P1 cases and API endpoints reported each release |
Performance testing
Prove the platform handles real payment volumes and peaks within SLA, and fails safely when overloaded.
| ID | Scenario | Expected result |
|---|---|---|
| PRF-01 | Load test at expected peak (payroll day, month end) | Throughput and latency within SLA; zero lost or duplicate payments |
| PRF-02 | Stress test beyond peak to find the breaking point | System degrades gracefully (queues, throttles); recovers without data loss |
| PRF-03 | Soak / endurance test (24 hours or more) | No memory leaks, growing queues or slowdowns over time |
| PRF-04 | Spike test (sudden burst) | Auto-scaling or queuing absorbs the spike; SLA recovers quickly |
| PRF-05 | Batch window (ACH file build, end-of-day processing) | Batch completes before the cut-off with margin |
| PRF-06 | API latency percentiles (p50, p95, p99) | Within agreed targets under load |
| PRF-07 | Instant payments end-to-end time (RTP / FedNow) | Response well inside the network timeout under load |
| PRF-08 | Concurrent payments on the same account | No race conditions; balance and limits stay correct |
| PRF-09 | Slow downstream dependency under load (screening, FX, ledger) | Timeouts and retries behave as designed; no pile-up or duplicates |
| PRF-10 | Failover under load | Traffic switches to standby; in-flight payments complete or are safely retried |
| PRF-11 | Database and storage growth | Query times stay within target with 12 months of data |
Security testing
Payments are a prime fraud and attack target. Test that only the right people can move the right money, and that data stays protected.
| ID | Scenario | Expected result |
|---|---|---|
| SEC-01 | Authentication and MFA / step-up for high-risk actions | New payee, large amount and limit changes require step-up |
| SEC-02 | Authorization: access another customer’s payment or account (IDOR) | Access denied; attempt logged and alerted |
| SEC-03 | Maker-checker bypass attempts | Same user cannot create and approve; role changes take effect immediately |
| SEC-04 | Payment tampering between approval and sending | Amount or beneficiary change after approval forces re-approval; message integrity checked |
| SEC-05 | Injection and input attacks (SQL, XML, script) | Inputs treated as data; no execution or error leaks |
| SEC-06 | API security (token expiry, scopes, rate limits, mTLS) | Expired or wrong-scope tokens rejected; bursts throttled |
| SEC-07 | Replay attack (same signed request or webhook sent again) | Rejected using nonce / timestamp / idempotency key |
| SEC-08 | Webhook and file signature verification | Unsigned or wrongly signed payloads rejected |
| SEC-09 | Encryption in transit and at rest | TLS 1.2+ only; sensitive data encrypted in databases, files and backups |
| SEC-10 | PII and card data masking (UI, logs, notifications, test data) | Full account and card numbers never appear in logs or messages |
| SEC-11 | Session management (timeout, concurrent sessions, logout) | Idle sessions expire; tokens invalidated on logout |
| SEC-12 | Audit log integrity | Logs cannot be edited or deleted by application users; every action recorded |
| SEC-13 | Vulnerability scanning and penetration test | No open critical or high findings at go-live |
| SEC-14 | Secrets management | No keys or passwords in code, config or logs; rotation works |
A/B testing
Experiments on payment journeys (screens, copy, flows) to improve conversion and experience. The money logic must be identical in every variant; only the experience changes.
| ID | Scenario | Expected result |
|---|---|---|
| ABT-01 | Same payment, both variants | Amount, fees, FX rate, routing and status identical in A and B |
| ABT-02 | Stable variant assignment | A user stays in the same variant across sessions and devices |
| ABT-03 | Required disclosures present in every variant | Fees, FX rate, delivery time and other required disclosures shown in A and B |
| ABT-04 | Feature flag kill switch | Variant can be switched off instantly; users fall back to control safely |
| ABT-05 | Metrics captured correctly | Conversion, drop-off, errors and time to complete tracked per variant |
| ABT-06 | Guardrail metrics monitored | Fraud rate, payment failures and support contacts do not worsen in the test variant |
| ABT-07 | No sensitive data sent to analytics tools | Account numbers, names and amounts masked or excluded from analytics events |
| ABT-08 | High-risk controls excluded from experiments | Sanctions, AML, limits and approvals never vary by variant |
| ABT-09 | Sample size and significance before decision | Decision made only after the planned sample size and significance level |
| ABT-10 | Rollout and cleanup | Winning variant rolled out gradually; losing code and flags removed |
DR testing
Disaster recovery: prove payments can continue from the recovery site within the agreed RTO (time to recover) and RPO (data you can afford to lose), with no lost or duplicate payments.
| ID | Scenario | Expected result |
|---|---|---|
| DRT-01 | Planned failover of the payment platform to the DR site | Service restored within RTO; all configuration, keys and certificates work at DR |
| DRT-02 | Unplanned failover during live processing | In-flight payments completed or safely retried; zero duplicates or losses |
| DRT-03 | Data loss within RPO | Last committed payments present at DR; gap (if any) within RPO and reconciled |
| DRT-04 | Network connectivity from DR (Fedwire, ACH operator, SWIFT, RTP / FedNow) | All network connections, certificates and IP allowlists work from DR |
| DRT-05 | Files and schedules after failover | No file sent twice or missed; scheduled and recurring payments run once |
| DRT-06 | Cut-off management during an outage | Urgent payments prioritized; customers and ops informed of delays |
| DRT-07 | Reconciliation after failover | Hub, ledger and network totals match after recovery |
| DRT-08 | Failback to primary | Return to primary without data loss or duplicates; DR changes synced back |
| DRT-09 | Backup restore | Backups restore cleanly and within target time; restored data verified |
| DRT-10 | Runbook and communication | Runbook followed step by step; roles, contacts and customer messages work |
UAT vs end-to-end (E2E) testing
Both run on full journeys, but they answer different questions: E2E asks “do all the systems work together?”; UAT asks “does this do the job the business needs?”.
| E2E testing | UAT | |
|---|---|---|
| Goal | Prove systems integrate correctly from channel to network to ledger | Prove the product meets business needs and is ready to use |
| Who runs it | QE / test engineers | Business users, operations, compliance, sometimes clients |
| Written in | Technical steps, messages, data checks | Business language and real tasks |
| Data | Synthetic, covering every path and code | Production-like, realistic business scenarios |
| Focus | Flows, mappings, statuses, reconciliation, negative paths | Usability, workflow fit, reports, wording, sign-off |
| Automation | Mostly automated | Mostly manual, guided by scripts |
| Output | Pass / fail evidence and defects | Formal business sign-off (go / no-go input) |
| Example | Wire created in UI produces correct pacs.008, status and ledger entries | Treasury user pays a supplier and confirms the confirmation and statement make sense |
UAT test cases
Business-facing acceptance tests run by business users and operations, in business language, on production-like data. They confirm the product does the job; E2E tests confirm the systems work together.
| ID | Scenario | Expected result |
|---|---|---|
| UAT-01 | Treasury user pays a supplier by wire using a saved beneficiary | Payment completes; confirmation and statement entry are correct and understandable |
| UAT-02 | Payroll file uploaded and approved by two approvers | All employees paid on payday; totals match payroll report |
| UAT-03 | Customer sets up, changes and cancels a monthly payment | Schedule works as expected; no payment after cancellation |
| UAT-04 | Operations investigates and repairs a rejected payment | Ops can find the reason, repair and resend within the ops screens |
| UAT-05 | Compliance analyst reviews and clears a sanctions hold | Case shows all needed information; decision recorded with audit trail |
| UAT-06 | Customer service answers “where is my payment?” | Agent sees status, tracking and next step in one screen |
| UAT-07 | Finance reconciles the day | Reports match ledger and bank statements without manual workarounds |
| UAT-08 | Corporate client receives status reports and statements in their ERP | Client confirms format and content are usable |
| UAT-09 | Fees and FX shown before confirming match what is charged | Business confirms disclosure and charges are correct |
| UAT-10 | Business sign-off on reports and notifications wording | Wording clear, branded and compliant |
Shift Left, AI First, UI Next — and Data First, AI Next
Two simple ideas shape how this playbook is used. Read the full article: Shift Left, AI First, UI Next.
| Idea | What it means for payments testing |
|---|---|
| Shift Left | Test from day one: validate ISO 20022 mapping, sanctions data and fee rules in design and API tests, not after go-live. |
| AI First | AI drafts test cases, test data and defect triage notes; testers review and approve. High-risk decisions stay with people. |
| UI Next | Test the capability through the API first, then each channel (screens, chat, files) as a thin layer on top. |
| Data First | Get the data right before adding AI: clean reference data, structured addresses, correct mappings, masked and realistic test data. |
| AI Next | Once data is trusted, use AI for anomaly detection, smart test selection, log triage and predicting risky releases. |
Guardrail: AI suggestions are never the final approver for money movement, compliance decisions or go-live sign-off.
Defect triage process
Triage turns a raw defect into a clear decision: how bad it is, who fixes it, and by when.
Steps
- Log with steps, expected vs actual, test case ID, evidence and payment reference.
- Check for duplicates and confirm it is a real defect (not data or environment).
- Classify severity (business impact) and priority (fix order).
- Assign an owner and target date.
- Decide: fix now, fix next release, accept risk, not a defect, or duplicate.
- Retest the fix and run the related regression cases.
- Close with root cause recorded.
| Severity | Meaning | Fix target | Go-live |
|---|---|---|---|
| Sev 1 | Money lost, duplicated or misrouted; compliance breach; no workaround | Same day | Blocker |
| Sev 2 | Payment blocked or wrong, workaround is hard | 1–2 days | Blocker |
| Sev 3 | Workaround exists; limited impact | Next sprint | Allowed with sign-off |
| Sev 4 | Cosmetic | Backlog | Allowed |
Cadence: daily triage call during test cycles (QE lead, dev lead, product owner, ops / compliance when needed). AI first: AI can suggest duplicates, severity and likely root cause from logs; the triage team decides.
Testing KPIs
Track a small set of KPIs every day of a test cycle. The Excel download calculates these automatically.
| KPI | Formula | Example target |
|---|---|---|
| Execution progress | Executed / planned (excluding N/A) | 100% before go-live |
| Pass rate | Passed / executed | 95% or higher |
| P1 pass rate | P1 passed / P1 executed | 100% |
| Open Sev 1 / Sev 2 | Count of open defects | 0 at go-live |
| Defect density | Defects per 100 executed tests | Trending down |
| Defect leakage | Defects found after release / total defects | Below 5% |
| Retest pass rate | Retests passed / retests run | 90% or higher |
| Rejected defect % | Not-a-defect / total logged | Below 10% |
| Automation coverage | Automated P1 cases / total P1 cases | Rising each release |
| Mean time to fix (Sev 1/2) | Average hours from logged to fixed | Within SLA |
Sample reports
Sample report with illustrative figures, to show the format.
1. Daily test status report (Shift Left)
| Area | Executed | Pass rate | Open defects | RAG |
|---|---|---|---|---|
| ACH | 40 / 42 | 95% | 2 (Sev 3) | Green |
| Wire / SWIFT | 33 / 38 | 88% | 1 Sev 2, 2 Sev 3 | Amber |
| Files and mapping | 12 / 17 | 83% | 1 Sev 2 | Amber |
| Risk and compliance | 10 / 10 | 100% | 0 | Green |
Top risks: FX booking retry not yet fixed (Sev 2). Next 24h: retest FIL-11 and WIR-06; start DR exercise.
2. AI-assisted defect triage summary (AI First)
| Defect | AI suggestion | Human decision |
|---|---|---|
| D-118 pacs.008 missing purpose code | Duplicate of D-104 (92% match) | Confirmed duplicate, closed |
| D-121 fee charged twice on return | Sev 1, root cause: fee reversal job | Agreed Sev 1, fix today |
| D-125 label typo on status screen | Sev 4 | Agreed, backlog |
AI drafts; the triage team approves every severity and decision.
3. Data quality report (Data First)
Gaps: 2.2% of legacy beneficiaries still need town and country completed before the ISO 20022 address rule applies to them.
4. Go / no-go summary
| Criterion | Status |
|---|---|
| All P1 cases passed | Met |
| Open Sev 1 / Sev 2 = 0 | Met |
| Parallel run reconciled to the cent | Met |
| Performance at peak within SLA | Met |
| DR exercise passed | Met |
| Business, compliance and ops sign-off | 2 of 3 received |
Recommendation: Go, subject to the final operations sign-off.