Payments

Accredited Linkly connectivity without locking the POS to one terminal vendor.

StamPOS separates the sale workflow from the payment-provider implementation, with its Linkly Cloud REST integration now accredited.

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
Accredited

Linkly Cloud REST

The assessed StamPOS integration has completed Linkly accreditation for its implemented payment workflow.

Local resilience

Persisted attempts

Payment attempts are recorded so an interrupted or uncertain result can be investigated instead of being treated as a simple decline.

Operator safety

Unknown means unknown

When the final result is uncertain, StamPOS warns the operator and uses transaction-status recovery before another payment is attempted.

Architecture

Provider-neutral adapter

The payment layer is structured so additional providers can be introduced without redesigning the core sales interface.

Deployment

Merchant onboarding

Production terminal availability, credentials and acquiring arrangements depend on the selected Linkly-supported provider, acquirer and merchant setup process.

Connectivity

Honest network requirements

Core POS data is local. Internet connectivity is required when the chosen payment service needs to authorise a card transaction.

What accreditation means

A major technical gate is complete.

Accreditation confirms the assessed integration against the applicable Linkly process. It does not replace merchant onboarding, acquirer approval, correct site configuration, hardware validation, user training or business reconciliation procedures.

Read the payment operations guide