
FNB says it reversed duplicate virtual-card charges traced to another bank's settlement file. Customers were left overdrawn while they waited.
FNB says duplicate charges that landed on some customers' virtual cards over several days have been reversed. The bank says the extra debits, for purchases at various merchants, arrived in a settlement file from a third-party acquiring bank, and that the acquirer has since submitted reversals which have been processed.
It has not said how many customers were affected, what the duplicates were worth in total, or which bank sent the file. Public complaints posted in the first ten days of November show what the wait looked like on individual accounts: balances driven negative, an SMS demanding an immediate repayment, debit orders put at risk, and customers told to wait 72 hours, or as long as five business days, for money the bank said they did not need to claim.
It is the second time this year that people paying with an FNB virtual card have been debited more than once for a single purchase. In March the bank said the fault was its own. This time it places the fault outside its systems.
An acquiring bank is the merchant's bank. It collects card payments for a retailer and sends the cardholder's bank a settlement file, the list of amounts to debit. FNB says the duplicated entries were in one of those files.
On 11 November the bank said the third-party acquirer had submitted the reversals and that those reversals had been successfully processed. It said it was monitoring the clean-up so that customers did not suffer a financial loss or damage to their credit records.
"Our priority remains to mitigate the risk of affected customers experiencing any financial loss, or adverse credit record implications as a result of this incident," FNB said. It added: "We sincerely apologise to the affected customers for the inconvenience caused."
Anyone who still sees a duplicate can call the number on the back of their card, use Secure Chat in the FNB app, or use the bank's other channels. The statement does not say whether overdraft interest, unpaid debit-order fees or other knock-on costs are reversed automatically, or whether a customer has to ask for them.
The bank's public account gives no dates and no amounts. The complaints customers put on Hellopeter do.
Thomas J Hunkin wrote on 4 November that two card purchases on his FNB cheque account on 2 November had each been debited twice: one of R31,429.00 and one of R459.48. He put the extra taken in error at R31,888.48. On 3 November at 19:33, he wrote, the FNB app told him:
We identified an error that may result in a duplicate settlement transaction reflecting on your account on 04 November 2026. We are working with the third-party acquirer to reverse the transaction and any related fees within 72 hours. No action is required from you at this stage.
Just under ten hours later, at 05:27 on 4 November, he wrote that an SMS said the account "is overdrawn by R20127.26. This amount must be repaid immediately. Please deposit funds today." FNB's reply on Hellopeter, posted at 09:26 on 5 November, apologised and said a formal complaint had been logged and referred on. It did not confirm that the R31,888.48 had come back, and it did not say the overdraft demand had been withdrawn.
The same 72-hour line appears in other complaints from those days, for much smaller sums. Stella O wrote on 4 November that a duplicated transaction of R2,350, a purchase at Uitkyk Vleis Mark, had left the account on a negative balance of R2,350, and that she had been told to wait 72 hours with no access to the money. Shiefaa Hendricks wrote on 5 November that duplicate settlements had reflected on 4 November for purchases already processed on 31 October. She had been told the issue was known and might take between 72 hours and five business days. Her available balance was affected, she wrote, and debit orders were at risk of being returned for insufficient funds. She asked for any charges or returned debit-order fees caused by the error to be refunded. Another customer, writing on the evening of 5 November, said they had queried transactions that went through twice, been told to wait 72 hours, and then been told the account was overdrawn and needed a deposit. They asked what a duplicated debit order would do to a credit record.
By 7 November the 72 hours had run out for at least one person. Arina Crous wrote that morning that she had received an official notification on the Tuesday saying duplicate transactions would be rectified within 72 hours, and that nothing had been resolved. Her account was in a negative balance and she could not use her own funds. She said agents were offering apologies and no date.
FNB's statement of 11 November calls the other party a third-party acquiring bank and stops there.
A customer, Babsy N, described a more specific message. In a complaint posted on 9 November she wrote that several duplicate card payments she had not initiated were later described to her as a known system issue, to be reversed within 72 hours, with no action required. The others were reversed. One stayed: a transaction she recorded as "PURCH MOMENT_DStv", R548.21, dated 5 November. She wrote that her own DStv payment that day, made in the FNB app from an FNBy Transact account, was R444.00, not R548.21. When she asked for that leftover entry to be investigated as part of the same duplicate-settlement problem, she wrote, the consultant's first suggestion was to place a hold on the account, cancel the card, and treat it as a different kind of incident. She said that would have stopped her transacting and disrupted legitimate debit orders.
Towards the end of that conversation, she wrote, FNB produced a general notification acknowledging an issue affecting credit card and virtual credit card duplicate settlement transactions originating from Nedbank. The notification, as she recorded it, said customers might see duplicate entries and that no action was required. On the morning of 10 November she updated the complaint: the outstanding transaction had been fixed the night before.
That is one customer's account of a notification. It is not a sentence in the statement FNB issued the next day. Nedbank has not, in the material checked for this story, confirmed that it was the acquirer, and FNB has not named it in public. What the two accounts do share is the mechanism: a duplicate settlement, a promise that the customer need do nothing, and a reversal that arrived on the bank's timetable rather than the customer's.
On 4 March, customers reported being charged twice, and in some cases three times, for card purchases. Several of the first complaints were Takealot orders. FNB then said the problem was wider than Takealot and was limited to its virtual card, the card customers create in the app for online payments and which the bank promotes as the safer way to pay because the security code changes.
"A technical processing error affecting a number of our virtual cards has resulted in some duplicated transactions," an FNB spokesperson said. "FNB has identified the source of the error and will reverse all duplicate charges as soon as possible. The matter is being urgently resolved and we apologise to all affected customers."
The bank later said the reversals would run on the evening of Friday 6 March. Before that statement, customers described the same knock-on effects seen in November. One said a support agent could not help or escalate a duplicate charge. Another said they were R2,700 in arrears because of the duplicated transactions and that Secure Chat was not resolving it. A third said a single Takealot purchase had been debited three times.
March and November are not the same incident. In March FNB called it a technical processing error on its own virtual cards. In November it says the duplicates arrived in a file from another bank. For the person watching the balance, the sequence is the one Hunkin's messages record: the app says no action is required, and the collections SMS asks for the money anyway.
FNB says the reversals have been processed and that its priority is that nobody is left out of pocket or marked on a credit record. It has not published a count of accounts, a rand total, the dates the file covered, or the name of the acquirer. It has not said why a duplicated line in an incoming settlement file was posted to accounts instead of being held. It has not said whether the overdraft interest and the returned debit-order fees that customers asked about, in writing, in the days before the statement, are being reversed with the original charge or only if someone complains.
A customer who still sees a second debit of the same purchase can use the number on the card or Secure Chat. The statement is the bank's word that the batch has been cleaned up. The complaints are the record of what happened to particular accounts before that word arrived.
Source: SA Tech News




