Documentation needed for onRequestSetPin

[prabhatsdp]

What is the basic purpose of this callback? Do we need to enter the pin via Physical Pin Pad or render a plain text Pin Pad ourselved on the screen?

Under what specific conditions is this method triggered? Will this trigger on specific devices, or cards?

What exact action is our application expected to perform when this is called?

[fangzhengwei]

Thanks for your feedback, please check the below response.

1. When a PIN is entered on the physical PIN pad, the SDK will call back the function onRequestSetPin(), which prompts the user in the app to enter a PIN, whether the entered PIN is an online PIN or an offline PIN, and the remaining number of attempts for the offline PIN.

   When a PIN is entered via rendering a plain text Pin Pad ourselved on the screen, SDK will call back the function onQposRequestPinResult(List dataList, int offlinePinTimes). please check online document for details.

2. Yes, the following conditions must be met, please check.

• A device with a physical keyboard, like the D70 and D80K.
• The card and pos must support PIN.
• For NFC transactions, you need to enter an amount greater than the contactless CVM limit.

3. When onRequestSetPin is called, you need to prompt the user to enter a PIN. If it is offline PIN, you also need to prompt the user about the remaining number of attempts for the offline PIN.

[prabhatsdp]

Thank you for the detailed explanation, @fangzhengwei. This is very helpful!

I have a quick follow-up regarding the onRequestSetPin callback. I noticed in the sample application that when this is triggered, a software UI dialog is rendered to capture the PIN:

// Payment Activity
viewModel.clearErrorState();
viewModel.titleText.set(getString(R.string.input_pin));
pinPadDialog = new PinPadDialog(PaymentActivity.this);

// PinPadDialog
this.mContext = context;
this.mThemeResId = R.style.dialog_pay_theme;
this.mDialogLayout = LayoutInflater.from(mContext).inflate(R.layout.view_paypass_dialog, null);
mDialog = new AlertDialog.Builder(mContext, mThemeResId).create();
mDialog.setCancelable(true);
mDialog.show();

Given that devices like the D70 already feature a built-in physical PIN pad, could you clarify under what specific conditions or on which devices this software UI fallback is expected to be called?

Additionally, could you briefly outline the expected end-to-end transaction flow for devices utilizing their hardware PIN pads?

Thanks again for your time and support!

[fangzhengwei]

I have checked with my team. To correct what I said earlier, please check the correct response below.

The onRequestSetPin() callback is only used for CR100 devices, the CR100 doesn't have a keyboard and requires a mobile app to function, it's a reader. When the onRequestSetPin() callback is received, the keyboard needs to be drawn on the mobile app and the user is requested to enter their PIN. so you see a software UI dialog rendered to capture the PIN from the demo sample code.

For the D70 with a physical PIN pad, when PIN input is requested, the SDK will call back onRequestDisplay() with the following enumerations, prompting the user to enter their PIN on the physical keyboard.

• Display.INPUT_ONLINE_PIN
• Display.INPUT_OFFLINE_PIN
• Display.INPUT_LAST_OFFLINE_PIN

For the complete transaction process, you can view our online document and android demo.

[prabhatsdp]

Thanks, @fangzhengwei, for the clarification.

This explanation aligns with both the sample code and the documentation. Could you please mark this reply as the Answer so that future developers can easily identify the correct response and avoid confusion?

Appreciate your efforts. Thanks!

[fangzhengwei]

Sure, welcome, let me do it.