Integrated bank chip card, digital RMB touch and quasi account reading interface method

Abstract

The invention discloses an integrated bank chip card, digital RMB touch and quasi account reading interface method, which comprises an interface calling process for reading a bank chip card and an interface calling process for digital RMB touch and quasi account, and is characterized in that an application layer and a service layer realize interaction by calling corresponding interfaces; therefore, on-line transactions of the bank chip card and the digital RMB and the quasi account can be realized. The method has the advantages that the intelligent POS machine can support two scenes of bank chip card reading, digital RMB touching and accurate account payment at the same time, in the payment scene, payment can be easily completed by taking out a mobile phone or a card to touch an induction area on the POS machine or inserting the card, the user does not need to select which payment card, and great convenience is brought to the use of the user.

Description

Technical Field

[0001] The present invention relates to the field of smart POS machine mobile payment technology, and in particular to a method for integrating a bank chip card, digital RMB touch and quasi-account reading interface. Background Art

[0002] As technology continues to advance, the functions and roles of smart POS machines will continue to evolve and innovate, providing merchants and consumers with more secure, convenient, and efficient services. At the same time, with the rise of emerging payment methods like mobile payments and digital currencies, smart POS machines also need to continue to innovate and upgrade to adapt to market changes.

[0003] POS machines can read bank cards in three ways: insert, swipe, and wave. The wave method requires the user to wave a card with a swipe function over a designated area on the POS machine, which then reads the card information using near-field communication (NFC) technology. This method improves transaction convenience, reduces physical contact, and increases security.

[0004] The digital RMB's "touch and pay" feature is an innovative payment method that allows users to complete payments through simple physical contact, greatly improving payment convenience and efficiency. This payment method, based on the NFC payment function of the digital RMB hardware wallet, allows users to complete payments with a simple tap of their phone or other device. The launch of the digital RMB aims to replace traditional cash payments, providing a new, digital payment method to meet modern society's demand for convenient, secure, and efficient payments.

[0005] At present, POS machines read bank cards, digital RMB "touch and pay" and quasi-account transactions, which are all separate transaction entrances. Different payment methods require the selection of different transactions to deduct money. The present invention provides an integrated bank chip card, digital RMB "touch and pay" and quasi-account reading interface method, which can effectively solve this problem. Regardless of whether it is a bank card, digital currency "touch and pay" or quasi-account transaction, a unified interface is called to complete card reading and deduction, which is very convenient to use. There is no need to go to the POS to select different payment interfaces according to the customer's payment method. Summary of the Invention

[0006] The purpose of the present invention is to provide an integrated bank chip card, digital RMB touch and quasi-account reading interface method, so as to solve the above-mentioned problems existing in the prior art.

[0007] In order to achieve the above object, the technical solution adopted by the present invention is as follows:

[0008] A method for integrating a bank chip card, a digital RMB payment and a quasi-account reading interface, including an interface calling process for reading a bank chip card and an interface calling process for a digital RMB payment and a quasi-account.

[0009] The interface call process for reading bank chip cards is as follows:

[0010] A1. The application layer calls the DeviceHelper.getPBOC().waitCard() interface to notify the service layer and wait for the card reading operation;

[0011] A2. The service layer searches for the card through the searchCard() method in the getPBOC interface callback. After reading the chip card, it calls back to the onCardPowerUp() method in the application layer through the OnSearchCardListener interface.

[0012] A3. The application layer starts calling the startPBOC method in the onCardPowerUp() method, notifying the service layer to start executing the card's PBOC process;

[0013] A4. The application layer processes the PBOC result through the onTransactionResult method in the OnPBOCHandler interface;

[0014] The interface calling process for the digital RMB touch and quasi-account is as follows:

[0015] B1. The application layer calls the DeviceHelper.getRFCardReader().waitCard() interface to notify the service layer and wait for the card reading operation;

[0016] B2. The service layer searches for the card through the waitCard() method in the getRFCardReader() callback. After reading the chip card, it calls back to the onCardPass method in the application layer through the OnPassListener parameter in the waitCard() method.

[0017] B3. The application layer calls the exchangeApdu interface in the onCardPass method to interact with the server for digital RMB payment and quasi-account instructions.

[0018] B4. When the command interaction result returns 9000, it means the interaction is successful;

[0019] B5. After all command interactions are successful, enter the online trading process.

[0020] Preferably, the PBOC process specifically includes the following contents:

[0021] C1. Detection card;

[0022] C2. Application selection: This includes creating a candidate list and selecting candidate applications. When creating the candidate list, select the PPSE named "2PAY.SYS.DDF01". The card will return a list of all supported AIDs. By comparing it with the terminal's local AID table, it will find commonly supported AIDs and create a candidate list. When selecting a candidate application, directly select the AID with the highest priority.

[0023] C3, Application initialization: When selecting AID, the data returned by the card must contain PDOL, and the tag list of PDOL must contain terminal transaction attributes;

[0024] C4. Read application data: If the card returns AFL during application initialization, you need to read the application data record;

[0025] C5. Terminal risk management: Blacklist detection is incorporated into the record reading process. When a record contains the primary account, the blacklist is checked immediately. If the account is on the blacklist, the transaction is terminated immediately.

[0026] C6. Online transactions.

[0027] Preferably, in step C4, the terminal can choose to support online ODA, then the record reading process will also be executed when the transaction is online. After the record reading is completed, the card can be taken away, and the subsequent process will no longer interact with the card.

[0028] Preferably, in step C5, the validity period check is placed before reading the last record. If the check fails, the last record does not need to be read.

[0029] Preferably, the interactive process of digital RMB payment and quasi-account instructions includes the following contents:

[0030] D1. Detection card;

[0031] D2. Application selection: This includes establishing a candidate list and selecting candidate applications. When establishing the candidate list, select the PPSE named "2PAY.SYS.DDF01". The card will then return a list of all supported AIDs. By comparing it with the local AID table of the terminal, it will find the commonly supported AIDs and establish a candidate list. When selecting a candidate application to use, directly select the AID with the highest priority. For quasi-accounts, proceed to step D3. For digital RMB payment, proceed to step D4.

[0032] D3. Feature Negotiation: Before the hardware wallet executes a transaction, it joins the feature negotiation mechanism to negotiate the transaction model, version, exchange interaction capability parameters, and subsequent function expansion. The negotiation determines the characteristics of the transaction between the two parties. Then, it proceeds to step D5.

[0033] D4. Obtain payment code: The terminal exchanges APDU commands with the card to obtain the payment code information in the card, and then sends the payment code information in the card to the backend for online transaction.

[0034] D5. Single offline payment: The payee's POS terminal sends a PAY OPERATION ONLINE command to the payment wallet. After receiving the command, the payee's hardware wallet generates the payer's payment information and returns it to the POS terminal. The payee's POS terminal then sends the payer's payment information and payment password to the payment operator's backend via a message to conduct an online transaction.

[0035] D6. Online transactions.

[0036] Preferably, in step D3, the characteristics of this transaction include transaction model, transaction instruction version information, expression version information, terminal type, and networking capability.

[0037] Preferably, in step D5, the payer's payment information includes session key, transaction index, plaintext data, MAC information

[0038] The beneficial effects of the present invention are as follows: 1. Through the method of the present invention, smart POS machines can simultaneously perform bank card, digital currency tap-to-pay, and quasi-account transactions, greatly facilitating user experience. 2. Through the method of the present invention, the smart POS machine's card-swiping and digital currency tap-to-pay functions utilize advanced NFC technology and UnionPay's security mechanisms, ensuring transaction and product security. During transactions, the NFC tag can read the unique business ID information on its built-in chip for comparison, effectively preventing duplication and tampering and improving payment security. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 It is a schematic diagram of the communication between the application layer and the service layer in the prior art;

[0040] Figure 2 This is a schematic diagram of the interface call flow for reading a bank chip card in an embodiment of the present invention;

[0041] Figure 3 This is a schematic diagram of the PBOC process in an embodiment of the present invention;

[0042] Figure 4 This is a schematic diagram of the interface call flow for digital RMB touch and quasi-account in an embodiment of the present invention;

[0043] Figure 5 This is a schematic diagram of the interaction between the digital RMB payment and quasi-account instructions in an embodiment of the present invention. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0045] In this embodiment, a method for integrating a bank card chip, a digital RMB touch and a quasi-account reading interface is provided. This method solves the drawbacks of the existing startActivityForResul t method through an interface call method. Through a well-defined interface protocol, the application layer and the server can implement the corresponding interface according to the defined interface specification, and achieve the implementation of business logic by calling the corresponding interface function. The method specifically includes two interface call processes, namely,

[0046] 1. Interface call process for reading bank chip cards

[0047] See attached Figure 2 ,The specific interface calling process is as follows,

[0048] 1.1. The application layer notifies the service layer by calling the DeviceHelper.getPBOC().waitCard() interface and waits for the card reading operation.

[0049] 1.2. The service layer searches for the card through the searchCard() method in the getPBOC interface callback. After reading the chip card, it calls back to the onCardPowerUp() method in the application layer through the OnSearchCardListener interface.

[0050] 1.3. The application layer starts calling the startPBOC method in the onCardPowerUp() method, notifies the service layer, and starts executing the card's PBOC process (refer to Figure 3 ).

[0051] 1.4. When the server-side PBOC process is completed, it will be called back to the application layer through the parameter OnPBOCHandler in the startPBOC method.

[0052] 1.5. Finally, the application layer processes the PBOC result through the onTransactionResult method in the OnPBOCHandler interface.

[0053] In this embodiment, the PBOC specification is called the China Financial Integrated Circuit (IC) Card Specification, which is a set of specifications that regulate the design, production, and use of IC cards. Contactless IC card transactions follow this standard process. The PBOC process is as follows:

[0054] (1) Application selection

[0055] Application selection primarily involves two steps: creating a candidate list and selecting a candidate application. When creating a candidate application, simply select the PPSE named "2PAY.SYS.DDF01." The card will then return a list of all supported AIDs. The card then compares this list with the terminal's local AID table to identify commonly supported AIDs, creating a candidate list. When selecting a candidate application, the user no longer needs to select a candidate; the highest-priority AID is directly selected.

[0056] (2) Application initialization

[0057] The terminal application initialization process is similar to card insertion, but requires that the data returned by the card include the PDOL (9F39) when selecting the AID, and the terminal transaction attributes (9F66) must be included in the PDOL tag list. Generally, the terminal transaction attributes are set during pre-processing. The card will then return the transaction result, indicating offline, online, or rejected, along with relevant data.

[0058] (3) Read application data

[0059] If the card returns AFL (0x94) during application initialization, the application data record needs to be read. In the original version of q'PBOC, AFL was only returned, and the record read process was only performed, when the card decided to complete the transaction offline. However, in the latest version of qPBOC, terminals can optionally support online ODA (offline authentication), and the record read process will also be performed when the transaction is online. After the record read is completed, the card can be removed, and the following process no longer interacts with the card.

[0060] (4) Terminal risk management

[0061] Terminal risk management mainly involves checking whether the main account is on the blacklist, whether the card is expired, etc.

[0062] In this embodiment, blacklist detection is integrated into the record reading process. When a record containing the primary account number is read, the blacklist is immediately checked. If the account number is on the blacklist, the transaction is immediately terminated. Previous versions only included the record reading process for offline transactions, and deductions were only made when the last record was read (generally, the last record contained the authorization code of the electronic cash issuing bank). Exiting early prevents deductions from occurring even when the transaction is terminated. The implementation in this embodiment also recommends checking the validity period before reading the last record. If the check fails, the last record is not read.

[0063] 2. Interface calling process for digital RMB touch and quasi-account

[0064] See attached Figure 4 ,The specific interface calling process is as follows,

[0065] 2.1. The application layer notifies the service layer by calling the DeviceHelper.getRFCardReader().waitCard() interface and waits for the card reading operation.

[0066] 2.2. The service layer searches for the card through the waitCard() method in the getRFCardReader() callback. After reading the chip card, it calls back to the onCardPass method of the application layer through the OnPassListener parameter in the waitCard() method.

[0067] 2.3. At this time, the application layer calls the exchangeApdu interface in the onCardPass method to interact with the server.

[0068] 2.4. When the command interaction result returns 9000, it means the interaction is successful.

[0069] 2.5. After all command interactions are successful, enter the online trading process.

[0070] In this embodiment, the quasi-account hard wallet has a single offline payment capability. The acceptance terminal obtains payment information and transmits it to the institution's backend for transaction by interacting with the quasi-account mode hard wallet through specific instructions. The process of digital RMB touch and quasi-account instruction interaction is as follows:

[0071] (1) Application selection

[0072] Application selection is a common process before transactions. To ensure application compatibility and scalability, the AID returned by the card is compared with the AID of the local terminal to find mutually supported AID applications.

[0073] (2) Feature Negotiation (quasi-account)

[0074] Before the hardware wallet executes a transaction, a feature negotiation mechanism is added to negotiate the transaction model, version, exchange interaction capability parameters, and subsequent function expansion. The negotiation determines the characteristics of the transaction between the two parties, including transaction model, transaction instruction version information, expression version information, terminal type, network capability, and other parameters.

[0075] (3) Get the payment code (touch and pay)

[0076] The terminal interacts with the card through APDU commands to obtain the payment code information in the card, and then sends it to the backend for online transactions.

[0077] (4) Single offline payment (quasi-account)

[0078] The payee's POS terminal sends a PAY OPERATION ONLINE command to the payer's wallet. Upon receiving this command, the payer's hardware wallet generates the payer's payment information (session key, transaction index, plaintext data, MAC, etc.) and returns it to the POS terminal. The payee's POS terminal then sends the payer's payment information (plaintext data, MAC) and payment password (optional) via a message to the payment operator's backend. Finally, the online transaction is completed.

[0079] By adopting the above technical solution disclosed in the present invention, the following beneficial effects are obtained:

[0080] This invention provides a method for integrating a bank chip card, digital RMB tap-to-pay, and quasi-account reading interface. Through this method, a smart POS machine can simultaneously perform bank card, digital currency tap-to-pay, and quasi-account transactions, greatly facilitating user experience. Through this method, the smart POS machine's card-swiping and digital currency tap-to-pay functions utilize advanced NFC technology and UnionPay's security mechanisms, ensuring transaction and product security. The NFC tag can read the unique business ID registration information of the built-in chip during transactions for comparison, effectively preventing duplication and tampering and improving payment security.

[0081] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for integrating a bank chip card, digital RMB tap-and-pay, and quasi-account reading interface, characterized by: Including the interface calling process for reading bank chip cards and the interface calling process for digital RMB touch and quasi-accounts, The interface call process for reading bank chip cards is as follows: A1. The application layer calls the DeviceHelper.getPBOC().waitCard() interface to notify the service layer and wait for the card reading operation; A2. The service layer searches for the card through the searchCard() method in the getPBOC interface callback. After reading the chip card, it calls back to the onCardPowerUp() method in the application layer through the OnSearchCardListener interface. A3. The application layer starts calling the startPBOC method in the onCardPowerUp() method, notifying the service layer to start executing the card's PBOC process; A4. The application layer processes the PBOC result through the onTransactionResult method in the OnPBOCHandler interface; The interface calling process for the digital RMB touch and quasi-account is as follows: B1. The application layer calls the DeviceHelper.getRFCardReader().waitCard() interface to notify the service layer and wait for the card reading operation; B2. The service layer searches for the card through the waitCard() method in the getRFCardReader() callback. After reading the chip card, it calls back to the onCardPass method in the application layer through the OnPassListener parameter in the waitCard() method. B3. The application layer calls the exchangeApdu interface in the onCardPass method to interact with the server for digital RMB payment and quasi-account instructions. B4. When the command interaction result returns 9000, it means the interaction is successful; B5. After all command interactions are successful, enter the online trading process.

2. The integrated bank chip card, digital RMB tap-to-pay, and quasi-account reading interface method according to claim 1, characterized in that: The PBOC process specifically includes the following contents: C1. Detection card; C2. Application selection: This includes creating a candidate list and selecting candidate applications. When creating the candidate list, select the PPSE named "2PAY.SYS.DDF01". The card will return a list of all supported AIDs. By comparing it with the terminal's local AID table, it will find commonly supported AIDs and create a candidate list. When selecting a candidate application, directly select the AID with the highest priority. C3, Application initialization: When selecting AID, the data returned by the card must contain PDOL, and the tag list of PDOL must contain terminal transaction attributes; C4. Read application data: If the card returns AFL during application initialization, you need to read the application data record; C5. Terminal risk management: Blacklist detection is incorporated into the record reading process. When a record contains the primary account, the blacklist is checked immediately. If the account is on the blacklist, the transaction is terminated immediately. C6. Online transactions.

3. The integrated bank chip card, digital RMB tap-to-pay, and quasi-account reading interface method according to claim 2, characterized in that: In step C4, if the terminal can choose to support online ODA, the record reading process will also be executed when the transaction is online. After the record reading is completed, the card can be taken away and there will be no further interaction with the card in the subsequent process.

4. The integrated bank chip card, digital RMB tap-and-pay, and quasi-account reading interface method according to claim 2, characterized in that: In step C5, the validity period check is placed before reading the last record. If the check fails, the last record does not need to be read.

5. The integrated bank chip card, digital RMB tap-and-pay, and quasi-account reading interface method according to claim 1, characterized in that: The interactive process of digital RMB payment and quasi-account instructions includes the following: D1. Detection card; D2. Application selection: This includes establishing a candidate list and selecting candidate applications. When establishing the candidate list, select the PPSE named "2PAY.SYS.DDF01." The card will then return a list of all supported AIDs. By comparing it with the terminal's local AID table, it will find commonly supported AIDs and establish a candidate list. When selecting candidate applications, directly select the AID with the highest priority. For quasi-accounts, proceed to step D3. For digital RMB payment, proceed to step D4. D3. Feature Negotiation: Before the hardware wallet executes a transaction, it joins the feature negotiation mechanism to negotiate the transaction model, version, exchange interaction capability parameters, and subsequent function expansion. The negotiation determines the characteristics of the transaction between the two parties. Then, it proceeds to step D5. D4. Obtain payment code: The terminal exchanges APDU commands with the card to obtain the payment code information in the card, and then sends the payment code information in the card to the backend for online transaction. D5. Single offline payment: The payee's POS terminal sends a PAY OPERATION ONLINE command to the payment wallet. After receiving the command, the payee's hardware wallet generates the payer's payment information and returns it to the POS terminal. The payee's POS terminal then sends the payer's payment information and payment password to the payment operator's backend via a message to conduct an online transaction. D6. Online transactions.

6. The integrated bank chip card, digital RMB tap-to-pay, and quasi-account reading interface method according to claim 5, characterized in that: In step D3, the characteristics of this transaction include transaction model, transaction instruction version information, expression version information, terminal type, and networking capability.

7. The integrated bank chip card, digital RMB tap-to-pay, and quasi-account reading interface method according to claim 5, characterized in that: In step D5, the payer's payment information includes the session key, transaction index, plaintext data, and MAC information.

Images