Mixing
Showing “this is secure†on credit card entry screen
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
2
down vote
favorite
Should I show some sort of "this site is secure" puffery (e.g. lock image, or some brief "this site is secure" boilerplate) on my credit card payment screen? If so, what should it look like? If not, why not?
I do want my customers to feel confident (as well as actually be safe) if they choose to enter their credit card details to pay my clients. I also want them to learn a healthy cynicism. Most of my customers are likely to have a very low level of technical knowledge about internet security and are usually either too trusting, and (in some cases) too suspicious of the wrong things.
I even had a customer call me up saying he wasn't sure if my payment page was secure because it didn't have any "padlock" image within the page. (yes, the page had a valid ssl certificate, the customer had the correct URL, and his version of Chrome was showing it with the green padlock with the "Secure" label at the time - after pointing this out he was happy to proceed).
I just feel it's a bit strange to splash a "this is secure" badge on a page because I know it means nothing, technically - because a phishing page would just as easily show the exact same badge.
Assumption: that my site is actually secure (let's just say I've tried my best and will continue to improve as much as possible).
For reference, here is the page as it currently stands:
Here's a mockup of what I mean:
security
asked 3 hours ago
Jeffrey Kemp
1155
New contributor
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
favorite
Should I show some sort of "this site is secure" puffery (e.g. lock image, or some brief "this site is secure" boilerplate) on my credit card payment screen? If so, what should it look like? If not, why not?
I do want my customers to feel confident (as well as actually be safe) if they choose to enter their credit card details to pay my clients. I also want them to learn a healthy cynicism. Most of my customers are likely to have a very low level of technical knowledge about internet security and are usually either too trusting, and (in some cases) too suspicious of the wrong things.
I even had a customer call me up saying he wasn't sure if my payment page was secure because it didn't have any "padlock" image within the page. (yes, the page had a valid ssl certificate, the customer had the correct URL, and his version of Chrome was showing it with the green padlock with the "Secure" label at the time - after pointing this out he was happy to proceed).
I just feel it's a bit strange to splash a "this is secure" badge on a page because I know it means nothing, technically - because a phishing page would just as easily show the exact same badge.
Assumption: that my site is actually secure (let's just say I've tried my best and will continue to improve as much as possible).
For reference, here is the page as it currently stands:
Here's a mockup of what I mean:
security
asked 3 hours ago
Jeffrey Kemp
1155
New contributor
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Should I show some sort of "this site is secure" puffery (e.g. lock image, or some brief "this site is secure" boilerplate) on my credit card payment screen? If so, what should it look like? If not, why not?
I do want my customers to feel confident (as well as actually be safe) if they choose to enter their credit card details to pay my clients. I also want them to learn a healthy cynicism. Most of my customers are likely to have a very low level of technical knowledge about internet security and are usually either too trusting, and (in some cases) too suspicious of the wrong things.
I even had a customer call me up saying he wasn't sure if my payment page was secure because it didn't have any "padlock" image within the page. (yes, the page had a valid ssl certificate, the customer had the correct URL, and his version of Chrome was showing it with the green padlock with the "Secure" label at the time - after pointing this out he was happy to proceed).
I just feel it's a bit strange to splash a "this is secure" badge on a page because I know it means nothing, technically - because a phishing page would just as easily show the exact same badge.
Assumption: that my site is actually secure (let's just say I've tried my best and will continue to improve as much as possible).
For reference, here is the page as it currently stands:
Here's a mockup of what I mean:
security
asked 3 hours ago
Jeffrey Kemp
1155
New contributor
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Should I show some sort of "this site is secure" puffery (e.g. lock image, or some brief "this site is secure" boilerplate) on my credit card payment screen? If so, what should it look like? If not, why not?
I do want my customers to feel confident (as well as actually be safe) if they choose to enter their credit card details to pay my clients. I also want them to learn a healthy cynicism. Most of my customers are likely to have a very low level of technical knowledge about internet security and are usually either too trusting, and (in some cases) too suspicious of the wrong things.
I even had a customer call me up saying he wasn't sure if my payment page was secure because it didn't have any "padlock" image within the page. (yes, the page had a valid ssl certificate, the customer had the correct URL, and his version of Chrome was showing it with the green padlock with the "Secure" label at the time - after pointing this out he was happy to proceed).
I just feel it's a bit strange to splash a "this is secure" badge on a page because I know it means nothing, technically - because a phishing page would just as easily show the exact same badge.
Assumption: that my site is actually secure (let's just say I've tried my best and will continue to improve as much as possible).
For reference, here is the page as it currently stands:
Here's a mockup of what I mean:
security
security
asked 3 hours ago
Jeffrey Kemp
1155
New contributor
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 3 hours ago
Jeffrey Kemp
1155
New contributor
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 3 hours ago
Jeffrey Kemp
1155
New contributor
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 3 hours ago
Jeffrey Kemp
1155
asked 3 hours ago
Jeffrey Kemp
1155
1155
New contributor
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jeffrey Kemp is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
Funny thing, I just did the research on this recently, because we faced the same "issue" in our e-commerce shop.
There is a good Baymard article referencing exactly this:
Visually Reinforce the Credit Card Section
One method we consistently observe to perform well for increasing users’ perceived security of sensitive fields is to visually encapsulate them. This can be achieved simply by using borders, background colors, shading, and other visual styling that will make one part of the form seem more robust than the rest. Remember: this is about perceived security of the fields, not their actual technical security.
So what we ended up doing, as nonsensical as it sounds, is actually add the word "secure" to the payment headline and a little lock icon near the credit card input field.
Note: This could be perceived as manipulative (referencing your healthy cynicism point), but I would argue it is simply to calm the user, since the page itself is already technically robust.
You could also purchase a trust seal for your site, to give your users something to hold on to when judging the seriousness of your shop. The Baymard article references these too.
Since our shop is already quite known here and trusted we didn't feel the need for one in our case.
edited 1 hour ago
Jeffrey Kemp
1155
answered 3 hours ago
Big_Chair
1,0531723
Excellent, that's exactly the sort of information I was after.
– Jeffrey Kemp
2 hours ago
1
"In our 2016 tests we also included a completely “homemade / fake†seal not issued by a 3rd party, with no meaning whatsoever beyond the icon itself. Note how the homemade seal performed significantly better than the SSL seals issued by established vendors except Norton. This suggests that beyond strong brand reconizability, it doesn’t matter too much which actual seal is chosen. Rather what’s most important is making sure there’s some kind of visual seal or icon present to indicate the robustness of the credit card fields."
– Jeffrey Kemp
2 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Funny thing, I just did the research on this recently, because we faced the same "issue" in our e-commerce shop.
There is a good Baymard article referencing exactly this:
Visually Reinforce the Credit Card Section
One method we consistently observe to perform well for increasing users’ perceived security of sensitive fields is to visually encapsulate them. This can be achieved simply by using borders, background colors, shading, and other visual styling that will make one part of the form seem more robust than the rest. Remember: this is about perceived security of the fields, not their actual technical security.
So what we ended up doing, as nonsensical as it sounds, is actually add the word "secure" to the payment headline and a little lock icon near the credit card input field.
Note: This could be perceived as manipulative (referencing your healthy cynicism point), but I would argue it is simply to calm the user, since the page itself is already technically robust.
You could also purchase a trust seal for your site, to give your users something to hold on to when judging the seriousness of your shop. The Baymard article references these too.
Since our shop is already quite known here and trusted we didn't feel the need for one in our case.
edited 1 hour ago
Jeffrey Kemp
1155
answered 3 hours ago
Big_Chair
1,0531723
Excellent, that's exactly the sort of information I was after.
– Jeffrey Kemp
2 hours ago
1
"In our 2016 tests we also included a completely “homemade / fake†seal not issued by a 3rd party, with no meaning whatsoever beyond the icon itself. Note how the homemade seal performed significantly better than the SSL seals issued by established vendors except Norton. This suggests that beyond strong brand reconizability, it doesn’t matter too much which actual seal is chosen. Rather what’s most important is making sure there’s some kind of visual seal or icon present to indicate the robustness of the credit card fields."
– Jeffrey Kemp
2 hours ago
add a comment |Â
up vote
3
down vote
accepted
Funny thing, I just did the research on this recently, because we faced the same "issue" in our e-commerce shop.
There is a good Baymard article referencing exactly this:
Visually Reinforce the Credit Card Section
One method we consistently observe to perform well for increasing users’ perceived security of sensitive fields is to visually encapsulate them. This can be achieved simply by using borders, background colors, shading, and other visual styling that will make one part of the form seem more robust than the rest. Remember: this is about perceived security of the fields, not their actual technical security.
So what we ended up doing, as nonsensical as it sounds, is actually add the word "secure" to the payment headline and a little lock icon near the credit card input field.
Note: This could be perceived as manipulative (referencing your healthy cynicism point), but I would argue it is simply to calm the user, since the page itself is already technically robust.
You could also purchase a trust seal for your site, to give your users something to hold on to when judging the seriousness of your shop. The Baymard article references these too.
Since our shop is already quite known here and trusted we didn't feel the need for one in our case.
edited 1 hour ago
Jeffrey Kemp
1155
answered 3 hours ago
Big_Chair
1,0531723
Excellent, that's exactly the sort of information I was after.
– Jeffrey Kemp
2 hours ago
1
"In our 2016 tests we also included a completely “homemade / fake†seal not issued by a 3rd party, with no meaning whatsoever beyond the icon itself. Note how the homemade seal performed significantly better than the SSL seals issued by established vendors except Norton. This suggests that beyond strong brand reconizability, it doesn’t matter too much which actual seal is chosen. Rather what’s most important is making sure there’s some kind of visual seal or icon present to indicate the robustness of the credit card fields."
– Jeffrey Kemp
2 hours ago
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Funny thing, I just did the research on this recently, because we faced the same "issue" in our e-commerce shop.
There is a good Baymard article referencing exactly this:
Visually Reinforce the Credit Card Section
One method we consistently observe to perform well for increasing users’ perceived security of sensitive fields is to visually encapsulate them. This can be achieved simply by using borders, background colors, shading, and other visual styling that will make one part of the form seem more robust than the rest. Remember: this is about perceived security of the fields, not their actual technical security.
So what we ended up doing, as nonsensical as it sounds, is actually add the word "secure" to the payment headline and a little lock icon near the credit card input field.
Note: This could be perceived as manipulative (referencing your healthy cynicism point), but I would argue it is simply to calm the user, since the page itself is already technically robust.
You could also purchase a trust seal for your site, to give your users something to hold on to when judging the seriousness of your shop. The Baymard article references these too.
Since our shop is already quite known here and trusted we didn't feel the need for one in our case.
edited 1 hour ago
Jeffrey Kemp
1155
answered 3 hours ago
Big_Chair
1,0531723
Funny thing, I just did the research on this recently, because we faced the same "issue" in our e-commerce shop.
There is a good Baymard article referencing exactly this:
Visually Reinforce the Credit Card Section
One method we consistently observe to perform well for increasing users’ perceived security of sensitive fields is to visually encapsulate them. This can be achieved simply by using borders, background colors, shading, and other visual styling that will make one part of the form seem more robust than the rest. Remember: this is about perceived security of the fields, not their actual technical security.
So what we ended up doing, as nonsensical as it sounds, is actually add the word "secure" to the payment headline and a little lock icon near the credit card input field.
Note: This could be perceived as manipulative (referencing your healthy cynicism point), but I would argue it is simply to calm the user, since the page itself is already technically robust.
You could also purchase a trust seal for your site, to give your users something to hold on to when judging the seriousness of your shop. The Baymard article references these too.
Since our shop is already quite known here and trusted we didn't feel the need for one in our case.
edited 1 hour ago
Jeffrey Kemp
1155
answered 3 hours ago
Big_Chair
1,0531723
edited 1 hour ago
Jeffrey Kemp
1155
edited 1 hour ago
Jeffrey Kemp
1155
edited 1 hour ago
Jeffrey Kemp
1155
1155
answered 3 hours ago
Big_Chair
1,0531723
answered 3 hours ago
Big_Chair
1,0531723
answered 3 hours ago
Big_Chair
1,0531723
1,0531723
Excellent, that's exactly the sort of information I was after.
– Jeffrey Kemp
2 hours ago
1
"In our 2016 tests we also included a completely “homemade / fake†seal not issued by a 3rd party, with no meaning whatsoever beyond the icon itself. Note how the homemade seal performed significantly better than the SSL seals issued by established vendors except Norton. This suggests that beyond strong brand reconizability, it doesn’t matter too much which actual seal is chosen. Rather what’s most important is making sure there’s some kind of visual seal or icon present to indicate the robustness of the credit card fields."
– Jeffrey Kemp
2 hours ago
add a comment |Â
Excellent, that's exactly the sort of information I was after.
– Jeffrey Kemp
2 hours ago
1
"In our 2016 tests we also included a completely “homemade / fake†seal not issued by a 3rd party, with no meaning whatsoever beyond the icon itself. Note how the homemade seal performed significantly better than the SSL seals issued by established vendors except Norton. This suggests that beyond strong brand reconizability, it doesn’t matter too much which actual seal is chosen. Rather what’s most important is making sure there’s some kind of visual seal or icon present to indicate the robustness of the credit card fields."
– Jeffrey Kemp
2 hours ago
Excellent, that's exactly the sort of information I was after.
– Jeffrey Kemp
2 hours ago
Excellent, that's exactly the sort of information I was after.
– Jeffrey Kemp
2 hours ago
1
1
"In our 2016 tests we also included a completely “homemade / fake†seal not issued by a 3rd party, with no meaning whatsoever beyond the icon itself. Note how the homemade seal performed significantly better than the SSL seals issued by established vendors except Norton. This suggests that beyond strong brand reconizability, it doesn’t matter too much which actual seal is chosen. Rather what’s most important is making sure there’s some kind of visual seal or icon present to indicate the robustness of the credit card fields."
– Jeffrey Kemp
2 hours ago
"In our 2016 tests we also included a completely “homemade / fake†seal not issued by a 3rd party, with no meaning whatsoever beyond the icon itself. Note how the homemade seal performed significantly better than the SSL seals issued by established vendors except Norton. This suggests that beyond strong brand reconizability, it doesn’t matter too much which actual seal is chosen. Rather what’s most important is making sure there’s some kind of visual seal or icon present to indicate the robustness of the credit card fields."
– Jeffrey Kemp
2 hours ago
add a comment |Â
Jeffrey Kemp is a new contributor. Be nice, and check out our Code of Conduct.
Jeffrey Kemp is a new contributor. Be nice, and check out our Code of Conduct.
Jeffrey Kemp is a new contributor. Be nice, and check out our Code of Conduct.
Jeffrey Kemp is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f120993%2fshowing-this-is-secure-on-credit-card-entry-screen%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
