EP4179486A1 - Système de paiement, registre de pièces de monnaie, unité d'abonnés, registre de transaction, registre de contrôle et procédé de paiement avec des ensembles de données de pièces de monnaie électroniques - Google Patents

Système de paiement, registre de pièces de monnaie, unité d'abonnés, registre de transaction, registre de contrôle et procédé de paiement avec des ensembles de données de pièces de monnaie électroniques

Info

Publication number
EP4179486A1
EP4179486A1 EP21739313.1A EP21739313A EP4179486A1 EP 4179486 A1 EP4179486 A1 EP 4179486A1 EP 21739313 A EP21739313 A EP 21739313A EP 4179486 A1 EP4179486 A1 EP 4179486A1
Authority
EP
European Patent Office
Prior art keywords
register
coin
electronic coin
transaction
data record
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP21739313.1A
Other languages
German (de)
English (en)
Inventor
Wolfram Dr. SEIDEMANN
Raoul-Thomas HERBORG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Giesecke and Devrient Advance52 GmbH
Original Assignee
Giesecke and Devrient Advance52 GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Giesecke and Devrient Advance52 GmbH filed Critical Giesecke and Devrient Advance52 GmbH
Publication of EP4179486A1 publication Critical patent/EP4179486A1/fr
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0655—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed centrally
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0658—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed locally
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/223—Payment schemes or models based on the use of peer-to-peer networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G06Q20/3678—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes e-cash details, e.g. blinded, divisible or detecting double spending
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3821—Electronic credentials
    • G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/383—Anonymous user system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/008—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols involving homomorphic encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash

Definitions

  • the invention relates to a payment system, a coin register, a subscriber unit, a transaction register, a monitoring register and a method for paying with electronic coin data sets.
  • Security of payment transactions and the associated payment transaction data means protecting the confidentiality of the data exchanged; as well as protection of the integrity of the exchanged data; as well as protection of the availability of the exchanged data.
  • a payment system is shown in FIG. 1a and FIG.
  • no central instance of the payment system for example a coin register 2 or a monitoring register, is required.
  • a terminal M1 divides a coin data set C a in order to obtain a coin data set C b .
  • Terminal M1 simultaneously forwards coin data set C b to terminals M2 and M3 in an unauthorized manner.
  • terminal M2 passes on coin data set C b and receives coin data set C B , which is then forwarded directly to terminal M4.
  • the terminal M4 forwards the coin data set C c directly to the terminal M6.
  • the terminal M6 forwards the coin data record C c directly to the terminal M8.
  • the unsuspecting participant with terminal M3 forwards the coin data set C b directly to terminal M5.
  • the terminal M3 is the Münz Scheme C b to the terminal M5 directly on.
  • the terminal M5 gives Münz Scheme C b to the terminal M7 spur. Both coin data sets C b and C c thus frequently change hands without a coin register 2 of the payment system finding out about this. If - as illustrated in FIG lb -.
  • the terminal M8 now also wants to register the coin data record C c as the coin data record C e with the coin register 2, the coin register 2 determines that the coin data record C b is already invalid. Ml's attack or cheating is only now being discovered. As a result, the coin register 2 accepts neither the coin data set C c nor the coin data set C e , which could financially harm the respective owners of the terminals M7 and M8.
  • An electronic payment system is described in US Pat. No. 5,872,844 A.
  • Electronic coin data sets (assets) are issued in the system by a central institution.
  • the electronic coin data records are transferred from the payer's terminal (wallet) to the payee's terminal.
  • the payee's end device routinely submits the transmitted coin data records for possible verification.
  • a fraud detection system samples coin records submitted for review to uncover "bad" coin records that have been used fraudulently. Upon such detection, the fraud detection system will identify the terminal that used the bad coin record and flag it as a "bad terminal”.
  • the fraud detection system compiles a list of such bad terminals and distributes the list to warn other terminals about the bad terminals. If a bad terminal subsequently attempts to dispense coin records (whether fraudulently or not), the intended recipient will check the list of bad terminals and not complete a payment transaction with the bad terminal.
  • This known system is not anonymous because a participant uses an identity number to generate a pseudonym which must be used by the institution both for the payment transactions to the other participant and for the generation and issue of the electronic coin data records.
  • the issued electronic coin data sets must contain a signature chain, which means that the memory requirement of the electronic coin data set per payment transaction increases, ie the electronic coin data set grows. End devices that are not trustworthy are not allowed on the system at all. It is therefore the object of the present invention to provide a method and a system in which a payment transaction between participants in a public payment system is secure, is designed to be flexible and simple. In particular, direct and anonymous payment should be created between the participants in the payment system.
  • the exchanged electronic coin records should be confidential to other system participants, but allow each system participant to perform basic checks on the electronic coin record, namely (1) detecting multiple dispensing attempts; (2) recognizing attempts to pay with non-existent monetary amounts; and (3) recognizing return criteria for already dispensed coin records, for example that an electronic coin record should expire.
  • This anonymous payment system should be scalable, pseudonymisable or even personalizable (non-anonymous, open to identity or amount) - especially for control purposes or when anonymous participants are involved - in order to ensure that this public payment system is not misused.
  • Anonymous participants or untrustworthy participants should therefore be allowed to participate in the payment system without jeopardizing security.
  • An electronic coin record should always consume the same storage space, regardless of its age or the transactions involved.
  • the task is solved in particular by a payment system for paying with electronic coin data records.
  • the payment system has a coin register that is set up to register the electronic coin data sets.
  • the payment system also has subscriber units that are set up to carry out payment transactions by transmitting the electronic coin data sets and to send status and registration requests relating to the electronic coin data sets to the coin register.
  • the payment system also has a monitoring register that is set up to evaluate monitoring data records relating to the payment transactions.
  • a monitoring data record is formed in the monitoring register from at least one register data record and at least one transaction data record, the at least one register data record being provided by the coin register and the at least one transaction data record being provided by a transaction data record source and/or the coin register.
  • a three-layer system architecture for a payment system is thus proposed.
  • the respective payment transaction is thus advantageously fundamentally anonymous, but can be scalably pseudonymous or even personalized by appropriate parameterization of a corresponding register data record or a transaction data record.
  • This increases participant acceptance, since the freedom to pay directly, i.e. without a checking authority, is taken into account and at the same time the trustworthiness requirement of an issuing authority, a central bank or a commercial bank is met, namely ensuring that the payment system is not misused.
  • a monetary amount (asset) is understood to mean a digital amount that can be credited to an account at a financial institution, for example, or exchanged for another means of payment.
  • An electronic coin record thus represents cash in electronic form.
  • An electronic coin data record for transferring monetary amounts differs significantly from the electronic data record for data exchange or data transfer, for example a register data record or a transaction data record, since a classic data transaction is based, for example, on a question-and-answer principle or on intercommunication between the data transfer partners, for example the subscriber unit and one of the registry entities (coin registry, watchdog registry, trade repository).
  • identification or identification data can be exchanged, which can provide conclusions about a subscriber ID and/or an identification number of a natural person as a user (participant) of the payment system. This means that anonymous payment is not possible.
  • An electronic coin data set is anonymous, unique, unambiguous and is part of a security concept.
  • the electronic coin data record has a monetary amount as a data element, ie a date that represents a monetary value of the electronic coin data record, and an obfuscation amount, for example a random number, as a data element.
  • the amount of obfuscation is only known in the first layer. Except for the issuer authority, the concealed amount is not known to any of the payment system authorities of the second or third layer, for example one of the registers such as coin registers, monitoring registers, transaction registers, personal registers.
  • the obfuscation amount is - except in the first layer (direct transaction layer) - a secret data element. The amount of obfuscation is secret to the coin register and the monitoring register.
  • An electronic coin data set is uniquely represented by these at least two data elements (monetary amount, concealment amount).
  • monetary amount, concealment amount An electronic coin data set is uniquely represented by these at least two data elements.
  • Anyone who has access to these data elements of an electronic coin record can use this electronic coin record to pay in a payment transaction. Knowledge of these two data elements (monetary amount, concealment amount) is therefore equivalent to possession of the digital money.
  • each electronic coin data set also has at least one check value as a data element, so that this then consists of at least three pieces of data (monetary amount, concealment amount, check value).
  • the check value is incremented when the electronic coin record is transmitted directly between two subscriber units. The function of the check value of the electronic coin record will be explained later.
  • a status (valid/not valid) of an electronic coin record can be present as a data element in the electronic coin record. In one embodiment, the status cannot be attached to the electronic coin data set and in this embodiment is only known to the subscriber unit (security element) itself and/or the coin register and is managed there.
  • each electronic coin data set can have a coin identifier as a data element, the coin identifier preferably being used to identify a register data set relating to the electronic coin data set and a transaction data set relating to the electronic coin data set. Similar to a transaction identifier in the transaction data record, a coin identifier is a data element for the unique assignment of the electronic coin data record in the payment system. This coin identifier is preferably a random number. The coin identifier (if traceable) gives conclusions about the life cycle of an electronic coin data record.
  • the electronic coin data record can have further data elements, for example which currency the monetary amount represents, by which issuing authority it was generated and/or a signature of an issuing authority.
  • the electronic coin data records are managed by the respective subscriber units, for example by security elements integrated there, and also transmitted by them.
  • the security element is incorporated into the subscriber unit ready for operation.
  • the subscriber unit can be, for example, a mobile terminal such as a smartphone, a tablet computer, a computer, a server or a machine.
  • the electronic coin data record is transmitted from the (first) security element of a first subscriber unit to the (second) security element of another subscriber unit, for example.
  • a subscriber unit-to-subscriber unit transmission link can be set up, via which, for example, a secure channel is set up between the two security elements, via which the electronic coin data set is then transmitted.
  • An application installed ready for operation on the subscriber unit can initiate and control the transmission of the coin data record by using input and/or output means of the respective subscriber unit. For example, amounts of electronic coin data records can be displayed and the transmission process can be monitored.
  • a transaction record source - as part of the third tier - is a data source that provides transaction records.
  • the transaction data record includes the information that is required in order to be able to clearly identify the transmission of the coin data record between two subscriber units of the payment system in the totality of the transmissions (payment transactions).
  • the transaction data record includes in particular the subscriber units participating in the transmission and information regarding the coin data record to be transmitted. With a transaction data record, the transmission of the electronic coin data record with regard to the subscriber units involved can be reconstructed in a clear or at least pseudonymised manner.
  • this transaction data source can be a subscriber unit, in particular a subscriber unit that sends or has sent the coin data record.
  • the subscriber unit creates the transaction record and provides this - as Transaction data source - ready to monitor registry.
  • a communication channel between the subscriber unit and the coin register can also be used here, the communication between the subscriber unit and the monitoring entity is preferably cryptographically secured and cannot be viewed by any intermediate entities (such as the coin register).
  • this transaction data source can be a transaction register, preferably a transaction register of the payment system.
  • This trade register preferably makes available the transaction data record made available to the trade register by a subscriber unit, in particular a subscriber unit sending or having sent the electronic coin data record, in particular in a changed anonymity level, for example as an anonymised and/or pseudonymised transaction data record.
  • the initial generation of a transaction data record can also take place here in a subscriber unit.
  • This transaction record can be changed in its anonymity level by means of a transaction repository and is provided by the transaction repository - as the source of the transaction record - to the monitoring repository. An explanation of the anonymity level and how to set or change it will follow later.
  • the transaction register changes the transaction data set generated by the subscriber unit and makes it available to the monitoring register as a source of transaction data.
  • a communication channel can be used between a subscriber unit and the coin register.
  • the communication for the transmission of the transaction data record between the transaction register and the monitoring register is preferably secured cryptographically and cannot be viewed or checked by any instances connected in between, for example a coin register or a subscriber unit.
  • a defined (certain) group of people in particular enforcement authorities in criminal prosecution, are granted access to confidential information in order to prevent or prosecute crimes.
  • a complex encryption process can be used to secure legitimate access.
  • the transaction data generated in the subscriber unit are immediately encrypted with a cryptographic key after creation. This key is made up of several subkeys from remote entities. In order to be able to decrypt the encrypted transaction data records so that it can be evaluated by the monitoring register, several (at least two) Partial key of different remote instances necessary. This ensures the confidentiality and data integrity of the payment system.
  • a transaction record preferably originates from and is generated by one of the subscriber units. Further processing, for example adjusting an anonymity level, is then carried out, for example, by a trade repository. A register record preferably originates from and is generated by one of the subscriber units or the coin register. Further processing, for example the adjustment of an anonymity level, is then carried out, for example, by the coin register.
  • the transaction data records and/or the register data records are not generated by the subscriber unit.
  • communications between the subscriber units and the associated status and registration requests are logged and/or evaluated by the transaction register (in the case of a transaction data record) and/or the coin register (in the case of a register data record) and for the generation and provision of the respective transaction data record and/or Register data set used.
  • An electronic coin record unlike a transaction record and/or a register record, cannot be generated by a subscriber unit or the transaction register or the coin register or the monitoring register.
  • An electronic coin data record is generated (and also its destruction or deletion) by an issuer of the payment system, preferably exclusively by the issuer of the payment system.
  • the transaction data record has, for example, a monetary amount of the electronic coin data record.
  • the transaction data record has a transaction number as a data element.
  • This transaction number is, for example, a random number generated before the generation step.
  • a random number generator of the subscriber unit or of the security element is preferably used for this purpose.
  • the Transaction Number an identification number of the transaction, unique and unique to the transmission from the sending subscriber unit.
  • the transaction number can identify the transaction in the payment system.
  • the transaction data record also has a masked electronic coin data record corresponding to the electronic coin data record to be transmitted, preferably instead of the monetary amount of the electronic coin data record or instead of the electronic coin data record.
  • the masking will be explained later.
  • the non-inclusion of the electronic coin data record allows two system requirements to be met, namely, firstly, that the electronic coin data record only exists once in the system (and not a copy of it in the transaction data record), and secondly, that possession of the electronic coin data record entitles payment, i.e a transaction data record that has not yet been encrypted (possibly after it has been transmitted to the second subscriber unit) or a decrypted transaction data record would potentially contain electronic coin data records that could be used for payment transactions, and the risk of fraud would therefore increase.
  • the transaction data record has a transaction time.
  • a time stamp is generated and added to the transaction data record.
  • the time stamp is preferably unique throughout the payment system.
  • the subscriber unit adds a transaction time to the encrypted transaction data record (in plain text), for example as metadata.
  • This transaction time can be in the trade repository as an input parameter for calculating a deletion time of the encrypted transaction data record.
  • the encrypted transaction data record could be automatically deleted from a transaction register after a set storage time, for example X months or Y years, has expired. This is advantageous in the event that the transaction data record is not sent to the transaction register until much later after the transmission of the coin data record, in order not to extend the storage (possibly in an illegal manner).
  • a subscriber identifier or the transaction number of the transaction data record could also be added in plain text as further metadata.
  • the transaction data record has an acknowledgment of receipt from the second subscriber unit.
  • the acknowledgment of receipt serves as proof or acknowledgment of proper receipt of the electronic coin data record in the second subscriber unit and possession of the acknowledgment of receipt in the first subscriber unit proves proper transmission of the electronic coin record.
  • this transaction data record contradicts the desire for anonymity for the payment transactions of the payment system.
  • the transaction data record is therefore encrypted in the subscriber unit.
  • the transaction record is preferably encrypted immediately after it is created, more preferably the creation and the encryption occur as an atomic operation. Encryption is done with a cryptographic key. This means that the transaction data set cannot be viewed by an uninvolved third party and its content is hidden from this uninvolved third party. This ensures that an attack on the subscriber identity module to spy out unencrypted transaction data is unsuccessful.
  • This cryptographic key is composed of at least two partial keys. Each subkey comes from a (single) remote entity. The remote instances are independent of each other. A remote entity has knowledge and possession of only a (own) part of the key. In particular, a remote entity is unaware of and does not possess a partial key of another remote entity.
  • the assembly of the cryptographic key also includes deriving a public key part of a PKI key infrastructure to be used for encryption, which may have been generated using an assembled private key part.
  • remote entity is meant here that this entity is not a (local) entity of a subscriber unit.
  • the remote entity is preferably not the coin register of the payment system, not the transaction register of the payment system and also not the monitoring register of the payment system, so that, in order to maintain anonymity and neutrality in the payment system, the register instances of the payment system cannot or cannot decrypt the encrypted transaction data record independently can contribute partial keys for decryption.
  • this encrypted transaction record can be decrypted by authorized parties as the remote entities.
  • authorized parties could be, for example, a law enforcement agency, a notary public, the Department of Justice, a central bank, a payment processing authority, a court of law, or others.
  • the cryptographic partial keys are each from a law enforcement agency; a notary authority; a Department of Justice entity; a central issuing authority of the payment system; or a commercial bank instance of the payment system.
  • the cryptographic key for encrypting the transaction data record is a public key part of an asymmetric
  • the cryptographic key for encrypting the transaction data record is a public key part of an asymmetric
  • PKI Key infrastructure
  • All remote entities only have a partial key of the decryption key, i.e. all remote entities or a subset of the remote entities are always required to jointly decrypt the encrypted transaction data record. This improves security against misuse, as multiple instances are required to perform data access, which represents significant overhead in an attack scenario.
  • the partial keys are combined into a common (private) decryption key. This combining is done in the trade repository, for example. Alternatively, the combining occurs in the first subscriber unit. This combining is done, for example, by addition or by bit-by-bit XOR operation, which no remote entity can obtain for itself merely by knowing the partial key(s). This shared (private) decryption key is then used to decrypt the encrypted transaction record.
  • the corresponding public key portion of this shared private decryption key is used in the first subscriber unit to encrypt the generated transaction record.
  • this public key part is preferably sent from the transaction register to the subscriber unit and received there.
  • the cryptographic key for encryption is a symmetric key, with the corresponding private key part for decrypting the transaction data record being composed of at least two cryptographic partial keys by an addition operation or a bitwise XOR operation.
  • This key concept guarantees that no remote entity could bypass all others to decrypt data on its own.
  • threshold cryptography is applied to allow that not all remote entities are required to contribute their partial key, but that a subset of the entities is sufficient to compose the decryption key. The rule here is that at least the number of the subset must contribute its respective partial key. If the subset is smaller than a predefined minimum number of remote instances, decryption is not possible.
  • the encryption methods described here are transparent in order to ensure user acceptance.
  • the (encrypted) transaction record is sent to a trade repository.
  • a customary communication protocol such as TCP/IP or mobile radio communication, can be used in this case.
  • a proactive command is sent to the subscriber unit, for example.
  • the trade register is preferably an instance of the payment system and is used to archive the (encrypted) transaction data record.
  • This (encrypted) transaction data record can be decrypted there, in particular after an official request, for example using composite (combined) partial keys from the remote authorities and can then be viewed by the requesting authority (court authority, etc.).
  • An inspection for control verification purposes in each transmitted electronic coin data set in the payment system and/or in each register data set, for example a modification to be registered or registered modification of an electronic coin data set in the payment system, is thus possible, but only under very strict technical conditions when using the complex encryption actionable.
  • the governmental request such as a court order, includes a subscriber unit identifier and requests all transaction records of that identifier within a specified time period or point in time.
  • the metadata of the transaction data record then simplifies the answering of this request at the trade repository.
  • the trade repository can be a non-public database of the payment system, for example.
  • the encrypted transaction records are stored in this database for possible later verification.
  • the transaction register is designed, for example, as a centrally managed database in the form of a data store or service server of the payment system.
  • a security element is installed ready for operation in a subscriber unit. This ensures that the transaction data records are generated and encrypted and, if necessary, also sent without manipulation.
  • the transaction data record is created in the security element and then encrypted by the subscriber unit.
  • a security element is a technical resource-limited facility.
  • a security element is, for example, a special computer program product, in particular in the form of a secure runtime environment within an operating system of a terminal, English Trusted Execution Environments, TEE, or eSIM software, stored on a data memory, for example a subscriber unit, such as (mobile) terminal, a machine or an ATM.
  • the security element is designed, for example, as special hardware, in particular in the form of a secure hardware platform module, English Trusted Platform Module, TPM or as a chip card or an embedded security module, eUICC, eSIM.
  • the security element provides a trustworthy environment and thus has a higher level of trust than a terminal device in which the security element is possibly integrated ready for operation.
  • Transmission of an electronic coin record is preferably between two security elements to create a trusted environment.
  • the logical transmission of the electronic coin data record is direct, whereas a physical transmission may involve one or more intermediary entities, for example one or more subscriber units for preparing the operational readiness of the security element(s) and/or a remote data storage service in which a wallet application with electronic Coin records are physically stored.
  • Security elements can transfer electronic coin data sets among one another and then continue to use them directly - without register check(s), especially if the payment system requires that electronic coin data sets of security elements are to be regarded as valid per se.
  • One or more electronic coin data records can be stored securely in a subscriber unit or a security element, for example a large number of electronic coin data records can be stored securely in a data memory exclusively assigned to a subscriber unit or a security element.
  • the data memory then represents an electronic purse application, for example.
  • This data memory can, for example, be internal, external or virtual to the security element.
  • the first security element could also be electronic coin data records from less trustworthy units, such as subscriber units, ie a terminal or a Machine, have received, for example via an import / export function of the security element. Electronic coin records obtained in this way that are not obtained directly from another security element are considered less trustworthy. It could be a requirement of the payment system to have to check the validity of such electronic coin data records using the coin register or, through an action (modification) by the receiving security element, to transfer the electronic coin data record to the receiving security element before it can be passed on.
  • less trustworthy units such as subscriber units, ie a terminal or a Machine
  • Transmission of the electronic coin data set between the first and the second security element can be integrated in a transmission protocol between two subscriber units and/or integrated in a secure channel between two applications of the respective subscriber unit.
  • the transmission can include an Internet data connection to an external data store, for example an online store.
  • the electronic coin data record (to be transferred or modified) is registered in a coin register of the payment system.
  • a coin register of the payment system For example, the establishment of a communication link to the coin register is provided for registering the electronic coin data set. This communication link does not necessarily have to be present during the transmission process (payment process).
  • the coin register is preferably provided for the administration and checking of masked electronic coin data records. The coin register can also manage and check other (non-payment) transactions between subscriber units.
  • the coin register is, for example, a database in which a register data record is generated and/or stored.
  • the coin register is set up to provide at least one register data set to the monitoring register.
  • a register record is a record that allows the validity, status, history and/or whereabouts of an electronic coin record to be known and/or verified.
  • a register data record is preferably uniquely assigned to an electronic coin data record. The register record is for verification only and cannot be used to replace the electronic coin record for payment transactions.
  • a register data set has one or more of the following data elements: a signature of the electronic coin data set; an area evidencing of an electronic coin record; a check value of the electronic coin record; a check value related to the electronic coin record; a counter value relating to the electronic coin record; a subscriber identifier of a subscriber unit sending the register data record; a masked electronic coin record; and/or a monetary amount of the electronic coin record. All of these data elements and their function are defined in the appropriate places.
  • the coin register provides a register data record.
  • the register data set has, for example, a masked electronic coin data set corresponding to an electronic coin data set as a data element.
  • the masked electronic coin record was provided by a subscriber unit or an issuing entity. Possession of a masked Electronic Coin Record does not allow disclosure of data elements of the (corresponding) Electronic Coin Record, making such Register Record with (only) masked coin records anonymous in relation to a subscriber identifier (this is also referred to hereinafter as identity-anonymous) and also anonymous in relation to a monetary amount of the electronic coin data set (this is also referred to below as anonymous amount).
  • identity-anonymous a subscriber identifier
  • anonymous amount of the electronic coin data set this is also referred to below as anonymous amount.
  • the register data set has, for example, a masked electronic coin data set (corresponding to an electronic coin data set) and an amount category relating to a monetary amount of the electronic coin data set corresponding to the masked electronic coin data set as data elements.
  • a register data record with a masked coin data record is anonymous in terms of identity and pseudonymous in terms of amount. Masking and also using amount categories will be explained later.
  • the register data record has, for example, as data elements, a coin identifier of an electronic coin data record, a check value of the electronic coin data record and a pseudonym of the subscriber identifier.
  • a register data record is pseudonymous in identity and anonymous in terms of amount.
  • masked electronic coin records are provided as a data element in the register record or as the register record. These masked electronic coin data sets are registered with their corresponding processing in the coin register. The masking will be explained later.
  • a validity status of the (masked) electronic coin data record can be derived from this.
  • the validity of the (masked) electronic coin data records is preferably noted (registered) in the coin register. Modifications, such as switching, dividing or combining, to the individual electronic coin data records are registered in the coin register.
  • Modifications requested or carried out or to be carried out preferably also cause a transaction data record to be provided (and possibly encrypted) as described above.
  • the transaction data source for example a transaction register, is also used for archiving modifications to an electronic coin data record. This to the information of the coin register or the monitoring register possibly redundant information in the payment system increases the stability and security of the payment system.
  • the registration of the processing or the processing steps for a respective modification in the coin register can also relate to the registration of test results and intermediate test results relating to the validity of an electronic coin data record in the coin register, in particular the determination of test values and counter values of corresponding electronic ones coin records. If processing is final, this is indicated, for example, by corresponding markings or a derived total marking in the coin register. Final processing then decides whether an electronic coin record is valid or invalid.
  • test results and intermediate test results relating to a respective modification or a transmission process between subscriber units or their security elements and relating to the validity (in particular for display) of an electronic coin data record are registered, in particular the determination of test values and counter values of corresponding electronic coin data records not in the coin register of the payment system, but in a monitoring register of the payment system.
  • a register data set relating to the electronic coin data set is replaced in the coin register by a registration data set to be registered relating to the electronic coin data set or the modified electronic coin data set.
  • the monitoring register is set up to store monitoring data sets.
  • a monitoring data set is formed from at least one transaction data set and at least one register data set in the monitoring register.
  • a monitoring data record corresponds to precisely one electronic coin data record and is derived from precisely one transaction data record (also corresponding to the electronic coin data set) and exactly one register data set (also corresponding to the electronic coin data set) formed in the monitoring register. This formation occurs after being provided by the transaction data source and/or coin register. A monitoring data record then relates to exactly one payment transaction.
  • a monitoring data record can also relate to a plurality of electronic coin data records, for example electronic coin data records, which are sent by a subscriber unit, preferably within a predefined period of time.
  • a monitoring data record is formed, for example, from a number of transaction data records relating to this subscriber unit, preferably also relating to this transaction period.
  • the monitoring data set is formed, for example, from a number of register data sets relating to modifications to coin data sets, initiated and/or requested and/or status-checked by the subscriber unit, preferably also relating to this transaction period.
  • a monitoring data record then relates to a plurality of transaction data records (corresponding to the respective electronic coin data records of this subscriber unit, preferably in this transaction period) and at least one, preferably several register data records (also corresponding to the respective electronic coin data records of this subscriber unit, preferably in this transaction period) formed in the monitoring register. This formation preferably takes place after the provision by the transaction data source and/or coin register.
  • a monitoring data record then relates to a number of payment transactions by this subscriber unit, preferably within a predefined period of time.
  • the monitoring data set can be evaluated by the monitoring register.
  • This evaluation relates to checking for the double issue of the electronic coin data sets or the unauthorized generation of monetary amounts by a subscriber unit and/or also checking for aging of electronic coin data sets.
  • By forming and evaluating in the monitoring register it can be determined, for example, that a subscriber unit has issued a coin data set twice or has changed a monetary amount.
  • the anonymity levels set ensure that the payment system is still anonymous or pseudonymous, but that the validity is reliably checked by monitoring the transactions.
  • each transaction is formed and evaluated, so that attempts at fraud can be uncovered at a later date.
  • the monitoring data records formed from (anonymized and/or pseudonymised) transaction data records and register data records enable transactions to be monitored during ongoing operation of the payment system.
  • the monitoring register is a separate instance of the same payment system from the coin register. By dividing the coin register and monitoring register within a payment system, the coin register can be designed less complex and depict a superficial check of validity, while in the monitoring register the correctness of transmission processes, any required de-anonymization of a subscriber unit and/or the check of count values or check values of electronic Coin records are done.
  • Both the coin register and the monitoring register can be decentralized public databases, for example.
  • This database makes it easy to check electronic coin data records for their validity and to prevent "double spending", i.e. multiple issues, without the transmission itself being registered or logged.
  • the database for example a distributed ledger technology, DLT, describes a technique for networked computers that come to an agreement about the sequence of certain transactions and that these transactions update data. It corresponds to a decentralized management system or a decentralized database.
  • the coin register is a centrally managed database, for example in the form of a publicly accessible data store or as a hybrid of a central and decentralized database.
  • the coin register and the monitoring register are designed as a service server of the payment system.
  • the coin register is preferably operable in at least two different modes. In a first mode only register data sets and in a second mode the register data sets and the transaction data sets are provided from the coin register to the monitoring register.
  • the mode is preferably selected on the basis of the anonymity of the subscriber unit.
  • subscriber identifiers authenticate themselves at the coin register in order to have an electronic coin data set registered (register request) or to query the status of an electronic coin data set (status request).
  • the authenticating subscriber unit transmits a subscriber identifier or a pseudonym of the subscriber identifier, which leads to the successful authentication of the subscriber unit at the coin register.
  • the second mode in the coin register is only set if a subscriber unit has successfully authenticated itself in the coin register. Through authentication in this second mode, the coin register recognizes the subscriber unit. All related register and Status requests are not (any longer) anonymous to the coin register. Due to the combination of authentication of the subscriber unit and the requirements desired by the subscriber unit, the coin register can (automatically) provide both register data records and transaction data records to the monitoring register. There these register data sets and transaction data sets are formed into monitoring data sets. Alternatively, the transaction data generated by the subscriber unit (instead of a transaction register) is provided directly to the coin register and from there to the monitoring register.
  • the first mode is always set when a subscriber unit does not identify itself on the coin register, ie does not authenticate itself or a requested authentication fails. This can be desired on the part of the subscriber unit, for example if the relevant subscriber in the payment system wants to remain anonymous.
  • the coin register cannot provide any transaction data records associated with a register data record, since it is not possible to identify the sending subscriber unit.
  • the transaction records are provided from the trade repository to the surveillance registry or otherwise directly from the subscriber unit to the surveillance registry. There these register data sets and transaction data sets are formed into monitoring data sets.
  • the mode can be set based on a topology of the subscriber unit, for example.
  • security elements trusted wallets
  • unknown terminal devices non-trusted wallets
  • a possibly successful authentication of this unknown terminal device is preferably not trusted in the coin register.
  • the coin register is also set up to register modified electronic coin data records, it also being possible for the status and/or register requests of the subscriber units to relate to the modified electronic coin data records.
  • every modification of a coin data set planned or carried out by a subscriber unit also leads to the generation of register data sets and transaction data sets, which are formed into monitoring data sets and evaluated in the monitoring register. This means that modifications to the coin data set are also archived in the monitoring register and can be checked.
  • the first subscriber unit sending the electronic coin data record sends the (encrypted) transaction data record to the transaction register.
  • the first subscriber unit may locally delete the transaction record to save storage space.
  • the transaction data record is sent with cryptographic transport security.
  • cryptographic transport security for example, mutual authentication between subscriber unit and trade register is used.
  • a key exchange is either negotiated in advance as a session key or issued in advance. This additional transport security prevents an attacker from learning that a transaction record is now being transmitted. This increases security when transferring the transaction data records.
  • the encrypted transaction data record is sent from the first security element to the transaction register. This keeps the trade repository up to date with regard to completed/planned transfers and recent transactions are promptly archived in the trade repository. Sending is also prioritized in the event that no connection to the transaction register was available at the time the coin data record was transmitted, and the subscriber unit or its security element is required to promptly send the encrypted transaction data record to the transaction register if a (recognized) available communication connection is available.
  • the electronic coin data set is transmitted from the first subscriber unit to the second subscriber unit.
  • the transmission takes place, for example, immediately before the transaction data record is generated.
  • the transfer occurs immediately after the generate step, so the transfer could be part of the atomic operation described above and just the whole chain of generate-transfer (-encrypt) can be performed. This avoids differences between the generated transaction data record and the actually transmitted coin data record.
  • a transmission protocol can ensure that a transmission process (payment process), even though it is executed asynchronously, can be trusted by checking for the presence of a received message and using security elements.
  • a two-stage transmission is preferably to be ensured so that amounts of money are not destroyed nor are they duplicated in the active state.
  • the generated transaction data record is stored in the first subscriber unit, preferably in a non-volatile manner.
  • the storage can be an intermediate storage as long as the electronic coin data set has not yet been successfully transmitted to the second subscriber unit. The storage takes place locally.
  • the transaction record can be used to repeat the transmission process between the subscriber units. In this case, no changes need to be made to the coin data record or the transaction data record itself.
  • the stored transaction data record is used for a necessary repetition (RETRY) of the transmission in the event of connection errors or authentication problems during transmission.
  • the stored transaction data set is used for reversal (ROLLBACK) if the transmission of the coin data set failed.
  • ROLLBACK reversal
  • the electronic coin data record in the event of a transmission error, is sent again using the stored transaction data record. It is assumed that the transmission of the electronic coin data set has failed, but the transmission process is to be completed. The transmission of the electronic coin record is promptly repeated.
  • the electronic coin data record to be resent corresponds to the electronic coin data record during the transmission of which a transmission error occurred. No changes are therefore required to the coin data record for resending.
  • a further transaction data record is generated for logging purposes.
  • a transmission error case is assumed, for example, if an acknowledgment of receipt was not received in the first security element within a predefined period of time.
  • a timer is started, for example; the timer is preferably started during the transmission step of the electronic coin data set.
  • the case of a transmission error can be indicated by an error message from the first or the second security element.
  • the error case is thus explicitly displayed.
  • the transmission error case can also be assumed by a detected connection fault (connectivity failure).
  • the error case is thus indicated implicitly.
  • the transmission error case can also occur due to failed authentication (authentication failure).
  • the transmission error can also occur when a terminal device (device shutdown) in which one of the security elements is installed ready for operation is switched off, or when the transmission range is exceeded (exceeded distance) due to a movement of a participant.
  • the transmission error case can also occur as a result of an internal error in the first or second security element, in an application of the terminal device, or in the respective terminal device.
  • the first subscriber unit preferably the first security element
  • queries the second subscriber unit preferably the second security element, at predefined periodic intervals and actively requests a confirmation of receipt, alternatively also when a time value of a timer has been exceeded.
  • a successful transfer is indicated in the first subscriber unit.
  • a user display can be updated or the monetary amount can be deleted from a list of available monetary amounts.
  • a participant (user) in the payment system is visualized by this display that the transmission process was successful.
  • an available monetary amount is updated, in particular reduced in accordance with the transmitted monetary amount.
  • the electronic coin data record is evaluated as an input parameter of an application of the first subscriber unit in the display step.
  • the transaction data of this electronic coin data record thus actively controls the transmission process, regardless of an application that is executable in the first subscriber unit. Changes to the electronic coin data set are visualized for a user by the application on the first subscriber unit, and the user accordingly receives prompt feedback on the validity/status of the electronic coin data set to be/are transmitted.
  • the transmission step is not carried out until a checking step reveals that a check value for a number of transmissions to the second subscriber unit or to one or more further subscriber units in the event of a failure
  • Establishment of a communication connection to the trade repository or failed sending of the (encrypted) transaction data record to the trade repository or the monitoring register is below or equal to a predefined threshold.
  • the number of transmissions of coin data sets from the first subscriber unit is thus limited to a maximum value if the respective transaction data sets have not been or could not be sent to the transaction register in the meantime. This forces the first subscriber unit to always check whether a threshold value, for example 100, more preferably 50, more preferably 10 transmissions, ideally 5 transmissions, has been reached.
  • a check value must be passed for a number of transmissions to the second subscriber unit or to one or more further subscriber units if the transmission failed
  • the encrypted transaction data record and/or a stored transaction data record must be sent to the transaction register or the monitoring register before the electronic coin data record is transmitted.
  • the number of transmissions of coin data records from the first subscriber unit is thus limited to a maximum value if the respective transaction data records have not been or could not be sent to the transaction register or the monitoring register in the meantime. This forces the first subscriber unit to send the encrypted transaction records. A transfer of coin data sets is prevented until the transaction data sets have been sent successfully.
  • the threshold value is, for example, 100, more preferably 50, more preferably 10 transmissions, ideally 5 transmissions.
  • a test value is incremented in the first subscriber unit if the electronic coin data record was successfully transmitted and the communication connection to the transaction register failed or the encrypted transaction data record was not sent to the transaction register.
  • the test value to be checked is always up-to-date in relation to transmitted coin data sets whose corresponding transaction data set has not yet been sent from the subscriber unit to the transaction register.
  • the further steps are carried out in the payment system: masking of the electronic coin data set by applying a homomorphic one-way function to the electronic coin data set to obtain a masked electronic coin data set and registering the masked electronic coin data set in a coin register of the payment system, the registration preferably for switching , Splitting or joining masked electronic coin records.
  • masking will be explained later.
  • the filing in the trade repository is limited to a predefined period of time.
  • This period begins, for example, at the time the encrypted transaction data record is received in the trade repository or is started by a transaction time that is attached to the encrypted transaction data record as metadata.
  • This period is, for example, a legal requirement, ie a minimum or maximum period of time for storing the transaction data records, for example as part of data retention, for example X months or Y years, such as 6 months or 2 years.
  • the method includes the further step of decrypting the encrypted transaction data record with a cryptographic key, the key for decrypting the encrypted transaction data record being composed of at least two cryptographic partial keys of respective different remote entities in the transaction repository.
  • the assembling takes place by means of an addition operation or a bitwise XOR operation.
  • the cryptographic key for decrypting the encrypted transaction data record is composed of a predefined number of cryptographic partial keys from different remote entities, the predefined number being less than the total number of the different entities.
  • the decryption only takes place upon external request. This request may be the result of an investigation to verify that a transaction actually took place.
  • the transaction register has a hardware security module, HSM for short, with the hardware security module being a secure key memory in which different generations of the partial keys of the respective remote instances are stored.
  • HSM hardware security module
  • the key generations are preferably tracked by an HSM of the transaction register.
  • the transaction register has a hardware security module against which the various instances authenticate themselves before decrypting the stored encrypted transaction data record.
  • the HSM can therefore fulfill various functions, it is primarily a secure key store and a secure processing unit.
  • the HSM module can contain, for example, different key generations of the partial keys, with the remote entities authenticating themselves to the HSM in order to enable decryption with all generations.
  • the encrypted transaction data record is re-encrypted.
  • the encrypted transaction data is always re-encrypted (i.e. decrypted and re-encrypted) when it is received, thus avoiding transaction data records being stored in different encrypted formats in the transaction register. This simplifies the administration of the encrypted transaction data records in the trade repository.
  • the encrypted transaction record is re-encrypted. This prevents transaction data records from being stored in different encrypted formats in the transaction register when the key of an instance is changed.
  • the encrypted transaction data record is decrypted.
  • the storage of the received encrypted transaction data sets is unaffected by this.
  • the payment system has a register of persons, natural persons being assigned to the respective subscriber identifiers of subscriber units of the payment system and/or to the respective pseudonyms of subscriber units in the register of persons.
  • An identifier of a subscriber unit (for example the subscriber ID of a terminal device) in the payment system is therefore uniquely assigned to a natural person.
  • This person assignment is carried out, for example, by an issuing entity of the payment system or a bank entity of the payment system and possibly also there managed.
  • This personal assignment can also be managed by a service entity, for example an entity that provides a purse application for the terminal or that provides online access to a cloud purse.
  • This assignment of person to identifier is only carried out by the respective instance after the person has been successfully identified, for example by presenting an official identification document such as an identity card or passport.
  • An amount category is, for example, an amount range (from to) in which the monetary amount of the coin data record lies.
  • an amount category is a rounded amount value of the monetary amount, either rounded up or down.
  • the storage of the received encrypted transaction data sets is unaffected by this.
  • the pseudonymised or amount-categorized transaction data record is sent to a monitoring register of the payment system and stored there.
  • anonymized or pseudonymised transaction data records can be stored in the monitoring register, which makes it possible to monitor transactions during ongoing operations.
  • a pseudonymised transaction data record can be pseudonymous in terms of amount and/or identity.
  • An anonymized transaction record can be anonymous in terms of amount and/or identity.
  • the pseudonymised register data set is sent to the monitoring register of the payment system and stored there.
  • anonymized or pseudonymised register data records can be stored in the monitoring register, which enables transactions to be monitored during ongoing operations.
  • a pseudonymised register data record can be pseudonymous in terms of amount and/or identity.
  • An anonymized register data set can be anonymous in terms of amount and/or identity.
  • pseudonymized or anonymized transaction or register data records an anonymity level for the respective transaction data record is changed.
  • the pseudonymized or anonymized transaction or register data record is always more anonymous than the (non-pseudonymized) transaction or register data record.
  • the pseudonymised transaction or register data set - as specified by the payment system - can also be stored unencrypted in the register instances (coin register, monitoring register, transaction register) and used for further validity checks in the payment system. In this way, cases of fraud or manipulations in the payment system could be better detected by the payment system itself, and an official request (judicial decision) may then not be necessary.
  • An anonymity level of a record reflects a degree of anonymity of the (coin or transaction or register) record, i.e. a possibility of associating a constant identity, such as subscriber identifier, ID number, natural person, etc., with a record.
  • the aim of the payment system is to transfer monetary amounts anonymously (level 1), i.e. it should not be possible for a participant in the payment system - based on analogue cash - to deduce the constant identity of the participant based on a received electronic coin data record.
  • Level 2 is a combination of levels 1 and 3, namely using a pseudonym (level 2). This is the temporary or permanent association of a derived identity with a record. The derivation is generated, for example, in a trusted entity such as an audit register.
  • a subscriber identifier in the encrypted transaction or register data record preferably has level 3 anonymity, so that (decrypting) the transaction or register data record indicates the constant subscriber identifier.
  • a monetary amount in the transaction or register data record preferably has level 3 anonymity, so that (decrypting) the transaction or register data record shows the exact amount.
  • the anonymity level of a subscriber identifier in the transaction or register data record differs from the anonymity level of an amount category, so that mixed forms (different gradations) can be present in a pseudonymised or anonymized transaction or register data record.
  • a register data record has one of various anonymity levels, with the coin register being set up to set the anonymity level of the register data record before it is made available to the monitoring register.
  • a transaction data record has one of various anonymity levels, the transaction data record source being set up to set the anonymity level of the transaction data record before it is made available to the monitoring register.
  • the anonymity level of a subscriber identifier of a subscriber unit in a transaction data record is preferably different from the anonymity level of a subscriber identifier of a subscriber unit in the register data record (corresponding to the transaction data record).
  • the anonymity level of a register data record is preferably lower than the anonymity level of a transaction data record (corresponding to the register data record).
  • the setting of the anonymity level is preferably changed by replacing an identifier of a subscriber unit with a pseudonym in the transaction data record or in the register data record (corresponding to the transaction data record).
  • the setting of the anonymity level is preferably changed by replacing a monetary amount of an electronic coin data record with an amount category in the transaction data record or in the register data record (corresponding to the transaction data record).
  • a system requirement can be that a transmission must be anonymous in terms of the amount, ie the monetary amount of the electronic coin data record and/or a participant identity should not be inferred from the transaction and register data records.
  • Another system requirement can be that a transmission must be identity-anonymous, i.e. based on the transaction and register data records, the (natural person of) the subscriber unit of the electronic coin data record and/or a subscriber identity should not be inferred.
  • the anonymity level can be set depending on a mode of the coin register, so that in the case of untrustworthy anonymous participants (first mode) a higher level of anonymity can be set for the transaction data records or the register data records in order to enable easier traceability of the coin data records.
  • a low level of anonymity is understood to mean that the data record is completely anonymous, i.e. neither a participant identification nor an amount can be inferred.
  • the highest level of anonymity is the unveiled (everyone can see) transmission of the participant identity (ID) and the amount of the electronic coin data record.
  • the task is also solved by a subscriber unit in the payment system described above.
  • the subscriber unit is preferably a security element.
  • the subscriber unit has a processing unit that is set up to transmit an electronic coin data set to another subscriber unit.
  • the subscriber unit has means for accessing a data memory, with at least one electronic coin data set being stored in the data memory.
  • the subscriber unit also has an interface which is set up for sending status and registration requests relating to the electronic coin data sets or the modified electronic coin data sets to the coin register.
  • the computing unit is also set up to generate a transaction data record relating to the transmission of the electronic coin data record, with the interface also being set up to set up a communication link to a transaction register as a transaction data source in order to send the generated transaction data record to the transaction register.
  • the task is also accomplished by a coin register in the payment system described above.
  • the coin register has an arithmetic unit that is set up to set a first mode or a second mode of the coin register according to an authentication success of a subscriber unit at the coin register.
  • the coin register has means for accessing a coin store, with electronic coin data sets being registered in the coin store.
  • the coin register has an interface that is set up to provide register data records in a first mode and to provide register data records and transaction data records in a second mode for the monitoring register.
  • the processing unit of the coin register is preferably set up to set an anonymity level for a register data record.
  • the arithmetic unit of the coin register is preferably set up to create register data records.
  • a register record preferably comprises a masked electronic coin record provided by a subscriber unit or issuer entity.
  • the register data record is then anonymous in terms of identity and amount and has a very low level of anonymity.
  • a register data record (alternatively) preferably has a masked electronic coin data record and an amount category relating to a monetary amount of an electronic coin data record corresponding to the masked electronic coin data record.
  • the register data record is then anonymous in terms of identity and pseudonymous in terms of amount and has a medium level of anonymity.
  • a register data record (alternatively) preferably has a coin identifier of an electronic coin data record, a check value of the electronic coin data record and a pseudonym of the subscriber identifier.
  • the register data record is then identity pseudonymous and neutral in terms of amount and has a higher average anonymity level.
  • the test value of the register data set is, for example, a signature or a known masked electronic coin data set, for example a previous version.
  • the interface or another interface of the coin register is preferably set up to receive status and registration requests relating to the electronic coin data records or the modified electronic coin data records from the subscriber unit.
  • the coin register comprises a status verifier arranged to generate a status report regarding a registered electronic coin record based on a status request from the subscriber unit, the interface or a further interface being arranged to provide the status report to the subscriber unit.
  • the coin register comprises a change verifier arranged to change an entry in the coin register relating to a registered electronic coin record based on a register request from the subscriber unit.
  • the interface or another interface of the coin register is preferably set up to request proof from the subscriber unit before the change is registered in the coin register.
  • the interface or a further interface is preferably set up to receive register data sets of generated electronic coin data sets from an issuer entity of the payment system.
  • a module preferably a hardware security module, is set up in the coin register to replace a subscriber identifier of the subscriber unit with a pseudonym of the subscriber unit in the register data record in order to obtain a pseudonymised register data record. Additionally or alternatively, the module is set up to replace a pseudonym of the subscriber unit with a subscriber identifier of the subscriber unit in the register data record in order to obtain an identity-open register data record. Additionally or alternatively, the module is set up to replace a monetary amount of an electronic coin data set with an amount category in the register data set in order to obtain a pseudonymised register data set. Additionally or alternatively, the module is set up to replace an amount category of the electronic coin data record with a monetary amount of the electronic coin data record in the register data record in order to obtain an open-ended register data record.
  • the task is also solved by a transaction register for the payment system described above.
  • the transaction register has means for accessing a data memory, with at least one transaction data record being stored in the data memory.
  • the trade repository also has an interface that is set up for communication with a subscriber unit in order to receive a transaction data record from the subscriber unit.
  • a module preferably a hardware security module, is set up in the transaction register to replace a subscriber identifier of the subscriber unit with a pseudonym of the subscriber unit in the transaction data record in order to obtain a pseudonymised transaction data record. Additionally or alternatively, the module is set up to replace a pseudonym of the subscriber unit with a subscriber identifier of the subscriber unit in the transaction data record in order to obtain an identity-open transaction data record. Additionally or alternatively, the module is set up to replace a monetary amount of an electronic coin data record with an amount category in the transaction data record, with a pseudonymised transaction data record to obtain. Additionally or alternatively, the module is set up to replace an amount category of the electronic coin data record in the transaction data record with a monetary amount of the electronic coin data record in order to obtain an open-ended transaction data record.
  • the interface or another interface of the transaction register is preferably set up to send a transaction data record to the monitoring register of the payment system.
  • the transaction data record is either anonymized or pseudonymised, or it corresponds to the transaction data record as provided by the subscriber unit, preferably in decrypted form.
  • the interface or another interface of the transaction register is preferably set up to receive a subscriber identifier or a pseudonym of the subscriber identifier from a person register of the payment system.
  • the transaction register also has: a hardware security module, set up for the secure storage of partial keys of different generations; and decrypting encrypted transaction records.
  • the HSM of the trade repository is set up to decrypt encrypted transaction data records; replacing a subscriber unit identifier with a pseudonym in the transaction record to obtain a decrypted pseudonymised transaction record.
  • the HSM of the trade repository is set up to decrypt encrypted transaction data records and to replace a monetary amount of an electronic coin data record with an amount category in the transaction data record in order to obtain a decrypted amount-categorized transaction data record.
  • the interface is set up to send the decrypted pseudonymised transaction data record or the decrypted amount-categorized transaction data record to a monitoring register of the payment system.
  • the object is also achieved by a monitoring register in a payment system as described above, the monitoring register having an interface for receiving transaction data records and/or register data records from the coin register, the interface or another interface being set up to receive transaction data records from a transaction data source .
  • the monitoring register also has a computing unit that is set up to form Monitoring data records from the received transaction data records and register data records and which is further set up to evaluate the monitoring data records formed.
  • the object is also achieved by a method for paying with electronic coin data records in a payment system described herein.
  • the method comprises the steps of: registering the electronic coin data records in a coin register of the payment system; Executing payment transactions by transmitting the electronic coin records by payment system subscriber units; sending status and/or registration requests regarding the electronic coin records by the subscriber units of the payment system; Evaluation of monitoring data sets relating to the payment transactions by a monitoring register of the payment system, with a monitoring data set being formed in the monitoring register from at least one register data set and at least one transaction data set, the at least one register data set being provided by the coin register and the at least one transaction data set coming from a transaction data set source and/or or provided to the coin register.
  • the payment system also has an issuing entity that is designed to create an electronic coin data record for the payment system.
  • a corresponding masked electronic coin data record is assigned to each electronic coin data record in the respective method.
  • Knowledge of a masked electronic coin record does not authorize spending the digital money represented by the electronic coin record. This represents a key difference between the masked Electronic Coin Records and the (non-masked) Electronic Coin Records.
  • a Masked Electronic Coin Record is unique and also unique to an Electronic Coin Record, so there is a 1-to-1 relationship between a Masked Electronic Coin Record and a (non-masked) electronic coin record.
  • the electronic coin data set is preferably masked by a processing unit of the subscriber unit.
  • the subscriber unit has at least one electronic coin record.
  • the masking can be performed by a processing unit of a subscriber unit receiving the electronic coin data set.
  • This masked electronic coin record is obtained by applying a one-way homomorphic function, specifically a cryptographic homomorphic function.
  • This function is a one-way function, i.e. a mathematical function that is “easily” calculable in terms of complexity theory, but is “difficult” to practically impossible to reverse.
  • a function is also referred to as a one-way function, to which no one has been available in a reasonable time and with reasonable effort practically executable reversal is known.
  • the calculation of a masked electronic coin data set from an electronic coin data set is comparable to the generation of a public key in an encryption method using a residual class group.
  • a one-way function is used that operates on a group where the discrete logarithm problem is difficult to solve, such as B.
  • a cryptographic method analogous to an elliptic curve encryption, ECC for short from a private key of a corresponding cryptographic method.
  • the reverse function ie the generation of an electronic coin data record from a masked electronic coin data record, is very time-consuming—equivalent to generating the private key from a public key in an encryption method using a residual class group.
  • the respective operations on the corresponding mathematical group are to be understood in the mathematical sense, for example the group of points on an elliptic curve.
  • the one-way function is homomorphic, i.e. a cryptographic method that has homomorphic properties. Mathematical operations can thus be carried out with the masked electronic coin data record, which can also be carried out in parallel on the (non-masked) electronic coin data record and can therefore be reproduced. With the help of the homomorphic one-way function, calculations with masked electronic coin data records in the coin register and/or the monitoring register can be reproduced without the corresponding (non-masked) electronic coin data records being known there. Therefore, certain calculations with electronic coin data sets, for example for processing the (non-masked) electronic coin data set (e.g.
  • the monitoring of the legality of the respective electronic coin dataset can be verified in the monitoring register.
  • the homomorphic property thus makes it possible to enter valid and invalid electronic coin data sets based on their masked electronic coin data sets in a coin register and a monitoring register, without knowledge of the electronic coin data sets, even if these electronic coin data sets are processed (split, connected, switched) or transmitted directly, i.e. an action is carried out with these electronic coin data sets. It is always ensured that no additional monetary amount was created or that an identity of the subscriber units or their security elements is recorded in the coin register or the monitoring register. Masking allows for a high level of security without giving any insight into the monetary amount or subscriber unit.
  • a status of the electronic coin data record can be set to inactive status in order to invalidate the electronic coin data record, then it is sent (as the first step of the transmission) to the second subscriber unit and, if there is an acknowledgment of receipt from the second subscriber unit, it is deleted of the electronic coin record in the first subscriber unit (as the second step of the transmission).
  • a confirmation of erasure from the first subscriber unit may be sent to the coin register or the second subscriber unit to indicate a successful erasure (performed in the first subscriber unit) of the electronic coin record.
  • the switching can preferably take place automatically upon receipt of the deletion confirmation of an electronic coin data set in the second subscriber unit.
  • it can also be done on request, for example by a command from the first subscriber unit and/or the second subscriber unit.
  • two electronic coin datasets can be combined into one electronic coin dataset (“merge”).
  • Switching, splitting and connecting are various modifications to an electronic coin record, i.e. actions with the electronic coin record. These modifications require the masked coin data set to be registered in the coin register of the payment system. The concrete implementation of the individual modifications will be explained later.
  • Switching also takes place when an electronic coin data set has been changed, for example split up or connected to other electronic coin data sets, in particular over to be able to settle a monetary amount to be paid appropriately.
  • the payment system should always be able to pay any monetary amount.
  • the payment system is set up to carry out the further steps: masking the electronic coin data set by applying a homomorphic one-way function to the electronic coin data set to obtain a masked electronic coin data set; associating the masked electronic coin record with a pseudonym to obtain a pseudonymized masked electronic coin record; and sending the pseudonymized masked electronic coin data record to a coin register and/or a monitoring register of the payment system. Modifications to the electronic coin data record are thus tracked in the coin register and documented in the monitoring register under a pseudonym, without anonymity in the payment system being removed. The monitoring register can thus identify the outgoing transactions at the subscriber unit even if it knows the affiliation of the pseudonym and the subscriber unit.
  • the pseudonymized masked electronic coin data record is preferably included in the transaction data record in the generation step by the first subscriber unit, more preferably instead of the masked electronic coin data record, and preferably sent in encrypted form to the transaction register. A later decryption reveals the pseudonym under which the transaction took place.
  • the selection of the respective pseudonymization can be set flexibly in the payment system and adapted to the actual requirements of the payment system, for example to the computing power of the transaction register or the coin register or the monitoring register or a transmission capacity in the payment system.
  • the selection can be a payment system default. Since a digital payment transaction (the transmission of electronic coin data records) of a large amount of money could also be divided into several digital payment transactions of smaller amounts of money, each of which can be below the limit value, the limit value must be subscriber unit-specific and/or time-dependent.
  • pseudonymization or even anonymization is carried out in a preferred embodiment.
  • a linking step is carried out before the masking step in order to link a pseudonym of the first subscriber unit with the electronic coin data record.
  • the pseudonym is preferably subscriber unit specific.
  • a pseudonym is any type of disguised identity that makes it possible to draw conclusions about the subscriber unit and the transactions carried out with it without merely knowing the electronic coin data record.
  • the pseudonym is temporary and can be replaced by another pseudonym. It disguises the constant identity (participant ID) of a participant in the payment system.
  • An association between a pseudonym and a constant subscriber identifier is stored, for example, in the system in a secure environment, such as a register of persons, and can be checked accordingly.
  • an anonymous data set is not provided with a subscriber ID or the subscriber ID can be freely selected and is not assigned to a natural person in the payment system.
  • the subscriber unit must be able to perform a modification (split, switch, connect) for each received coin record in order to link the pseudonym to the coin record.
  • the registration in the coin register associated with each modification is sufficient in order to be able to unambiguously assign all coin data record transactions that were carried out with the subscriber unit to this subscriber unit on the basis of the linked pseudonym.
  • a surveillance register can, with knowledge of the Association of pseudonym and subscriber unit identify incoming transactions at the subscriber unit.
  • modifications to the electronic coin record are linked to a pseudonym stored on the subscriber unit.
  • This pseudonym can either be permanent or only valid for a certain period of time.
  • an anonymous masked electronic coin record lies in the identifiability of the subscriber unit by the surveillance register when using the pseudonym.
  • An anonymous masked electronic coin record does not contain any information about its origin, so it cannot be linked to a subscriber unit.
  • a pseudonymized masked electronic coin record has an association with a pseudonym of the subscriber unit, so that the subscriber unit that sent the pseudonymized masked electronic coin record to the monitoring register can be identified via the linked pseudonym.
  • the mechanism described is sufficient to determine whether the sum of the monetary amounts of all transactions in a subscriber unit is below a limit value, preferably within a specific time unit. If it is recognized that the limit value is exceeded by a desired modification, the coin register or the monitoring register could promptly prevent such a modification by blocking or rejecting the registration of the corresponding electronic coin data set in the coin register. Alternatively or additionally, the subscriber unit could be informed that the modification (and thus the transaction) would only be carried out if the subscriber unit de-anonymizes itself, e.g. discloses personal access data, before the modification is registered and the electronic coin record is validated, thereby completing the transaction would be accepted.
  • the number of area confirmations or area verifications that the monitoring register requests from the first subscriber unit is reduced by sending the pseudonymized masked electronic coin data record instead of an anonymous masked electronic coin data record.
  • the monitoring register, the coin register, the transaction register and/or the subscriber units can process the masked electronic coin records in an anonymous or in a pseudonymous mode.
  • the monitoring register requests necessary and other (catch up) area proofs or area confirmations.
  • pseudonymous mode the monitoring register demands at least does not accept one of the other area proofs or area confirmations, but checks for the pseudonym whether a (catch-up) criterion is met.
  • An electronic coin record can already be treated as valid if the necessary checks have been carried out. Only when the (catch-up) criterion is met are area reports or a total area report (or confirmation) requested from the subscriber unit. For example, a period of time or a number of masked electronic coin data sets can be used as (catch-up) criteria for the pseudonym.
  • the first (sending) subscriber unit receives a request for a sum area confirmation or a sum area proof from the monitoring register, and sends the requested sum area confirmation or the requested sum area proof to the monitoring register.
  • the first subscriber unit generates an unsolicited summary area confirmation or an unsolicited summary area proof, and sends the unsolicited summary area confirmation or the requested summary area proof to the monitoring register.
  • a sum range confirmation or a sum range proof is information from the subscriber unit about a sum of monetary amounts of a plurality of electronic coin data sets, preferably electronic coin data sets transmitted directly between subscriber units. This total information is compared in the monitoring register with an area information. If the specified range is exceeded, the electronic coin data records are de-anonymized in order to be able to secure and control the transfer of large monetary amounts.
  • the first subscriber unit preferably forms a sum of monetary amounts from a number of electronic coin data records, confirming with the sum range confirmation that the sum formed is within a range.
  • the sum range confirmation is understood in the monitoring register as an indication of the subscriber unit and the subscriber unit is classified as trustworthy.
  • the subscriber unit creates a sum range verification for a number of electronic coin data sets that can be checked by the monitoring register. The total range is then checked by the monitoring register and there is a confirmation that the total is in range (or not). The proof of total area is preferably also part of the transaction data record for the transaction register.
  • the multiple electronic coin data records only include selected electronic coin data records. Thus, the sum range confirmation or the sum range proof is not carried out for all electronic coin data sets of the subscriber units, but only for a specific selection. In one embodiment, the selection relates only to electronic coin data sets sent from pseudonymised, masked electronic coin data sets.
  • only electronic coin data records are affected by sent anonymous masked electronic coin data records or sent pseudonymized masked electronic coin data records.
  • only electronic coin data records are affected by anonymous masked electronic coin data records sent, pseudonymised masked electronic coin data records sent and/or masked electronic coin data records not sent to the monitoring register.
  • the several electronic coin data records are selected as a selection criterion after a preselected period of time. A day, a week or even a much shorter period can be selected as the period.
  • This selection is preferably masked and then sent to the trade repository in encrypted form as part of the transaction record.
  • a list in the first subscriber unit or in the monitoring register is to be used as a selection criterion, based on which list the electronic coin data records are selected.
  • This list is preferably masked and then sent to the trade repository in encrypted form as part of the transaction record.
  • the monitoring register requests area confirmations or area verifications from subscriber units as part of a sum check.
  • the anonymous masked electronic coin record monitoring register employs a first sum checking mode.
  • the monitoring register applies a second sum checking mode.
  • the monitoring register checks a proof of area for each modified electronic coin data set received.
  • the monitoring register regularly or quasi-randomly requests area confirmations or area verifications from subscriber units. This takes place, for example, in the first sum check mode.
  • the monitoring register only requests an area confirmation or an area verification from the subscriber unit once a number of coin data sets have been received for a pseudonym. This takes place, for example, in the second sum check mode. This number is preferably dependent on subscriber unit type and/or coin denomination range. This means that the area proofs or area confirmations can be flexibly tailored to a specific user situation and thus increase the security of the payment system.
  • the masking of the electronic coin data record and linking the masked electronic coin data record in the second subscriber unit with a pseudonym of the second subscriber unit in the second subscriber unit and sending the pseudonymised masked electronic coin data record to the surveillance register is not carried out.
  • These identified outbound transactions are preferably sent to the trade repository in encrypted form as part of the transaction record.
  • the linking step of pseudonymizing is preferably performed by signing the respective masked electronic coin data record in the second subscriber unit with a private signature key of the second subscriber unit to obtain a signed masked electronic coin data record as a pseudonymized masked electronic coin data record or as a pseudonymized masked electronic coin data record transmitted.
  • Signing is done with a private signature key of the subscriber unit.
  • This signature key is preferably subscriber-unit-specific, i.e. knowing the verification key, it can be traced who last modified (switched, divided, connected) the coin data set.
  • the signed masked electronic coin record is registered in the audit register.
  • the signed, masked electronic coin data record is preferably included in the transaction data record in the generation step by the first subscriber unit, more preferably instead of the masked electronic coin data record, and is thus sent to the transaction register in encrypted form. Subsequent decryption then reveals the signature under which the transaction took place.
  • an asymmetric cryptosystem in which the subscriber unit using a secret signature key, here as a private Signature key or "private key”, calculates a value for a data set. This value enables anyone to check the authorship and integrity of the data set using a public verification key, the "public key”.
  • the step of registering preferably involves checking the signature in the monitoring register, with the monitoring register having the public verification key of the signature for this purpose.
  • the signature can now be checked by the monitoring register, in that a public verification key for the signature is known there.
  • the public verification key for checking the signature is preferably known only to the surveillance register, which means that the method remains anonymous to the subscriber units among themselves.
  • the coin register preferably registers any modification, i.e. switching, splitting and/or connecting together with the signature of the subscriber unit.
  • the coin register and/or the monitoring register can monitor and determine the sum of monetary amounts for all transactions of a subscriber unit.
  • the signature is, for example, part of the transaction data record and is sent to the trade repository either in encrypted form or in plain text and stored (archived) there.
  • the signature is preferably valid within a specific time unit, the specific time unit preferably being one day.
  • Each subscriber unit therefore has an asymmetric key pair in order to sign each modification with the private signature key.
  • the public key is known to the surveillance registry (and also to the coin registry).
  • the audit trail can link each transaction to the subscriber unit as the sender or recipient of the coin record.
  • the electronic coin data sets are issued by a central issuing authority, each electronic coin data set additionally having a test value.
  • the check value is incremented when the electronic coin data set is transmitted directly between two subscriber units, or the check value is invariant in the case of an action (modification) carried out by subscriber units with the electronic coin data set.
  • the method includes the following step: determining by the subscriber unit based on the check value of an electronic coin data record whether this electronic coin data record is displayed by the subscriber unit at the payment system or determining by the subscriber unit based on the check value of the electronic coin data record whether the electronic coin data record to the central issuing authority is returned.
  • the recognition of return criteria it is also determined on the basis of the above-mentioned test value for transaction data records that have not been sent or based on a further test value whether the electronic coin data record is displayed by the first subscriber unit in the payment system, in particular a coin register, and/or whether the electronic coin data record is returned to the central issuing authority.
  • Each test value of the electronic coin data record is used in the method to enable or improve a control function in the payment system.
  • Each verification value is preferably a data element of the electronic coin record readable by the subscriber unit or a data element in the subscriber unit and its value can be determined by the subscriber unit.
  • the check value for the return criteria is coupled to an electronic coin record.
  • the incrementing is either incremented by a sending subscriber unit immediately before the coin data record is sent to a receiving terminal. Or the incrementing occurs in a receiving subscriber unit immediately after receipt of the coin record.
  • the number of direct transmissions between subscriber units is recorded for each coin record.
  • the test value is invariant in the event of an action (invariant to action) carried out by subscriber units with the electronic coin data record.
  • Action-invariant means that the test value remains unchanged during an action with the coin data set.
  • the action-invariant test value is not specific to the electronic coin data set but is group-specific and therefore applies to a number of different coin data sets in order to maintain anonymity and prevent coin data set tracking. Any modification to the coin data record carried out by a terminal device, ie in particular switching, dividing, combining, as will be described later, is considered an action with a coin data record.
  • an action means each transmission of the coin data record, for example to a (different) subscriber unit or also to an entity in the payment system.
  • an action means redeeming the coin data set to credit a monetary amount of the coin data set or changing the currency system.
  • the display corresponds to the sending of a switching command to a coin register of the payment system in order to cause the coin data set to be switched there to the subscriber unit sending the coin data set.
  • the display causes the coin data record to be marked in a monitoring register of the payment system.
  • the check value and/or the coin data record can, but does not have to, be transmitted to the payment system for the purpose of display.
  • the return of the electronic coin record by the subscriber unit entails either redeeming a monetary amount associated with the electronic coin record or issuing a new electronic coin record of an identical monetary amount.
  • the return of the electronic coin data set by the subscriber unit can trigger a resetting or deletion of all entries in the monitoring register in the payment system relating to the electronic coin data set. In this way, digital traces of the electronic coin data record are deleted and the anonymity of the procedure is secured.
  • the subscriber unit uses the check value of the electronic coin record to determine whether to return the electronic coin record to the central issuing authority.
  • a criterion for the return of an electronic coin data record can thus be defined with the test value.
  • the electronic coin data set is returned to the central issuing authority by the payment system (the monitoring register) as a result of the display.
  • the payment system the monitoring register
  • the result of the determination is communicated to the subscriber unit and the subscriber unit is requested by the payment system to return the electronic coin data record.
  • the payment system requests the modification of the electronic coin data record as a result of the display. Modifying, for example splitting, combining or switching, requires the electronic coin data set to be registered in the payment system. In many configurations of the digital currency system, a return to the issuing authority is not necessary and sometimes also not sensible. This is especially true when the coin record was modified rapidly promptly after it was issued. In this embodiment, the coin record is not returned, but is considered returned.
  • a counter value in the payment system (the monitoring register) relating to this electronic coin data record is determined as a result of the display by the payment system using the check value of the electronic coin data record.
  • the check value of the coin data record is preferably transmitted from the subscriber unit to the payment system (the monitoring register).
  • the counter value is not part of the coin data set.
  • the counter value is preferably managed in the payment system.
  • the counter value is preferably incremented with each action (modification, transmission, redemption) relating to the electronic coin data set.
  • the counter value is preferably increased with different weighting for different actions. This makes it possible to better control the return according to different actions.
  • the check value is thus provided in the coin data record as a data element which is incremented in particular with each direct transmission between subscriber units.
  • the counter value in the payment system includes the check value, for example by adding the previous counter value to the check value.
  • each electronic coin data record has a first check value and a second check value.
  • the first check value is then correspondingly incremented when the electronic coin data record is transmitted directly between two subscriber units, the first check value of the electronic coin data record being used to determine whether the electronic coin data record is displayed by the subscriber unit in the payment system.
  • Based on at least the second check value of the electronic coin data set it is determined whether the electronic coin data set is returned to the central issuing authority.
  • a display check value is provided separately from a return check value in the coin record.
  • the second check value is preferably invariant in an action carried out by subscriber units with the electronic coin data record, with the second check value preferably being at least one value from the following list: return date of the electronic coin record; issue date of the electronic coin record; electronic coin record registration date; and electronic coin record identification value.
  • the action-invariant test value is not specific to the electronic coin data set but is group-specific and therefore applies to a number of different coin data sets in order to maintain anonymity and prevent coin data set tracking.
  • the second action-invariant check value is not individual for the electronic coin data record, but applies to a number of different coin data records (group ID) in order to maintain anonymity and prevent coin data record tracking.
  • the second check value is variable and includes the first check value to determine whether the electronic coin record is returned.
  • a sum could be formed and this sum could be compared with a predefined threshold value.
  • the number of direct transmissions could be a return criterion, so that no infrastructure for evaluating the coin data sets with regard to the return of the coin data sets would have to be provided in the payment system, ie simpler and more secure management would be possible while creating the control functions.
  • the exceeding of a threshold value of the check value of the electronic coin data record is determined by a first terminal device and an action with this electronic coin data record, in particular the direct transmission of this electronic coin data record from the first terminal device to a second terminal device, is only carried out if in first terminal it has been determined that no other electronic coin data set is present in the first terminal. This ensures that a payment transaction between two terminals can still be carried out and completed with the coin data set despite a large number of direct transmissions of this coin data set between terminals due to a lack of alternative coin data sets in the terminal.
  • the exceeding of a blocking threshold value of the test value of the electronic coin data set is determined by a first subscriber unit and an action with this electronic coin data set, in particular the direct transmission of this electronic coin data set from the first subscriber unit to a second subscriber unit, is blocked, regardless of this whether or not there is another electronic coin record in the first subscriber unit.
  • a threshold value is thus defined which, when it is reached, completely prevents (blocks) direct forwarding (transmission) between subscriber units.
  • this coin data record could be stored in a secure memory area, in addition only a return process but no action process of the subscriber unit has access.
  • the imminent blocking can be detected in advance by the subscriber unit and a user of the subscriber unit can be informed in order to prevent the blocking of the coin data set by immediately returning the coin data set. Additionally or alternatively, the subscriber unit may return the electronic coin record upon detecting that the blocking threshold has been exceeded.
  • the threshold value of the check value is preferably lower than the blocking threshold value of the check value.
  • the blocking threshold can be a multiple of the threshold in order not to block the coin record too early.
  • the threshold value is ten, for example, or five, for example, or 3, for example.
  • the blocking threshold value is correspondingly 30, or, for example, 15, or, for example, 10.
  • the issuer entity queries test values of coin data sets at predefined periodic intervals or in a specifically controlled manner and automatically requests an electronic coin data set back if a test value of the electronic coin data set is exceeded.
  • the monitoring register of the payment system determines a counter value in the monitoring register relating to the electronic coin data set using the test value of the electronic coin data set. If the counter value exceeds a threshold value, the electronic coin data record is returned (directly or indirectly) to the central issuing authority. In this case, preferably only masked coin data records are managed in the monitoring register.
  • the issuer instance or the payment system requests the corresponding coin data set from the subscriber unit or provides corresponding information from the payment system to the subscriber unit for (direct) return.
  • the counter value is preferably increased with each action on the electronic coin data set, the counter value preferably being increased with different weighting for different actions.
  • the check value of the electronic coin data set is reset by the payment system. This simplifies the procedure since the subscriber unit does not have to be adjusted to the sum of all permitted actions, but only to the sum of consecutively permitted direct transmissions.
  • the highest test value of the electronic coin part data records is determined by the payment system and this highest check value is adopted as the check value of the combined electronic coin data set.
  • the monitoring register determines a new test value from the sum of all test values of the electronic coin part data records divided by the product of the number of coin part data records with a constant correction value, this new test value being the test value of the combined electronic coin dataset is adopted, the correction value being greater than or equal to 1 and the correction value preferably depending on a maximum deviation of the individual test values of the electronic coin part datasets or on a maximum test value of one of the electronic coin part datasets, with the correction value being more preferably less than or equal to 2.
  • the correction value is constant throughout the system.
  • the electronic coin data record is returned from the monitoring register to the issuing entity when the terminal device initiates the redemption of a monetary amount of the electronic coin data record to an account in the payment system and/or when the subscriber unit exchanges the monetary amount of the electronic coin data record for a requests another currency system of the payment system.
  • An electronic coin record can be split in a subscriber unit and this split is then registered in the coin register.
  • This has the advantage that an owner of the at least one electronic coin data record is not forced to always transfer the entire monetary amount at once, but rather to form and transfer corresponding partial monetary amounts.
  • the monetary value can be divided symmetrically or asymmetrically without restrictions as long as all electronic coin data subsets have a positive monetary amount that is smaller than the monetary amount of the electronic coin data set from which it is split and the sum of the electronic coin subdata sets is equal to the electronic coin subdata set to be split.
  • fixed denominations can be used.
  • the division into partial amounts is arbitrary.
  • the splitting triggers the execution of the method described above for generating and encrypting a transaction record, and the masked split electronic coin split record may be part of a transaction record for the trade repository.
  • the method preferably has the following further steps: switching over the transmitted electronic coin part data record; and/or merging the transmitted electronic coin record with a second electronic coin record to form a (new) linked electronic coin record.
  • the partial electronic coin data set received from the first subscriber unit results in a new electronic coin data set, preferably with the same monetary amount, the so-called electronic coin data set to be switched over.
  • the new electronic coin data set is generated by the second subscriber unit, preferably by using the monetary amount of the received electronic coin data set as the monetary amount of the electronic coin data set to be switched.
  • a new concealment amount for example a random number, is thereby generated.
  • the new obfuscation amount is added to the obfuscation amount of the received electronic coin record so that the sum of both obfuscation amounts (new and received) serves as the obfuscation amount of the electronic coin record to be switched.
  • the electronic coin part data set received and the electronic coin part data set to be switched over are preferably masked in the subscriber unit by applying the homomorphic one-way function to the electronic coin part data set received and the electronic coin part data set to be switched over, respectively, in order to obtain a masked electronic coin part data set received and a masked electronic coin part data set to be switched over .
  • the switching triggers for example, the execution of the method described above for generating and encrypting a transaction record and the masked electronic coin part record to be switched can be part of a transaction record for the trade register.
  • the switching is thus secured by adding a new spoof amount to the spoof amount of the received electronic coin record, thereby obtaining a spoof amount that only the second subscriber unit knows.
  • Newly created obfuscation amounts must have high entropy since they are used as the blinding factor for the corresponding masked electronic coin part records.
  • a random number generator on the security element is preferably used for this purpose. This safeguard can be tracked in the coin register.
  • additional information that is required to register the switching of the masked electronic coin data set in the coin register is preferably calculated in the subscriber unit.
  • the additional information includes a range verification of the masked electronic coin record to be switched and a range verification of the masked received electronic coin record.
  • the proof of area is proof that the monetary amount of the electronic coin data record is not negative, the electronic coin data record was validly created and/or the monetary amount and the concealed amount of the electronic coin data record are known to the creator of the area proof.
  • the area credential serves to provide such credential(s) without revealing the monetary amount and/or the concealment amount of the masked electronic coin record.
  • the changeover of the masked electronic coin data set is then registered in the remote coin register.
  • registration triggers the execution of the method described above for generating and encrypting a transaction record, and the masked electronic coin part record to be switched may be part of a transaction record for the transaction register.
  • the registering step is preferably performed when the second subscriber unit is connected to the coin register. While the electronic coin records are used for direct payment between two subscriber units, the masked coin records can be registered with a pseudonym in the coin register.
  • the registration triggers for example, the execution of the method described above for generating and encrypting a transaction record and the pseudonymized masked electronic coin part record to be switched can be part of a transaction record for the transaction record.
  • a further electronic coin data record (connected electronic coin data record) is determined from a first and a second electronic coin part data record for connecting electronic coin part data records.
  • the concealment amount for the electronic coin data set to be connected is calculated by forming the sum of the respective concealment amounts of the first and the second electronic coin data set.
  • the monetary amount for the associated electronic coin data record is preferably calculated by forming the sum of the respective monetary amounts of the first and the second electronic coin data record.
  • the first electronic coin part data record, the second electronic coin part data record, and the electronic coin data record to be connected in the (first and/or second) subscriber unit are created by applying the homomorphic one-way function to the first electronic coin part data record, the second electronic coin part data record, and the to masking the connecting electronic coin data set to obtain a masked first electronic coin part data set, a masked second electronic coin part data set, and a masked electronic coin data set to be connected, respectively.
  • additional information needed to register the linking of the masked electronic coin records in the remote coin register is computed in the subscriber unit.
  • the additional information includes area evidence of the masked first electronic coin part record and area evidence of the masked second electronic coin part record.
  • the area proof is a proof that the monetary amount of the electronic coin record is not negative, the electronic coin record validly created and/or the monetary amount and the obfuscation amount of the electronic coin record are known to the creator of the area credential.
  • area verification serves to provide such verification(s) without revealing the monetary value and/or the amount of obfuscation of the masked electronic coin record.
  • range proofs are also called "zero knowledge range proofs”. Ring signatures are preferably used as area verification.
  • the connection of the two masked electronic coin part data sets is then registered in the remote coin register. For example, registration triggers the execution of the method described above for generating and encrypting a transaction record, and the masked linked electronic coin part record may be part of a transaction record for the transaction repository.
  • two electronic coin data records or two electronic coin part data records can be combined.
  • the monetary amounts as well as the concealment amounts are added up.
  • the validity of the two original coin data records can also be carried out when connecting.
  • the registering step comprises receiving the masked electronic coin part data set to be switched over in the coin register, checking the masked electronic coin part data set to be switched over for validity; and registering the masked electronic coin part record to be switched in the coin register if the verifying step is successful, whereby the electronic coin part record to be switched is deemed to be verified.
  • a first layer electronic coin data records are transmitted directly between individual subscriber units or their security elements.
  • a second layer testing layer
  • masked electronic coin data sets are registered and checked in a coin register and a monitoring register.
  • no payment transactions are recorded, only masked electronic coin data records, their status, possibly test values, signatures and modifications for the purpose of verifying the validity of (non-masked) electronic coin data records. This ensures the anonymity of the participants in the payment system.
  • the second layer provides information about valid and invalid electronic coin data records, for example to avoid multiple issuance of the same electronic coin data record or to verify the authenticity of the electronic coin data record as validly issued electronic money or to record the sum of monetary amounts per security element in order to record this sum to compare with a limit value and to prevent or allow a modification accordingly.
  • the second layer may use a counter value of an electronic coin record to determine whether the electronic coin record has expired and is to be returned, or modified appropriately so that it is deemed to be returned.
  • a third shift archiving layer
  • encrypted transaction data records are stored in a transaction repository and decrypted and checked on official request as shown above.
  • the payment system also includes, for example, an issuer entity that generates electronic coin data sets (creation) and requests them again (deletion).
  • an issuer entity that generates electronic coin data sets (creation) and requests them again (deletion).
  • a masked electronic coin data record can also be issued by the issuer entity to the coin register and/or the monitoring register of the payment system for registering the electronic coin data record.
  • a subscriber unit can have a security element or itself be a security element in which the electronic coin data record is securely stored.
  • An application that controls or at least initiates parts of the transmission process can be installed ready for operation on the subscriber unit.
  • Electronic coin data records can be transmitted with the aid of terminal devices as subscriber units, which are logically and/or physically connected to the security elements.
  • the communication between two subscriber units can be wireless or wired, or e.g. also optically, preferably via QR code or barcode, and can be designed as a secure channel, for example between applications of the subscriber units.
  • the optical path can include, for example, the steps of generating an optical code, in particular a 2D code, preferably a QR code, and reading in the optical code.
  • the transmission of the electronic coin data record is secured, for example, by cryptographic keys, for example a session key negotiated for an electronic coin data record exchange or a symmetric or asymmetric key pair.
  • the exchanged electronic coin records are protected from theft or tampering.
  • the level of security elements thus complements the security of established blockchain technology.
  • the coin data records are transmitted as APDU commands.
  • the coin data record is preferably stored in an (embedded) UICC as a security element and is managed there.
  • An APDU is a combined command / Data block of a connection protocol between the UICC and a terminal.
  • the structure of the APDU is defined by the ISO-7816-4 standard.
  • APDUs represent an information element of the application layer (layer 7 of the OSI layer model).
  • the electronic coin data sets can be transmitted in any format. This implies that it communicates, i.e. can be transmitted, on any channel. They do not have to be saved in a fixed format or in a specific program.
  • a mobile telecommunications terminal for example a smartphone
  • the subscriber unit can also be a device such as a wearable, smart card, machine, tool, vending machine or even a container or vehicle.
  • a subscriber unit is thus either stationary or mobile.
  • the subscriber unit is preferably designed to use the Internet and/or other public or private networks.
  • the subscriber unit uses a suitable connection technology, for example Bluetooth, LoRa, NFC and/or WiFi, and has at least one corresponding interface.
  • the subscriber unit can also be designed to be connected to the Internet and/or other networks by means of access to a mobile radio network.
  • two subscriber units set up a local wireless communication connection via the protocol of which the transmission between the two security elements located therein is then introduced.
  • the first and/or second security element processes the received electronic coin data records in the presence or receipt of a plurality of electronic coin data records according to their monetary value. Provision can thus be made for electronic coin data records with a higher monetary value to be processed before electronic coin data records with a lower monetary value.
  • the subscriber unit can be designed, after receiving an electronic coin data record, to connect this to the electronic coin data record already present in the subscriber unit depending on attached information, for example a currency or denomination, and to carry out a corresponding step of connecting. Furthermore, the subscriber unit can also be designed to automatically carry out a switchover after receipt of the electronic coin data set.
  • further information is transferred from the first subscriber unit or first security element to the second subscriber unit during transmission or second security element transmitted, for example a currency.
  • this information can be included in the electronic coin data set.
  • the procedures are not limited to one currency.
  • the payment system can be set up to manage different currencies from different publishers.
  • the methods also allow the electronic coin data record to be converted into book money, ie, for example, the monetary amount can be redeemed in an account held by the participant in the payment system. This repositioning is also a modification. Upon redemption, the electronic coin record becomes invalid and is deemed to have been returned.
  • the at least one initial electronic coin data record is preferably created exclusively by the issuer entity, with the divided electronic coin data records, in particular electronic partial coin data records, also being able to be generated by a subscriber unit. Creating and choosing a monetary amount preferably also includes choosing a high entropy obfuscation amount.
  • the publishing entity is a computing system, which is preferably remote from the first and/or second subscriber unit. After creating the new electronic coin record, the new electronic coin record is masked in the issuer instance by applying the homomorphic one-way function to the new electronic coin record to obtain a masked new electronic coin record accordingly. Furthermore, additional information needed to register the creation of the masked new electronic coin record in the remote coin register is calculated in the issuer entity.
  • This additional information is preferably proof that the (masked) new electronic coin data record originates from the issuing authority, for example by signing the masked new electronic coin data record.
  • the issuing entity signs a masked electronic coin data record with its signature when the electronic coin data record is generated.
  • the signature of the issuing authority is stored in the coin register.
  • the signature of the issuing authority is different from the signature generated by a subscriber unit or a security element.
  • the issuer entity can preferably deactivate an electronic coin data record that is in their possession (that is, of which they know the monetary amount and the obfuscation amount) by using the masked electronic coin data record to be deactivated with the homomorphic one-way function and prepares a disable command for the coin register.
  • a part of the deactivation command is preferably also the proof that the deactivation step was initiated by the issuing authority, for example in the form of the signed masked electronic coin data set to be deactivated.
  • range checks for the masked electronic coin record to be deactivated could be included in the deactivate command. Disabling may be the result of a return.
  • the deactivation of the masked electronic coin data set is then registered in the remote coin register.
  • the deactivation step is triggered with the deactivation command.
  • the create and deactivate steps preferably take place in secure locations, especially not in the subscriber units.
  • the steps of creation and deactivation are carried out or initiated only by the publishing entity. These steps preferably take place in a secure location, for example in a hardware and software architecture that was developed for processing sensitive data material in insecure networks.
  • the deactivation of the corresponding masked electronic coin data set has the effect that the corresponding masked electronic coin data set is no longer available for further processing, in particular transactions. However, in one embodiment it can be provided that the deactivated, masked electronic coin data record remains in the archives of the issuing authority.
  • the fact that the deactivated masked electronic coin data set is no longer valid or returned can be identified, for example, using a flag or another coding, or the deactivated masked electronic coin data set can be destroyed and/or deleted.
  • the deactivated electronic coin record is also physically removed from the subscriber unit or security element.
  • processing operations for the electronic coin data sets and the corresponding masked electronic coin data sets are made possible by the method according to the invention.
  • Each of the processing operations (in particular creating, deactivating, dividing, connecting and switching over) is registered in the coin register and appended there in unchangeable form to the list of previous processing operations for the respective masked electronic coin data set.
  • Each of the processing operations initiates the process of creating and encrypting a transaction record, for example.
  • the registration is independent of the payment process between the subscriber units, both in terms of time and place (spatial).
  • the creation and destruction up to the destruction of money require additional approval, for example in the form of a signature, by the issuing authority to be registered in the coin register (ie to be logged).
  • Processing in the direct transaction layer only affects the ownership and/or the assignment of the coin data records to subscriber units of the respective electronic coin data records.
  • a registration of the respective processing in the coin register or the monitoring register is implemented, for example, by corresponding list entries in a database that includes a series of markings that must be carried out by the coin register.
  • a possible structure for a list entry includes, for example, column (s) for a predecessor coin data set, column (s) for a successor coin data set, a signature column for the issuer instance, a signature column for the sending and / or receiving security element, a Signature column for coin division operations and at least one marking column.
  • a change (modification) is definitive if and the required markings have been validated by the coin register or the monitoring register, i.e.
  • At least two, preferably three or even all of the aforesaid flags can also be replaced by a single flag which is then set if all tests have been successfully completed.
  • the two columns for predecessor data sets and successor data sets can each be combined into one in which all coin data sets are listed together. In this way, more than two electronic coin data sets could then be managed per field entry, and thus, for example, a split into more than two coin data sets could be implemented.
  • a masked electronic coin data set is invalid if one of the following checks applies, i.e. if:
  • the masked electronic coin record is not the successor of a valid masked electronic record unless signed by the issuing authority;
  • the monetary amount of the masked electronic coin data record means that a limit value for a maximum permissible monetary amount, in particular per unit of time, is exceeded and the required deanonymization is rejected by the corresponding subscriber unit;
  • the payment system is preferably designed to carry out the above-mentioned method and/or at least one of the embodiment variants.
  • a further aspect relates to a currency system comprising an issuer entity, a coin register layer, a first security element and a second security element, the issuer entity being designed to create an electronic coin data record.
  • the masked electronic coin data set is designed to be demonstrably created by the issuing authority.
  • the verification layer is designed to perform a registration step as set forth in the above method.
  • the security elements i.e. at least the first and second security element, are suitable for performing one of the above-mentioned methods (i) for transmission and (ii) for generating + encrypting + initiating.
  • the issuing entity is authorized to initially create an electronic coin data record and finally withdraw it.
  • Processing for example the step of connecting, splitting and/or switching, can and preferably is performed by a subscriber unit.
  • the deactivation processing step can preferably only be carried out by the publishing entity.
  • the coin register, the monitoring register and the issuer entity are preferably arranged in a common server entity or are present as a computer program product on a server and/or a computer.
  • the transaction register is preferably arranged in a server instance that is different from the common server instance or is present there as a computer program product.
  • An electronic coin data set can be in a variety of different
  • the electronic coin data set can be presented in the form of a file, for example.
  • a file consists of data that is related in terms of content and is stored on a data carrier, data storage device or storage medium. Each file is initially one-dimensional
  • An application program or an operating system of the security element and/or the terminal interprets this bit or byte sequence as text, an image or a sound recording, for example.
  • the file format used can be different, for example it can be a pure text file that represents the electronic coin data set. In particular, the monetary amount and the blind signature are mapped as a file.
  • the electronic coin data record is, for example, a sequence of American Standard Code for Information Interchange, or ASCII for short, characters.
  • ASCII American Standard Code for Information Interchange
  • the monetary amount and the blind signature are shown as this sequence.
  • the electronic coin record can also be in a subscriber unit from a
  • the electronic coin data record can be received as a QR code in a subscriber unit and can be output from the subscriber unit as a file or character string.
  • the data store is an internal data store of the subscriber unit.
  • the electronic coin data sets are stored here. This ensures easy access to electronic coin data records.
  • the data memory is in particular an external data memory, also called online memory.
  • the security element or the subscriber unit has only one means of access to the electronic coin data records that are stored externally and thus securely.
  • the security element or subscriber unit is lost or if the security element or subscriber unit malfunctions, the electronic coin data records are not lost. Since owning the (unmasked) electronic coin records is equivalent to owning the monetary amount, using external data storage allows money to be stored and managed more securely.
  • the subscriber unit preferably has an interface for communication using a standard Internet communication protocol, for example TCP, IP, UDP or HTTP.
  • the transmission may include communication over the cellular network.
  • a communication protocol for wireless communication for wireless communication.
  • near-field communication is provided, for example by means of a Bluetooth protocol or NFC protocol or IR protocol; WL AN connections or mobile phone connections are conceivable as an alternative or in addition.
  • the electronic coin data set is then adapted according to the protocol properties or integrated into the protocol and transmitted.
  • the interface for issuing the at least one electronic coin data record is a data interface for providing the electronic coin data record to the other subscriber unit using an application.
  • the electronic coin data set is transmitted here using an application.
  • This application then transfers the electronic coin data record in an appropriate file format.
  • a file format specific to electronic coin records can be used.
  • the coin data record is an ASCII character string or a text message, such as SMS, MMS, instant messenger (like Threema or WhatsApp).
  • the coin record is transmitted as an APDU character string.
  • a purse application can also be provided.
  • the exchanging subscriber units preferably ensure that an exchange using the application is possible, ie that both subscriber units have the application and are ready to exchange.
  • the subscriber unit also has an interface for receiving electronic coin data records.
  • the interface for receiving the at least one electronic coin data record is an electronic detection module of the security element or terminal device, set up to detect an electronic coin data record presented in visual form.
  • the detection module is then, for example, a camera or a barcode or QR code scanner.
  • the interface for receiving the at least one electronic coin dataset is a protocol interface for wirelessly receiving the electronic coin dataset from another security element or end device using a communication protocol for wireless communication.
  • a communication protocol for wireless communication for wireless communication.
  • near-field communication is provided, for example by means of a Bluetooth protocol or NFC protocol or IR protocol.
  • WLAN connections or mobile radio connections are conceivable.
  • the interface for receiving the at least one electronic coin data record is a data interface for receiving the electronic coin data record from the other subscriber unit using an application.
  • This application then receives the coin data set in a corresponding file format.
  • a file format specific to coin records can be used.
  • the coin data record is transmitted as an ASCII character string or as a text message, such as SMS, MMS, Threema or WhatsApp.
  • the coin record is transmitted as an APDU character string.
  • the transfer can take place using a wallet application.
  • the subscriber unit comprises at least one security element reader, set up to read a security element; a random number generator; and/or a communication interface to a vault module and/or bank institution with access to a bank account to be authorized.
  • the data store is a shared data store that can be accessed by at least one other subscriber unit, each of which has a Has application, this application is set up to communicate with the coin register for the appropriate registration of electronic coin part data records.
  • a solution is therefore proposed here that issues digital money in the form of electronic coin data sets, which is based on the use of conventional (analog) banknotes and/or coins.
  • the digital money is represented here by electronic coin data records.
  • (analogue) banknotes these electronic coin records will also be usable for all forms of payments, including peer-to-peer payments and/or POS payments. Knowing all the components (in particular the monetary amount and the obfuscation amount) of a valid electronic coin dataset is tantamount to owning (owning) the digital money. It is therefore advisable to treat these valid electronic coin data records confidentially, i.e. to store them in a security element/safe module (of an end device) and process them there, for example.
  • masked electronic coin data records are held in the coin register as a unique, corresponding public representation of the electronic coin data record. Knowing or possessing a masked electronic coin record does not constitute possession of money. Rather, it is like verifying the authenticity of the analog currency.
  • the coin register also contains, for example, markings about executed and planned processing of the masked electronic coin data set.
  • a status of the respective masked electronic coin data record is derived from the markings for the processing, which indicates whether the corresponding (non-masked) electronic coin data record is valid, i.e. ready for payment. Therefore, a receiver of an electronic coin data record will first generate a masked electronic coin data record and have the validity of the masked electronic coin data record authenticated by the coin register.
  • a great advantage of this solution according to the invention is that the digital money is distributed to terminals, dealers, banks and other users of the system, but no digital money or other metadata is stored in the coin register or the monitoring register - ie shared entities.
  • the proposed solution can be integrated into existing payment systems and infrastructures.
  • a payment process can take place with banknotes and/or coins, but the change or change is available as an electronic coin data set.
  • ATMs with an appropriate configuration, in particular with a suitable communication interface, and/or mobile terminals can be provided for the transaction.
  • an exchange of the electronic coin data record for banknotes or coins is conceivable.
  • the steps of creating, switching, splitting, connecting and deactivating (returning) listed here are each triggered by a corresponding create, switching, splitting, connecting or deactivating command (return commands).
  • Fig.la,b an embodiment of a payment system according to the prior art
  • FIG. 2 shows an embodiment of a payment system according to the invention
  • FIG. 3 shows a further development of the exemplary embodiment of a payment system from FIG. 2;
  • FIG. 4a shows an embodiment of a coin register of the payment system according to the invention in a first mode
  • 4b shows an embodiment of the coin register of the payment system according to the invention in a second mode
  • FIG. 5 shows a further development of the exemplary embodiment of a payment system from FIG. 2;
  • FIG. 6 shows an exemplary embodiment of a method flow chart of a method according to the invention in a subscriber unit
  • FIG. 7 shows an exemplary embodiment of a method flow chart of a method according to the invention in a transaction register
  • FIG. 8 shows an exemplary embodiment of an encryption and decryption of a transaction data record
  • Fig. 9 shows an alternative development of the embodiment of a payment system
  • FIG. 10 shows an exemplary embodiment of a data structure in the coin register and monitoring register
  • FIG. 11 shows one embodiment of a system according to the invention for splitting and switching and direct transmission of electronic coin records
  • FIG. 12 shows an embodiment of a payment system according to the invention for connecting electronic coin data sets
  • FIG. 13 shows an exemplary embodiment of a method flow chart of a method according to the invention and corresponding processing steps of a
  • FIG. 14 shows an exemplary embodiment of a method flow chart of a method according to the invention and corresponding processing steps of a
  • FIG. 17 shows an exemplary embodiment of a sequence of payment processes according to the invention with monitoring of the monetary amounts per subscriber unit;
  • FIG. 18 shows an exemplary embodiment of a sequence of an area confirmation according to the invention.
  • FIG. 1a and 1b show an exemplary embodiment of a payment system BZ according to the prior art. These Fig.la and Fig.lb have already been described in the introduction to the description. It is repeatedly pointed out that a terminal M8 would like to register the coin data record C c as the coin data record C e in the coin register 2 and the coin register 2 determines that the coin data record C b is already invalid. As a result, the coin register 2 accepts neither the supposedly valid coin data set C c nor the coin data set C e to be switched over .
  • the problem can occur when, for example, an attacker with terminal Ml is a further Münz Scheme C b (pirated) at two terminals M2 and M3 directly. As soon as one of the two participants with the terminal M2 registers the coin data record in the coin register 2 (so-called coin conversion), the coin data record C b becomes invalid. An unsuspecting participant with Terminal M3 instead forwards the coin data set C b directly to terminal M5 without having it registered. Only terminal M7 breaks through the direct transmission chain and shows the coin data set C b in coin register 2. At the same time, the subscriber with terminal M2 divides the coin data set C b into coin data sets C c and C x and forwards C c directly to terminal M4.
  • Terminal M4 forwards the coin data set C c directly to terminal M6.
  • Terminal M6 forwards the coin data record C c directly to terminal M8.
  • An attack double issuing of an electronic coin data record
  • M1 is therefore only discovered late in the prior art and a large number of direct transmissions were carried out in an unauthorized manner.
  • the risk that manipulation(s) have been carried out on the electronic coin data set increases.
  • the coin data set should expire, i.e. on the one hand the number of direct transmissions of coin data sets should be limited and on the other hand it should be possible to trace who caused the attack if an attack is detected (Here terminal Ml) has carried out.
  • a method/system is described below in which transaction data from subscriber units (terminals or security elements) are archived in a remote transaction register and can be checked in the event of an official decision.
  • the payment system comprises at least two, preferably a large number of subscriber units TEs, which are also referred to or illustrated below as security elements SEx or terminal devices Mx, and a transaction register.
  • the payment system can also include, for example, at least one issuing authority 1, one or more commercial banks, one (or more) central coin register 2, which registers the coin data sets and checks and logs the modifications to the coin data set. Further examples of payment systems according to the invention are shown in Figs. 6, 7, 14 and 16.
  • the payment system BZ includes at least two security elements SEI and SE2.
  • the SEI and SE2 can be placed ready for operation in respective terminals M1 and M2 and logically or physically connected to the respective terminal M1 and M2.
  • a transaction register 4 of the payment system BZ is shown.
  • an issuing entity 1 for example a central bank, which generates the electronic coin data record C
  • an issuing entity 1 for example a central bank, which generates the electronic coin data record C
  • a register data set RDS for example a masked electronic coin data set Z
  • the register data record RDS is output in step 104, for example by the issuing entity 1 directly or via the first terminal M1 to the coin register 2.
  • the register data set RDS for example the masked electronic coin data set Z, is alternatively generated by the first terminal M1 (or second terminal M2) and sent to the coin register 2 in step 104.
  • a transaction data set TDS is generated in the first terminal M1.
  • the transaction data record TDS has a subscriber ID of the sending terminal device Ml, a subscriber ID of the receiving terminal device M2, optionally a transaction number, optionally a monetary amount of the coin data record, optionally a masked coin data record Z corresponding to the electronic coin data record C (masking is explained later ) and optionally a transaction time.
  • Each subscriber ID of a terminal device is assigned to a natural person in the payment system, which is carried out and also managed in the person assignment 7 . This assignment 7 is only carried out after the person has been successfully identified by presenting an identity card or passport. This assignment 7 can be changed at the request of the person, for example when changing the subscriber unit or adding another subscriber unit.
  • the transaction data record TDS After the transaction data record TDS has been generated, it can be encrypted by the first terminal M1 using a cryptographic key; this is shown in more detail in FIG.
  • the transaction data can be read out
  • the payment system BZ of FIG. 2 accordingly introduces at least three different layers for the coin data set-based transmission. These layers handle different tasks, have different interest groups, different attack vectors, and different implementations. The separation of these specific tasks within the BZ payment system into isolated layers reduces the complexity within the individual layers and makes the payment system more flexible, more secure and more resistant to attacks. The advantage of this multi-layer payment system BZ is that data relevant to data protection is strictly separated from the rest of the payment ecosystem and is only made accessible on the basis of strict organizational processes.
  • the payment system shown in FIG. 2 has a three-layer structure. In a first layer, the issuing authority 1, for example a central bank, is responsible for money creation and destruction, as will be explained later. Commercial banks (not shown) can store coin data sets C, for example in vault modules that are designed as highly secure modules, for example as HSMs. This layer distributes money to users and sends or receives money to/from the central bank.
  • the person assignment 7 is also arranged in this first layer.
  • the issuing authority 1 can be reached for the TEs, for example, via an air interface, for example mobile radio or WLAN or NFC.
  • the provision of subscriber units TE must meet regulatory requirements.
  • all subscriber units TE should be provided by an entity authorized to issue subscriber units TE.
  • the person assignment (person register 7) is responsible for managing the personal identities of the users (natural persons).
  • this can be realized by providing each subscriber unit with an individual key and a certificate signed by its intermediate or root CA (Certificate Authority). This means that only subscriber units TE signed by the root CA can set up a secure communication channel, and malicious or modified subscriber units TE with invalid keys are blocked.
  • the unique serial number of each certificate allows an assignment to a specific user to be established if the relationship between the serial number and the user is recorded in the personal register 7 .
  • the coin register 2, the monitoring register 6 and the transaction register 4 are provided in a second layer.
  • This layer is used for the secure process of checking the coin data records C, in particular the validity, the presence of the correct monetary value and the authenticity of the coin data records C in circulation and checks whether coin data records C were issued twice.
  • This layer can be a "distributed network".
  • the BZ payment system is completely private. By default, payment transactions are not traceable, i.e. anonymous. This applies both to the participant (payer, payee) and to the monetary amount (payment amount).
  • the transaction register 4 is provided to set up a criminal prosecution system and/or to allow anonymous - untrustworthy participants in the payment system BZ. It is conceivable to decouple this transaction register 4 from the payment system BZ in order to follow the principle of "separation of concerns". For the sake of simplicity, the trade register 4 is subsequently assigned to the second layer of the payment system BZ. Information that is relevant for tracing a coin data record C is stored in a transaction register 4 (the second layer) as a "trusted entity", ie a trustworthy entity.
  • the purpose of the trade register 4 is to keep data elements (payer, payee, monetary amount) of the payment transactions on the payment system 2 traceable and to track payments with the associated subscriber units TE, their monetary amounts and a transaction time, along with other information.
  • the trade repository 4 can monitor transactions for various scenarios such as money laundering, terrorist financing or tax evasion, but also analyze the usage of a single coin record. No personal information of a natural person is preferably stored in the trade register, only subscriber unit identifiers or their pseudonyms.
  • the subscriber unit can be identified.
  • participant units are not linked to natural persons in order to remain anonymous.
  • participation in the payment system is only permitted with limited functionality or restrictions on monetary amounts.
  • Access to the trade repository can be strictly controlled and the TDS stored there secured.
  • the advantage of this structure is that unauthorized tapping from the trade register does not constitute procurement of money and the monetary amounts cannot be stolen.
  • the trade repository 4 is responsible as a trustworthy authority to protect people's privacy in regular situations and to disclose (encrypted) transaction data sets to TDS if this is necessary due to court decisions or if this is requested by the surveillance repository 6. This can be used to check that no irregular transactions or money operations are taking place, in particular that no (new) money is being created or destroyed illegally.
  • the trade register 4 represents an extension for use cases in criminal prosecution, with the aim of uncovering suspicious transaction data.
  • the transaction register 4 represents an extension for applications in which subscriber units cannot or do not want to authenticate themselves to the coin register 2 .
  • the trade register 4 stores (encrypted) data records about transactions TDS that are (must) be reported by the participants involved and passes them on to the authorities or the monitoring register 6 of the payment system BZ according to a proper procedure.
  • the transaction data records TDS can be stored in encrypted form in the transaction register 4 . This ensures that due process must be followed and no one can access this sensitive transaction data at will.
  • a re-encryption unit can be used in the trade repository 4, which re-encrypts the TDS so that a law enforcement agency only has access to officially approved data. Metadata such as transaction time and participant ID are used to provide the requested data.
  • the transcryption unit of the trade repository 4 can access and decrypt all data.
  • the third layer is a direct transaction layer 3 in which all participants, ie consumers, dealers, etc., participate equally via their subscriber units TE in order to exchange electronic coin data records C.
  • Each subscriber unit TE can have a wallet application to manage coin data sets C.
  • the transmission 105 takes place, for example, wirelessly via WLAN, NFC or Bluetooth, ie preferably locally.
  • the transmission 105 can be additionally protected by cryptographic encryption methods, for example by negotiating a session key or by using a PKI infrastructure.
  • the transmission 105 can also take place using an online data memory, from which the electronic coin data set C is transmitted to the TE2 (M2, SE2).
  • a secure channel is set up between the SEI and the SE2, within the framework of which both SEs authenticate one another.
  • the transmission path between SEI and SE2 is not necessarily direct, but can be an Internet or near-field communication path with entities connected in between (end devices, routers, switches, applications).
  • SEs as a secure environment instead of terminals ME as TEs, a higher level of trust is generated, ie trustworthiness in the payment system BZ is increased.
  • a timer is optionally started at the same time as the eMD C is sent or immediately before or after it. Before that, the eMD C can be invalidated and then no longer used by the SEI for actions (as described below).
  • the eMD C is thus blocked in the payment system BZ due to a transmission process 105 that has already been initiated (and has not yet ended). This prevents double spending. Invalidating allows for easy handling during the transfer process 105. If the eMD C is properly received in the SE2, the SE2 generates an acknowledgment of receipt and sends it back to the SEI. The acknowledgment of receipt from the SE2 can be sent as a deletion request, because the eMD C can (may) only be validated and used in the SE2 after the eMD C has been deleted in the SEI. Optionally, the deletion of the eMD C can be displayed by the SEI.
  • an amount display of the SEI (or a terminal ME1 in which the SEI is logically located) is updated.
  • the monetary amount of the eMD C is subtracted from an amount of the SEI available for payment transactions.
  • a deletion confirmation can be sent from the SEI to the SE2. This serves as an acknowledgment that the eMD C is no longer available in the SEI and can therefore be validated in the SE2.
  • the SE2 can convert the status of the eMD C in the SE2 into an active status, the eMD C is thus validated and can be used for further payment transactions or actions (split, combine, switch) in the SE2 from this point in time .
  • the eMD C of the SE2 in coin register 2 is switched to the SE2 (see below), whereby the eMD C is registered to the SE2 (step 104).
  • a transmission error in the transmission 105 can be determined in the SEI, for example by exceeding a predefined period of time, indicated by a timer or by receiving an error message from SE2 or the terminal M1 or the other terminal M2 (not shown). For example, a counter value can be incremented with each new attempt to transmit the eMD C (RETRY) and if a maximum permissible number of retries is exceeded, for example 10 or 5 or 3 times, it is decided in step 308 automatically and independently of the error that no new Sending attempt (RETRY) is carried out, but the transmission 105 is to be ended as unsuccessful and a ROLLBACK has to be carried out.
  • RETRY a maximum permissible number of retries
  • the status of the eMD is reported to the coin register 2 by the SEI.
  • a connection is then established with coin register 2 to query the status of the eMD C. If the coin register 2 continues to report an inactive status to the eMD C (registered on the SEI), no transaction error (manipulation attempt) is assumed. However, if the coin register 2 reports an active status to the eMD C or a registration to another SE, a transaction error (attempted manipulation) is assumed and the payment system is alarmed.
  • the transaction data record TDS of the SEI is used as evidence.
  • the electronic coin data record C can be requested in advance from an issuing entity 1 and optionally received by a terminal M (or an SE) or the issuing entity 1 or another payment system. Steps 104 and 105 may correspond to steps 104 and 105 of FIG.
  • An action (split, connect, switch, transfer, redeem, change) on the eMD C can correspond to one of the actions of FIGS. 9 to 12.
  • a genuine random number is generated as the concealment amount n.
  • the concealment amount n is known in the direct transaction layer 3 and also in the issuer instance 1, it is secret for the transaction register 4, the monitoring register 6 and the coin register 2.
  • the concealment amount n is linked to a monetary amount Ui.
  • An i-th electronic coin data set according to the invention could therefore read:
  • Ci ⁇ u,; r,j (1)
  • the electronic coin data set C can include at least one check value.
  • the check value represents, for example, the number of offline transmissions (payment transactions) with this electronic coin data set.
  • the check value represents, for example, the number of off-line transmissions (payment transactions) of the subscriber unit without performing any registration.
  • the electronic coin data set C can include a coin identifier M-ID.
  • the coin identifier is, for example, a unique number that is unique in the BZ payment system.
  • the coin identifier M-ID is a random number generated by the subscriber unit or the issuer entity 1 .
  • a valid electronic coin record can be used for payment.
  • the owner of the two values Ui and r therefore owns the digital money.
  • the digital money is defined by a pair consisting of a valid electronic coin data set Ci and a corresponding masked electronic coin data set Zi.
  • a register data set, RDS for short, is assigned to the electronic coin data set.
  • a masked electronic coin data set Zi as RDS is obtained by applying a homomorphic one-way function f(Ci) according to equation (2):
  • This function f(Ci) is public, i.e. every system participant can call up and use this function.
  • This function f(Ci) is defined according to equation (3):
  • H and G are generator points of a group G in which the discrete logarithm problem is hard, with the generators G and H for which the discrete logarithm of the other base is unknown .
  • G and H are generator points of an elliptic curve encryption, ECC, - ie private keys of the ECC are.
  • Equation (3) is a "Pederson commitment for ECC" that ensures that the monetary amount Ui can be granted to a coin register 2, i.e. "committed”, without revealing it to the coin register 2.
  • the RDS can also include an amount category in addition to the masked coin data record Zi.
  • the amount category is a pseudonymised form of the monetary amount Ui of the electronic coin data record C.
  • the amount category is a range specification (from to) in which the monetary amount Ui lies.
  • the amount category is a range threshold value (greater than; smaller than), above or below which the monetary amount Ui lies.
  • the amount category is a rounded value of the monetary amount Ui.
  • the amount category is a rounded up value of the monetary amount Ui. This means that the RDS is pseudonymous in terms of amount and identity.
  • the RDS can include a coin identifier M-ID in addition to or instead of the masked coin data record Zi. This creates a clear reference to the electronic coin data set C in the RDS.
  • the RDS may comprise a pseudonym P of the subscriber unit.
  • the pseudonym can be managed in the person assignment 7 . This means that the RDS is anonymous in terms of amount and pseudonymous in terms of identity.
  • the RDS can also include a check value p of the coin data set.
  • an RDS can be equated with a masked coin data set Z, since this is a very preferred embodiment.
  • the coin register 2 is therefore only sent (revealed) to the RDS, for example the masked coin data record Zi, which is shown in FIG. 2 as step 104 (registration, registration request).
  • Equation (3) is a one-way function, which means that computing Zi from Ci is easy because an efficient algorithm exists, whereas computing Ci from Zi is very difficult because there is no polynomial-time solvable algorithm.
  • equation (3) is homomorphic for addition and subtraction, which means that:
  • Equation (3) allows monitoring of valid and invalid electronic Münz Schemesn Ci to lead on the sole basis of the masked Münz Scheme Zi and to ensure that no new monetary amount U j has been created.
  • the coin data set Ci can be divided according to equation (1) into:
  • Equation (9) can be used, for example, to check a “symmetrical or asymmetrical splitting” processing or a “symmetrical or asymmetrical splitting” processing step of a coin data record according to FIG. , Ck has.
  • the condition of equation (9) is checked to validate split coin data sets and C k and invalidate coin data set Ci.
  • FIG. 11 or 14 Such a division of an electronic coin record Ci is shown in FIG. 11 or 14.
  • FIG. Electronic coin data records C can also be combined (connected) in the same way, see FIG. 12 or 13 and the explanations relating thereto.
  • Cij aj H + bj G (9c)
  • Cij - aj H (9d) it being possible in one embodiment to carry out a ring signature only for specific bits.
  • At least one test value pu can also be kept in the electronic coin data record C as a further data element.
  • This test value p,i is incremented as subscriber units TE1, TE2 with each direct transmission 105 of this electronic coin data record C between subscriber units TE1, TE2, ie terminals M1, M2 or security elements SEI, SE2.
  • a counter value pu can also be managed or determined, which includes the check value pu, for example as the sum of the previous (registered) counter value pu and the check value pu, in order to determine whether the coin data record C is to be returned.
  • Each action with the coin data set C increases this counter value pu.
  • Different action types weight the counter value pu differently, so that, for example, a direct transfer of the coin data record C has a higher weight than a modification (dividing, combining, Switch). In this way, the service life and the actions carried out in a coin data record C are evaluated and criteria for its return are defined according to the actions carried out.
  • the check value pu and also the counter value pu map the life cycle of the coin data set C, on the basis of which a decision is then made about a return.
  • a test value p can also be provided in a subscriber unit TE (i.e. the terminals M1, M2 or security elements SEI, SE2 shown in FIG. 2), which indicates the number of coin data records C already transmitted without (immediate) associated transmission of an encrypted transaction data record TDS to the trade repository 4 represents.
  • This test value p is compared with a threshold value X when a connection error is detected (in step 307 of FIG. 6). In the process, it is determined whether a further (offline) transmission 105 may be carried out (payment system specification) or not.
  • the transaction register 4 is shown in FIG.
  • the transaction register 4 is in communication with the monitoring register 6 in order to register the RDS or anonymised or pseudonymised transaction data records TDS* in the monitoring register 6 .
  • a subscriber unit identifier in the decrypted transaction data record TDS is replaced by a pseudonym P of the subscriber unit TE.
  • a monetary amount in the transaction data record TDS is replaced by an amount category.
  • This can be performed by an HSM in the transaction repository 4.
  • the pseudonymised transaction data TDS * and/or the amount-categorized transaction data TDS * are sent to the monitoring register 6 (according to step 412 of FIG. 7), while the transaction data records TDS generated by the subscriber unit TE are stored in the transaction register 4.
  • an RDS is calculated from the electronic coin data set Ci, for example a masked electronic coin data set Zi, for example in the SEI, using equation (3) and this RDS is registered in a monitoring register 6 together with the test value pi.
  • the transmitted electronic coin data set Ci is received as Ci * .
  • the SE2 Upon receipt of the electronic coin data set Ci * , the SE2 is in possession of the digital money that the electronic coin data set Ci * represents. With the direct transmission 105 it is available to the SE2 for further actions.
  • SEI Due to the higher degree of trustworthiness when using SEs, SEI, SE2 can trust one another and, in principle, no further steps are necessary for the transmission 105 . However, the SE2 does not know whether the electronic coin data set Ci * is actually valid. To further secure the transmission 105, further steps can be provided in the method, as will be explained below.
  • another RDS for example the masked transmitted electronic coin data record Zi*
  • the RDS ie, for example, the masked, transmitted electronic coin data record Zi *
  • the RDS is then transmitted to the coin register 2 in step 104 and searched for there. If both RDSs match with regard to the same coin data set C, i.e. for example a match with a registered and valid masked electronic coin data set Zi, the validity of the received coin data set Ci * is displayed to the SE2 and it applies that the received electronic coin data set Ci * is equal to the registered electronic Coin record Ci is.
  • the validity check can be used to determine that the received electronic coin data set Ci * is still valid, ie that it has not already been used by another processing step or in another transaction/action and/or has undergone further modification was.
  • the electronic coin data record Ci authorizes payment, i.e. to carry out a transaction successfully, in particular if the coin data record Ci is valid, for example if the electronic coin data record Ci has an active status.
  • the status is preferably only set to an active status upon receipt of the deletion confirmation from the SEI.
  • the masked electronic coin records Zi are registered in the coin register 2, such as a public database. This registration 104 first makes it possible to check the validity of the electronic coin data set Ci, for example whether new monetary amounts were (illegally) created.
  • the masked electronic coin data sets Zi are stored in the coin register 2. All processing of the electronic coin data record Zi is registered there or in the monitoring register 6, whereas the actual transfer of the digital money is recorded in a (secret, i.e. not known to the public) direct transaction layer 3 of the Payment system BZ takes place. In addition, monitoring of the coin data set C and the subscriber unit TE can be recorded in a monitoring register 6 in this payment system BZ.
  • the electronic coin data sets C can be modified to prevent multiple spending or to ensure more flexible transmission 105 .
  • Examples of operations are listed in Table 1 below, whereby a corresponding processing step is also carried out with the specified command:
  • Table 1 Number of operations that can be carried out per processing of a C in the TE or the publisher instance
  • Table 1 shows that for each coin data set, each of the processing (modification) “Create”, “Return”, “Split”, “Connect” and “Switch” different operations “Create Signature”; “Create random number”; “Create Mask”; “Range checking” can be provided, with each of the processing operations being registered in the coin register 2.
  • each of the processing operations in the monitoring register 6 is appended in unalterable form to a list of previous processing operations for masked electronic coin records Zi.
  • the monitoring register 6 thus represents an archive for RDS concerning previous coin data sets the operations of all other processing can be carried out on the subscriber units TE, ie the terminals M or their security elements SE.
  • the number of operations for each processing is marked in Table 1 with "0", "1" or "2".
  • the number “0” indicates that a subscriber unit TE or the issuer entity 1 does not have to carry out this operation for this processing of the electronic coin data record C.
  • the number “1” indicates that the subscriber unit TE or the issuer entity 1 must be able to perform this operation once for this processing of the electronic coin data record C.
  • the number “2” indicates that the subscriber unit TE or the issuer entity 1 must be able to carry out this operation twice for this processing of the electronic coin data set.
  • one embodiment can also provide for an area check to be carried out by the publishing entity 1 when creating and/or deleting.
  • Table 2 below lists the operations required for the coin register 2 and/or the monitoring register 6 for the individual processes: Table 2 - Number of operations that can be performed per processing of a C in the coin register
  • Table 3 shows the components to be preferably installed for the system participants in the payment system of FIG. 1:
  • Table 3 shows an overview of the components to be used preferably in each system participant, i.e. the issuing entity 1, a subscriber unit TE and the register entities, namely the coin register 2, the monitoring register 6, the transaction register 4.
  • the subscriber units TE can be designed using an e-wallet for electronic coin data sets Ci (with the test value p, pn pn), i.e. as an electronic wallet with a memory area in which a large number of coin data sets Ci can be stored, and thus, for example, in the form of an application be implemented on a smartphone or IT system of a retailer, a commercial bank or another market participant.
  • the components in the subscriber unit TE as shown in Table 3 are implemented in software. It is assumed that the coin register 2, the trade register 4 and/or the monitoring register 6 is based on a server or on a DLT and is operated by a number of trusted market participants.
  • an RDS relating to the electronic coin data record C can be replaced by an RDS relating to the electronic coin data record C or a modified electronic coin data record C to be registered.
  • Any previous versions or earlier modifications are then managed, for example, in the monitoring register 6 as a monitoring data record ÜDS and are made available for this purpose by the coin register 2 to the monitoring register 6 during the replacement process and are kept there.
  • the history of the electronic coin data record C can thus be logged by the monitoring register 6 .
  • the monitoring register 6 stores monitoring data sets, ÜDS for short.
  • a ÜDS is formed from at least one TDS and at least one RDS in the monitoring register 6.
  • a ÜDS corresponds to exactly one electronic coin data set C and is formed in monitoring register 6 from exactly one TDS, which also corresponds to the electronic coin data set, and exactly one RDS, which also corresponds to the electronic coin data set. This formation occurs after the TDS has been provided by the trade repository and the RDS has been provided by the coin repository.
  • a monitoring data record ÜDS relates to exactly one payment transaction.
  • an LJDS can also relate to a plurality of electronic coin data sets C, for example all electronic coin data sets C that were sent by a subscriber unit TEx within a predefined period of time.
  • an ÜDS is formed, for example, from a number of TDSs relating to this subscriber unit TEx in the period.
  • the ÜDS is formed, for example, from several RDS relating to modifications to coin data records C. The modifications are initiated and/or requested and/or status checked by the TEx within the period.
  • a ÜDS then relates to a plurality of TDS (corresponding to the respective electronic coin data records C of this subscriber unit TE, preferably in this transaction period) and at least one, preferably several register data records RDS (also corresponding to the respective electronic coin data records C of this subscriber unit TE, preferably in this transaction period) formed in the monitoring register 6.
  • a monitoring data record ÜDS then relates to a number of payment transactions for this subscriber unit TEx, preferably within a predefined period of time.
  • the monitoring data set ÜDS can be evaluated by the monitoring register 6 .
  • This evaluation relates to checking for duplicate issuing of the electronic coin data records C or the unauthorized generation of monetary amounts by a subscriber unit TE and/or also checking aging of electronic coin data records C.
  • By forming and evaluating in the monitoring register 6 it can be determined, for example, that a subscriber unit TE has issued a coin data set C twice or has changed a monetary amount.
  • it can be established that a coin data record C has not been used for a predefined period of time and the subscriber TE is informed of this or an automatic return to the issuer entity 1 is initiated.
  • FIG. 3 shows a further development of the exemplary embodiment of a payment system from FIG. 2. Reference is made to the explanations of FIG. 2 to avoid repetition. The configurations of FIG. 3 can also be combined with the configurations of FIG. 2 .
  • FIG. 3 the data flow of electronic coin datasets C, RDS, TDS and ÜDS in the payment system BZ is illustrated by different lines.
  • the transmission 105 of electronic coin data records C is represented by a dotted line between two subscriber units TE. This transmission 105 represents a payment process (payment transaction) in the payment system BZ.
  • TDSs are created by a TE and made available to the trade repository 4 (see FIGS. 6 to 8).
  • the TDS can also be sent directly to a monitoring register 6 be sent.
  • a communication channel between subscriber unit and coin register 2 is used to send the TDS to the monitoring register.
  • coin register 2 is denied access to the TDS.
  • the ÜDS are then formed in the monitoring register 6 from the TDS and the RDS.
  • data elements that can lead to a TDS are also shown as a solid line in the BZ payment system.
  • subscriber identifiers or pseudonyms P derived therefrom are kept in the personal register 7 or a commercial bank 1a or a service server (not shown).
  • This assignment is then made available to the transaction register 4 in order, for example, to pseudonymize a TDS of a subscriber unit TE1 in order to provide a pseudonymized TDS * to the monitoring register 6 .
  • the pseudonymization of a TDS will be explained in more detail with steps 410 and/or 411 of FIG.
  • a TE (here the TE2) is authenticated at the coin register 2.
  • subscriber identifiers or pseudonyms P are queried.
  • the coin register 2 is aware of subscriber identifiers and can use them in a second mode (Fig. 4b) to provide TDS to the monitoring register 6.
  • a TE (here the TE2) does not authenticate itself at the coin register 2.
  • the coin register 2 is therefore not aware of subscriber identifiers and only provides RDS to the monitoring register 6 in a first mode (FIG. 4a).
  • FIG. 3 the sending of RDS in the payment system BZ is shown with a dashed line.
  • RDS are created by a TE and made available to the coin register 4 (according to FIG. 2).
  • the RDS are provided in both modes of the coin register of the monitoring register 6 in order to check the validity, the status, the modifications, the test values and the lifetime (return value) of an electronic coin data record C.
  • an assignment of the person register 7 or the TE is made known to the coin register 2 in order, for example, to pseudonymize an RDS in order to provide a pseudonymized RDS * to the monitoring register 6 .
  • Pseudonymizing an RDS is similar to steps 410 and/or 411 of FIG. 7, but is independent of pseudonymizing a TDS.
  • Fig. 3 three logical representatives of interfaces are shown for the coin register, an interface of the coin register 2 to the TE, an interface of the coin register 2 to the monitoring register 6 and an interface to the issuing authority 1. Not shown but conceivable is an interface to a transaction register 4, to forward TDS to monitor register 6. These interfaces can be designed physically as one interface and only be designed as logically separate.
  • a mode switch MODE in coin register 2 sets either the first mode of the coin register 2 in which only the RDS are provided to the monitoring register 6 or sets the second mode of the coin register 2 in which the RDS and the TDS are sent to the monitoring register 6 to be provided.
  • the TDS can be obtained from the authentication data.
  • FIG. 4a shows an embodiment of a coin register 2 of the payment system BZ according to the invention in a first mode.
  • the interface to the TE of the coin register 2 receives a registration and/or status request from the TE regarding an electronic coin data set C. It is determined that the TE sent these requests anonymously. There is no authentication, so the coin register 2 is operated in the first mode.
  • the registration requirements can be checked using the status verifier and the TE can receive a corresponding status message.
  • further checks can be requested using status verifiers and change verifiers, and an RDS can be made available to monitoring register 6 for these purposes.
  • the TDS that may be necessary to check the requirements of the TE are not provided by the coin register 2 and can, for example, be queried directly from the TE or the transaction register 4 at the request of the monitoring register 6.
  • FIG. 4b shows an embodiment of the coin register 2 of the payment system BZ according to the invention in a second mode.
  • the interface to the TE of the coin register 2 receives a registration and/or status request from the TE regarding an electronic coin data set C. It is determined that the TE can/will authenticate itself at the coin register 2. Authentication takes place in which a subscriber ID or a pseudonym is queried from the coin register 2 and received in the coin register 2 . The successful authentication of the TE results in the coin register 2 being operated in the second mode.
  • the registration requirements can be checked using the status verifier and the TE can receive a corresponding status message.
  • TDS that may be necessary to check the requirements of the TE are identified by the subscriber ID provided with the authentication or its pseudonym in Used in combination with the RDS from coin register 2 to provide TDS to monitor register 6.
  • FIG. 5 shows a further development of the exemplary embodiment of a payment system from FIG. To avoid repetition, reference is made to the explanations of FIG. 2 and FIG. 3 .
  • the configurations of FIG. 5 can also be combined with the configurations of FIG. 2 .
  • a masked electronic coin data set Z described above is used as the RDS. This is anonymous in terms of amount and identity.
  • This cryptographic key is, for example, a public key part of a corresponding composite private key part.
  • This private key part is composed of three partial keys 8a, 8b, 8c, the partial keys 8a, 8b, 8c being added or XORed, for example.
  • This combination of the partial keys 8a, 8b, 8c takes place either in the first terminal M1 or in the transaction register 4.
  • This combination of the partial keys 8a, 8b, 8c is, for example, secret throughout the system. Knowing or possessing only one partial key 8a, 8b, 8c does not allow the transaction data record TDS to be decrypted.
  • FIG. 8 shows an embodiment for encrypting and decrypting a transaction data record TDS.
  • the encrypted transaction data record TDS is sent from the first terminal M1 to the transaction register 4 and stored there.
  • the time of sending is preferably closely linked to the transmission 105 of the electronic coin data record, so that the transaction register 4 is always up to date on the transactions carried out in the payment system BZ.
  • an official decision for example a court decision, could be ordered to decrypt the encrypted transaction data set TDS in order to uncover and analyze the transaction recorded therewith (the transmission 105).
  • all stored transactions would then be queried, for example, at the transaction register 4 for a terminal M (using the identifier) over a specific point in time or a specific period of time.
  • other attributes of the transaction data such as the monetary value of the coin data sets, the respective transaction partners, etc., could be queried.
  • the transaction data can be read out decrypted by a plurality of remote entities as authorized parties generating (or providing) a decryption key by combining their partial keys.
  • the remote entities are, for example, law enforcement agencies, notaries, the Ministry of Justice, a central bank or others. All remote entities (authorized parties) only have partial keys 8a, 8b, 8c of the decryption key. All members or a minimum number n of m remote entities are required to jointly decrypt the transaction data record TDS. From a technical point of view, the individual sub-keys 8a, 8b, 8c of the various remote entities are assembled into a common private key part by addition or by bit-by-bit XOR linking.
  • This private key part (which corresponds to the corresponding public key part of the encryption) is then used to decrypt the transaction data set TDS.
  • This concept guarantees that no remote entity alone can decrypt the TDS transaction record and thus bypass other entities. If the concept does not depend on the availability of all m remote entities, threshold cryptography could be applied to use a subset n of these subkeys 8a, 8b, 8c. This subset n then defines the minimum number of partial keys 8a, 8b, 8c to be combined.
  • storing transaction data in the trade repository can fulfill the following additional tasks:
  • the issuing authority for example a central bank, always knows the exact amount of coin data sets currently in circulation. It is thus possible to track and deactivate both subscriber units and coin data sets that have not participated in the payment system BZ for a long period of time, for example 1 year, in order not to jeopardize the security of the payment system BZ.
  • step 301 a transaction data record TDS is generated.
  • the transaction data record TDS includes the subscriber identifiers from the first subscriber unit TE1 (sending TE) and from the second subscriber unit TE2.
  • information about the electronic coin data set C to be transmitted (or transmitted) is included, for example the monetary value v.
  • the masked electronic coin data set Z can be introduced into the TDS.
  • a transaction time can be contained in the TDS, which characterizes the time of the transmission 105 of the electronic coin data record C between the two subscriber units TE.
  • the time of generation 301 can be closely coupled in time to the time of transmission 105 .
  • a specification of the payment system BZ can require that the electronic coin data record C must first be transmitted (step 105) before the encrypted transaction data record TDS is to be sent.
  • the generated transaction data record TDS is encrypted.
  • the first subscriber unit TE1 has a public key part K, which is made up of partial keys from different remote entities.
  • the key composition is shown in FIG.
  • the subscriber unit TE1 receives a corresponding cryptographic key K in step 302, for example when the transaction register 4 requests the key.
  • the key K can be a key of a PKI structure or a symmetric key.
  • step 303 the transaction data record TDS is then encrypted with the cryptographic key K in the first subscriber unit TE1, for example by an encryption module or a processing unit of the first subscriber unit TE1.
  • FIG. 6 Not shown in FIG. 6 is an optional linking step of (plain text) metadata to the encrypted transaction data record TDS, for example an identifier of the first subscriber unit TE1, an identifier of the second subscriber unit TE2 and/or a transaction time.
  • This metadata allows the encrypted TDS stored locally and/or in the trade repository 4 to be indexed or catalogued.
  • step 304 a communication link to the transaction register 4 is then initiated. An attempt is thus made to set up a communication channel between the first subscriber unit TE1 and the transaction register 4 . Initiating also includes the respective subscriber unit TE recognizing/knowing that an offline transaction is currently planned/performed and no connection to the remote transaction register 4 can or should be established.
  • the subscriber unit TE1 is queried as to whether a connection could be set up in step 304. If the test step 305 is yes, the encrypted transaction data record TDS is sent to the transaction register 4 in step 306 . If necessary, further transaction data sets TDS from earlier transmissions of electronic coin data sets C are also sent if this communication connection has been established for the first time since these transmissions. In this context, a check value is then also reset (not shown in FIG. 6), which represents a number of transmissions of electronic coin data sets C that took place without sending a transaction data set TDS. In a test step 305a, a query may be made as to whether a transmission error occurred when the encrypted transaction data record TDS was sent 305 .
  • test step 305a fails, the encrypted and/or unencrypted transaction data record TDS is then optionally stored locally in the first subscriber unit TE2 for archiving purposes or for storing a history or for queries based on official requests.
  • the electronic coin data record C is then transmitted to the second subscriber unit TE2 in step 105 if a specification in the payment system BZ is that the encrypted transaction data record TDS is to be sent first before the electronic coin data record C can be transmitted in step 105.
  • the masked electronic coin data record Z after the transmission 105, the masked electronic coin data record Z must be registered 104 in the coin register 2 it is described in Figures 9, 17 and 18.
  • test step 305 (offline transaction, flight mode, no transmission of the transaction data TDS (from the subscriber) desired) and also in the yes case of test step 305a (transmission error, connection termination), a connection error is determined in step 307.
  • a test value p is compared with a threshold value X in the first subscriber unit TE1.
  • the check value in step 308 represents a number of (offline) transmissions 105 of electronic coin data sets C that took place without sending a transaction data set TDS. These (offline) transmissions 105 originating from the first subscriber unit TE1 can have been transmitted to any other subscriber unit TEx. If test step 308 is yes, i.e.
  • test value p is greater than the threshold value X, for example 100 or 50 or 10 transmissions, the transaction data record TDS is stored (encrypted and/or unencrypted) and step 304 must be repeated. If the test step 308 is not, the transmission 105 takes place if a specification in the payment system BZ is that the encrypted transaction data record TDS is to be sent first before the electronic coin data record C may be transmitted in step 105 . In step 310, the test value p is then incremented, i.e. increased in stages, preferably increased by 1.
  • Steps 308 to 310 ensure that the offline behavior of the subscriber units TE remains monitored and not via a predefined specific one (pay system default) threshold X of transmission counts is possible.
  • Transaction data records TDS of an offline transaction that cannot be sent immediately, ie a transmission 105 without registering 104 or reports to one of the register instances 2, 4, 6 of the payment system BZ, are buffered in step 309 and sent at a later point in time.
  • the number of offline transactions that a subscriber unit TE is allowed to carry out is limited by the system and checked using the test value p in step 308. If the threshold value X is reached, the transaction data records TDS must first be sent before another offline transaction 105 is possible (see step 309 to step 304).
  • This test value p can be recorded and managed independently of other tests in the subscriber unit TE.
  • This check value p can be combined with other check or counter values pu, pu of the coin data record C for checking in the coin register 2 or the monitoring register 6, see payment system BZ in FIG. 9.
  • a general first specification in the payment system BZ can be that coin data records C are only transmitted between TEs before a transaction data record TDS is created for this. A TDS would then always relate to a coin data set C that has already been transmitted; step 105 would have to be carried out before the associated steps 301, 303.
  • a general first specification in the payment system BZ can be that coin data records C are only transferred between TEs (step 105) after a transaction data record TDS has been created for this (step 301). A TDS would then always relate to a coin data set C still to be transmitted, step 105 would have to be carried out after the associated step 301.
  • a second general specification in the BZ payment system could relate to the local storage of the TDS in the TE. It may be required that TDS are also stored locally (ie history or archiving). The storage step 309 should then not only be provided for transmission repetitions (in the event of an error in a first transmission attempt). It can be a default detail that the TDS are also to be stored encrypted in the TE.
  • This local storage of the TDS which is redundant to the storage of the TDS in trade repository 4, can also be read out as part of an official request (a court order), i.e. the participant can be forced to provide this local storage or the transfer of the local storage in take place in a (background) process of the subscriber unit TE without subscriber interaction.
  • a third general specification in the payment system BZ can be to store pseudonymised TDS * in a monitoring register 6 of the payment system BZ. These pseudonymised TDS * are taken into account when validating the coin data sets in order to be able to detect fraud scenarios within the payment system.
  • a fourth general requirement in the payment system BZ can be not to send encrypted TDS to the trade register 4 when an offline transaction is planned/performed.
  • This requirement can be closely coupled to the test value p, so that a subscriber unit TE issues a warning to the subscriber even before selecting a transmission mode (online or offline) that a test value p has exceeded a threshold value for the maximum number of offline transmissions 105 and no further offline transmission is possible without prior sending of the (old) TDS to the trade repository 4 (with reset of the check value counter).
  • FIG. 7 shows an exemplary embodiment of a method flow chart of a method 400 according to the invention in a transaction register 8 .
  • the blocks of the method 400 shown in dashed lines are optional.
  • step 401 an encrypted transaction data record TDS is received by a subscriber unit TE in the transaction register 4 .
  • This transaction data record TDS was generated according to the method shown in FIG.
  • step 402 it is checked whether different generations of partial keys are present in the payment system BZ, for example the transaction register 4, preferably an HSM module within the transaction register 4 as a key memory. If step 402 is yes, the transaction data record TDS is decrypted with the private key part k of the cryptographic key as the decryption key in step 403 and encrypted again with a cryptographic key, for example with an HSM key of the trade repository 4. In this way it can Storage of differently encrypted transaction records TDS, which are encrypted with different key versions of the remote entities, in the transaction register 4 can be prevented. The administrative effort in the trade register 4 is thus reduced.
  • the transaction data record TDS is stored in a memory area and archived there. If necessary, the transaction data record TDS has metadata in plain text, which is entered or tracked in a database of the transaction register 4 . If, for example, a transaction time is available as metadata of the TDS, a deletion time can be generated as part of data retention. The TDS would then be automatically deleted from the trade repository 4 after a set period of time (the time of deletion) has elapsed.
  • the TDS are stored in encrypted form in the transaction register 4 (e.g. a database as a trustworthy entity), and several partial keys are required for their decryption are. This ensures that due process must be followed and no one can access sensitive TDS transaction data at will.
  • the transaction register 4 e.g. a database as a trustworthy entity
  • step 405 partial keys of the cryptographic key k are received and combined in step 406 in the transaction register 4, for example to form the private key part of the private key part when using a PKI key structure.
  • the combination is secret, for example, in order not to allow owners of the partial keys 8a, 8b, 8c to combine the decryption key.
  • the combined key can also be composed of only a subset of partial keys, which is possible by using threshold cryptography.
  • a decryption request is made to the trade register 4 in step 407.
  • the metadata of the transaction data records can be matched with parameters of the decryption question, for example to query all transaction data records with a specific participant ID for a specific point in time or period.
  • each remote entity is requested to authenticate itself at the transaction register 4.
  • only a subset of remote entities required to decrypt the desired transaction data record(s) TDS is queried.
  • the decryption then takes place with the combined key from the jointly present partial keys of the remote entities.
  • a subscriber unit identifier in the decrypted transaction data record TDS is replaced by a pseudonym of the subscriber unit TE.
  • the pseudonym preferably corresponds to the pseudonym of FIGS.
  • a monetary amount in the decrypted transaction data record TDS is replaced by one or more amount categories.
  • the monetary amount of the coin data set C is rounded up or down, for example:
  • the monetary amount is sorted into one or more amount categories that represent amount ranges, for example:
  • Steps 410 and/or 411 can be performed by an HSM in the trade repository 4 .
  • the pseudonymised transaction data TDS * and/or the amount-categorized transaction data are sent (back) in step 412 to the monitoring register 6 or the subscriber unit TE. changed for the respective transaction record.
  • the encrypted transaction data records TDS are stored in the transaction register (step 404, possibly after step 412).
  • the pseudonymised transaction data set TDS * always has a higher level of anonymity than the (non-pseudonymised) transaction data set TDS.
  • the pseudonymised transaction data record TDS * can also be stored unencrypted in the coin register 2, monitoring register 6 and/or the transaction register 4 - as specified by the payment system BZ - and used for further validity checks in the payment system BZ. This would allow cases of fraud or manipulation in the BZ payment system to be better detected by the BZ payment system itself, and an official request (judicial decision) may then not be necessary.
  • the measures described here for pseudonymizing or anonymizing a TDS to obtain a pseudonymized TDS * or an anonymized TDS * can also be used for anonymizing or pseudonymizing Register Data Records RDS to obtain a pseudonymized RDS * or an anonymized RDS * .
  • levels of anonymity are provided for the RDS and the TDS.
  • These levels of anonymity can, for example, comprise 3 levels, for example level 1 (anonymous), level 2 (pseudonymous) and level 3 (open, non-anonymous, personalized). These levels can be set in coin register 2 and/or transaction register 4. These levels may be system requirements to be able to track coin records C without (or to be able to) track identities/amounts.
  • each TDS or RDS can either be identity-anonymous, identity-pseudonymous or identity-open.
  • anonymity levels apply in particular to the data element "monetary value of coin data record C" in the respective RDS or TDS. This means that each TDS or RDS can either be anonymous, pseudonymous or open-ended.
  • anonymity levels may vary within the RDS or TDS for different data elements.
  • the anonymity level of a subscriber identifier can be different from an anonymity level of a monetary amount.
  • the anonymity level of a subscriber identifier (identity) is preferably lower than an anonymity level of a monetary amount in order to protect the identity of the subscriber over the payment amount.
  • the TDS for the subscriber identifier and/or the monetary amount preferably have a lower anonymity level than the RDS.
  • Amount-neutral register changes can also be carried out, with at least one RDS of an already registered coin data set being replaced in the coin register 2 by at least one RDS of a coin data set to be registered.
  • the coin register 2 will therefore only have RDS for the electronic coin data records currently available in the payment system BZ.
  • FIG. 8 shows an embodiment of an encryption and decryption of a transaction data record TDS.
  • the remote instances 8a, 8b, 8c each have partial keys whose bitwise addition results in a private key part k of a cryptographic key (key pair).
  • the private key part k is stored, for example, in a key memory of the transaction register 4, for example a hardware security module of the transaction register 4.
  • the public key part K is derived from the private key part k and made available to the subscriber unit TE.
  • the encryption step 303 in FIG. 6 of the generated transaction data record TDS or the re-encryption step 403 in FIG. 7 of the decrypted transaction data record TDS is then carried out with the public key part K.
  • This asymmetric crypto-system must ensure that the public key part K is actually the key part derived from the combined private key part k and that this is not a forgery by a fraudster.
  • Digital certificates that confirm the authenticity of the public key part K are used for this purpose. The digital certificate may itself be protected by a digital signature.
  • the transaction data record TDS encrypted with the public key part K is stored in the transaction register 4 .
  • the subset or all of the removed ones must Authenticate instances at the trade repository 4. If authentication is successful, the transaction data record TDS is decrypted using the private key part k.
  • the transaction data record generated consists, for example, of a transaction number, a recipient address (here from TE2), a sender address (here from TE1) and a monetary amount of the eMD C.
  • the transaction data record generated can also be used in TE1 to log the transmission 105 in order to transmit in the transmission - carry out a reversal (ROLLBACK) or repetition (RETRY) of the transmission 105 in the event of an error.
  • ROLLBACK reversal
  • RETRY repetition
  • FIG. 9 shows an alternative development to FIG. 5 of the exemplary embodiment of a system from FIG. 2. Reference is made to the explanations of FIG. 2 and FIG. 5 to avoid repetition. The configurations of FIG. 9 can also be combined with the configurations of FIG. 5 .
  • Fig. 9 shows an embodiment of a payment system BZ with terminals Ml and M2 (as examples of subscriber units TE), an issuer entity 1, a coin register 2, a monitoring register 6 and a transaction register 4.
  • the terminals Ml and M2 can also be devices or security elements SEI , be SE2.
  • the coin register 2 contains a register 210 in which only valid masked electronic coin data sets Zi are stored.
  • the electronic coin data record Ci represents a monetary amount Ui.
  • the electronic coin data set Ci is output to a first terminal Ml.
  • Electronic coin data sets Ci preferably for which a masked electronic coin data set Zi is registered, can be used for payment.
  • the masked electronic coin data record Zi can also be referred to as an amount-masked electronic coin data record, since the monetary amount Ui is unknown to the coin register 2 (and also remains unknown later on).
  • a recipient, for example a second terminal M2 here, of the electronic coin data set Ci can check its validity using the coin register 2 .
  • the coin register 2 can confirm the validity of the electronic coin data set Ci using the masked electronic coin data set Zi.
  • the masked electronic coin data record Zi is an anonymous electronic coin data record, particularly since it does not know the owner of the associated electronic coin data record Ci.
  • the anonymity level of a masked coin data set Zi in the register 201 of the coin register 2 is accordingly level 1 (completely anonymous).
  • the second terminal M2 sends masked electronic coin data sets Zi * anonymously to the coin register 2 in an anonymous mode M2a, ie in particular only sends the masked electronic coin data set Zi*.
  • the coin register 2 processes the anonymously sent masked electronic coin data record Zi* in an anonymous mode 2a, in which, for example, only confirms to the second terminal M2 that the transmitted masked electronic coin data record Zi* is valid.
  • the coin register 2 stores in the register 210 anonymous (amount) masked coin data sets Zi from electronic coin data sets Ci of the issuer entity 1 or from modified electronic coin data sets of the terminals M.
  • FIG. 9 also shows that the second terminal M2 can also send masked electronic coin data sets Si* in a pseudonymous mode M2p to the monitoring register 6 via the coin register 2 in a pseudonymised form.
  • the second terminal M2 links, for example, the masked electronic coin data set Zi * with a pseudonym P M 2 and sends the pseudonymized masked electronic coin data set Si * via the coin register 2 to the monitoring register 6.
  • the second terminal M2 could a pseudonymized masked electronic coin data set Si * by appending of the pseudonym P M 2 to the masked electronic coin data set Zi*.
  • the second terminal M2 creates a signature via the masked electronic coin data record Zi* and adds the signature to the coin data record Zi*.
  • the public key of the signature key pair for example, can serve as the pseudonym Piv ß.
  • the pseudonym P M 2 is derived from a subscriber identifier, such as a terminal number, IMEI, IMSI or a similarly derived identifier.
  • the pseudonym P may be a derivation of the subscriber unit identifier mentioned above.
  • the pseudonym P can also be listed in the person assignment 7 of the publishing entity 1 (or alternatively of a service provider, for example a purse application provider or an online storage provider) next to the subscriber unit identifier.
  • the pseudonym P can only be assigned to a natural person in a trustworthy authority.
  • the monitoring register 6 processes the pseudonymously transmitted masked electronic coin data record Si* in a pseudonymous mode 2p, in which the second terminal M2 is also confirmed that the transmitted masked electronic coin data record Zi* is valid.
  • the assignment of the masked electronic coin data record Zi to the pseudonym P M 2 is additionally stored in a data structure 220 of the monitoring register 6 .
  • the data structure 220 can be used as a register for masked electronic coin data sets Zi that are still to be checked, ie can also fulfill the function of a coin register 2 .
  • the monitoring register 6 postpones or skips in particular a verification step carried out in the anonymous mode 2a (more frequently or always).
  • the checking step it is checked—preferably still without knowing the monetary amount Ui—whether the monetary amount Ui of the masked electronic coin data record Zi is within a range.
  • the aspects described below build at least partially on details of this embodiment of FIG. 2, 3 or 5.
  • the more complex pseudonymous mode 2p or M2p is primarily described there, since the simpler anonymous mode 2a or M2a runs without a pseudonym (or signature).
  • configurations are described in FIGS. 17 and 18 which can only optionally be combined with the details of the other configurations.
  • Figure 10 shows a data structure for a coin register 2 and/or a monitoring register 6 of the previous figures.
  • data from the coin register 2 and/or the monitoring register 6 are shown together in a common data structure as a table for illustration purposes.
  • the registers 2, 6, the masked electronic coin data sets Zi and possibly their processing are registered.
  • the coin register 2 and the monitoring register 6 can be accommodated in a common server instance and are only logically separated from one another in order to be able to reduce the computing effort for the individual checks through strict assignments.
  • the registers 2, 6 are also physically separated from one another. Both registers 2, 6 are preferably arranged locally at a distance from the subscriber units TE and are housed, for example, in a server architecture.
  • Each processing operation for processing (creating, deactivating, dividing, connecting and switching over) is registered in the coin register 2 and appended there, for example in unchangeable form, to a list of previous processing operations for masked electronic coin data sets Zi.
  • the individual operations or their test results that is to say the intermediate results of processing, are recorded in the coin register 2 .
  • this data structure can also be cleaned up or compressed, if necessary according to predetermined rules, or be provided separately in a cleaned up or compressed form.
  • the "Create” and “Deactivate” processing which per se affects the existence of the monetary amount Ui, i.e. the creation and destruction of money, requires additional approval by the issuing authority 1 in order to be in the coin register 2 and/or the Monitoring register 6 registered (ie logged) to be.
  • the respective processing is registered, for example, by corresponding list entries in the database according to FIG. These list entries are the RDS.
  • Each list entry has further markings 25 to 28, which are the intermediate results of the respective Documented processing that must be performed by the coin register 2 and / or the monitoring register 6.
  • the markings 25 to 28 are preferably used as an aid and are discarded after the commands from the coin register 2 and/or the monitoring register 6 have been completed.
  • the checks corresponding to the markings 27b and 27c are not necessary for pseudonymised coin data records because they are carried out later in a different form.
  • the checking steps of the markings 25, 26, 27a and 28, on the other hand, are necessary.
  • necessary or validity-relevant test steps and subsequent or validity-independent test steps are referred to in part, since they are directly or indirectly made up for.
  • a coin record can be treated as valid if the necessary checks have been made.
  • the data highlighted in bold in columns 24, 28 and 29 in Fig. 10 are only relevant for coin data records received in pseudonymised form and therefore primarily relate to entries in the monitoring register 6.
  • An optional marker 29 can indicate the completion of processing, for example.
  • the markings 29 are, for example, in the state and are set to the state “1” after all tests have been successfully completed (for markings 25-28) and are set to the state “0” if at least one test has failed.
  • a (completion) marking 29 with the value "2" could indicate, for example, that only the necessary tests were completed and tests that could be made up for were omitted. If checks for one or more entries are made later by the end device with the pseudonym, the marking can be set to the value "1".
  • the markers 27b and 27c of the examinations to be made up for could of course also be used and/or a separate pseudonym marker could be used.
  • a possible structure for a list entry of a coin data record includes, for example, two columns 22a, 22b for a predecessor coin data record (Ol, 02), two columns 23a, 23b for a successor coin data record (Sl, S2), a signature column 24 for signatures from Issuer instance(s) 1 and signatures of terminals M, and six marking columns 25, 26, 27a, 27b and 27c and 28.
  • Each of the entries in columns 25 to 28 has three alternative states "1" or "0".
  • Column 25 indicates whether a validity check in column 22a/b with regard to an electronic predecessor coin data set was successful.
  • the state "1" means that a Validity check determined that the column 22a/b electronic coin record is valid and the status "0" indicates that a validity check determined that the column 22a/b electronic coin record is invalid and the status indicates that a validity examination is not yet completed.
  • a common O-flag both valid is preferred for multiple predecessor coin data sets rather than two separate O-flags.
  • Column 26 indicates whether a first check calculation for the masked electronic coin records was successful. The first check calculation checks in particular whether the command is amount-neutral, ie primarily that the sum of the monetary amounts involved is zero.
  • the "1" state means that a calculation was successful and the "0" state indicates that the calculation was unsuccessful and the state indicates that a calculation is not yet complete.
  • the first area proof of column 27a is always necessary for the coin record(s) to be considered valid.
  • a typical example of a necessary check is checking that the monetary amount is not negative (or that none of the monetary amounts is negative).
  • the second and third proof of area does not affect the validity of the coin data set and can be made up for pseudonymized masked coin data sets, for example in a later transaction of the pseudonym.
  • the area verification in column 27b is used to check whether the monetary amount of the masked coin data record (or each coin data record) is below a maximum amount. The maximum amount can be predetermined system-wide or for specific end device types.
  • a sum of monetary amounts that the subscriber unit TE (sent or received) in a certain period of time - such as 24 hours - is compared with a total limit value or, for example, a number of transactions per time unit for the subscriber unit TE is checked, such as maximum 5 per minute or 100 per day.
  • the limit values can be specified system-wide by the payment system BZ or can be defined for specific subscriber unit types (that is to say subscriber unit-specific). For example, a Type X coffee maker is designed to only dispense four portions of hot beverages per minute and accordingly only allows four coin transactions per minute.
  • Column 28 indicates whether a signature of the electronic coin data record matches the signature in column 24, with status "1" meaning that a validity check revealed that the signature could be identified as that of the issuing authority and the state "0" indicates that a validity check revealed that the signature could not be identified as that of the publisher authority and the state indicates that a validity check has not yet been completed.
  • a change in the status of one of the markings requires the approval of the coin register 2 and/or the monitoring register 6 and must then be stored invariably in the data structure of FIG.
  • Processing is final in anonymous mode (or for an anonymous masked coin data set) if and only if the required markings 25 to 28 have been validated by the coin register 6, i.e. after the corresponding check from state "0" to state "1” or the status "1" was changed.
  • Processing in the pseudonymous mode (or for a pseudonymised masked coin data set) is completed when the checks for the markings 25 to 27a and 28 have been carried out by the monitoring register 6.
  • a data structure without final markings 29 is assumed and the validity of anonymous coin data sets is considered first.
  • the coin register 2 looks for the last change affecting the masked electronic coin record Z. It applies that the masked electronic coin data record Z is valid if the masked electronic coin data record Z is listed for its last processing in one of the successor columns 23a, 23b if and only if this last processing has the corresponding final marking 25 to 28. It also applies that the masked electronic coin data record Z is valid if the masked electronic coin data record Z is listed for its last processing in one of the predecessor columns 22a, 22b if and only if this last processing failed, i.e. at least one of the corresponding required states of markings 25 to 28 is set to "0".
  • the masked electronic coin record Z is not found in the coin register 2, it is invalid. It also applies that the anonymous masked electronic coin data record Z is not valid for all other cases. For example, if the last processing of the masked electronic coin data record Z is listed in one of the successor columns 23a, 23b, but this last processing never became final, or if the last processing of the masked electronic coin data record Z is in one of the predecessor columns 22a, 22b and this last processing is final.
  • the checks made by coin register 2 and/or monitor register 6 to determine if processing is final are represented by columns 25 through 28:
  • the status in column 25 indicates whether the masked electronic coin record(s). are valid according to predecessor columns 22a, 22b.
  • the status in column 26 indicates whether the calculation of the masked electronic coin record according to equation (10) is correct.
  • the status in column 27a indicates whether the area verifications for the masked electronic coin records Z could be verified successfully.
  • the status in column 28 indicates whether the signature in column 24 of the masked electronic coin data record Z is a valid signature of the issuing authority 1.
  • the status "0" in a column 25 to 28 indicates that the check was unsuccessful.
  • the status "1" in a column 25 to 28 indicates that the check was successful.
  • the status in a column 25 to 28 indicates that no check has taken place.
  • the statuses can also have a different value, as long as it is possible to clearly distinguish between the success/failure of a test and whether a specific test was carried out.
  • One processing is, for example, “creating” an electronic coin data record Ci.
  • the creation in the direct transaction layer 3 by the issuer entity 1 involves choosing a monetary amount Ui and creating an obfuscation amount n, as already described with equation (1). As shown in FIG. 10, no entries/markings are required in the columns 22a, 22b, 23b and 25 to 27 during the "generate" processing.
  • the masked electronic coin data set Zi is registered in the successor column 23a. This registration preferably takes place before the transmission 105 to a subscriber unit TE, in particular or already during generation by the issuing entity 1, with equation (3) having to be executed in both cases.
  • the masked electronic coin data record Zi is signed by the issuing authority 1 when it is created, this signature is entered in column 24 to ensure that the electronic coin data record Ci was actually created by an issuing authority 1, with other methods also being possible. If the signature of a received Zi matches the signature in column 24, the marking in column 28 is set (from "0" to "1"). The markings according to columns 25 to 27 do not require a status change and can be ignored. The proof of area is not required since the coin register 2 and/or the monitoring register 6 can be confident that the issuing authority 1 will not issue any negative monetary amounts. In an alternative embodiment, however, it can also be sent by the issuer instance 1 in the create command and can be checked by the coin register 2 and/or the monitoring register 6 .
  • the masked electronic coin data record Zi is to be checked when deactivating whether the signature matches the signature according to column 24 in order to ensure that the electronic coin data record Ci was actually created by an issuing authority 1, although other means can be used for this check. If the signed Zi, which is also sent in the deactivation command, can be confirmed as signed by the issuer authority 1, the marker 28 is set (from "0" to "1"). The markings according to columns 26 to 27 do not require a status change and can be ignored. The markings according to columns 25 and 28 are set after appropriate examination.
  • a processing is, for example, the "split".
  • the division i.e. the division of an electronic coin data set Zi into a number n, for example 2, of electronic partial coin data sets Z j and Z k takes place first in the direct transaction layer 3, as is shown in Figures 11, 13 and 14, with the monetary amounts U j and the concealment amount h are generated.
  • V k and r k are given by equations (7) and (8).
  • the markings 24 to 27 are set in the coin register 2 and/or the monitoring register 6, the predecessor column 22a is written with the electronic coin data record Zi, successor column 23a is written with Z j and successor column 23b is written with Z k .
  • the status changes required according to columns 24 to 27 take place after the corresponding check by the coin register 2 and/or the monitoring register 6 and document the respective check result.
  • the flag according to column 28 is ignored in anonymous mode.
  • a first proof of area RI according to column 27a must be provided to show that no monetary amount is negative.
  • a second proof of area R2 in column 27b is not necessary, since the monetary partial amounts of the successor are always smaller than the initial monetary amount of the predecessor.
  • a summary area statement R3 in column 27c is also usually not required (no new monetary amounts).
  • Column 24 is used for entering a generated signature dividing the coin data record subscriber unit TE.
  • connection i.e. the joining together, of two electronic coin data sets Zi and Z j to form an electronic coin data set Z m takes place first in the direct transaction layer 3, as is shown in FIGS. 12 and 13, with the monetary amount u m and the concealment amount r m being calculated will.
  • the markings 25 to 28 are set in the coin register 2 and/or the monitoring register 6, the predecessor column 22a is written with the electronic coin data record Zi, the predecessor column 22b is written with Z j and the successor column 23b is written with Z m .
  • the marks in columns 25 through 28 require status changes and coin register 2 and/or the monitoring register 6 carries out the appropriate checks.
  • a first proof of area RI according to column 27a must be provided to show that no new money was generated.
  • a second proof of area R2 in column 27b makes sense since the new monetary amount of the successor could be greater than a maximum value.
  • a cumulative area statement R3 in column 27c is also generally useful since the terminal device could use newly received predecessors. The marking according to column 28 can be ignored.
  • Column 24 is used for entering a generated signature connecting the coin data record subscriber unit TE.
  • Switching is necessary when an electronic coin data set has been transferred to another subscriber unit TE and a renewed issue by the transmitting subscriber unit TE is to be ruled out.
  • switching over also called “switch”
  • the electronic coin data record C k received from the first subscriber unit TE1 is exchanged for a new electronic coin data record Ci with the same monetary amount.
  • the new electronic coin data record Ci is generated by the second subscriber unit TE2. This switching is necessary in order to invalidate (make invalid) the electronic coin data record C k received from the first subscriber unit TE2, thereby avoiding the same electronic coin data record C k being issued again.
  • the first subscriber unit TE1 Since the first subscriber unit TE1 is aware of the electronic coin data set C k , as long as the electronic coin data set C k is not switched, the first subscriber unit TE1 can forward this electronic coin data set C k to a third subscriber unit TE.
  • the switching is effected for example by adding a new fogging amount r to add fogging amount r k of the obtained electronic Münz Scheme C k, n is obtained whereby a fogging amount, known only to the second subscriber unit TE2. This can also be done in the coin register 2 or the monitoring register 6.
  • the modifications “split” and “connect” to an electronic coin data record can also be delegated from one subscriber unit TE1 to another subscriber unit TE, for example, if a communication connection to the coin register 2 and/or to the monitoring register 6 is not available.
  • FIG. 11 shows an exemplary embodiment of a payment system BZ according to the invention for the “split”, “connect” and “switch” actions of electronic coin data records C.
  • Each of the received amounts U j , U k must be greater than 0 because negative monetary amounts are not permitted.
  • the monetary amount Ui is divided symmetrically into a number n of equal monetary partial amounts Uj.
  • the number n is an integer greater than or equal to two.
  • splitting is symmetrical, an individual, unique spoofing amount h is formed in the subscriber unit TE1 for each coin portion, the sum of the number n of spoofing amounts h of the coin portion data sets being equal to the spoofing amount r, of the split coin data set:
  • the last partial amount of concealment h_ h is equal to the difference between the amount of concealment n and the sum of the remaining partial amounts of concealment:
  • the obfuscation can h_i amounts to r, n -i be arbitrarily selected and the procedure of the equation (13a) is by means of appropriate calculation of the "last" h_ individual fogging amount satisfies h.
  • a signature is calculated in the respective subscriber unit TE.
  • n is the number of symmetrically divided coin part data sets.
  • the signature of the k-th partial coin data set k can be checked according to (13c) with the following verification key Sig:
  • Equation 13e Equation 13e simplifies to:
  • Equation 13f The simplification based on Equation 13f makes it possible to completely dispense with zero-knowledge proofs, which means that the use of a symmetrical distribution saves an enormous amount of computing power and data volume.
  • a partial coin data set, here C k is then transmitted from the first subscriber unit TE1 to the second subscriber unit TE2.
  • a switching operation makes sense in order to exchange the electronic coin data record C k received from the first subscriber unit TE1 for a new electronic coin data record Ci with the same monetary amount.
  • the new electronic coin data record Ci is generated by the second subscriber unit TE2.
  • the monetary amount of the coin data record Ci is adopted and not changed, see equation (11).
  • the coin data set Ci to be switched is masked by the equation (3) to obtain the masked coin data set Z ⁇ .
  • FIG. 12 shows an embodiment of a payment system according to the invention for connecting (also called combining) electronic coin data sets.
  • the two coin data sets Ci and are received in the second subscriber unit TE2.
  • a new coin data set Z m is now obtained by adding both the monetary amounts and the concealed amount of the two coin data sets Ci and .
  • the obtained coin data C m to be connected is masked and the masked coin data Z m is registered in the coin register 2 .
  • the signature of the second subscriber unit TE2 is entered, since this has received the coin data sets Ci and .
  • the highest of the two individual check values of the respective electronic partial coin data records Ci and Ci is determined. This highest check value is adopted as the check value Ci and the combined electronic coin record.
  • a new check value is determined from the sum of all check values of the electronic coin part data sets Ci and divided by the product of the number (here two) of the coin part data sets Ci and with a constant correction value.
  • the correction value is constant throughout the system.
  • the correction value is greater than or equal to 1.
  • the correction value is preferably dependent on a maximum deviation of the individual test values of the electronic coin part data sets Ci and/or on a maximum test value of one of the electronic coin part data sets Ci and .
  • the correction value is more preferably less than or equal to 2. This new check value is adopted as the check value of the combined electronic coin data set C m .
  • FIGS. 13 and 14 each show an exemplary embodiment of a method flowchart of a method 100.
  • FIGS. 13 and 14 are explained together below.
  • a coin data record is requested and provided by the issuer entity 1 to the first subscriber unit TE1 after the electronic coin data record has been created.
  • a signed masked electronic coin record is sent at step 103 to the coin register 2 and/or the monitoring register 6.
  • the received electronic coin data set Ci is masked according to equation (3) and signed in step 103p according to equation (3a).
  • step 104 the masked electronic coin data record Zi is registered in the coin register 2 or the monitoring register 6 .
  • the subscriber unit TE1 can switch over the electronic coin data set received, then a signature Si would be entered in the coin register 2 or the monitoring register 6 .
  • the coin data record Ci is transmitted in the direct transaction layer 3 to the second subscriber unit TE2.
  • a validity check is carried out with prior masking, in which case the coin register 2 and/or the monitoring register 6 confirms the validity of the coin data set Zi or Ci.
  • a received coin data set C k is then switched over (of course, the received coin data set Ci could also be switched over) to a new coin data set Ci, whereby the coin data set C k becomes invalid and double issuance is prevented.
  • the monetary amount v /, - of the transmitted coin data set C k is used as the "new" monetary amount.
  • the concealment amount n is created.
  • the additional obfuscation amount r add is used to prove that no new money (in the form of a higher monetary amount) was generated by the second subscriber unit TE2. Then the masked coin data set is signed and the signed, masked coin data set Zi to be switched over is sent to the coin register 2 and/or the monitoring register 6 and the switching over from C k to Ci is instructed.
  • a signature S k is created by the first subscriber unit TE1 or the second subscriber unit TE2 and stored in the coin register 2 and/or the monitoring register 6 .
  • a signature Si could also be created and stored in the coin register 2 and/or monitoring register 6 if transmitting subscriber units TE were registered instead of receiving subscriber units TE.
  • step 108' the corresponding check is carried out in coin register 2 and/or monitoring register 6.
  • Z k is entered in column 22a according to the table in FIG Coin register 2 and/or the monitoring register 6 whether Z k is (still) valid, i.e. whether the last processing of Z k is entered in one of the columns 23a/b (as proof that Z k is not further divided or deactivated or connected was made) and whether a check for the last processing failed.
  • Zi is entered in column 23b and the markings in columns 25, 26, 27 are initially set to "0". A check is now made as to whether Zi is valid, in which case the check according to equations (16) and (17) can be used. If it is good, the mark in column 25 is set to “1”, otherwise to “0”.
  • the second subscriber unit TE2 When checking the signature, it can be checked in pseudonymous mode whether the second subscriber unit TE2 has exceeded a limit value for monetary amounts. The check is carried out with regard to a unit of time, for example a daily limit value could be monitored with it. If the limit is exceeded, the denied Coin register 2 and/or the monitoring register 6 first switches over the coin data set Ci and requests the second subscriber unit TE2 to deanonymize itself. Depending on the system, deanonymized switching may be permitted.
  • two coin data records C k and Ci are connected to a new coin data record C m , as a result of which the coin data records C k , Ci become invalid and double dispensing is prevented.
  • the monetary amount u m is formed from the two monetary amounts and U k Ui.
  • the concealment amount r m is formed from the two concealment amounts r k and r i .
  • the masked coin data set Z m to be connected is obtained by means of equation (3) and this (together with other information) is sent to the monitoring register 6 and/or the coin register 2 and connection is requested as processing.
  • a signature S k and a signature Si are generated and communicated to the monitoring register 6 and/or the coin register 2 .
  • step 109' the corresponding check is made in the coin register 2 and/or the monitoring register 6.
  • Z m is entered in the column 23b according to the table in FIG. 10, which is also the same as a paraphrase.
  • a check then takes place in the coin register 2 and/or the monitoring register 6 as to whether Z k and Zi are (still) valid, i.e. whether the last processing of Z k or Zi is entered in one of the columns 23a/b (as proof of this that Z k and Zi were not split further or deactivated or connected) and whether a check for the last processing failed.
  • the markings in columns 25, 26, 27 are initially set to "0".
  • the signature it can be checked whether the second subscriber unit TE2 has exceeded a limit value for monetary amounts. The check is carried out with regard to a unit of time, for example a daily limit value could be monitored with it. If the limit value is exceeded, the coin register 2 and/or the monitoring register 6 initially refuses the connection of the coin data record C m and requests the second subscriber unit TE2 to deanonymize itself. A deanonymized connection may then be permitted.
  • a coin data set Ci is asymmetrically divided into two partial coin data sets C k and Q, whereby the coin data set Ci is invalidated and the two asymmetrically divided partial coin data sets C k and Q are to be validated.
  • the monetary amount Ui is divided into different sized part monetary amounts U k and U j.
  • the concealment amount r i is divided into the two concealment amounts r k and h.
  • the masked partial coin data records Z k and Z j are obtained by means of equation (3) and these with further information, for example the Zero-knowledge-proofs sent to coin register 2 and/or monitor register 6 requesting splitting as processing.
  • a signature Si is created and sent to the coin register 2 and/or to the monitoring register 6 .
  • step 110' the corresponding check is carried out in the coin register 2 and/or the monitoring register 6.
  • Z j and Z k are entered in the columns 23a/b according to the table in FIG.
  • a check is then carried out in the monitoring register 6 and/or the coin register 2 to determine whether Zi is (still) valid, i.e. whether the last processing of Zi is entered in one of the columns 23a/b (as proof that Zi is not further divided or disabled or connected) and whether a check for the last processing failed.
  • the markings in columns 25, 26, 27 are initially set to "0".
  • a check is now made as to whether Z j and Z k are valid, in which case the check according to equations (16) and (17) can be used.
  • the marking in column 25 is set to "1".
  • the signature it can be checked whether the second subscriber unit TE2 has exceeded a limit value for monetary amounts. The check is carried out with regard to a unit of time, for example a daily limit value could be monitored with it. If the limit value is exceeded, the coin register 2 and/or the monitoring register 6 initially refuses to split up the coin data record Ci and requests the second subscriber unit TE2 to deanonymize itself. Deanonymized splitting may then be permitted.
  • FIG. 15 shows an exemplary embodiment of a first subscriber unit TE1 according to the invention.
  • the first subscriber unit TE1 can be a device M1 in which a security element SEI is incorporated.
  • the term device M1 is used below.
  • Electronic coin data sets Ci can be stored in a data memory 10, 10' in the device M1.
  • the electronic coin data sets Ci can be on the data memory 10 of the device M1 or be available in an external data memory 10'.
  • the electronic coin data records Ci could be stored in an online memory, for example a data memory 10' of a provider for digital purses.
  • private data storage for example a network attached storage, NAS could also be used in a private network.
  • the electronic coin record Ci is presented as a hard copy.
  • the electronic coin data record can be represented by a QR code, an image of a QR code, or a file or a character string (ASCII).
  • the device Ml has at least one interface 12 available as a communication channel for issuing the coin data set Ci.
  • This interface 12 is, for example, an optical one Interface, for example for displaying the coin data set Ci on a display unit (display), or a printer for printing out the electronic coin data set Ci as a paper printout.
  • This interface 12 can also be a digital communication interface, for example for near-field communication such as NFC, Bluetooth, or an Internet-enabled interface such as TCP, IP, UDP, HTTP or access to a chip card as a security element.
  • This interface 12 is a data interface, for example, so that the coin data record Ci is transmitted between devices via an application, for example an instant messenger service, or as a file or as a character string.
  • the interface 12 or another interface (not shown) of the device M1 is set up to interact with the coin register 4.
  • the device M1 is preferably online-capable.
  • the device Ml also have an interface for receiving electronic coin data sets.
  • This interface is set up to receive visually presented coin data sets, for example using a detection module such as a camera or scanner, or digitally presented coin data sets, received via NFC, Bluetooth, TCP, IP, UDP, HTTP or coin data sets presented using an application.
  • the device M1 also includes a computing unit 13 which can carry out the method described above for masking coin data sets and the processing of coin data sets.
  • the device Ml is online capable and can preferably recognize by means of a location detection module 15 when it is connected to a WLAN.
  • the location recognition module 15 recognizes when the device M1 is in predefined GPS coordinates including a defined radius and performs the special functions according to the location zone defined in this way. This location zone can either be introduced manually into the device M1 or via other units/modules into the device M1.
  • the special functions that the device Ml performs when recognizing the location zone are, in particular, the transmission of electronic coin data sets from / to the external data memory 10 from / to a vault module 14 and, if necessary, the transmission of masked coin data sets Z to the coin register 4 and / or the monitoring register 6, for example as part of the above processing of a coin data record.
  • the device M1 is accordingly set up to carry out the method according to FIG.
  • the device Ml is set up to create and encrypt a transaction data record TDS.
  • the device M1 is set up to initiate communication with a transaction register.
  • the device M1 is set up to send the encrypted transaction data set TDS to the transaction register.
  • the device Ml is to set up to attach TDS metadata (in plain text) to the transaction record.
  • the device M1 is set up to store the transaction data record TDS locally (temporarily).
  • all coin data records Ci are automatically linked to form a coin data record in device M1 upon receipt (see link processing or link step). That is, as soon as a new electronic coin data set is received, a connect or toggle command is sent to the coin register 4.
  • the device M1 can also prepare electronic coin data records in algorithmically defined denominations and store them in the data memory 10, 10', so that a payment process is also possible without a data connection to the coin register 4 and/or monitoring register 6.
  • a payment system is shown in FIG. 16 for better understanding.
  • the overall system according to the invention includes an issuing authority (central bank) la.
  • further issuer instances lb, lc can be provided which, for example, issue electronic coin data records in a different currency.
  • at least one payment system BZ is shown, in which at least one coin register 2, a monitoring register 6 and a transaction register 4 of the payment system BZ are provided in order to register the coin data sets Ci or Zi and to check and log the modifications to the coin data set Ci.
  • the publishing entity la can also be provided as part of the payment system BZ.
  • bank instance(s) can be arranged between the issuing instances la-c and the payment system BZ.
  • Registers 2, 4, 6 are housed together, for example, in one server entity and are logically separated from one another there. Alternatively, the registers 2, 4, 6 are also spatially/physically separated from one another.
  • the trade register 4 can also be arranged as a unit external to the payment system BZ.
  • a judicial/judicial authority 9 is shown, which requests a judicial request for decrypting encrypted transaction data records TDS from the payment system BZ (or directly from the transaction register) if fraud is suspected.
  • Remote entities 8a-c with corresponding sub-keys are also shown to provide their sub-keys to the transaction repository 4 in the event of a request for a cryptographic key to be obtained as a decryption key.
  • FIG. 16 provides a large number of participants, which are shown as terminal devices Mx (with respective SEx).
  • the terminals Ml to M6 can directly exchange coin data records Ci in the direct transaction layer 3.
  • terminal M5 transmits a coin record to terminal M4.
  • terminal M4 transmits the coin record to terminal M3.
  • the terminal M6 transmits a coin data set to the terminal Ml.
  • the test value pn of the coin data set to be sent or received and, if applicable, the counter value p is used in each transmitting terminal device Mx or each receiving terminal device Mx to check whether the coin data set is displayed in the payment system and/or whether the coin data set is displayed in the Publishing authority la is to be returned.
  • the payment system BZ checks, for example, using the check value pn or one of the check value pn derived counter value pa for each coin data set C whether the coin data set C is to be returned or not.
  • a test value is provided in each terminal Mx in order to monitor a number of transaction data sets TDS that have not yet been sent, despite the coin data sets being transmitted.
  • FIG. 17 shows a flow chart of a method with which, for example, compliance with a limit value for monetary amounts per unit of time is made possible.
  • the upper part of the figure shows the payment system BZ consisting of three terminals M1, M2, M3. Three data structures 910, 920, 930 of the respective registers 2, 4, 6 are shown in the lower part of the figure.
  • the valid masked coin data records Zi are stored in the data structure 910 of the coin register 2 .
  • the data structure 920 of the monitoring register 6 includes the assignment of pseudonymously transmitted, masked coin data sets to the pseudonym and can be viewed as the monitoring register 6 of coin data sets that are still to be checked pseudonymously. Based on the data in the data structure 920, the monitoring register 6 can decide whether an area verification is requested for a pseudonym.
  • Encrypted transaction data records TDS are stored in the data structure 930 of the transaction register.
  • the first terminal Ml split a coin 901.
  • the coin register 2 therefore knows that the coin Ci is a result of this split and stores the masked coin record Zi in the data structure 910.
  • the first terminal Ml could report the split to the monitoring register 6 anonymously or send pseudonymously. In the illustration, it is assumed that the terminals M1 and M3 send their masked coin data records to the monitoring register 6 anonymously.
  • the first terminal M1 sends the coin Ci directly to the second terminal M2 in a direct transmission step 902. Neither the coin register 2 nor the monitoring register 6 receive any information about this.
  • the first terminal Ml generates a transaction data record TDS902 regarding the transmission step 902, encrypts this transaction data record TDS902 and sends it to the transaction register 4.
  • the encrypted transaction data record TDS902 contains an identifier of the first terminal Ml, an identifier of the second terminal M2 and the monetary amount ui of the coin ci
  • the second terminal M2 converts the coin Ci into the coin C2 (switches over) 903.
  • the new masked coin data record Z2 is stored in the data structure 910 of the coin register 2 and the old masked coin data record Zi is deleted (or marked as invalid).
  • the second terminal M2 sends its masked (or at least the displayed) coin data sets pseudonymously to the monitoring register 6.
  • the monitoring register 6 thus also receives the information that the second terminal M2 with the pseudonym P M 2 has received the coin Ci (and now has coin C2) and accordingly stores the masked coin data record Z2 (and/or the masked coin data record Zi) in the data structure 920 of the monitoring register 6 for P M 2.
  • the monitoring register 6 will skip at least one verification step, such as area verification for the coin data record Z2 or total area verification for the terminal M2.
  • the second terminal M2 sends the coin C2 in a further direct transmission step 905 to the third terminal M3. Neither the coin register 2 nor the monitoring register 6 receive any information about this.
  • the second terminal M2 generates a transaction data record TDS905 with regard to the transmission step 905, encrypts this transaction data record TDS905 and sends it to the transaction register 4.
  • the encrypted transaction data record TDS905 contains an identifier for the second terminal M2, an identifier for the third terminal M3 and the monetary value 02 of the coin C2.
  • the third terminal M3 connects the received coin C2 to the connected coin C3 in step 904 and sends this information to the coin register 2 with anonymous masked coin data records. .. and Z3 or a cumulative area proof for the third terminal M3. Only then does the coin register 2 delete the masked coin data record Z2 (and the other coin data records of the process) from the data structure 910 and save the new masked coin data record Z3 as a valid masked coin data record.
  • the third terminal M3 in step 906 sends the coin C3 directly to the second terminal M2. Neither the coin register 2 nor the monitoring register 6 receive any information about this.
  • the third terminal M3 generates a transaction data record TDS906 with regard to the transmission step 906, encrypts this transaction data record TDS906 and sends it to the transaction register 4.
  • the encrypted transaction data record TDS906 contains an identifier for the third terminal M3, an identifier for the second terminal M2 and the monetary value 03 of the coin C3.
  • the second terminal M2 converts the coin C3 into the coin C4 (switch) and sends a masked coin data record Z4 together with its pseudonym to the monitoring register 6.
  • the monitoring register 6 receives the information and carries out the necessary checks. With the help of the data structure 920, the monitoring register 6 determines whether one or more checks are to be made up for the pseudonym of the terminal M2. If the criterion for catching up, such as time elapsed or the number of transactions for a pseudonym, is not yet met, only the further masked coin data record Z4 for the pseudonym is noted in the data structure 920 des Monitoring register 6.
  • the coin register 2 stores the masked coin data set Z4 in the data structure 910 and deletes the masked coin data set Z3 there. On the other hand, if a criterion for a catch-up test step is met, it first carries out the catch-up test step (or its equivalent).
  • the monitoring register 6 has the information that the second terminal device M2 had the coin C 2 (see step 3). Since the sum of the monetary amounts of C 2 and coin coin C4 might exceed its Münzschwellwert, calls the monitoring register 6 from the second terminal M2 a sum detection area (or a total area confirmation) on. The proof of the sum range shows that the sum of the monetary amounts of the coins C 2 and C 4 has not yet exceeded the—for example daily—limit of the transactions for the second terminal M2.
  • the monitoring register 6 can also monitor a limit for a time-independent number of transactions (area verification after 3/5/10/... transactions).
  • the monitoring register 6 can make up for a range check for the individual coin data sets that are linked in the data structure 920 of the monitoring register 6 with the pseudonym P M 2 (Is the monetary amount of each coin data set Z2 and Z4 less than X? ). If checks were successfully made up for, the corresponding data records in the data structure 920 of the monitoring register 6 can also be deleted.
  • the transaction register 4 has the transaction data records TDS 902 , TDS 905 and TDS 906 in encrypted form.
  • the transaction data records are decrypted and pseudonymised.
  • the identifiers of the terminals M1 to M3 are replaced by the pseudonyms P and the respective amount is converted into amount categories.
  • the pseudonymized unencrypted transaction data records are sent to the monitoring register 6. Since the sum of the monetary amounts of C 2 and coin coin C4 might exceed its Münzschwellwert, calls the monitoring register 6 from the second terminal M2 a sum detection area (or a total area confirmation) on.
  • the amount categories in the pseudonymised transaction data records TDS* are meaningful in such a way that the monitoring register 6 can itself carry out the proof of the sum range using the pseudonymised transaction data records TDS *.
  • the monitoring register 6 can now also carry out a range check for the individual coin data sets using the pseudonymised transaction data sets TDS * .
  • FIG. 18 shows a further exemplary embodiment of a sequence in a payment system BZ with masked coin data sets.
  • a first terminal Ml sends anonymous in steps 151 masked coin data sets to coin register 2.
  • a second terminal M2 sends pseudonymized masked coin data sets to monitoring register 6 in steps 161.
  • the coin register 2 responds to each of the anonymous transmission steps 151 of the first terminal Ml (in its anonymous mode) with a (recoverable) check for the masked coin data set or the first terminal Ml. Any additional tests that may be necessary are not shown in FIG.
  • the coin register 2 requests, for each masked coin record, a range verification that the monetary amount of the masked coin record from step 151 is below a maximum value (or equivalent range confirmation).
  • the coin register 2 requests proof (or confirmation) of the total area from the first terminal M1.
  • the first terminal M1 must create the (or the) requested evidence(s) in step 153 and send them in step 154 so that the (at least one) masked coin data record of step 151 in the coin register 2 is treated as valid.
  • the monitoring register 6 reacts to the first transmission steps 161 of the second terminal M2 (in its pseudonymous mode) by skipping a (repeatable) check for the masked coin data record or the second terminal M2.
  • the masked coin data set sent pseudonymously is registered as valid. Necessary checks, not shown here, are carried out, for example, which, however, do not require further communication with the second terminal M2.
  • the monitoring register 6 stores an association between the pseudonym and the pseudonymously transmitted masked coin data record(s).
  • the monitoring register 6 also reacts analogously to a second (or further) transmission steps 161 of the second terminal M2. In doing so, it checks whether a catch-up criterion has been met for the pseudonym.
  • the monitoring register 6 establishes that a check should be carried out for the pseudonym. It sends a request 162 to the second terminal M2, for example to create area verifications for a number of coin data records or a total area verification.
  • the second terminal M2 creates a number of area verifications, a total area verification or a total area confirmation and sends this to the monitoring register 6 in step 164.
  • multiple coin data records of the second terminal M2 are selected and a sum is formed from their monetary amounts.
  • These coin data records relate either only to pseudonymised coin data records or to anonymous and pseudonymised coin data records (here, the masked coin data records that have already been sent are taken into account and the sum is formed from the monetary amounts of the corresponding unmasked coin data records).
  • the selection can be made using criteria that are either known by the system or by the monitoring register 6 in step 162 were transferred.
  • the criteria are, for example, a period of time, in particular a predefined period of time, in which a total of all monetary amounts should/may not exceed a certain range, for example a monetary amount x euros per time unit y.
  • the criterion can also be a list in the first terminal M1 or in the monitoring register 6.
  • step 164 the requested sum area confirmation (or the requested sum area proof) is transmitted from the second terminal M2 to the monitoring register 6 .
  • the area generally relates to a total of all transactions within a specific time unit that are received and/or sent by a terminal.
  • a mechanism is therefore created with which it is determined how high the total of all monetary amounts that were sent or received by a terminal within a specific time unit is.
  • all of the elements described and/or drawn and/or claimed can be combined with one another as desired.
  • TDS (encrypted) transaction record TDS * Pseudonymized/Anonymized Transaction Record RDS Registry Record
  • Check value (for direct transmission of the coin data set) p , counter value (for aging of the coin data set) p Check value for transaction register n Number of symmetrically divided partial coin data sets n Concealment amount, random number h, h Concealment amount of a divided electronic coin data set r m Concealment amount of an electronic coin data set to be connected Ci* transmitted electronic coin data set *, Ck* transmitted split electronic coin part record,

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un système de paiement destiné à effectuer des paiements avec des jeux de données de pièces de monnaie électroniques qui présente un registre de pièces de monnaie, destiné à enregistrer les jeux de données de pièces de monnaie électroniques, des unités d'abonnés, destinées à effectuer des transactions de paiement par transfert des jeux de données de pièces de monnaie électronique et à envoyer des demandes de statut et d'enregistrement concernant les jeux de données de pièces de monnaie électroniques au registre de pièces de monnaie et un registre de contrôle, destiné à évaluer des jeux de données de contrôle concernant les transaction de paiement, un jeu de données de contrôle présent dans le registre de contrôle se composant d'au moins d'un jeu de données de registre et d'au moins un jeu de données de transaction, ledit au moins un jeu de données de registre étant fourni par le registre de pièces de monnaie et ledit au moins un jeu de données de transaction étant fourni par une source de jeux de données de transaction et/ou le registre de pièces de monnaie. L'invention concerne en outre un registre de pièces de monnaie, un registre de contrôle, un registre de transaction, une unité d'abonnés et un procédé de paiement avec des jeux de données de pièces de monnaie électroniques.
EP21739313.1A 2020-07-08 2021-06-30 Système de paiement, registre de pièces de monnaie, unité d'abonnés, registre de transaction, registre de contrôle et procédé de paiement avec des ensembles de données de pièces de monnaie électroniques Pending EP4179486A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102020004122.1A DE102020004122A1 (de) 2020-07-08 2020-07-08 Bezahlsystem, münzregister, teilnehmereinheit, transaktionsregister, überwachungsregister und verfahren zum bezahlen mit elektronischen münzdatensätzen
PCT/EP2021/068059 WO2022008320A1 (fr) 2020-07-08 2021-06-30 Système de paiement, registre de pièces de monnaie, unité d'abonnés, registre de transaction, registre de contrôle et procédé de paiement avec des ensembles de données de pièces de monnaie électroniques

Publications (1)

Publication Number Publication Date
EP4179486A1 true EP4179486A1 (fr) 2023-05-17

Family

ID=76829537

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21739313.1A Pending EP4179486A1 (fr) 2020-07-08 2021-06-30 Système de paiement, registre de pièces de monnaie, unité d'abonnés, registre de transaction, registre de contrôle et procédé de paiement avec des ensembles de données de pièces de monnaie électroniques

Country Status (5)

Country Link
US (1) US20230267426A1 (fr)
EP (1) EP4179486A1 (fr)
CN (1) CN116057555A (fr)
DE (1) DE102020004122A1 (fr)
WO (1) WO2022008320A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4407545A1 (fr) * 2023-01-26 2024-07-31 Giesecke+Devrient advance52 GmbH Élément sécurisé, procédé de remplacement d'un jeton électronique de l'élément sécurisé et élément sécurisé spécial

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5872844A (en) 1996-11-18 1999-02-16 Microsoft Corporation System and method for detecting fraudulent expenditure of transferable electronic assets
US20130311348A1 (en) * 2012-03-09 2013-11-21 Gideon Samid Fitting digital currency into modern transactional ecosystems
ZA201502969B (en) * 2014-05-09 2016-01-27 Univ Stellenbosch Enabling a user to transact using cryptocurrency
WO2017218440A1 (fr) * 2016-06-13 2017-12-21 CloudMode, LLC Déclenchement et transfert sécurisés d'une base de données cryptographique et/ou d'une unité cryptographique
CN110073633B (zh) 2018-11-07 2023-03-31 创新先进技术有限公司 使用同态加密的区块链数据保护
US11127002B2 (en) 2018-11-27 2021-09-21 Advanced New Technologies Co., Ltd. System and method for information protection
KR102256377B1 (ko) * 2019-01-24 2021-05-27 주식회사 더휴먼플러스 블록체인 기반 가상화폐 자동이체 방법 및 그를 위한 서버

Also Published As

Publication number Publication date
US20230267426A1 (en) 2023-08-24
WO2022008320A1 (fr) 2022-01-13
DE102020004122A1 (de) 2022-01-13
CN116057555A (zh) 2023-05-02

Similar Documents

Publication Publication Date Title
EP4111348B1 (fr) Procédé de transmission directe de jeux de données de pièces de monnaie électroniques entre terminaux, système de paiement, système de protection et unité de surveillance
DE69534490T2 (de) Verfahren zur sicheren anwendung digitaler unterschriften in einem kommerziellen verschlüsselungssystem
EP3474172B1 (fr) Contrôle d'accès à l'aide d'une chaîne de blocs
DE69521413T2 (de) Verschlüsselungseinrichtung und verfahren mit möglichkeit zur gesicherten zentralen schlüsselablage
WO2020212331A1 (fr) Dispositif pour le transfert direct d'ensembles de données de pièces de monnaie électroniques vers un autre dispositif et système de paiement
DE102019002732A1 (de) Verfahren zum direkten Übertragen von elektronischen Münzdatensätzen zwischen Endgeräten sowie Bezahlsystem
WO2022008322A1 (fr) Procédé, unité participante, registre de transaction et système de paiement pour gérer des ensembles de données de transaction
CN109417478A (zh) 多链路密码逻辑区块链
EP3319006A1 (fr) Procédé de contrôle d'authenticité hors ligne d'un document virtuel
EP3318999A1 (fr) Procédé de délivrance d'une version virtuelle d'un document
DE112021002053T5 (de) Verrauschte Transaktion zum Schutz von Daten
WO2022008319A1 (fr) Entité d'émission et procédé d'émission d'ensembles de données électroniques de pièces de monnaie, et système de paiement
WO2022233454A1 (fr) Procédé d'enregistrement d'un ensemble de données de pièces électroniques dans un registre de pièces ; registre de pièces ; unité d'abonné et produit de programme d'ordinateur
WO2022200035A1 (fr) Procédé et dispositif pour générer, fournir et transférer un ensemble de données ou un certificat électronique de confiance sur la base d'un document électronique concernant un utilisateur
EP4111399B1 (fr) Procédé, terminal, entité de surveillance et système de paiement pour gérer des ensembles de données électroniques de pièces de monnaie
EP4179486A1 (fr) Système de paiement, registre de pièces de monnaie, unité d'abonnés, registre de transaction, registre de contrôle et procédé de paiement avec des ensembles de données de pièces de monnaie électroniques
EP4179489A1 (fr) Procédé, terminal et registre de pièces pour transmettre des jeux de données de pièces électroniques
EP4111347B1 (fr) Procédé de transmission directe d'ensembles de données de pièce de monnaie électronique entre terminaux, système de paiement, système de protection et entité de surveillance
DE102021000570A1 (de) Verfahren zum bereitstellen eines nachweisdatensatzes; verfahren zum prüfen eines nachweisdatensatzes; ein münzregister; eine teilnehmereinheit und ein computerprogrammprodukt
DE102020104902A1 (de) Verfahren zum direkten übertragen von elektronischen münzdatensätzen zwischen endgeräten, bezahlsystem, währungssystem und überwachungsinstanz
WO2023202836A1 (fr) Dispositifs, système et procédé de paiement électronique scriptural

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230208

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)