The first thing to do after your site is created is to determine which verification methods to use. If you need help with selecting methods contact support for further analysis.
After you determine your verification methods you can create a user to verify. The user then can visit Trust Swiftly to complete the verification.
You can be notified about completed verifications and review their information if you need detailed data.
Each verification method has its time and place to be used with a customer. Typically your team knows best when to require verification, or your fraud tool will identify risky customers. Instead of declining or refunding a transaction due to risk, we can require varying levels of verification. The below provides some example tips for a successful implementation of Trust Swiftly.
Communicating with Customers - Trust Swiftly allows you to customize most of the experience to your brand, so any interactions also look trustworthy to your customers. Adding your logo and customizing the SMS improves completions of verifications. It is important customers understand that your business partners with Trust Swiftly to perform the verifications for the safety of both parties. Some customers may ask why they need to do any verifications or think it is too much work. A link in your initial communication to a page on your website with FAQ () and details about the process can help alleviate non-compliance. (Can be a hidden page if you want to hide from some fraudsters) It can be useful to offer a less intensive alternate verification requirement if a customer refuses one type. If a customer refuses to do any verifications, it doesn't mean they are immediately a fraudster and should be handled case by case.
Example Communication Email -