Andrew Anagnostellis from Umgeni Investments:
Look, I just wanted to go back to the connectivity issue firstly just to say congratulations on the disclosures, very timely and comprehensive. My question really goes to your initial point where you were -- said you were very concerned about the issue itself, the first time in many years. Isn't it a concern here that it sort of seems to have crept up on Tyro? I note 7th of January, the disclosure talked about 15% impact. The next week, it was 30% impact. Isn't it a concern that the outage seems to have been much more serious and much quicker? And is it something, looking back on it, that should have been attended to quicker? Or were the company's existing procedures and policies in place and you were comfortable that this was properly handled in accordance with the disaster recovery plans you would have had in place?
Robert Michael Sean Cooke, Tyro Payments Limited - MD, CEO & Director:
Thanks for the question, Andrew. Now look, just trying to answer that in an overall way. The disclosures, the first disclosure we made related to the number of terminals which were impacted at that point in time, there were more terminals that lost connectivity over the first series of days. So we've reported as events unfolded and reflected what the impact was. As I just called out, it was circa 30% of our merchants, of which 19% at the peak were fully impacted and 11% were partially impacted. In terms of the event itself, as we've sort of -- or as we have disclosed in the release that we made in the past, this was something that arose from an issue sitting on the terminal. It was not something that was able to be foreseen. The -- when the incident happened on the evening of the 5th of January, at 10:00 that evening, a major incident event was called. All our emergency response and disaster recovery initiatives kicked in at that point. And I could tell you, everything humanly possible was done to mitigate the impact on our merchants. So I'm very comfortable that all due process and procedures were implemented, and everything that was possible to be done was done. As I've called out, though, this is something that has never happened in our history. This has happened with other institutions, though, in the past. What Tyro is doing which is quite different to anybody else, we are not comfortable sitting here today, and I'm not comfortable sitting here today without a fall-over solution -- a fail-over solution, which is why we are developing our dongle, which will be issued to every merchant as a fail-over. Now that's something no other institution has done, notwithstanding that fact others have had incidences like this occur. So we are taking this. We recognize it could happen. I'm not prepared to sit here and ignore it going forward. I don't think it will ever happen again due to the root cause of this issue. However, I'm not prepared to ask people just to trust us. We will actually have an alternate path for people to transact with us.
- Forums
- ASX - By Stock
- TYR
- Ann: Half Yearly Report and Accounts
Ann: Half Yearly Report and Accounts, page-75
-
- There are more pages in this discussion • 31 more messages in this thread...
You’re viewing a single post only. To view the entire thread just sign in or Join Now (FREE)
Featured News
Add TYR (ASX) to my watchlist
(20min delay)
|
|||||
Last
81.0¢ |
Change
0.035(4.52%) |
Mkt cap ! $426.8M |
Open | High | Low | Value | Volume |
77.5¢ | 81.5¢ | 77.5¢ | $1.412M | 1.777M |
Buyers (Bids)
No. | Vol. | Price($) |
---|---|---|
2 | 96814 | 80.5¢ |
Sellers (Offers)
Price($) | Vol. | No. |
---|---|---|
81.0¢ | 85873 | 3 |
View Market Depth
No. | Vol. | Price($) |
---|---|---|
2 | 96814 | 0.805 |
3 | 13966 | 0.800 |
1 | 12466 | 0.795 |
1 | 20000 | 0.785 |
4 | 9564 | 0.780 |
Price($) | Vol. | No. |
---|---|---|
0.810 | 85873 | 3 |
0.815 | 44015 | 3 |
0.820 | 61466 | 8 |
0.825 | 30000 | 2 |
0.830 | 7000 | 2 |
Last trade - 16.10pm 06/11/2024 (20 minute delay) ? |
Featured News
TYR (ASX) Chart |