Choose an Integration Option
Selecting the right integration option for your application depends on your app framework and the channels you use to deliver services to your customers. Explore and choose an integration approach that best aligns with your business's needs and requirements.
Mobile
Web / Mobile Web
Server to Server
REST API
No Code Options
SmartCheck™
SmartCheck™ allows for direct verification from your browser without any coding. This option enables easy verification job runs:
Convenience: Directly perform verifications through the Smile ID Dashboard.
No Code Required: Perfect for non-technical users, offering a simple way to verify identities.
Comprehensive Verification: Provides a suite of verification services, including ID checks and biometrics, from the dashboard.
Smile Links provides a no-code solution for businesses aiming to simplify the user verification process without the need for complex code integration. It allows for the creation of customizable verification flows shared via secure links.
Features of Smile Links:
Ease of Use: Easily generate verification links from the Smile ID Portal.
Customization: Customize the verification interface with your company branding for a consistent, professional user experience.
Flexibility: Supports multiple ID types and verification methods in a single link, accommodating a wide range of verification needs.
Efficiency: Smoothly track and manage your Smile Links through the Smile ID Portal for a seamless verification process.
Available Products via Each Integration Option
Mobile
Yes
Yes
Yes
Yes
REST API
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Server-to-Server
Yes
Yes
Yes
Yes
Yes
Yes
SmartCheck™
Yes
Yes
Yes
Yes
Yes
Yes
Smile Links
Yes
Yes
Yes
Web/Mobile Web
Yes
Yes
Yes
Yes
Asynchronous vs. Synchronous
When integrating with Smile ID using the Basic KYC, Enhanced KYC, or KYB (Know Your Business), developers have the flexibility to utilize either an Asynchronous or a Synchronous endpoint for each product. The choice between these two endpoints depends largely on the specific requirements of the application, particularly concerning real-time processing and resilience to ID authority availability.
Asynchronous Endpoint: Reliability and Scalability for High-Volume Operations
The Asynchronous endpoint is engineered to provide a guaranteed eventual response, a critical feature for applications where immediate, real-time feedback is not strictly necessary but reliable completion of the verification process is paramount. This endpoint is particularly robust in scenarios where ID authorities (external data custodians that hold user ID information) may experience temporary unavailability or delays. The Asynchronous endpoint queues the request and retries it for a maximum of 4 times before giving up.
Given its inherent reliability and ability to handle delayed responses gracefully, the Asynchronous endpoint is highly recommended for high-volume applications. These include platforms that process a large number of verification requests per minute. For these applications, the ability to scale without being bottlenecked by immediate ID authority responses is invaluable. When utilizing Smile ID product Asynchronous endpoints, it is mandatory to include a callback URL in your request. This callback URL serves as the destination for Smile ID to send the verification response once it's available, allowing your application to receive and process the results efficiently without constantly polling for updates.
Synchronous Endpoint: Real-Time Verification for Immediate User Experiences
The Synchronous endpoint is designed for real-time environments where an immediate response is crucial for the user experience. This is common in mobile applications or web interfaces where a user is actively waiting for a verification outcome before proceeding with their interaction.
However, a key characteristic of the Synchronous API is that it does not guarantee a response in the event that the underlying ID authority is unavailable. If the ID authority cannot be reached or is experiencing issues at the moment of the request, the Synchronous API will likely return an error or a timeout after a maximum of 30 seconds, informing the application that the verification could not be completed at that specific time. This limitation means that applications relying on the Synchronous endpoint must implement appropriate error handling, fallback mechanisms or status check polling to manage scenarios where an immediate verification is not possible.
Last updated
Was this helpful?