Android Integration Guide

Importing DyScan
The easiest way to integrate DyScan is by using our Nexus repository, which is covered in this guide.
If you would rather include DyScan directly as a library, see the instructions here.
In the project-level build.gradle add the Dyneti Maven repository (credentials provided during integration):
1
allprojects {
2
    repositories {
3
        // Other repositories are here
4
        maven {
5
            credentials  {
6
                username = "nexusUsername"
7
                password = "nexusPassword"
8
            }
9
            url "https://nexus.dyneti.com/repository/maven-releases/"
10
            authentication {
11
                basic(BasicAuthentication)
12
            }
13
        }
14
    }
15
}
Copied!
In the app-level build.gradle add the dependency:
1
dependencies {
2
    // Other dependencies are here
3
    implementation 'com.dyneti.android.dyscan:dyscan:1.1.6'
4
}
Copied!
If you would rather integrate without using our Nexus repository, see Manually Importing the Library.
Initializing DyScan (only for version 1.1.0 and up)
In your Application class add the following line to init DyScan.
1
public class DyScanApplication extends Application {
2
​
3
  //...
4
​
5
  @Override
6
  public void onCreate() {
7
    super.onCreate();
8
    //...
9
    DyScan.init(this, "{YOUR_API_KEY}");
10
    //...
11
  }
12
}
Copied!
Camera features support
By default, DyScan uses uses-feature tags in its AndroidManifest.xml file to filter out devices that don't support the required camera features. This filtering affects the host app's supported device count in Google Play.
You can override this filtering by adding the below lines into your AndroidManifest.xml manifest tag section:
1
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
2
    xmlns:tools="http://schemas.android.com/tools">
3
    ...
4
​
5
    <uses-feature android:name="android.hardware.camera" android:required="false" tools:replace="required" />
6
    <uses-feature android:name="android.hardware.camera.autofocus" android:required="false" tools:replace="required" />
7
​
8
    ...
9
</manifest>
Copied!
If you choose to override the default tags settings inAndroidManifest.xml, you should additionally check manually if the device is supported before calling DyScan functions to avoid a bad user experience (see below).
1
if (DyScan.isDeviceSupported(context)) {
2
    // open DyScanActivity
3
    Intent intent = new Intent(context, DyScanActivity.class);
4
    startActivityForResult(intent, SCAN_REQUEST_CODE);
5
} else {
6
    // alternate flow if device is not supported
7
}
Copied!
Interfacing DyScan
If your app already has card.io, see the migrating from card.io guide.
Import the following DyScan classes in your Activity that will launch DyScan:
1
import com.dyneti.android.dyscan.DyScanActivity;
2
import com.dyneti.android.dyscan.CreditCard;
Copied!
This example assumes that you're going to launch the scanner from a button, and that you've set the button's onClick handler in the layout XML via android:onClick="onScanPress". (If not, the process is analogous, just use the code inside this function). onScanPress is implemented as
1
public void onScanPress(View v) {
2
    Intent scanIntent = new Intent(this, DyScanActivity.class);
3
​
4
    // for version lower than 1.1.0
5
    scanIntent.putExtra(DyScanActivity.EXTRA_API_KEY, "{api_key_string}");
6
    
7
    // MY_SCAN_REQUEST_CODE (e.g., 1337) is arbitrary and is only used within this activity.
8
    startActivityForResult(scanIntent, MY_SCAN_REQUEST_CODE);
9
}
Copied!
Next, override onActivityResult() to get the scan result.
1
@Override
2
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
3
   super.onActivityResult(requestCode, resultCode, data);
4
​
5
   if (requestCode == MY_SCAN_REQUEST_CODE) {
6
       if (data != null && data.hasExtra(DyScanActivity.EXTRA_SCAN_RESULT)) {
7
           CreditCard scanResult = data.getParcelableExtra(DyScanActivity.EXTRA_SCAN_RESULT);
8
           // Do stuff with results in scanResult 
9
       }
10
   }
11
}
Copied!
If you are using Stripe, see this guide for how to implement these functions.
The CreditCard class contains fields String cardNumber, int expiryMonth, int expiryYear, and boolean isFraud. Note that isFraud is currently always set to false, and expiryYear is the full four-digit year.
Customizing DyScanActivity
The DyScanActivity can be customized by passing EXTRAs along with the intent. This allows you to modify both the appearance and behavior of the Activity.
EXTRA
Description
Default Value
EXTRA_HELPER_TEXT_STRING
What to text to display to the user to guide them in scanning their card. It is highly recommended that you set this value; otherwise we will try to provide this text based on EXTRA_LANGUAGE.
Dependent on EXTRA_LANGUAGE
EXTRA_HELPER_TEXT_COLOR
The color to use to display the helper text.
Color.WHITE
EXTRA_HELPER_TEXT_SIZE_SP
The size of the helper text in sp unit.
18
EXTRA_HELPER_TEXT_FONT_FAMILY
The font family name of the helper text. The font needs to be placed in assets first.
Default font
EXTRA_SHOW_HELPER_TEXT
Whether to show the helper text on screen.
true
EXTRA_SHOW_CORNERS
Whether to show the scan area outline
true
EXTRA_CORNER_THICKNESS
How thick to make the lines outlining the scan area, indicating to the user where to place their credit card. Input as a float.
15f
EXTRA_CORNER_INACTIVE_COLOR
The color to use in drawing the outline of the scan region when nothing of interest is detected.
Color.GRAY
EXTRA_CORNER_ACTIVE_COLOR
The color to use in drawing the outline of the scan region when corners are detected.
Color.CYAN
EXTRA_CORNER_COMPLETED_COLOR
The color to use in drawing the outline of the scan region when we have successfully scanned a card.
Color.GREEN
EXTRA_BACKGROUND_COLOR
The color to use to obscure everything outside the scan region in order to draw the user’s attention to the scan region.
Color.GRAY
EXTRA_BACKGROUND_OPACITY
The opacity to use when obscuring everything outside the scan region, as an integer ranging from 0 (transparent) to 255 (opaque).
115
EXTRA_SHOW_ROTATE_BUTTON
Whether to show the button which allows the user to rotate the scan region by 90 degrees, facilitating the scanning of vertical cards. 
false
EXTRA_SHOW_MANUAL_ENTRY_BUTTON
Whether to show a button at the bottom of the screen allowing the user to choose to exit the scanning Activity. 
false
EXTRA_MANUAL_ENTRY_STRING
The String to display on the manual entry button if shown. This should be set if you are showing the manual entry button.
​
EXTRA_SHOW_RESULT_OVERLAY
Whether to briefly show the scanned card number (and date, if present) as an overlay over the screen after a successful scan.
false
EXTRA_RESULT_OVERLAY_ALWAYS_HORIZONTAL
Whether to display number on completion horizontally in fixed position.
false
EXTRA_SHOW_DYNETI_LOGO
Whether to show a dark blue Dyneti logo and wordmark above the scan region.
true
EXTRA_SHOW_CARD_OVERLAY
Whether to show the overlay displaying a sample card number and expiration date hinting at the user to place their card in the scan region.
true
​
If you want to have more control over the experience than DyScanActivity provides, we also offer a DyScanView. 
​

iOS Integration Guide

React Native Integration Guide

Last modified 2mo ago

Copy link

Contents

Importing DyScan

Initializing DyScan (only for version 1.1.0 and up)

Camera features support

Interfacing DyScan

Customizing DyScanActivity