Make acceptance reproducible.
Prove the behavior that matters to your integration, from successful requests to duplicates, uncertainty, revocation and exit.
Record the conditions before the result.
Each test record needs a case identifier, interface/version, environment, release identifier, named actor and scope, synthetic inputs, expected outcome, observed result, redacted correlation references, reviewer and date. Mark a case not applicable with a reason. Fixtures, local browser tests and approved provider observations are different evidence classes.
Minimum scenario matrix
Apply financial cases only where the approved relationship executes or records those operations. Software, distribution and data partners still need identity, data-scope, compatibility and exit tests.
| Case | Expected observation | Evidence |
|---|---|---|
| A01 · Authorized success | Exactly one verified business effect; receipt/journal where applicable. | Request, authoritative outcome and persisted result. |
| A02 · Duplicate request | Same key/body replays; changed body conflicts. | Response comparison and effect count. |
| A03 · Duplicate event | No second financial effect. | Event receipt and resulting movement count. |
| A04 · Timeout after submit | Unknown result remains blocked until lookup/evidence resolves it. | Original reference, lookup and final resolution. |
| A05 · Invalid evidence | Invalid authentication or mismatched amount/asset/account cannot confirm. | Denied transition and redacted reason. |
| A06 · Late / reordered outcome | Transition follows current state; exceptional confirmation is explicitly authorized. | Timeline and authorized resolution. |
| A07 · Reversal / refund | Original history retained; correcting action is separately authorized. | Original and correcting references. |
| A08 · Settlement variance | Short, over, unmatched and duplicate evidence remain explicit. | Statement, per-asset totals and exception disposition. |
| A09 · Cross-tenant / own-record denial | No foreign record, existence leak or unauthorized effect. | Allowed/denied actor matrix. |
| A10 · Revocation / disabled capability | Existing session cannot bypass current denial. | Before/after grant and denied operation. |
| A11 · Dependency outage / recovery | Durable work remains recoverable without blind duplicate execution. | Fault window, backlog and recovery result. |
| A12 · Version / data / exit | Selected client/schema compatibility, scoped export and disconnect are demonstrated. | Compatibility matrix, redacted export and revocation test. |
Acceptance is a signed-off scope.
The decision states passed/failed/not-applicable cases, material defects, permitted operations and limits, responsible reviewers, evidence location and expiry. A fixture pass cannot close a provider-acceptance item; local browser success cannot close a production deployment item. Failed material cases require remediation or an explicit bounded decision from the authorized owner.