@urovotest/urovosdk-docs-mcp 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +176 -0
- package/docs/00-overview.md +37 -0
- package/docs/01-integration/android-permissions.md +22 -0
- package/docs/01-integration/quickstart-zh.md +54 -0
- package/docs/02-reference/emv/emv-api.md +3308 -0
- package/docs/02-reference/emv/emv-appendix.md +112 -0
- package/docs/02-reference/emv/emv-callback.md +1155 -0
- package/docs/02-reference/emv/emv-enum.md +324 -0
- package/docs/02-reference/error-codes.md +59 -0
- package/docs/02-reference/general/beeper.md +160 -0
- package/docs/02-reference/general/devicemanager.md +460 -0
- package/docs/02-reference/general/insertcardreader.md +307 -0
- package/docs/02-reference/general/install-manager.md +202 -0
- package/docs/02-reference/general/led-light.md +144 -0
- package/docs/02-reference/general/magcardreader.md +191 -0
- package/docs/02-reference/general/pinpad.md +3309 -0
- package/docs/02-reference/general/printer.md +1410 -0
- package/docs/02-reference/general/psam2.md +55 -0
- package/docs/02-reference/general/rfcardreader.md +1090 -0
- package/docs/02-reference/general/scanner-custom.md +196 -0
- package/docs/02-reference/general/scanner.md +214 -0
- package/docs/02-reference/general/sdk-log-output-management.md +124 -0
- package/docs/02-reference/general/serial-port-deprecated-suggest-using-module-14-serialtool.md +406 -0
- package/docs/02-reference/general/serial-port.md +326 -0
- package/docs/02-reference/general/sle4428-4436-4442.md +1890 -0
- package/docs/02-reference/general/system-manager.md +212 -0
- package/docs/02-reference/module-index.md +30 -0
- package/docs/02-reference/source-emv_sdk.md +3927 -0
- package/docs/02-reference/source-general_sdk.md +8978 -0
- package/docs/02-reference/undocumented/kiosk-lock-task.md +92 -0
- package/docs/03-demo/activity-map.md +27 -0
- package/docs/api-registry.json +4733 -0
- package/docs/search-index.json +2688 -0
- package/docs/source/emv_sdk.md +3927 -0
- package/docs/source/general_sdk.md +8978 -0
- package/docs/source/kiosk_lock_task.md +86 -0
- package/package.json +36 -0
- package/src/launch.js +22 -0
- package/src/lib/check-update.js +92 -0
- package/src/lib/create-mcp-server.js +90 -0
- package/src/lib/docs-tools.js +206 -0
- package/src/server.js +10 -0
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: EMV Appendix API
|
|
3
|
+
module: EMV Appendix
|
|
4
|
+
domain: emv
|
|
5
|
+
tags: ["emv", "emv-appendix", "emv appendix"]
|
|
6
|
+
---
|
|
7
|
+
# EMV Appendix
|
|
8
|
+
|
|
9
|
+
共 **4** 个 API/条目,来源 `emv_sdk.md`。
|
|
10
|
+
|
|
11
|
+
## API 索引
|
|
12
|
+
|
|
13
|
+
| 方法 | 类路径 | Demo Activity |
|
|
14
|
+
|------|--------|---------------|
|
|
15
|
+
| [CVM processing FAQ](#cvm-processing-faq) | `-` | - |
|
|
16
|
+
| [EMV kernel using FAQ](#emv-kernel-using-faq) | `-` | - |
|
|
17
|
+
| [# For NFC (Contactless) issues](#for-nfc-contactless-issues) | `-` | - |
|
|
18
|
+
| [Contact](#contact) | `-` | - |
|
|
19
|
+
|
|
20
|
+
## CVM processing FAQ
|
|
21
|
+
|
|
22
|
+
- **源文档章节:** 4.1
|
|
23
|
+
|
|
24
|
+
- Source section: `4.1`
|
|
25
|
+
|
|
26
|
+
|
|
27
|
+
|
|
28
|
+
Purpose:
|
|
29
|
+
Q1:Howto handleOnlinePINverification?
|
|
30
|
+
|
|
31
|
+
|
|
32
|
+
Source details:
|
|
33
|
+
```text
|
|
34
|
+
Q1:Howto handleOnlinePINverification?
|
|
35
|
+
Trigger: The EMV kernel invokes the onRequestPinEntry() callback when cardholder PIN
|
|
36
|
+
verificationisrequired.
|
|
37
|
+
ApplicationResponse:CallgetPinBlock()orgetPinBlockEx()(refertodeviceSDK)tolaunchthe
|
|
38
|
+
PINentryinterface.
|
|
39
|
+
UserActionHandling:
|
|
40
|
+
|
|
41
|
+
Success:CallmEmvApi.sendPinEntry()toconfirmPINsubmission.
|
|
42
|
+
Cancellation:CallmEmvApi.cancelPinEntry()iftheuserabortsinput.
|
|
43
|
+
Skip(ifallowed):CallmEmvApi.bypassPinEntry()forscenariosbypassingPINvalidation.
|
|
44
|
+
Q2:Howdoes EMVthe kernel handleofflineplainPin andofflineencrypt pin?
|
|
45
|
+
TheEMVkernelhandlesPINentryandverificationautomaticallyviathePINpad.
|
|
46
|
+
Noapplicationinterventionrequired(Trytestwithsampleapplication).
|
|
47
|
+
Q2:Howiscardholdersignaturetriggered inEMVtransactions?
|
|
48
|
+
The EMV kernel requests signature verification by invoking
|
|
49
|
+
onRequestDisplayText(ContantPara.DisplayText.APPROVED_PLEASE_SIGN) with parameter
|
|
50
|
+
ContantPara.DisplayText.APPROVED_PLEASE_SIGN
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
## EMV kernel using FAQ
|
|
54
|
+
|
|
55
|
+
- **源文档章节:** 4.2
|
|
56
|
+
|
|
57
|
+
- Source section: `4.2`
|
|
58
|
+
|
|
59
|
+
|
|
60
|
+
|
|
61
|
+
Purpose:
|
|
62
|
+
Q1:MissingPAN(Tag 0x5A) -Howto Fallback?
|
|
63
|
+
|
|
64
|
+
|
|
65
|
+
Source details:
|
|
66
|
+
```text
|
|
67
|
+
Q1:MissingPAN(Tag 0x5A) -Howto Fallback?
|
|
68
|
+
if0x5Anotreturn,needuse0x57datatogetPAN.
|
|
69
|
+
Q2:Howto Debug EMV(Contact/UPI) andNFC Issues?
|
|
70
|
+
1. EnableLogging:CallLogOutEnable()API(activatesbothEMV&NFClogs).
|
|
71
|
+
2. PullLogsSeparately:PulllogsviaADB.
|
|
72
|
+
1. # For EMV (Contact/UPI) issues
|
|
73
|
+
2. adb pull /data/data/com.urovo.demos/files/UROPE/Trace.txt
|
|
74
|
+
3.
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
## # For NFC (Contactless) issues
|
|
78
|
+
|
|
79
|
+
- **源文档章节:** 4.3
|
|
80
|
+
|
|
81
|
+
- Source section: `4.3`
|
|
82
|
+
|
|
83
|
+
|
|
84
|
+
|
|
85
|
+
Purpose:
|
|
86
|
+
5. adb pull /data/data/com.urovo.demos/files/UROPE/TraceCL.txt
|
|
87
|
+
|
|
88
|
+
|
|
89
|
+
Source details:
|
|
90
|
+
```text
|
|
91
|
+
5. adb pull /data/data/com.urovo.demos/files/UROPE/TraceCL.txt
|
|
92
|
+
Q3: OfflinePIN fails onAndroid5.1/6.0?
|
|
93
|
+
Fix:CallsetContext(MainActivity.this)beforetransaction.
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
## Contact
|
|
97
|
+
|
|
98
|
+
- **源文档章节:** 4.2
|
|
99
|
+
|
|
100
|
+
- Source section: `4.2`
|
|
101
|
+
|
|
102
|
+
|
|
103
|
+
|
|
104
|
+
Purpose:
|
|
105
|
+
if you have any issue , please contact Xiray or Ron, xiaofeng.xia@urovo.com,
|
|
106
|
+
|
|
107
|
+
|
|
108
|
+
Source details:
|
|
109
|
+
```text
|
|
110
|
+
if you have any issue , please contact Xiray or Ron, xiaofeng.xia@urovo.com,
|
|
111
|
+
an.luo@urovo.com ,wewill help you.
|
|
112
|
+
```
|