Card Scanner
PCI compliance during scanning is required for companies that deal with payment card information. VGS Collect SDK provides several card scan solutions for the Payment Card Industry to help protect your businesses and the sensitive information of your consumers. You can add one of the proposed card scanning solutions into your application.
BlinkCard - is an AI-driven credit card scanning solution The VGS card scanner module helps to integrate the scanner with VGSCollectSDK.
It's required to use only the Card Scan Modules listed here, which are audited by VGS PCI requirements.
CardScan (BlinkCard) module
You can add a card scanning solution to your application by adding android BlinkCard adapter.
It provides a fast and easy way to scan payment cards and import them to VGS Collect. This tutorial is aimed at helping you to adapt the BlinkCard SDK to the VGS Collect Android SDK.
NoteWe offer already existing solution for using BlinkCard and still stay in PCI scope. Please contact with BlinkCard team if you have any issues related to the core API of the card scanner.
See below for more information about how to integrate BlinkCard SDK into your app, and also check the latest release notes.
You can start by watching our step-by-step tutorial, in which you’ll find out how to make BlinkCard SDK a part of your Android app.
To see BlinkCard in action, check our demo app.
Pricing
BlinkCard The module is a paid integration. Please contact Microblink for more details.
Before you start
Using the BlinkCard API in your app requires a valid license. You can obtain a trial license by registering for Microblink dashboard. After registering, you will be able to generate a license for your app. The license is bound to the package name of your app, so please make sure you enter the correct package name when asked.
Requirements
VGS Collect configured in your app (vault ID + environment)
Valid BlinkCard license key from Microblink
App minimum SDK: 24
Step 1 - Add the dependency
Step 2 - Configure scan settings
Create scan settings with your BlinkCard license key:
Step 3 - Build the scan intent
Map your VGS Collect field names to the scanner. The adapter uses these to populate your fields after a successful scan:
All field name setters are optional — only configure the ones your form uses.
Step 4 - Launch the scanner
Step 5 - Handle the result
Forward the result to VGS Collect. The adapter automatically populates your bound fields:
On a successful scan, your VGS Collect fields are populated with tokenized card data. No raw card values are ever exposed to your app.
Error handling
The adapter handles all scanner errors internally. Your onActivityResult is always called regardless of outcome:
Card scanned successfully
Fields populated, RESULT_OK
User cancelled
Fields not populated, RESULT_CANCELED
License invalid or expired
Fields not populated, RESULT_OK, error logged
Card not recognised
Fields not populated, RESULT_OK, error logged
If your license is invalid, contact Microblink to verify or renew it.
Security
Scanned card data is never exposed to your app in raw form.
All values are routed through VGS Collect's secure tokenization pipeline.
The adapter does not log, store, or cache any sensitive card values.
Further information
For detailed setup, dependency information, and troubleshooting, refer to the README.
Last updated

