Platforms
Once you've decided to adopt BlinkCard into your payment card workflow, you'll need to choose the integration option that best suits your business needs.
Right now, those include:
-
A native integration with your mobile app
-
A cross-platform integration with your mobile app (ReactNative, Cordova, Flutter and Capacitor)
-
A browser-based integration with your website or web app
-
An API integration on your own infrastructure or Microblink's Cloud
Let’s take a closer look at some technical information each of these options entails:
PLATFORM | MOBILE | WEB | |||
---|---|---|---|---|---|
Solution | Native SDKs | Cross-platform SDKs | In-browser SDK | Self-hosted API | |
File size | <10MB, compressed | <10MB, compressed | ~11MB, compressed | None (no change to the end user) | |
Processing | Client-side | Client-side | Client-side | Server-side | |
Version upgrades | Requires SDK & app update | Requires SDK & app update | Requires SDK & app update | Requires container update | |
Skillset needed | iOS or Android development (Objective-C, Swift, Java, Kotlin) | Mobile cross-platform development (JavaScript, TypeScript, Dart, C#) | Frontend development (JavaScript, TypeScript) | Backend development (any framework compatible with REST) & DevOps (Docker, Kubernetes) | |
User interface | Built-in, customizable | Built-in, localized | Built-in, customizable | Absent, available | |
Estimated integration time | One day* | Two days* | One day* | Two weeks |
*Using a default UI. Customizing the UI requires additional development time, depending on the scope of changes you wish to make.
Start building
Now that you have a better understanding of the platforms BlinkCard is available on, you can get started with an integration that best fits your needs.
To do so, you'll need a license. That license will allow you to unlock the SDK in your mobile or web application. More information is available in the next section on Licensing, however, we recommend creating a free account at developer.microblink.com where your licenses will be managed.
Next, it will be necessary to determine if you'll be using Microblink's user experience or building your own. Our's is the result of extensive user testing and there are vast customization options available.
During the integration, it's critical to follow the best practices. These tips will ensure you achieve optimal success rates using the solution and offer the best experience possible.
Finally, every use case and business is unique. To accommodate such diversity there are a variety of settings and configurations available. We cover the common ones in these documents but for an exhaustive list, refer to the relevant platform's technical docs.