# Sms verification
**URL:** https://meta.discourse.org/t/sms-verification/135060
**Category:** Feature
**Created:** [December 4, 2019, 1:03pm UTC](https://meta.discourse.org/t/sms-verification/135060 "2019-12-04T13:03:16Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@Bingo](https://meta.discourse.org/u/Bingo)
#### Post date: [December 4, 2019, 1:03pm UTC](https://meta.discourse.org/t/sms-verification/135060/1 "2019-12-04T13:03:16Z")
Hello,
I’m not able to find any plugin for user verification with sms/call but I’ve seen it on some discourse based forums
---
### Author:  [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [December 4, 2019, 3:28pm UTC](https://meta.discourse.org/t/sms-verification/135060/2 "2019-12-04T15:28:07Z")
My guess would be that they’re using their own login provider as an SSO method for Discourse… so that verification is happening outside of Discourse.
Note that SMS isn’t generally considered secure due to sim swap attacks.
> **[SIM swap attack](https://en.wikipedia.org/wiki/SIM_swap_scam)**
>
> A SIM swap attack (also known as port-out scam, SIM splitting, simjacking, and SIM swapping) is a type of account takeover fraud that generally targets a weakness in two-factor authentication and two-step verification in which the second factor or step is a text message (SMS) or call placed to a mobile telephone.
> The fraud exploits a mobile phone service provider's ability to seamlessly port a phone number to a device containing a different subscriber identity module (SIM). This mobile number po...
---
### Author:  [@Bingo](https://meta.discourse.org/u/Bingo)
#### Post date: [December 4, 2019, 3:29pm UTC](https://meta.discourse.org/t/sms-verification/135060/3 "2019-12-04T15:29:53Z")
Please check [swapd.co](http://swapd.co) they are using it I want to use the same
---
### Author:  [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [December 4, 2019, 3:48pm UTC](https://meta.discourse.org/t/sms-verification/135060/4 "2019-12-04T15:48:10Z")
Thanks for the link. It appears they built a custom plugin for their site to verify users with Twilio’s sms service. As far as I know this isn’t a publicly available plugin.
---
### Author:  [@Bingo](https://meta.discourse.org/u/Bingo)
#### Post date: [December 5, 2019, 1:37am UTC](https://meta.discourse.org/t/sms-verification/135060/5 "2019-12-05T01:37:42Z")
Can you suggest another verification than sms to verify client is legit
---
### Author:  [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [December 5, 2019, 1:49am UTC](https://meta.discourse.org/t/sms-verification/135060/6 "2019-12-05T01:49:58Z")
What do you mean by legit? I guess I need more information on what you’re trying to achieve through verification.
Are you trying to make creating new accounts more difficult for spammers/attackers? Are you trying to make individual accounts more secure (Discourse has 2-factor authentication built-in)?
---
### Author:  [@Bingo](https://meta.discourse.org/u/Bingo)
#### Post date: [December 5, 2019, 1:55am UTC](https://meta.discourse.org/t/sms-verification/135060/7 "2019-12-05T01:55:57Z")
Yes I want to make difficult to sign up for spammers
---
### Author:  [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [December 5, 2019, 2:11am UTC](https://meta.discourse.org/t/sms-verification/135060/8 "2019-12-05T02:11:47Z")
Are you doing this for an existing forum, or for a new one?
I ask because Discourse already has a lot of protections in place to make things more annoying for spammers. So if you’re starting a new site you may find that you don’t need additional verification.
For example, you can restrict permissions on new users so they can’t post links or images until they’ve used the site for a little while. You also have the option to configure [Akismet](https://meta.discourse.org/t/discourse-akismet-anti-spam/109337) for your forum, which will scan all new posts and user bios for spam, and automatically flag possible spam posts for review.
There’s also a third-party plugin that integrates with [Stop Forum Spam](https://www.stopforumspam.com/)
> [@Stop Forum Spam Plugin](https://meta.discourse.org/t/stop-forum-spam-plugin-auto-silence-known-spammers/121037):
>
> Overview The [Stop Forum Spam plugin](https://github.com/singerscreations/discourse-stopforumspam) (unofficial) can help weed out human spammers who are able to bypass Discourse’s built-in spam tools (thanks to their awesome human powers). Right after a new user signs up on your forum (before they have time to post), this plugin will check the user’s email address, forum username, and/or IP address (depending on your plugin settings) against the [Stop Forum Spam](https://www.stopforumspam.com/) database. If the user is found in this database of known spammers, their user account will be imm…
---
### Author:  [@Bingo](https://meta.discourse.org/u/Bingo)
#### Post date: [December 5, 2019, 2:15am UTC](https://meta.discourse.org/t/sms-verification/135060/9 "2019-12-05T02:15:16Z")
Actually I want to create paid membership forum where user have to pay to create account and must needed to verified that the user is 100% real and legit not spammer
Can you suggest on this?
I’m sorry for this questions but I’m new with discourse
---
### Author:  [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [December 5, 2019, 2:23am UTC](https://meta.discourse.org/t/sms-verification/135060/10 "2019-12-05T02:23:22Z")
Oh I see, There are a couple of options that allow you to take payment and associate it with forum membership.
- You can [integrate with Memberful](https://memberful.com/help/third-party-integrations/discourse/)
- Use the Patreon plugin: [Discourse Patreon](https://meta.discourse.org/t/discourse-patreon-integration/44366)
- Or you could set up a Wordpress site to take payments via a Wordpress plugin and manage users that way: [Manage group membership in Discourse with WP Discourse SSO](https://meta.discourse.org/t/managing-discourse-group-membership-with-wp-discourse/74724)
We’re planning to add a way to accept payments within Discourse directly in the future, but don’t have an exact date yet.