Synchronize binding

Use syncBindingState to reconcile the device binding state between the Thales SDK and the Thales backend.

Call this when you suspect the SDK state is stale. This can happen after network errors, app reinstall, or interrupted device binding.

SDK integration

Call syncBindingState and handle the result in the success or error callback.

Android

This call is asynchronous.

Invoke the runOnUiThread(Runnable) callback when you need to update the UI.

visaCTFHelper.syncBindingState(correlationId, 
                               vProvisionTokenId, 
                               new SyncBindingStateListener() {
            @Override
            public void onError(TMGClientException exception) { 
                // Handle error
            }

            @Override
            public void onSuccess(BindingState bindingState) {
                // Use bindingState to choose the next flow.
            }
        });

The SDK returns the current binding state in onSuccess, or an error in onError.

iOS

This call is asynchronous.

Invoke the DispatchQueue.main.async callback when you need to update the UI.

let vProvisionedTokenID: String = ""
let correlationID: String = ""

// Start sync binding state
visaCTFHelper.syncBindingState(forVProvisionedTokenID: vProvisionedTokenID,
                                correlationID: correlationID) { (state, error) in
    if error == nil {
        // Use state to choose the next flow.
    } else {
        // Handle error
    } 
}

Next steps

Use the returned BindingState to continue with the right flow:

• UNBOUND: Start device binding. See Create device binding (green flow).
• PENDING_ACTIVATION: Resume device binding. This typically means the issuer required step-up authentication using an ID&V method. See Create device binding (yellow flow).
• BOUND: Authenticate transactions. See Authenticate a transaction.