On-device charging provides the capability to store sensitive data, such as
stored-value account (SVA) balances, on a smartphone, which can interact with external
systems through near-field communication.
Provision Secure Element Keys for DIRECT Mode
Each new secure element that is issued by the SAP Mobile Platform operator can be identified by a unique ID, and requires a specific keyset. The secure element unique ID is stored in a structure called Card Production Life Cycle (CPLC) data, which uniquely identifies each secure element and is stored into each secure element prior to configuration.
Generate Private Keys Used by On-Device Charging
By default, encrypting communications between the MER and the point of sale, on device charging requires two root keys—Mer Private chargeKey (MPcK) and Mer Private readKey (MPrK)—that are installed into each MER, and generate a specific and separate keyset for each merchant. The keys, which are 192 bits in size, are used by 3-DES algorithms (DESede/CBC/PKCS5Padding).