---
title: "Araxi H1 Update Flags Terminal Delays, Pay@ Strong"
description: "Araxi’s H1 business update says payment terminal orders were postponed, but Pay@ is trading ahead of expectations, with 4 months in interim results."
canonical_url: "https://liners.com/news/araxi-h1-2027-business-update-payat-terminal-delays"
markdown_url: "https://liners.com/news/araxi-h1-2027-business-update-payat-terminal-delays.md"
type: "article"
language: "en"
published_at: "2026-10-01T10:03:57.782Z"
updated_at: "2026-10-01T10:04:55.120Z"
---

# Araxi H1 Update Flags Terminal Delays, Pay@ Strong

Araxi’s H1 business update says payment terminal orders were postponed, but Pay@ is trading ahead of expectations, with 4 months in interim results.

## Breadcrumbs

- [News](/news)
- [Araxi H1 Update Flags Terminal Delays, Pay@ Strong](/news/araxi-h1-2027-business-update-payat-terminal-delays)

## Content

## In Short
Araxi released a business update for the six months ended 30 September 2026. The group said trading in its payments terminal business was below expectations due to delayed orders and maintenance pressure. It also said Pay@ is performing well and four months of Pay@ results will be included in interim numbers.

## What Happened
Araxi told shareholders it is operating in an uncertain South African business environment, where supply chains, input costs, and delayed capital spending are affecting large organisations.

In its payments division, Araxi said the local market for payment terminals continues to grow, but customer buying decisions are shifting. Enterprise buyers are reassessing whether they should own or rent terminal fleets, mainly to reduce lifetime costs. Merchants are also rethinking which terminal types they need in stores.

Araxi pointed to three device trends. First, demand for low-cost card payment devices to expand acceptance. Second, standalone terminals are evolving into software-driven commerce devices, meaning hardware that runs apps, like a smartphone for checkout. Third, NFC-enabled phones are starting to compete with dedicated terminals via SoftPOS or Tap-to-Pay, which turns a phone into a card terminal.

Despite these long-term tailwinds, Araxi said regulatory changes and the South African Reserve Bank modernisation initiative contributed to postponed terminal orders and deployments. It also said terminal maintenance was negatively impacted. Management described H1 performance in the terminal business as disappointing and well below expectations, but said the pipeline for H2 is reasonable.

Araxi added that Halo Dot made progress with new clients and global partnerships.

On acquisitions and integration, Araxi said the [Pay@](/pay-at) business continues to perform well and positively against expectations. It also said four months of Pay@’s performance will be included in interim results.

In software, Araxi said its recovery continued, with increasing sales, a strong project pipeline, and improved profitability from tighter cost controls. The group highlighted demand for services in AI, agentic AI, intelligent data, and cloud, meaning software that automates tasks, uses data more effectively, and runs on remote servers.

## Why It Matters
For South Africa’s payments ecosystem, Araxi’s update shows a near-term slowdown in physical terminal rollouts, even while digital payments adoption keeps rising.

The shift toward SoftPOS and app-based commerce devices suggests hardware providers will need to compete more on software, services, and total cost of ownership. If Pay@ continues to outperform, it could help offset volatility in the terminal cycle and reshape how investors view Araxi’s payments mix going into H2 and the interim results period.

## Sources and products

- [SHARENET - Your Key To Investing on The JSE Securities Exchange - South Africa](https://www.sharenet.co.za/v3/sens_display.php?tdate=20260930170500&seq=82)
- [Pay@](/pay-at)

## Related pages

- [Market Trends](/news)

## Access and citation

- [Canonical HTML page](https://liners.com/news/araxi-h1-2027-business-update-payat-terminal-delays)
- [Markdown route index](/sitemap.md)
- [Agent access guide](/llms.txt)