Under The Stack

Under The Stack
  • 0,0 (0)
  • Affaires

One practical lesson about in-store commerce technology. Delivered every Tuesday. Each week you'll receive one conversation with the people shaping the future of in-person retail - one lesson that you can apply immediately.

Épisodes

  1. -2 j

    What is payment testing?

    1. Test the entire checkout journey, not just the payment transaction The biggest mistake organisations make is treating payment testing as “did the card go through?” David argues that’s far too narrow. A real checkout includes: POS softwareBarcode scannersReceipt printersPayment terminalCash handling (where applicable)Customer interactionIf you only test one component in isolation, you can successfully process a payment while still delivering a broken customer experience. The objective is to validate the entire customer journey, because that’s what customers actually experience. --- 2. Simulated terminals are useful - but they’re not reality “When was the last time you paid on a simulated terminal when you went to Tesco?” His point is simple: Retailers deploy physical devices, not simulations. Simulators are faster and easier, but they cannot accurately reproduce: firmware changeshardware behaviourPIN entrycard insertionreceipt printingreal-world device interactionsFor anything being deployed into stores - or for certification - testing should happen on the actual hardware. --- 3. Lack of test coverage is one of the industry’s biggest hidden risks Many retailers believe they’re testing thoroughly because they have dozens of automated tests. David argues the opposite. Often they’re missing: international cardsforeign issuersDCC scenariosdifferent payment methodsedge casesA solution that works perfectly with UK Visa cards might fail for an overseas Mastercard customer. Automation allows organisations to expand coverage from tens of scenarios into hundreds without multiplying manual effort. --- 4. Start simple, then expand You don’t automate every possible payment journey on day one. David recommends: Purchase transactionsRefundsMost common payment methodsHighest-volume hardwareEdge cases afterwardsIn other words: Automate the journeys that matter most first, then continuously widen the safety net. This makes automation practical instead of overwhelming. --- 5. Every technology change introduces payment risk Modern payment environments are constantly evolving. New: firmwarepayment applicationspayment terminalswalletswearablescontactless technologiesEach seemingly small change can alter how a transaction behaves. David’s message is that testing shouldn’t be viewed as something you do before launch - it should become an ongoing capability that evolves alongside your payment estate.

    What is payment testing?
  • 1 épisode

À propos

One practical lesson about in-store commerce technology. Delivered every Tuesday. Each week you'll receive one conversation with the people shaping the future of in-person retail - one lesson that you can apply immediately.

Informations

  • Création
    Under The Stack
  • Années d’activité
    2026
  • Épisodes
    1
  • Classification
    Tous publics
  • Copyright
    © 2026 Under The Stack
  • Site web de l’émission
    Under The Stack