Build with the Reader SDK on iOS to process in-person payments with Square hardware.
Reader SDK

Build on iOS

Build for iOS to process in-person payments with Square hardware with the Reader SDK.

Prerequisites and assumptions Permalink Get a link to this section

To build with the Reader SDK, the following must be true:

  • You have a Square account enabled for payment processing. If you have not enabled payment processing on your account (or you are not sure), visit squareup.com/activation.

  • You are using Xcode 10.2 or later.

  • You have set your Xcode iOS deployment target to iOS 11.

Note

If you need to support iOS 10, you must restrict build architectures to arm64 using the following steps:

  1. Open the Build Settings tab for your target in Xcode.

  2. Set the Architectures and Valid Architectures values to arm64.

  3. Open your Info.plist file in Xcode.

  4. Set UIRequiredDeviceCapabilities to arm64.

Your application is not able to run on a device that does not support 64-bit code.

Additionally, this guide makes the following assumptions:

  • Your version of the Reader SDK adheres to the Square update policy. To limit risk to developers and their users, Square enforces an update policy for the Reader SDK requiring developers keep their version of the Reader SDK current.

  • You are generally familiar with developing applications on iOS. If you are new to iOS development, you should visit the Apple Training Center before continuing.

Information you need Permalink Get a link to this section

To use the steps in this topic, you need:

  • Your application ID. Find your application ID on the Credentials page of your Square application in the Developer Dashboard.

  • Your Reader SDK repository password. Find your Reader SDK repository password on the Reader SDK page of your Square application in the Developer Dashboard.

Step 1: Request Reader SDK credentials Permalink Get a link to this section

  1. Open the Square Developer Dashboard. You are prompted to sign in or create an account.

  2. Create a Square application.

  3. Choose the new application to open the Square application settings pages.

  4. Open the Reader SDK page, and then choose Request Credentials to generate your Reader SDK repository password.

    A graphic showing the Reader SDK page in the Developer Dashboard with the generated Reader SDK repository password.

Step 2: Install the Reader SDK Permalink Get a link to this section

Download and configure the latest version of SquareReaderSDK.xcframework in your project root. The framework is installed in the current directory.

  • 1
  • 2
  • 3
ruby <(curl https://connect.squareup.com/readersdk-installer) install \
--app-id SQUARE_READER_SDK_APPLICATION_ID                             \
--repo-password SQUARE_READER_SDK_REPOSITORY_PASSWORD

Step 3: Configure your iOS project for the Reader SDK Permalink Get a link to this section

Add a Reader SDK build phase Permalink Get a link to this section

  1. Add the Reader SDK to your project:

    • Open the General tab for your application target in Xcode.

    • Drag the newly downloaded SquareReaderSDK.xcframework into the Embedded Binaries section, and then choose Finish in the dialog box that appears.

  2. Open the Xcode workspace or project for your application.

  3. On the Build Phases tab for your application target, choose the + button (at the top of the pane).

  4. Choose New Run Script Phase.

  5. Paste the following into the editor panel of the new run script:

    • 1
    • 2
    FRAMEWORKS="${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}"
"${FRAMEWORKS}/SquareReaderSDK.framework/setup"

    Important

    To avoid "No such file or directory" build errors, make sure that the Reader SDK Run Script phase is the last phase in the list.

Disable bitcode Permalink Get a link to this section

The Reader SDK does not currently support bitcode. To disable bitcode:

  1. Open the Build Settings tab for your application target.

  2. In the top right search field, search for "bitcode".

  3. Change the value of Enable Bitcode to NO.

Embed Swift libraries Permalink Get a link to this section

If your application target is pure Objective-C and contains no Swift code, you must include the standard Swift libraries with your application.

  1. Open the Build Settings tab for your application target.

  2. In the top right search field, search for "embed swift".

  3. Change the value of Always Embed Swift Standard Libraries to Yes.

Add support for required interface orientations Permalink Get a link to this section

  1. In Xcode, open the General tab for your application target.

  2. Make sure the Landscape Left and Landscape Right device orientations are supported, as shown:

ios-device-orientation

If your application runs on iPhone, it must support portrait and landscape interface orientations so that the Reader SDK can display the signature screen during checkout.

If you want specific screens in your application to only support the portrait orientation, you can override the supportedInterfaceOrientations method in your UIViewController subclasses.

Update your Info.plist Permalink Get a link to this section

Add or update the following key-value pairs on the Info tab for your application target to explain why your application requires these device permissions. Xcode can display human-readable labels (such as Privacy - Microphone Usage Description) rather than the raw keys.

KeyDescription
NSLocationWhenInUseUsageDescriptionThis application integrates with Square for card processing. To protect buyers and sellers, Square requires your location to process payments.
NSMicrophoneUsageDescriptionThis application integrates with Square for card processing. To swipe magnetic cards using the headphone jack, Square requires access to the microphone.
NSBluetoothPeripheralUsageDescriptionThis application integrates with Square for card processing. Square uses Bluetooth to connect your device to compatible hardware.
NSCameraUsageDescriptionThis application integrates with Square for card processing. Upload your account logo, feature photo, and product images with the photos stored on your mobile device.
NSPhotoLibraryUsageDescriptionThis application integrates with Square for card processing. Upload your account logo, feature photo, and product images with the photos stored on your mobile device.
NSBluetoothAlwaysUsageDescriptionThis application integrates with Square for card processing. Square uses Bluetooth to connect your device to compatible hardware.

Note

Your application does not need to request Bluetooth, Camera, or Photo Library permissions to use the Reader SDK. The usage descriptions are required due to the way the Reader SDK is built.

Step 4: Request location permission Permalink Get a link to this section

Add code to ensure that your application has permission to use location services before starting a checkout flow. The location permission is managed by Apple's CLLocationManager class.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
import CoreLocation

class YourViewController: UIViewController {
    private lazy var locationManager = CLLocationManager()

    func requestLocationPermission() {
        switch CLLocationManager.authorizationStatus() {
        case .notDetermined:
            locationManager.requestWhenInUseAuthorization()
        case .restricted, .denied:
            print("Show UI directing the user to the iOS Settings app")
        case .authorizedAlways, .authorizedWhenInUse:
            print("Location services have already been authorized.")
        }
    }
}

Step 5: Request microphone permission Permalink Get a link to this section

Add code to ensure that your application has permission to access the microphone before starting checkout. The microphone permission is managed by Apple's AVAudioSession class. You must have the record permission from AVAudioSession to use Square Magstripe Readers.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
import AVFoundation

extension <#YourViewController#> {
    func requestMicrophonePermission() {
        // Note: The microphone permission prompt will not be displayed
        // when running on the simulator
        AVAudioSession.sharedInstance().requestRecordPermission { authorized in
            if !authorized {
                print("Show UI directing the user to the iOS Settings app")
            }
        }
    }
}

Step 6: Add code to initialize the Reader SDK Permalink Get a link to this section

Update the application:didFinishLaunchingWithOptions: method in your application delegate to initialize the Reader SDK.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
import SquareReaderSDK

func application(
    _: UIApplication,
    didFinishLaunchingWithOptions launchOptions:
    [UIApplicationLaunchOptionsKey: Any]? = nil
) -> Bool {
    SQRDReaderSDK.initialize(applicationLaunchOptions: launchOptions)

    return true
}

Step 7: Add code to request a mobile authorization code Permalink Get a link to this section

The Reader SDK requires a mobile authorization code from the Mobile Authorization API. Mobile authorization codes allow custom mobile applications to process payments on Square hardware on behalf of a specific Square account for a given location.

Mobile authorization codes are short lived and should be used immediately to authorize the Reader SDK. Authorization is valid until it is explicitly revoked by calling deauthorize or your application fails to take a payment within 90 days. Mobile authorization codes do not need to be manually refreshed under normal operations.

Did you know?

Production applications should request mobile authorization codes programmatically, but you can generate mobile authorization codes on the Reader SDK page of your application settings or manually with cURL during development.

Create a function, retrieveAuthorizationCode, to handle the work of calling your authorization service and handling the result.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
import SquareReaderSDK

func retrieveAuthorizationCode() -> String {
    // TODO: Add code to retrieve a mobile authorization code.
    return "<Mobile Authorization Code>"
}

Step 8: Add code to authorize the Reader SDK Permalink Get a link to this section

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
import SquareReaderSDK

func authorizeReaderSDKIfNeeded() {
    if SQRDReaderSDK.shared.isAuthorized {
        print("Already authorized.")
    } else {
        let authCode = retrieveAuthorizationCode()
        SQRDReaderSDK.shared.authorize(withCode: authCode) { _, error in

            if let authError = error {
                // Handle the error
                print(authError)
            } else {
                // Proceed to the main application interface.
            }
        }
    }
}

Step 9: Implement CheckoutControllerDelegate methods Permalink Get a link to this section

Your view controller must conform to the SQRDCheckoutControllerDelegate protocol to handle results and errors from the checkout flow. In most cases, your view controller should implement SQRDCheckoutControllerDelegate. If you choose to implement the delegate as a separate object, make sure it is retained until the checkout flow completes.

Did you know?

This view controller is a good place to add a button that starts the contactless reader connect flow using the Reader SDK settings view controller. A Square contactless reader cannot be connected until the Reader SDK is authorized. Authorization is completed in Step 8 which means you can now connect a reader. See Connect a Contactless Reader for information about connecting a reader.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
import SquareReaderSDK

extension <#YourViewController#>: SQRDCheckoutControllerDelegate {
    func checkoutControllerDidCancel(
        _: SQRDCheckoutController
    ) {
        print("Checkout cancelled.")
    }

    func checkoutController(
        _: SQRDCheckoutController, didFailWith _: Error
    ) {
        // TODO: Handle checkout errors
    }

    func checkoutController(
        _: SQRDCheckoutController,
        didFinishCheckoutWith _: SQRDCheckoutResult
    ) {
        // TODO: Handle checkout success
    }
}

Step 10: Add code to start the checkout flow Permalink Get a link to this section

Create an SQRDCheckoutParameters object. At a minimum, you need to set the amount of money to be charged. You then start the checkout flow by instantiating a Square checkout controller (SQRDCheckoutController) and presenting it.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
import SquareReaderSDK

extension <#YourViewController#> {
    func startCheckout() {
        // Create a money amount in the currency of the authorized Square account
        let amountMoney = SQRDMoney(amount: 100)

        // Create parameters to customize the behavior of the checkout flow.
        let params = SQRDCheckoutParameters(amountMoney: amountMoney)
        params.additionalPaymentTypes = [.cash, .manualCardEntry]

        // Create a checkout controller and call present to start checkout flow.
        let checkoutController = SQRDCheckoutController(
            parameters: params,
            delegate: self
        )
        checkoutController.present(from: self)
    }
}

Step 11: Add code to handle the checkout result Permalink Get a link to this section

Implement the success and failure delegate methods. For now, print the checkout result to the Xcode console on success and error information on failure.

The Reader SDK provides error types for all failable operations. For example, errors that occur while presenting the checkout flow are always of the SQRDCheckoutControllerError type. Error objects always contain user displayable details (error codes and descriptions) and debugging information (debug codes and debug messages).

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
// Success delegate method
func checkoutController(
    _: SQRDCheckoutController,
    didFinishCheckoutWith result: SQRDCheckoutResult
) {
    // result contains details about the completed checkout
    print("Checkout completed: \(result.description).")
}

// ...
// Failure delegate method
func checkoutController(
    _: SQRDCheckoutController, didFailWith error: Error
) {
    // Checkout controller errors are always of type SQRDCheckoutControllerError
    let checkoutControllerError = error as! SQRDCheckoutControllerError

    switch checkoutControllerError.code {
    case .sdkNotAuthorized:
        // Checkout failed because the SDK is not authorized
        // with a Square merchant account.
        print("Reader SDK is not authorized.")
    case .usageError:
        // Checkout failed due to a usage error. Inspect the userInfo
        // dictionary for additional information.
        if let debugMessage = checkoutControllerError.userInfo[SQRDErrorDebugMessageKey],
            let debugCode = checkoutControllerError.userInfo[SQRDErrorDebugCodeKey] {
            print(debugCode, debugMessage)
        }
    }
}

Test the Reader SDK on iOS Permalink Get a link to this section

The Reader SDK provides a testing module that contains additional initializers that are not exposed in the Reader SDK framework. You can use these initializers to construct mock objects in your tests. For example, you might initialize a SQRDCard object in a unit test and use it to verify the behavior of your application.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
import SquareReaderSDK.Testing // import the Testing module

func test_updateWithCard() {
    let card = SQRDCard(brand: .visa, lastFour: "1111")
    self.cardView.updateWithCard(card)

    XCTAssertEqualObjects(self.cardView.lastFourLabel.text, "1111")
    XCTAssertEqualObjects(self.cardView.brandLabel.text, "Visa")
}

Related topics Permalink Get a link to this section

If you need more assistance, contact Developer Support or ask for help in the Developer Forums.

On this page