Français
English
Español
Deutsch
NorskPractical guide
Test an order and payment without duplicate effects
Check order states, stock and payment events before opening the shop.
Practical guide
A case to prepare your project
A customer confirms twice after a connection failure. The provider also delivers the same notification twice. The system should recognise the event and prevent duplicate fulfilment or stock reduction.
Illustrative scenario, to adapt to your organisation.Prepare and perform the checks
Prepare a test environment
Use provider test tools, fictitious orders and isolated stock. Define currency, amounts, states and expected timing.
Simulate interruptions
Test double clicks, declines, late and replayed notifications, mismatched amounts and simultaneous purchases of the last item.
Reconcile records
Compare order, provider reference, amount, currency and stock movements. Resolve differences through an authorised, logged action.
A reusable acceptance checklist
Agree thresholds, owners and test data before testing. Retain dated results, exceptions and the acceptance decision.
| Check | Expected result | Evidence to retain |
|---|---|---|
| Server calculation | A browser-side price change does not alter the accepted server amount. | Order and server calculation compared. |
| Authentic notification | Invalid signatures or inconsistent amounts cannot confirm payment. | Test events and logs without secrets. |
| Replayed event | One event cannot apply a transition or stock movement twice. | Event identifier and action history. |
| Last available item | Concurrent purchases follow the agreed availability rule. | Simultaneous test and before/after inventory. |
Decide using evidence
Prepare procedures for unmatched payments, refunds and unavailable notifications. Keep exercises in the test environment; complete provider contractual validation before real activation.
Standards and reading
References checked on .
Relevant ISO standards
- ISO/IEC 25010:2023
Evaluate product consistency and reliability.
- ISO/IEC 27001:2022 (+ Amd 1:2024)
Scope commercial information risks.
These standards help define scope and expected evidence. Citing them does not certify Salott-IT or establish your project’s conformity. A dedicated assessment is required. Include applicable amendments when scoping the engagement.
Technical documentation
Reference books
- E-commerce 2023–2024: Business, Technology, Society · Global Edition, 18th edition
Kenneth C. Laudon & Carol G. Traver · Pearson · 2024 (eText)
Original synthesis based on official summaries, open documentation and publishers’ public descriptions or contents. Books are selected references, not a universal ranking. Copyrighted book and standards text is not reproduced.
Start with your actual situation.
Scope, responsibilities, timing and acceptance criteria will be defined in the proposal.