Jump to Content
Developer Documentation
HomeGuidesRecipes
Log InDeveloper Documentation
Log In
HomeGuidesRecipes

Point of Sale - Spice Payments Adaptor

  • Getting Started
    • Minimum Development checklist
    • Recommended Implementation
  • Integration Features
    • Error Messaging
    • Manual Override - Network Disconnect
    • Payment Provider
    • Ping Test
    • Signature Transactions
    • Transaction Recovery
  • Spice Certification Process
    • Certification test suite
    • Post-certification best practice guide
  • Release notes

Point of Sale - SPI Library

  • Getting Started
    • Minimum development checklist
    • Steps to integrate
  • Integration Features
    • Auto Address Resolution
    • Pre-authorisation
    • Pay at table
  • Libraries and Sample
    • .NET
    • JavaScript
    • Java/Android
    • iOS
  • Designing the UI
    • Payment Provider
    • Non Web-Based EFTPOS UI
    • Web-based EFTPOS UI
    • Transaction recovery and 'unknown' status
    • Transaction UI
  • SPI Library Certification Process
    • Certification test suite
    • Post-certification best practice guide
  • Release Notes
    • Upgrading to SPI Client 2.8
    • Upgrading to SPI Client 2.5
    • Upgrading to SPI Client 2.4
    • Upgrading to SPI Client 2.3

Resources

  • Devices
    • Test Terminal and Guides
    • Magic numbers for test transactions
  • General Troublshooting
    • Spice FAQ
    • SPI FAQ
  • Glossary
Powered by 

Error Messaging

Suggest Edits

Spice is responsible for supplying the transaction user interface, managing the transaction workflow and handling errors. The POS will only need to produce one piece of UI for this integration. In the event that a transaction is initiated but Spice is not running an error must be displayed to the user.

Recommendation: "Please check that Spice is running."

Updated 5 months ago