How to Remotely Inject Test Keys (Master Key or DUKPT Key) into a Terminal: Difference between revisions

Latest revision as of 05:11, 8 April 2024

Please visit new link of same subject:

https://smartpossdk.gitbook.io/cloudpossdk/faq/key-injection/inject-test-keys-remotely

We're making a move! Our site's content is migrating to a new URL, to provide you with an enhanced browsing experience. Please update your bookmarks accordingly. Thank you for your continuous support!

@@ Line 1: / Line 1: @@
-Follows are the steps:
+{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/key-injection/inject-test-keys-remotely}}
-* Send us the serial number.
-* Send us the key file, the key file will be configured to our demo server, the follows are the key file template:
-  ## key type: 1 dukpt key 2 master key 3 transport key
-  ##
-  ## dukpt key
-  ## 1.sn = key_index, usage, counter, ksn, initial key
-  ##
-  ## usage, 0:PIN Key, 1:MAC Key, 2:Data Key
-  ##
-  ## master key
-  ## 2.sn = key_index, hex_master_key(length: 32 or 48)
-  ##
-  ## transport key
-  ## 3.sn = key_index, hex_transport_key(length: 32 or 48)
-  ##
-.WP17391Q20000031 = 0, 0, 0, FFFF9876543210E0, 6AC292FAA1315B4D858AB3A3D7D5933A
-.WP17391Q20000031 = 9, 38383838383838383838383838383838
-* We will config the demo certificate for the terminal and let you know. Please notice this step will replace the owner of the terminal, when you ends the test phase, and want to apply your own owner certificate, all the test certificates should be clear, the clear process will need us to approve, so it will generate a token file in an inserted TF card, send us the token file, after we signed, we will return you a .sig file, after you verify in the terminal, then the certificates will be removed. Then you can install your owner again.
-* Get and install the key loader demo from ftp://sdkuser:wizsdkar@ftp.wizarpos.com/KeyInjectDemoAgent-release.apk. Run the key loader demo to inject your keys.