GF
Gwen F
1 reviews | Active since Oct 2013
30 Aug 2025, 09:59
No feedback Appalling service DISGUSTED SECURITY SERVICES
Good day I reported ***** activity on my Discovery bank account on 22/08. I . to open a ******** case of ***** @ SAPS. I made an affidavit & emailed the Affidavit & case number to Discovery bank. I was advised the case will take 72hours for feedback I did my follow ups with the ***** department several times, was told that the case is still reviewed. I could not be transferred to the investigator as per Discovery bank protocols. I am now sitting with no hope when I will receive my money. Why will Discovery Bank allow money to go missing from an account, why is there security so appalling & disgusting that their System will allow money to disappear without raising questions & let the account owner be alerted. Other banks will make sure a person's money us well protected. FNB will never allow it their clients money are very safe. DISCOVERY BANK, PLEASE PUT MY MONEY BACK INTO MY ACCOUNT.
Helpful (0)
Replies (5)0
Replies (5)
Discovery Bank's replyOfficial
30 Aug 2025, 13:53Hi Gweni,
Thank you for reaching out to us.
I apologize for the inconvenience caused by this.
I will look into this and provide you with feedback.
Regards,
Jabulile
Thank you for reaching out to us.
I apologize for the inconvenience caused by this.
I will look into this and provide you with feedback.
Regards,
Jabulile
Discovery Bank's reply30 Aug 2025, 13:53
Official
Hi Gweni,
Thank you for reaching out to us.
I apologize for the inconvenience caused by this.
I will look into this and provide you with feedback.
Regards,
Jabulile
Thank you for reaching out to us.
I apologize for the inconvenience caused by this.
I will look into this and provide you with feedback.
Regards,
Jabulile
GF
Gwen F's updateReviewer Update
01 Sept 2025, 08:44Thank you for your response on this platform but I DIN NOT received any feedback from Discovery Bank which is really a disgust to keep their so-called clients waiting.
GF
Gwen F's update01 Sept 2025, 08:44
Reviewer Update
Thank you for your response on this platform but I DIN NOT received any feedback from Discovery Bank which is really a disgust to keep their so-called clients waiting.
GF
Gwen F's updateReviewer Update
01 Sept 2025, 08:46Thank you for your response on this platform but I DID NOT received any feedback from Discovery Bank which is really a disgust to keep their so-called clients waiting.
GF
Gwen F's update01 Sept 2025, 08:46
Reviewer Update
Thank you for your response on this platform but I DID NOT received any feedback from Discovery Bank which is really a disgust to keep their so-called clients waiting.
GF
Gwen F's updateReviewer Update
01 Sept 2025, 08:48Will I ever advised my family & friends to join Discovery Bank??????? Based on my experiences, is Questionable.
I was with FNB & this would never happen.
I was with FNB & this would never happen.
GF
Gwen F's update01 Sept 2025, 08:48
Reviewer Update
Will I ever advised my family & friends to join Discovery Bank??????? Based on my experiences, is Questionable.
I was with FNB & this would never happen.
I was with FNB & this would never happen.
GF
Gwen F's updateReviewer Update
01 Sept 2025, 13:35Major South African bank has a serious security flawBy Seth ThorneIndependent tests revealed that Discovery Bank has a serious security vulnerability that could allow online purchases to go through without the correct CVV number.
Discovery Bank is South Africa’s premier new digital bank with 1.1 million clients and 2.5 million accounts, with between 1,300 and 1,400 new clients signing up each day.
However, it looks like these clients are now facing a significant security risk. Anonymous complaints submitted to Newsday pointed to weaknesses that were later confirmed through multiple tests.
These tests showed that transactions could be completed using incorrect CVV numbers, suggesting the bank may not be verifying this information during online purchases.
The card verification value (CVV) is the set of three digits printed on the back of the card which acts as a security measure when making payments online.
Entering the CVV is an important security feature as it ensures that the person making the purchase has the card.
This is not the first time this issue raised concerns about Discovery Bank’s card security related to online purchases.
Six years ago, MyBroadband reported that one could type in any three digits for the CVV when buying something online with a Discovery Bank card, and the transaction would be approved.
At the time, Discovery Bank told MyBroadband that they detected the CVV issue a week prior, “and immediately started implementing a series of steps to correct the issue”.
“It has been fully resolved and has not led to ***** being experienced or our clients incurring any losses.”
Newsday asked Discovery Bank about the issue, which has also dogged the financial institution in the past.
Discovery Bank told Newsday that when in-app authentication is presented, they do not fail a transaction due to an incorrect CVV.
This is because Discovery Bank considers the in-app authentication to be stronger security than the CVV data.
“For Card Not Present transactions where in-app authentication is not requested, we do fail the transaction if the CVV is incorrect,” Discovery Bank added.
Testing Discovery Bank card security
Newsday, with the help of an independent software engineer and security expert, put Discovery Bank’s security to test through local and international online purchases.
We used a Discovery Bank card to make a small online purchase from Checkers Sixty60, one of South Africa’s most popular online shopping platforms.
When asked for the CVV, a **** “123” code was used, which took us to the next step, in app authorisation.
After approving the transaction in the Discovery Bank app, the transaction was approved, and the money went out of the account.
This supports the claim that they “do not fail a transaction due to an incorrect CVV,” because the bank considers “the in-app authentication stronger than the CVV data.”
Next, we placed an online order on Temu, the popular Chinese online shopping platform which has gained great support in South Africa.
We placed a R217 order, which required a CVV. Again, we used the incorrect “123” number. Immediately, it said that the payment was successful on the Temu site.
No in-app authentication was requested. However, we received multiple notifications that the payment was pending.
In a matter of 5 minutes, two notifications came through that the payment went through, and then the card was declined.
However, while Discovery said that the payment was declined, our bank balance told a different story.
On the app, the Temu payment, which never required in-app authentication, was pending for several hours until it was ultimately approved.
There was another R4.34 charge, which was taken off for international payments.
This test raises questions about Discovery Bank’s claim that card not present transactions, where the CVV number is incorrect, will fail.
In this test, no in-app authentication was requested, the wrong CVV was entered, and the transaction still went through.
The screenshots below show the tests conducted by Newsday regarding the Discovery Bank security vulnerability.
CVV authentication
Discovery Bank is South Africa’s premier new digital bank with 1.1 million clients and 2.5 million accounts, with between 1,300 and 1,400 new clients signing up each day.
However, it looks like these clients are now facing a significant security risk. Anonymous complaints submitted to Newsday pointed to weaknesses that were later confirmed through multiple tests.
These tests showed that transactions could be completed using incorrect CVV numbers, suggesting the bank may not be verifying this information during online purchases.
The card verification value (CVV) is the set of three digits printed on the back of the card which acts as a security measure when making payments online.
Entering the CVV is an important security feature as it ensures that the person making the purchase has the card.
This is not the first time this issue raised concerns about Discovery Bank’s card security related to online purchases.
Six years ago, MyBroadband reported that one could type in any three digits for the CVV when buying something online with a Discovery Bank card, and the transaction would be approved.
At the time, Discovery Bank told MyBroadband that they detected the CVV issue a week prior, “and immediately started implementing a series of steps to correct the issue”.
“It has been fully resolved and has not led to ***** being experienced or our clients incurring any losses.”
Newsday asked Discovery Bank about the issue, which has also dogged the financial institution in the past.
Discovery Bank told Newsday that when in-app authentication is presented, they do not fail a transaction due to an incorrect CVV.
This is because Discovery Bank considers the in-app authentication to be stronger security than the CVV data.
“For Card Not Present transactions where in-app authentication is not requested, we do fail the transaction if the CVV is incorrect,” Discovery Bank added.
Testing Discovery Bank card security
Newsday, with the help of an independent software engineer and security expert, put Discovery Bank’s security to test through local and international online purchases.
We used a Discovery Bank card to make a small online purchase from Checkers Sixty60, one of South Africa’s most popular online shopping platforms.
When asked for the CVV, a **** “123” code was used, which took us to the next step, in app authorisation.
After approving the transaction in the Discovery Bank app, the transaction was approved, and the money went out of the account.
This supports the claim that they “do not fail a transaction due to an incorrect CVV,” because the bank considers “the in-app authentication stronger than the CVV data.”
Next, we placed an online order on Temu, the popular Chinese online shopping platform which has gained great support in South Africa.
We placed a R217 order, which required a CVV. Again, we used the incorrect “123” number. Immediately, it said that the payment was successful on the Temu site.
No in-app authentication was requested. However, we received multiple notifications that the payment was pending.
In a matter of 5 minutes, two notifications came through that the payment went through, and then the card was declined.
However, while Discovery said that the payment was declined, our bank balance told a different story.
On the app, the Temu payment, which never required in-app authentication, was pending for several hours until it was ultimately approved.
There was another R4.34 charge, which was taken off for international payments.
This test raises questions about Discovery Bank’s claim that card not present transactions, where the CVV number is incorrect, will fail.
In this test, no in-app authentication was requested, the wrong CVV was entered, and the transaction still went through.
The screenshots below show the tests conducted by Newsday regarding the Discovery Bank security vulnerability.
CVV authentication
GF
Gwen F's update01 Sept 2025, 13:35
Reviewer Update
Major South African bank has a serious security flawBy Seth ThorneIndependent tests revealed that Discovery Bank has a serious security vulnerability that could allow online purchases to go through without the correct CVV number.
Discovery Bank is South Africa’s premier new digital bank with 1.1 million clients and 2.5 million accounts, with between 1,300 and 1,400 new clients signing up each day.
However, it looks like these clients are now facing a significant security risk. Anonymous complaints submitted to Newsday pointed to weaknesses that were later confirmed through multiple tests.
These tests showed that transactions could be completed using incorrect CVV numbers, suggesting the bank may not be verifying this information during online purchases.
The card verification value (CVV) is the set of three digits printed on the back of the card which acts as a security measure when making payments online.
Entering the CVV is an important security feature as it ensures that the person making the purchase has the card.
This is not the first time this issue raised concerns about Discovery Bank’s card security related to online purchases.
Six years ago, MyBroadband reported that one could type in any three digits for the CVV when buying something online with a Discovery Bank card, and the transaction would be approved.
At the time, Discovery Bank told MyBroadband that they detected the CVV issue a week prior, “and immediately started implementing a series of steps to correct the issue”.
“It has been fully resolved and has not led to ***** being experienced or our clients incurring any losses.”
Newsday asked Discovery Bank about the issue, which has also dogged the financial institution in the past.
Discovery Bank told Newsday that when in-app authentication is presented, they do not fail a transaction due to an incorrect CVV.
This is because Discovery Bank considers the in-app authentication to be stronger security than the CVV data.
“For Card Not Present transactions where in-app authentication is not requested, we do fail the transaction if the CVV is incorrect,” Discovery Bank added.
Testing Discovery Bank card security
Newsday, with the help of an independent software engineer and security expert, put Discovery Bank’s security to test through local and international online purchases.
We used a Discovery Bank card to make a small online purchase from Checkers Sixty60, one of South Africa’s most popular online shopping platforms.
When asked for the CVV, a **** “123” code was used, which took us to the next step, in app authorisation.
After approving the transaction in the Discovery Bank app, the transaction was approved, and the money went out of the account.
This supports the claim that they “do not fail a transaction due to an incorrect CVV,” because the bank considers “the in-app authentication stronger than the CVV data.”
Next, we placed an online order on Temu, the popular Chinese online shopping platform which has gained great support in South Africa.
We placed a R217 order, which required a CVV. Again, we used the incorrect “123” number. Immediately, it said that the payment was successful on the Temu site.
No in-app authentication was requested. However, we received multiple notifications that the payment was pending.
In a matter of 5 minutes, two notifications came through that the payment went through, and then the card was declined.
However, while Discovery said that the payment was declined, our bank balance told a different story.
On the app, the Temu payment, which never required in-app authentication, was pending for several hours until it was ultimately approved.
There was another R4.34 charge, which was taken off for international payments.
This test raises questions about Discovery Bank’s claim that card not present transactions, where the CVV number is incorrect, will fail.
In this test, no in-app authentication was requested, the wrong CVV was entered, and the transaction still went through.
The screenshots below show the tests conducted by Newsday regarding the Discovery Bank security vulnerability.
CVV authentication
Discovery Bank is South Africa’s premier new digital bank with 1.1 million clients and 2.5 million accounts, with between 1,300 and 1,400 new clients signing up each day.
However, it looks like these clients are now facing a significant security risk. Anonymous complaints submitted to Newsday pointed to weaknesses that were later confirmed through multiple tests.
These tests showed that transactions could be completed using incorrect CVV numbers, suggesting the bank may not be verifying this information during online purchases.
The card verification value (CVV) is the set of three digits printed on the back of the card which acts as a security measure when making payments online.
Entering the CVV is an important security feature as it ensures that the person making the purchase has the card.
This is not the first time this issue raised concerns about Discovery Bank’s card security related to online purchases.
Six years ago, MyBroadband reported that one could type in any three digits for the CVV when buying something online with a Discovery Bank card, and the transaction would be approved.
At the time, Discovery Bank told MyBroadband that they detected the CVV issue a week prior, “and immediately started implementing a series of steps to correct the issue”.
“It has been fully resolved and has not led to ***** being experienced or our clients incurring any losses.”
Newsday asked Discovery Bank about the issue, which has also dogged the financial institution in the past.
Discovery Bank told Newsday that when in-app authentication is presented, they do not fail a transaction due to an incorrect CVV.
This is because Discovery Bank considers the in-app authentication to be stronger security than the CVV data.
“For Card Not Present transactions where in-app authentication is not requested, we do fail the transaction if the CVV is incorrect,” Discovery Bank added.
Testing Discovery Bank card security
Newsday, with the help of an independent software engineer and security expert, put Discovery Bank’s security to test through local and international online purchases.
We used a Discovery Bank card to make a small online purchase from Checkers Sixty60, one of South Africa’s most popular online shopping platforms.
When asked for the CVV, a **** “123” code was used, which took us to the next step, in app authorisation.
After approving the transaction in the Discovery Bank app, the transaction was approved, and the money went out of the account.
This supports the claim that they “do not fail a transaction due to an incorrect CVV,” because the bank considers “the in-app authentication stronger than the CVV data.”
Next, we placed an online order on Temu, the popular Chinese online shopping platform which has gained great support in South Africa.
We placed a R217 order, which required a CVV. Again, we used the incorrect “123” number. Immediately, it said that the payment was successful on the Temu site.
No in-app authentication was requested. However, we received multiple notifications that the payment was pending.
In a matter of 5 minutes, two notifications came through that the payment went through, and then the card was declined.
However, while Discovery said that the payment was declined, our bank balance told a different story.
On the app, the Temu payment, which never required in-app authentication, was pending for several hours until it was ultimately approved.
There was another R4.34 charge, which was taken off for international payments.
This test raises questions about Discovery Bank’s claim that card not present transactions, where the CVV number is incorrect, will fail.
In this test, no in-app authentication was requested, the wrong CVV was entered, and the transaction still went through.
The screenshots below show the tests conducted by Newsday regarding the Discovery Bank security vulnerability.
CVV authentication