iOS Integration Guide

Importing DyScan

The easiest way to integrate DyScan is by using CocoaPods, which is covered in this guide.

If you would rather include DyScan directly as a framework, see the instructions here. If you use Carthage as your dependency manager, see the instructions here. If you use Swift Package Manager, see the instructions here.

Follow the instructions below corresponding with your DyScan version to access the necessary repositories.

After getting the access token for Dyneti's repo access, open up your Podfile and above the target add this line:

source ''

Later when asked for a password for user "dyscan", paste the access token that we provided.

Then, inside the target with the other dependencies, add the appropriate line below for your specific version of Swift. If you are unsure what Swift version you are using, use Universal variant.

pod 'DyScan'

Include use_frameworks! in your Podfile if you have not done so already (see here for a sample Podfile). Then in a terminal in the directory of your iOS project, run

$ pod install

If 2FA is set up on your GitHub account, this step may fail. To rectify this, you will need to generate a personal access token in GitHub. This can be done by logging into GitHub and following the directions by navigating to Settings > Developer settings > Personal access tokens.

If your app does not already ask for camera permissions, add the key “NSCameraUsageDescription” (Privacy - Camera Usage Description) to your app's Info.plist file. You should set the value to be the string a user sees when they are prompted for the camera permission (e.g. To scan credit cards).

If you are getting an error like dyld: Library not loaded: @rpath/DyScan.framework/DyScan CocoaPods probably has not configured the dependency properly. In Pods/Target Support Files/Pods-{Project}/Pods-{Project} add the line install_framework "${PODS_ROOT}/DyScan/Swift5_1/DyScan.framework" in both the debug and release configurations (you should see many other similar lines). In "Embed Pods Frameworks" in your project's build phases, add ${PODS_ROOT}/DyScan/Swift5_1/DyScan.framework as an input path.

Initializing DyScan (only for version 1.1.1 and up)

In your AppDelegate add import DyScan and the following line to configure DyScan.

class AppDelegate: UIResponder, UIApplicationDelegate {
    internal func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        DyScanApp.configure(apiKey: "{YOUR API KEY}")
        return true

Interfacing DyScan

If your app already has, see the migrating from guide.

DyScan can be used in two ways:

  • As a view controller: Quick and easy. Create a view controller that is presented modally. The DyScan view controller handles all aspects of the UX. We currently support two view controllers. One is intended for when DyScan is optionally accessed from a checkout form. The other is intended for when DyScan is the default method of entering payment information, and provides an option to enter numbers manually instead.

  • As a view: More flexible. Create a DyScanView to do card scanning only and manage everything else yourself. This enables a broader range of presentations, such as in-place transitions, but requires that you handle the rest of the UI yourself.

Regardless of which methodology you use, the failure callback will provide a reason for why scanning was not successful. You do not have to use this value (for example you could always go to manual entry on any failure), but this gives you the opportunity to react differently based on the reason, for example by requesting the user to enable the permissions. The possible values are:




There was an issue with the API key. Make sure that the API key has been set prior to calling prepare.


The camera setup has failed. For example, there might not be any cameras available for use at the time.


The user has not granted the app permissions to open the camera, so we have no way of proceeding with the scan.


The user chose to exit.

import DyScan in the file that contains the view controller that will instantiate DyScan. In your app, create an extension for your view controller that conforms to DyScanViewControllerDelegate. This will require you to implement two functions, onFailure, and onSuccess. onFailure is called whenever a scan event is unsuccessful (for any reason, including the user choosing to cancel).

Optionally, you can implement the function onProgressUpdate to access information about the card being scanned while the scan is ongoing (available for version 1.2.9 of DyScan and up). The DyScanProgressUpdate class has two attributes (both of string type): lastFourDigits and network, which correspond to the last four digits and network of the credit card (e.g., Visa or Mastercard) being scanned, respectively. You may choose to surface this information to your users to give them more feedback as they are waiting for their card to scan.

extension ExampleViewController: DyScanViewControllerDelegate{
    func onFailure(_ paymentViewController: DyScanViewController!, reason: DyScanExitReason) {
        paymentViewController.dismiss(animated: true, completion: nil)
        // Implement functionality for failure cases
    func onSuccess(_ cardInfo: DyScanCreditCardInfo!, in paymentViewController: DyScanViewController!) {
        paymentViewController.dismiss(animated: true, completion: nil)
        // Implement functionality after card is read (information is stored in cardInfo)
    func onProgressUpdate(_ progressUpdate: DyScanProgressUpdate, in paymentViewController: DyScanViewController!){
        let network =
        let lastFourDigits = progressUpdate.lastFourDigits
        // Implement functionality to use this info mid-scan

If you are using Stripe, see this guide for how to implement these functions.

DyScanCreditCardInfo has the following fields:




The card number read, as a string.


If read, the expiration month of the card, otherwise nil. The value is accessed asnullableExpiryMonth.uintValue.


If read, the expiration year of the card, otherwise nil. The value is accessed asnullableExpiryYear.uintValue.


Currently always nil.


The x position of the card number, as a fraction of the scan region width. The value is accessed ascardNumberX.doubleValue.


The y position of the card number, as a fraction of the scan region height. The value is accessed ascardNumberY.doubleValue.


The x position of the expiration date, as a fraction of the scan region width. The value is accessed asexpiryX.doubleValue.


The y position of the expiration date, as a fraction of the scan region width. The value is accessed asexpiryY.doubleValue.


If read, the expiration month of the card, otherwise 0. To maintain good style, we recommend using nullableExpiryMonth if writing in Swift.


If read, the expiration year of the card, otherwise 0. To maintain good style, we recommend using nullableExpiryYear if writing in Swift.


For the OCR-only version of DyScan, isFraud is always false.


Whether the card scanned was vertical or horizontal.

To instantiate DyScan, create an instance of DyScanViewController, and set the paymentDelegate attribute of it to your view controller (using self). Then, present the view controller.

let viewController = DyScanViewController()
viewController.paymentDelegate = self
viewController.apiKey = "{YOUR API KEY}" // for version lower than 1.1.1
let navigationController = UINavigationController(rootViewController: viewController)
navigationController.modalPresentationStyle = .fullScreen
present(navigationController, animated: true, completion: nil)

Customizing the Appearance

The DyScan UI is customizable through the following options



Default Value


The language to display



Whether to display the credit card number to the user after the card has been read.



Whether to display number on completion horizontally in fixed position.



Whether to display the Dyneti logo and wordmark above the scan region.



Whether to show the number overlay.



The color of the number overlay text.



The opacity of the number overlay text.



The card number shown in the number overlay text.

"4242 4242 4242 4242"


The expiration shown in the number overlay text.



Whether to show the corners found by the scanner or not.



The thickness of lines that show the corners.



The color of the corner in its normal, no corner found state.



The color of the corner when it has found a corner.



The color of the corner when scanning is completed.


The color of the background.



The opacity of the background.



Whether to use the torch automatically in dark environments. If set to false, torch toggle button will appear.



Whether to cause the phone to vibrate on a successful scan.



The accessibility label of card scan frame.

"Align your card to this frame"


Whether to allow cards to scan in sideways orientation. If set to true, vertical cards will be able to be scanned when positioned in the horizontal scan window. Note that enableSidewaysScanning and showRotateButton should not simultaneously be set to true when using the view controller, and that isVertical should not be used when enableSidewaysScanning is set to true when using DyScan as a view.


The following fields can only be used in the view controller:



Default Value


Whether to show the helper text.



The text displayed in helper text. If this is set, it will override the set language. By default, the text is displayed in one line and font size is automatically shrunk to fit on the screen. To display it in multiple lines, use\n for line breaks.



The color of the helper text.



The font and text size of the helper text.

System font, size: 25

helperTextPosition:Enum DyScanHelperTextPosition

The position of the helper text. DyScanHelperTextPosition enum values: top, center, bottom



Whether to show a rotate button to support vertical cards better.


Additionally, there are some public fields you can use to easily add buttons with additional functionality to your scan screen. Note that these are available only if you are using DyScan as a view. The fields are described below:

Public fields




Whether to set scan region to vertical card orientation

  • true - vertical card

  • false - horizontal card

Also can be used to get current scan region orientation (true when vertical).


Whether to turn torch on or off.

Also can be used to check if torch is currently turned on (true when torch is on).

Last updated