.hheaders describing the SDK API
CardknoxPaymentsSDKdoes not contain
bitcodeand cannot be integrated with applications that require
arm6464-bit architecture for device builds - simulator targets are not supported
NSBluetoothAlwaysUsageDescriptionkey to the application
Targetinfo.plist file with the content similar to
XCodeproject to the application
CardknoxPaymentsSDKprovides the following objects:
CardknoxSDK- Used to initialize the
CardknoxPaymentsSDKwith client metadata, such as client’s software name and software version, as well as with the Cardknox API key to associate processed transactions with. Additionally, the type exposes a handful of lifecycle methods, which are named appropriately with their counterpart in the respective client’s class where they are meant to be called in. It is important for the
CardknoxPaymentsSDKlifecycle methods to be in sync with their client’s app lifecycle in order to initialize and dispose of the internal data structures.
PaymentTransactionRequest- A request type. Type’s constructor arguments represents the bare minimum of required parameters to make a transaction request against the Cardknox API. Developers can call in scope and out of scope functions on an instance of this type to process a transaction.
PaymentTransactionResponse- A response type that is the result of both the in scope and out of scope functions. This object is returned by the in scope function or delivered via the
NSNotificationCenterfor the out of scope function. For out of scope function, this type offers a utility conversion static method to convert the
NSNotificationobject into an instance of this type.
CardknoxCardReaderCallback- A type representing a callback when the SDK is being used to process ‘out of scope’ transactions using a physical card reader device. To receive callbacks back from the SDK, the user needs to subscribe with the
NSNotificationCenterby using a tag value on the
CardknoxCallbackCardReaderType- a type containing an enumeration of all possible callback types. Each
CardknoxCardReaderCallbackobject received through the
NSNotificationCentercontains one enumeration value.
TransactionParameters- used for sending transaction parameters.
Headersin any of the
registrar-prefixed files such as
registrar-x86_64. Registrar files can differ in content, but all of them provide identical definitions for
xExpprovided value is ““, error is
“xExp field is invalid (null, empty or pure whitespace)”
xExpprovided value is “021”, error is:
xExp parameter should be 4 characters long. Expecting 4 digit characters where first 2 digits are months, and second 2 digits year (2/2020 should be passed in as 0220)
xExpprovided value contains a non-digit or a non-integer value is passed in. For example, if the value is “a03”, the error is:
Unable to parse an integer number out of xExp value. Expecting a string with 4 digit characters.