Linkly Cloud REST
Pairing, purchases, refunds, transaction status, recovery, logon and settlement are being prepared for accreditation.
Payments
Connected EFTPOS without locking the POS to one terminal vendor.
StamPOS separates the sale workflow from the payment-provider implementation, with Linkly Cloud REST as the first production integration path.
How it works
The sale remains a StamPOS workflow.
StamPOS creates and records the sale locally, then passes the payment request through the configured provider adapter. The operator receives one consistent workflow while the payment layer handles provider-specific communication.
1Create saleProducts, totals and operator details are stored locally
2Create payment attemptA unique transaction and recovery reference is recorded
3Send to providerThe configured terminal service handles card interaction
4Complete or recoverThe final outcome is stored and the receipt workflow continues
Persisted attempts
Payment attempts are recorded so an interrupted or uncertain result can be investigated instead of being treated as a simple decline.
Unknown means unknown
When the final result is uncertain, StamPOS can warn the operator and use transaction status recovery before another payment is attempted.
Provider-neutral adapter
The payment layer is structured so additional providers can be introduced without redesigning the core sales interface.
Merchant onboarding
Production terminal availability and credentials depend on the selected provider, acquirer and merchant setup process.
Honest network requirements
Core POS data is local. Internet connectivity is required when the chosen payment service needs to authorise a card transaction.
Accreditation status
Built against the official test path.
StamPOS is currently progressing through Linkly sandbox testing and accreditation preparation. Public production claims will be updated only after the required evidence and approval process are complete.