SCard React Native Reference Documentation
SCard
Current Version: 11.6.1
Chilkat.SCard
Enumerate available PC/SC smart card readers and identify the reader the
application should use.
Connect to a reader/card, check card presence and status, and manage the
active PC/SC connection.
Send APDU commands directly to the card and receive the raw response
bytes and status words.
Issue lower-level reader control commands when supported by the reader
driver and PC/SC environment.
Monitor reader or card status changes so applications can detect card
insertion, removal, or state changes.
Use PC/SC transactions for coordinated card access and inspect detailed
error information when reader or card operations fail.
For an extended overview, see
SCard Class Overview.
Communicate directly with smart card readers and cards through PC/SC.
Chilkat.SCard is the low-level PC/SC smart card interface for
applications that need direct reader and card communication. It supports
reader discovery, reader connection, card status checking, APDU transmission,
reader-control commands, status-change monitoring, transactions, and
diagnostic access to underlying PC/SC errors. Use this class when the
application needs APDU-level control rather than a higher-level certificate,
minidriver, or PKCS#11 abstraction.
Reader discovery
Connect to cards
Transmit APDUs
Reader-control commands
Status monitoring
Transactions and diagnostics
Chilkat.SCard for direct PC/SC
reader and APDU-level work; use Chilkat.ScMinidriver for
card-minidriver certificate and key-container operations, and
Chilkat.Pkcs11 for PKCS#11 token or HSM sessions.
Object Creation
// npm install @chilkat/react-native react-native-nitro-modules
// (React Native 0.76+ with the New Architecture; then `pod install` for iOS. The Chilkat
// native library is downloaded and verified during the native build -- see the package README.)
import { Chilkat, SCard } from '@chilkat/react-native'
// Once per app start, before any other Chilkat call:
Chilkat.unlockBundle('Anything for 30-day trial') // shorthand for new Global().unlockBundle(..)
const sCard = new SCard()
// ... the native object is released when `sCard` is garbage collected, or now with sCard.dispose()Creates the underlying native Chilkat object. SCard is a Nitro Module HybridObject: use it from the JavaScript thread only (it cannot be passed to a Worklet or another runtime). Every member is synchronous and blocks the JavaScript thread until Chilkat returns; a method that can take a while also exists as a ...Async twin returning a Promise, which runs the same call on a native worker thread so the UI keeps rendering. While such a call is pending, every other call on this object throws, except abort() and assigning onPercentDone / onProgressInfo.
Releases the native object immediately instead of waiting for garbage collection (useful for a large BinData or an open socket). Calling it more than once is harmless; any other use of the object afterwards throws. An object with a pending ...Async call cannot be disposed until the promise settles.
Errors
A method that can fail throws a plain Error: a method whose only outcome is success or failure returns void and throws on failure; a method producing a string or an object returns it and throws where Chilkat would have returned null. The error's message is "Class.method(...): reason", where the reason is the last informative line of the object's lastErrorText, which holds the full Chilkat log of the failed call. A ...Async twin rejects its promise with the same Error instead of throwing. Properties never throw, and methods that answer a question (has..., is..., ...) return a plain boolean.
try {
sCard.someMethod(...)
} catch (e) {
console.log((e as Error).message) // SCard.someMethod(...): <reason>
console.log(sCard.lastErrorText) // the full Chilkat log of the failed call
}
// The same call without blocking the JavaScript thread:
try {
await sCard.someMethodAsync(...)
} catch (e) {
console.log((e as Error).message) // SCard.someMethodAsync: <reason>
}Properties
ActiveProtocol
readonly activeProtocol: string
The name of the active protocol if connected smart card reader, or an empty string if not connected. Possible values are T0, T1, raw, undefined, or if not connected to a reader.
CardAtr
readonly cardAtr: string
This is the Current ATR of a card in the connected reader.
topConnectedReader
readonly connectedReader: string
The name of the currently connected smart card reader, or an empty string if not connected.
topContext
readonly context: string
Contains the string user or system if this object has established a context (by calling EstablishContext). Contains the empty string if no context is established.
DebugLogFilePath
debugLogFilePath: string
If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.
Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.
Possible causes of hangs include:
- A timeout property set to 0, indicating an infinite timeout.
- A hang occurring within an event callback in the application code.
- An internal bug in the Chilkat code causing the hang.
LastErrorHtml
readonly lastErrorHtml: string
Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastErrorText
readonly lastErrorText: string
Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
LastErrorXml
readonly lastErrorXml: string
Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastMethodSuccess
lastMethodSuccess: boolean
Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.
PcscLibPath
pcscLibPath: string
For Linux systems only. Specifies the full path of the libpcsclite.so shared lib. This property should only be used if the libpcsclite.so is in a non-standard location or if Chilkat cannot automatically located it.
topReaderStatus
readonly readerStatus: string
The current status of the connected reader. Possible values are:
absent- There is no card in the reader.present- There is a card in the reader, but it has not been moved into position for use.swallowed- There is a card in the reader in position for use. The card is not powered.powered- Power is being provided to the card, but the reader driver is unaware of the mode of the card.negotiable- The card has been reset and is awaiting PTS negotiation.specific- The card has been reset and specific communication protocols have been established.
ScardError
readonly scardError: string
The last error returned by an underlying PC/SC function. Can be one of the following:
SCARD_W_REMOVED_CARD- The smart card has been removed, so that further communication is not possible.SCARD_W_RESET_CARD- The smart card has been reset, so any shared state information is invalid.
...
VerboseLogging
verboseLogging: boolean
If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.
Version
readonly version: string
Methods
BeginTransaction
Establishes a temporary exclusive access mode for doing a series of commands in a transaction.
Returns normally on success; throws an Error on failure.
CheckStatus
Check the current status of the currently connected reader. Calling this method updates the ReaderStatus, ActiveProtocol, and CardAtr properties. If this method returns false, none of the properties are updated.
Connect
Establish a connection to a reader. The reader is the name of a reader returned from ListReaders. The shareMode can be shared, exclusive, or direct. The preferredProtocol can be 0 (valid only if the shareMode = direct), T0, T1, raw, or no_preference. (No preference is effectively T0 or T1.)
If successful, the state of this object instance is that it's connected to the reader.
Disconnect
Terminates a connection with a reader. The disposition can be one of the following values:
leave: Do nothing.reset: Reset the card (warm reset).unpower: Power down the card (cold reset).eject: Eject the card.
Returns normally on success; throws an Error on failure.
EndTransaction
Ends a previously begun transaction. The disposition is the action to be taken on the reader, and can be leave which is to do nothing, reset, unpower, or eject.
Returns normally on success; throws an Error on failure.
EstablishContext
Creates an Application Context to the PC/SC Resource Manager. This must be the first WinSCard function called in a PC/SC application. The scope can be user or system. After calling, this object will have context and all other methods will use the established context. The Context property will hold the value user or system if context was established, or will be empty if no context was established.
Returns normally on success; throws an Error on failure.
FindSmartcards
Returns JSON containing information about the smartcards currently inserted into readers.
Returns normally on success; throws an Error on failure.
GetAttrib
Get an attribute from the IFD Handler (reader driver).
The attr can be one of the following:
ASYNC_PROTOCOL_TYPESATR_STRINGCHANNEL_IDCHARACTERISTICSCURRENT_BWTCURRENT_CLKCURRENT_CWTCURRENT_DCURRENT_EBC_ENCODINGCURRENT_FCURRENT_IFSCCURRENT_IFSDCURRENT_IO_STATECURRENT_NCURRENT_PROTOCOL_TYPECURRENT_WDEFAULT_CLKDEFAULT_DATA_RATEDEVICE_FRIENDLY_NAMEDEVICE_IN_USEDEVICE_SYSTEM_NAMEDEVICE_UNITESC_AUTHREQUESTESC_CANCELESC_RESETEXTENDED_BWTICC_INTERFACE_STATUSICC_PRESENCEICC_TYPE_PER_ATRMAX_CLKMAX_DATA_RATEMAX_IFSDMAXINPUTPOWER_MGMT_SUPPORTSUPRESS_T1_IFS_REQUESTSYNC_PROTOCOL_TYPESUSER_AUTH_INPUT_DEVICEUSER_TO_CARD_AUTH_DEVICEVENDOR_IFD_SERIAL_NOVENDOR_IFD_TYPEVENDOR_IFD_VERSIONVENDOR_NAME
The attribute data is returned in bd.
Returns normally on success; throws an Error on failure.
GetAttribStr
Get a string typed attribute from the IFD Handler (reader driver).
The attr can be one of the following, but should be limited to the particular attributes that return string values.
ASYNC_PROTOCOL_TYPESATR_STRINGCHANNEL_IDCHARACTERISTICSCURRENT_BWTCURRENT_CLKCURRENT_CWTCURRENT_DCURRENT_EBC_ENCODINGCURRENT_FCURRENT_IFSCCURRENT_IFSDCURRENT_IO_STATECURRENT_NCURRENT_PROTOCOL_TYPECURRENT_WDEFAULT_CLKDEFAULT_DATA_RATEDEVICE_FRIENDLY_NAMEDEVICE_IN_USEDEVICE_SYSTEM_NAMEDEVICE_UNITESC_AUTHREQUESTESC_CANCELESC_RESETEXTENDED_BWTICC_INTERFACE_STATUSICC_PRESENCEICC_TYPE_PER_ATRMAX_CLKMAX_DATA_RATEMAX_IFSDMAXINPUTPOWER_MGMT_SUPPORTSUPRESS_T1_IFS_REQUESTSYNC_PROTOCOL_TYPESUSER_AUTH_INPUT_DEVICEUSER_TO_CARD_AUTH_DEVICEVENDOR_IFD_SERIAL_NOVENDOR_IFD_TYPEVENDOR_IFD_VERSIONVENDOR_NAME
Throws an Error on failure (where the description says null is returned, the method throws instead).
GetAttribUint
Get an unsigned integer typed attribute from the IFD Handler (reader driver).
The attr can be one of the following, but should be limited to the particular attributes that return unsigned integer values.
ASYNC_PROTOCOL_TYPESATR_STRINGCHANNEL_IDCHARACTERISTICSCURRENT_BWTCURRENT_CLKCURRENT_CWTCURRENT_DCURRENT_EBC_ENCODINGCURRENT_FCURRENT_IFSCCURRENT_IFSDCURRENT_IO_STATECURRENT_NCURRENT_PROTOCOL_TYPECURRENT_WDEFAULT_CLKDEFAULT_DATA_RATEDEVICE_FRIENDLY_NAMEDEVICE_IN_USEDEVICE_SYSTEM_NAMEDEVICE_UNITESC_AUTHREQUESTESC_CANCELESC_RESETEXTENDED_BWTICC_INTERFACE_STATUSICC_PRESENCEICC_TYPE_PER_ATRMAX_CLKMAX_DATA_RATEMAX_IFSDMAXINPUTPOWER_MGMT_SUPPORTSUPRESS_T1_IFS_REQUESTSYNC_PROTOCOL_TYPESUSER_AUTH_INPUT_DEVICEUSER_TO_CARD_AUTH_DEVICEVENDOR_IFD_SERIAL_NOVENDOR_IFD_TYPEVENDOR_IFD_VERSIONVENDOR_NAME
Returns 0xFFFFFFFF on failure.
topGetStatusChange
Blocks execution until the current availability of the cards in a specific set of readers changes.
This function receives a list of reader names in stReaderNames. It then blocks waiting for a change in state to occur for a maximum blocking time of maxWaitMs (in milliseconds) or forever if 0 is used.
Information about the current reader states and which reader(s) changed is returned in json. See the example below for more information.
To wait for a reader event (reader added or removed) you may use the special reader name \\?PnP?\Notification.
To cancel the ongoing call, call Cancel().
The stReaderNames contains the reader names to check. The json is empty on input, and if the call returns success contains information about the state (after the event change) of each reader.
Returns normally on success; throws an Error on failure.
GetStatusChangeAsync
Asynchronous form of GetStatusChange: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.
Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.
Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.
GetStatusChangeCancel
Cancels an ongoing GetStatusChange method call. This would be called from a separate thread in your application if GetStatusChange was called synchronously.
Returns normally on success; throws an Error on failure.
ListReaderGroups
Returns a list of currently available reader groups on the system. The reader groups are returned in readerGroups.
Returns normally on success; throws an Error on failure.
ListReaders
Returns a list of currently available readers on the system.
Returns normally on success; throws an Error on failure.
Reconnect
Reestablishes a connection to a reader that was previously connected to using Connect().
In a multi application environment it is possible for an application to reset the card in shared mode. When this occurs any other application trying to access certain commands will be returned the value SCARD_W_RESET_CARD. When this occurs Reconnect() must be called in order to acknowledge that the card was reset and allow it to change its state accordingly.
The shareMode can be shared, exclusive, or direct. The preferredProtocol can be 0 (valid only if the shareMode = direct), T0, T1, raw, or no_preference. (No preference is effectively T0 or T1.) The action is the desired action taken on the card/reader. It can be leave, reset, unpower, or eject.
If successful, the state of this object instance is that it's connected to the reader.
Returns normally on success; throws an Error on failure.
ReleaseContext
Destroys a communication context to the PC/SC Resource Manager. This must be the last function called in a PC/SC application.
Returns normally on success; throws an Error on failure.
SendControl
Sends a command directly to the IFD Handler (reader driver) to be processed by the reader.
This is useful for creating client side reader drivers for functions like PIN pads, biometrics, or other extensions to the normal smart card reader that are not normally handled by PC/SC.
The command data is sent in bdSend. The response is written to bdRecv.
Returns normally on success; throws an Error on failure.
SendControlHex
Sends a command directly to the IFD Handler (reader driver) to be processed by the reader.
This is useful for creating client side reader drivers for functions like PIN pads, biometrics, or other extensions to the normal smart card reader that are not normally handled by PC/SC.
The command data is provided as a hex string in sendData. The response is written to bdRecv.
Returns normally on success; throws an Error on failure.
Transmit
Sends an APDU to the smart card contained in the currently connected reader. The protocolName can be T0, T1, or raw. The APDU to be sent is contained in bdSend. The response from the card is contained in bdRecv. The maxRecvLen is the maximum response size (in bytes) willing to be accepted.
Returns normally on success; throws an Error on failure.
TransmitHex
Sends an APDU to the smart card contained in the currently connected reader. The protocolName can be T0, T1, or raw. The APDU (in hexadecimal) to be sent is passed in apduHex. The response from the card is contained in bdRecv. The maxRecvLen is the maximum response size (in bytes) willing to be accepted.
Returns normally on success; throws an Error on failure.
Events
While a method runs, SCard reports progress through two optional callback properties. Assign a function to receive the event, or undefined to stop receiving it. The callbacks are delivered on the JavaScript thread, so they are useful with the ...Async methods: during a synchronous call the JavaScript thread is busy inside Chilkat, and the events can only arrive after it returns.
const sCard = new SCard()
sCard.onPercentDone = (pct) => setProgress(pct) // pct is 0..100
sCard.onProgressInfo = (name, value) => console.log(`${name}: ${value}`)
sCard.heartbeatMs = 250 // let abort() take effect within a quarter second
const pending = sCard.someMethodAsync(...)
cancelButton.onPress = () => sCard.abort() // the promise then rejects
await pendingPercentDone fires when an operation's completion percentage is known; ProgressInfo delivers named progress values (what is reported depends on the class and method). There is no AbortCheck callback: to cancel a pending ...Async call, call abort() on the object. Chilkat notices the request at its next progress check, which happens at least every heartbeatMs milliseconds on the classes that have that property (0, the default, disables the heartbeat, so set it for a responsive cancel), and the promise rejects with Chilkat's abort error. abort() is harmless when nothing is pending.
PercentDone
onPercentDone?: (pctDone: number) => void
This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).
The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.
To abort the operation, set the abort output argument to true. This will cause the method to terminate and return a failure status or corresponding failure value.
Example:
sCard.onPercentDone = (pct) => {
// pct ranges from 0 to 100.
setProgress(pct) // runs on the JavaScript thread: React state may be updated directly
}
await sCard.someMethodAsync(...)
// To stop an operation from within the callback, call sCard.abort()ProgressInfo
onProgressInfo?: (name: string, value: string) => void
This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.
Note: Some Chilkat methods don't fire any ProgressInfo events.
Example:
sCard.onProgressInfo = (name, value) => console.log(`${name}: ${value}`)
await sCard.someMethodAsync(...)