Discord verification bot.
How it works?
The Svipe Verification Bot works in combination with the Svipe ID app to provide a fully automated and secure way for Discord guilds to verify the age of their users and avoid bots by linking a Discord account to a passport or ID card but without sharing any personal information.
This allows other guild members to know that a newly joining user is a human and not a bot swarm, as well as being confident that the ones they are interacting with online aren’t underage, while allowing all users to remain anonymous in Discord.
If you have any questions, join our discord server, we would love to answer them.
Step 1: Invite the bot
Just click the invite link.
The bot will request these 3 permissions:
The two first ones are essential and the bot will not function properly without them.
The last one is optional and allows the bot automatic configuration function to work properly. Although not recommended, you can opt-out from this permission but then step 2 below cannot be skipped.
The bot also requires the server member intent, i.e. it needs to be able to list your users and their roles. However, it does not use the presence or message content intent, i.e. it cannot read messages on your server and cannot monitor online presence of your users.
Step 2 (optional): Configure the bot
This section is targeted at experienced discord guild owners who are migrating from another user verification/age verification method. For newly started guild owners or guilds with no previous user verification mechanisms, we highly recommend going directly to step 3 and utilize our auto-configuration system.
Use the slash-command /configure to configure your bot.
/configure alone will show your current bot configuration and contextual help.
If you have opted to remove the manage channel permission, you must configure an existing channel for the log_channel parameter AND the bot needs to be invited to it and have write permission to it. Enabling the bot will fail otherwise.
If you want to configure already existing roles for the bot to use for the verified and 18+ users, the roles must be “below” the Svipe verification bot role (see example below). The bot can only manage the roles below itself, not the ones above.
When you are satisfied with the configuration, do /configure command:enable to start using the bot. This will auto-create missing channels or roles and verify required permissions. Upon success, the bot will be enabled for your guild. In case of errors, the bot will notify you and suggest possible actions to fix the issues encountered.
Step 3: Post an invitation to verify
The invitation message can be customized using /post_invitation invite_message:<Message of your choice, to be displayed as a Discord embed>
You can post as many invitations as you like, each one with its own custom message.
Posting an invitation also automatically enables the bot in case it wasn’t enabled before.
Important note: the bot must have permission to send messages to the channel where you want to post the invitation. Otherwise, the bot will not be able to post the invitation.
Step 4: Configure your server
It is now up to you to configure access to your channels based on the verification status of the users. The meaning of the roles are as follows:
Role in parameter role_verified: the user has verified with SvipeID using a valid ICAO 9303 government issued document (i.e. typically a passport, but also many national ID cards and residence permits). This means that the discord account is now associated with a well defined “real human”, yet the identity behind the account cannot be retrieved.
Role in parameter role_18plus: in addition to having verified with SvipeID, the user has accepted to share his or her birth date with bot and the bot has confirmed this person is 18 years old or older. Absence of the 18plus role however does not necessarily imply that the user is underage as the user may simply have decided not to share his or her birth date
FAQ for admins
This is indeed tricky as a user could ask a friend to scan the QR code during the verification and can indeed happen. The situation is however the same for any kind of age verification, online or even in the real world, including a teenager asking an older friend to buy beer for him ;-)
To mitigate this, we have set limits so that a given document can verify at most one Discord account.
That account can then use the Svipe ID to verify again as many times as the users wish, on as many guilds as they want — but that Svipe ID cannot verify another Discord account.
We have also implemented age roll-back protection: if an account has been verified once with age x, it can never be verified again with a lower age. This means that by asking an older friend to do a verification, the user will essentially destroy his or her own ability to do future verifications for this account.
In case of doubts about the verification of one particular user, we recommend the admin to simply delete the roles from that user and suggest a new verification. While the first verification with Svipe ID requires scanning the document, a re-verification only takes seconds for a legit user, and is extremely cumbersome if the user indeed asked someone else.
Svipe ID requires a phone with NFC and a ICAO 9303 document (issued by 140+ countries). Without this, a user cannot verify with the Svipe verification bot.
However, you as a guild admin, are always the one taking the final decision and you can at any time overpower the bot and manually verify a user by assigning the corresponding roles.
Nope. We do not keep track of this. As soon as a user has verified and the roles are assigned, the bot forgets everything about this.
The log_channel is meant to be a channel for you to keep an audit log of everything that has happened on your guild.
If this is not sufficient for your needs, we’d be more than happy to hear about your use case and we can certainly find a solution!
We’d love to hear about your use case!
The free version of the bot will be limited to “verified” and “18+”, but we are planning on
Offering a lot more features in an upcoming premium version.
Take a look at our developper page to check what verified information Svipe can offer: https://developer.svipe.com/documentation#/oidc?id=scopes . The discord bot can access and use any of this for verification purposes (assuming the user consents sharing the data).
FAQ for users
Unfortunately, there are currently no automated ways of doing this at this point. We recommend you try to recover your original account using means available on Discord.
We might introduce a mechanism to allow re-assigning account verifications at some point in the future. You may also contact us directly through the Svipe discord server for assistance.
You can have the Svipe ID app on multiple devices. Just onboard on each device using the same identity document.
Multiple devices identified with one document share the same SvipeID — so you can definitely use another device to verify.
Verifying an account with multiple SvipeIDs would typically mean that several persons are using the same Discord account. While this could technically work, we do not currently see a clear use case for it and have disabled this possibility.
However, we’d be glad to hear from you if you have a valid use-case for such a feature and can enable it in a future release if we believe it could be useful.
Have you maybe asked someone else to verify your account for you at some point in time ? ;-) Our algorithms are monitoring this and your account has now been blocked from any further verifications.
Algorithmic mistakes happen - so if you see this message while having acted in good faith, please contact us, we will investigate this and gladly help you.
Have you tried to cheat ? Then sorry - your discord account and the SvipeID used to verify it are irremediably blocked from further verifications.
Then you cannot use the Svipe verification bot. Svipe ID does not allow any identification method lower than cryptographic verification through NFC.
Contact an admin of the guild you want to be verified on. They may or may not propose alternative ways to verify yourself. The guild admins are always the ones to take the final decision and may allow for lower level of security on their server.