This is an old revision of the document!

Getting Started with iOS

The CoChip SDK is a library for communicating with the PayConex Plus Payment Gateway. It wraps a set of interfaces and logic that connects the Payment Gateway, the Card Reader Devices and the client's side security.

This page presents the basic steps to build your own solution using our SDK.


This guide is applicable from SDK Version 1.4.10 and 1.5.1. For older versions, use the menu navigation on the left side of this page.

Step 01 - Download The Components

You can find our current supported version at the Download SDK Versions page.


Select the Plugins you'll be using in your application. That depends on the Card Reader Devices you are going to use. If you don't want to start from scratch, also download the Sample App provided to the version. This App will give you a good start point for you POS project.

Step 02 - Create Your Project and Install the SDK

The installation of the SDK is as easy as adding the CoChip SDK to your project. For that you are going to:

  • I) Include in your project: libgochipsdk_version.a, Core.h, libcommon.a and librest-connector-wn.a.
  • II) Using Xcode, select your project, navigate to Build Phases, open Link Binary with Libraries and include libcore-sdk.a in your project.
  • III) Add payconfig.xml into your Xcode project.
  • IV) Using Xcode, select your project, navigate into your Xcode Build Settings and make sure the Other Linker Flags option is set to -ObjC.

The payconfig.xml file contains URLs used to access the servers, so don't forget to add it to your project, or the communication is not going to happpen.

If you want to start with the Sample App, just follow the steps of creating a new project from an existing source. Each IDE works in a different way, but when creating a new project, most offer an option to create based on an existing project or based on source files where you just have to point to a repository. This repository would be the decompressed folder of the Sample App in the last step of the previous section.

Step 03 - Implement the CoreAPIListener

The application needs to implement the Core API Listener (CoreAPIListener) to interact with the SDK.

On iOS this makes the most sense in a ViewController, as follows:

  • @interface ViewController : UIViewController <CoreAPIListener>

For further reading on CoreAPIListener, consult the Core API Listener page at the SDK Documentation section.

The CoreAPIListener protocol contains all the methods used for interactions.

If your application contains multiple view controllers, instead of each controller conforming CoreAPIListener protocol and implementing all of its methods, you can use the following listeners, which are suited for your controller.


Then, register the listeners implementing the interfaces above:

  • [[WTPSTerminal singleton] registerCoreAPIDeviceListener:self];

Step 04 - Initialise the Terminal

  • I) You should use the Terminal (singleton instance) provided by the SDK.

To init terminal, Where self is an object that implements the CoreAPIListener.

  • [[WTPSTerminal singleton] init:self];

The terminal can also be initialized without CoreAPIListener

  • [[WTPSTerminal singleton] initialize];

  • II) Now, set the Terminal Mode, (TEST, DEV or LIVE), depending on your needs.

This is an easy one as well. All you have to do is to set the terminal mode to the right type.

The Test Mode should be used for development - It's going to make your app to use the gatewayTestUrl defined in payconfig.xml when communicating with the server. Before initiate your Terminal, enable the Test Mode:

  • [[WTPSTerminal singleton] setMode:TEST];

After finishing the development of your app, don't forget to change the mode again to go Live (Live Mode, that points to gatewayLiveUrl defined in payconfig.xml file).

  • [[WTPSTerminal singleton] setMode:LIVE];

You still have one option: the Dev Mode.

  • [[WTPSTerminal singleton] setMode:DEV];

The Dev Mode is used to point to gatewayDevUrl defined in payconfig.xml file. The Dev Host usually contains unreleased features.

  • III) Now, set the Terminal Log Level (NONE, ERROR, TEST or FULL), depending on your needs.

This is also an easy one. All you have to do is to set the terminal log level to the right type.

  • LEVEL_FULL: This level will allow SDK to print all logs into the log file and the console. Level FULL will be default level for TEST or DEV mode.
  • LEVEL_TEST: This level will allow SDK to print logs which do no contain any sensitive data e.g. requests and responses to the server, tlv strings, emv tags, encrypted data, etc. Level Info will be default level for LIVE mode.
  • LEVEL_ERRORThis level will allow SDK to print only errors. Any error that occurs in the SDK, any error that the server returns, any error that the device returns. No other logs such as events, method calls will be printed.
  • LEVEL_NONE: This level will disable logs in the SDK.

  • [[WTPSTerminal singleton] setLogLevel:LEVEL_FULL];

  • IV) Once the Terminal is created, initialize it.

The arguments are the terminal ID and secret. These are credentials required to use a Terminal using the SDK.

  • [[WTPSTerminal singleton] initWithConfiguration:TERMINAL_ID withSecret:SECRET];

Step 05 - Handle the Initialisation Response

Once the Terminal is initialized, it is necessary to handle all response types.

The Terminal initialization attempts to connect to the server and the response must then be verified. The SDK does that with the methods: onError and onSettingsRetrieved.

Successful Response

If your initialization worked properly, without problems, your application is going to receive the response at the onSettingsRetrieved method.

  • - (void)onSettingsRetrieved:(CoreSettings *)settings{
       // ...

You need to use the argument returned to extract the response.

Unsuccessful Response

If anything went wrong with the initialization, your application is going to receive an error at the onError method.

  • - (void)onError:(CoreErrorType)error{
    	// ... treatment for initialization error

In the event of an error, your application can show the error text, a generic message or execute a particular action, based on the error.

Step 06 - Install Your Plugins

  • I) Copy the appropriate plugin(s) to your project folder.
  • II) Using Xcode, select your project, navigate to Build Phases, open Link Binary with Libraries and include downloaded plugin(s) in your project.
  • III) The following frameworks need to be included in the Xcode project.
  • IV) Additional Frameworks Required per Device, in case you are using any of the plugins.
  • BBPosDevice

  • Rambler

  • Bluepad

Step 07 - Initialize the Device

Now we can initialize the device using our Terminal.

The first argument is a DeviceEnum corresponding to the device your application is going to use. The second argument is a connection type. The third argument is optional for initializing a bluetooth device with a pre stored bluetooth address.

  • [[WTPSTerminal singleton] initDevice:BBPOSDEVICE withConnectionType:BLUETOOTH withBluetoothAddress:nil];

For devices connecting via Bluetooth, onSelectBTDevice method will return list of available devices. It will be possible to choose the device from the list to connect to it.

  • - (void)onSelectBTDevice:(NSArray *)devices{
    	// ...

Call selectBTDevice (to connect to the device) to pass the position of the device from the list. The argument passed is the position of the device selected by the user from the list returned by the onSelectBTDevice above.

  • terminal.selectBTDevice(0);

Step 08 - Implement Your Features

For further reading on how to execute transactions (Sale, Refund, Report, etc.) visit the section Default Mode and explore the options.

Also, in case you are interested in working with different flow configurations, like a offline terminal, visit Offline Mode, or with unattended terminals, visit Polling Mode. More options are also available in Transaction Flows.

The following pages will assist you in understanding and implementing your features:

If you have questions, please talk to us using the Contact link at the top (right side) of this page. We would love to help!