Skip to content
Last updated

Testing

You don't need a physical terminal to build and test your integration. Each integration path connects to its own simulator that replicates the behaviour of a real Tyro terminal, so you can exercise the full transaction lifecycle from your own machine.

Simulator by integration path

JS library.NET libraryIn-store API
SimulatorIntegration server simulatorTest integration serverSandbox (TID-based scenarios)
Scenarios triggered byMagic valuesSimulated scheme responsesTerminal ID (TID)
ReferenceGet started with the JS libraryTest integration serverTesting

Mandatory and optional test cases by feature

Certification requirement level differs by feature, and — for several features — by whether your business is Retail or Hospitality. Build your test-case list against this table before starting certification, so you're not scoping test cases for something that's merely optional for your vertical, or missing one that's compulsory.

FeatureHospitalityRetail
Payment, cashout and refund — PaymentCompulsoryCompulsory
Payment, cashout and refund — RefundCompulsoryCompulsory
Payment, cashout and refund — CashoutOptionalOptional
Integrated receiptsHighly recommendedHighly recommended
Settings, POS and API keys — Tyro settings pageCompulsoryCompulsory
Settings, POS and API keys — POS informationCompulsoryCompulsory
Settings, POS and API keys — API key configurationCompulsoryCompulsory
Manual settlementOptionalOptional
ReportsHighly recommendedOptional
Pre-authorisationOptionalOptional
Split paymentsHighly recommendedOptional
TippingHighly recommendedOptional
Bar tabsOptionalOptional
Headless pairingOptionalOptional
Headless transactional UIOptionalOptional

"Highly recommended" isn't enforced as a certification blocker the way "Compulsory" is, but Tyro still expects a documented reason for skipping it — raise this with your Partner Manager rather than silently omitting the test cases.