Payment processing method and apparatus for identity card

Abstract

The embodiment of the specification provides a payment processing method and device of an identity recognition card, wherein the payment processing method of the identity recognition card comprises the following steps: in a transaction payment process of a park user using an identity recognition card, a transaction amount input by a merchant on a merchant device is acquired, near field communication is established between the merchant device and the identity recognition card, identity recognition card verification is performed based on the near field communication and cooperation with the identity recognition card, payment credentials of the identity recognition card are read after the verification is passed, and finally, the payment credentials are sent to a merchant system accessed by the merchant device, and the merchant system calls a payment interface based on transaction information and the payment credentials to perform transaction payment processing. In this way, the near field communication between the identity recognition card of the park user and the merchant device is used to realize the transaction payment of the park user using the identity recognition card in the park scene.

Description

[0001] This application is a divisional application of Chinese invention patent application No. 202610544005.3, filed on April 23, 2026, entitled "Payment Processing Method and Apparatus for Identification Card". Technical Field

[0002] This document relates to the field of payment processing technology, and in particular to a payment processing method and apparatus for an identification card. Background Technology

[0003] With the continuous development and promotion of the Internet and smart hardware, more and more users are starting to pay for transactions in cashless ways. After purchasing goods offline, users can easily and quickly complete transactions by interacting with merchants' terminal devices through their own devices. Among these, NFC (Near Field Communication) technology, with its convenience and security features, has been widely used in smart access cards, payments, and other related fields. Users can make payments quickly and securely through NFC. As the number of users using NFC technology for payments continues to increase, their needs are becoming more diverse, which places higher demands on NFC payment providers. Summary of the Invention

[0004] This specification provides one or more embodiments of a payment processing method using an identification card, applied to a merchant device. The method includes: obtaining a transaction amount input by the merchant and establishing near-field communication (NFC) with the identification card of a user within the park; performing identification card verification based on the NFC and the identification card; and reading the payment voucher from the identification card after successful verification; and sending the payment voucher to the merchant system connected to the merchant device to perform transaction payment processing through the associated account configured on the identification card, based on the transaction information and the payment voucher, by calling a payment interface.

[0005] This specification provides one or more embodiments of another payment processing method using an identity card, applied to a server. The method includes: receiving transaction information submitted by a merchant's system via a payment interface call, and a payment credential from a user's identity card. The payment credential is read from the identity card after the merchant's device establishes near-field communication with the identity card and verifies the card. Payment verification is performed on the transaction information based on the identity card's configuration. After successful verification, transaction payment is processed based on the associated account configured on the identity card.

[0006] This specification provides one or more embodiments of a payment processing device for an identification card, operating on a merchant device. The device includes: a near-field communication (NFC) establishment module configured to acquire a transaction amount input by the merchant and establish NFC communication with the identification card of a user within the park; an identification card verification module configured to perform identification card verification based on the NFC communication and the identification card, and read the payment voucher from the identification card upon successful verification; and a payment voucher sending module configured to send the payment voucher to a merchant system connected to the merchant device, so as to call a payment interface based on the transaction information and the payment voucher to perform transaction payment processing through the associated account configured on the identification card.

[0007] This specification provides one or more embodiments of another identity card payment processing device, running on a server. The device includes: a call receiving module configured to receive transaction information submitted by a merchant's system via a payment interface call, and a payment credential from a user's identity card. The payment credential is read from the identity card after the merchant's device establishes near-field communication with the identity card and verifies the card. A payment verification module configured to verify the transaction information based on the identity card's configuration. A transaction payment module configured to process the transaction payment based on the associated account configured on the identity card after successful verification.

[0008] This specification provides one or more embodiments of a payment processing device for an identity card, comprising: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire a transaction amount input by a merchant and establish near-field communication with the identity card of a user within the park; perform identity card verification based on the near-field communication and the identity card, and read the payment voucher from the identity card after successful verification; and send the payment voucher to a merchant system connected to the merchant device, so as to call a payment interface based on the transaction information and the payment voucher to perform transaction payment processing through the associated account configured on the identity card.

[0009] This specification provides one or more embodiments of another payment processing device for an identity card, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: receive transaction information submitted by a merchant system calling a payment interface, and a payment credential from an identity card of a user within the park. The payment credential is read from the identity card after the merchant's device establishes near-field communication with the identity card and verifies the identity card. Payment verification is performed on the transaction information based on the identity card's configuration. After successful verification, transaction payment processing is performed on the transaction information based on the associated account configured on the identity card.

[0010] This specification provides one or more embodiments of a computer-readable storage medium for storing computer-executable instructions. When executed, these instructions implement the following process: obtaining the transaction amount input by the merchant and establishing near-field communication with the user's identification card; performing identification card verification based on the near-field communication and the identification card; and reading the payment voucher from the identification card upon successful verification; and sending the payment voucher to the merchant system connected to the merchant's device to process the transaction payment through the associated account configured on the identification card, based on the transaction information and the payment voucher.

[0011] This specification provides one or more embodiments of another computer-readable storage medium for storing computer-executable instructions that, when executed, implement the following process: receiving transaction information submitted by a merchant's system via a payment interface call, and a payment credential from a user's identification card. The payment credential is read from the identification card after the merchant's device establishes near-field communication with the identification card and verifies the card. Payment verification is performed on the transaction information based on the identification card's configuration. Upon successful verification, transaction payment is processed based on the associated account configured on the identification card. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1 A schematic diagram illustrating the implementation environment of a payment processing method for an identity card provided in one or more embodiments of this specification; Figure 2A flowchart illustrating a payment processing method for an identification card, provided for one or more embodiments of this specification; Figure 3 A schematic diagram of a card information configuration page provided for one or more embodiments of this specification; Figure 4 A schematic diagram of a funds management page provided for one or more embodiments of this specification; Figure 5 A schematic diagram illustrating an authorized merchant configuration page provided for one or more embodiments of this specification; Figure 6 This specification provides a flowchart of a payment processing method for an identity card applied in a payment scenario within a park, as provided in one or more embodiments of the present specification. Figure 7 A flowchart illustrating a payment processing method for an identity card applied in an off-site payment scenario within a park, provided by one or more embodiments of this specification. Figure 8 This specification provides a flowchart of a payment processing method for an identification card applied in an institutional payment scenario, which is illustrated in one or more embodiments of this specification. Figure 9 A flowchart illustrating another payment processing method for an identification card provided in one or more embodiments of this specification; Figure 10 A schematic diagram illustrating an embodiment of a payment processing device for an identity card provided in one or more embodiments of this specification; Figure 11 A schematic diagram of another embodiment of a payment processing device for an identity card provided in one or more embodiments of this specification; Figure 12 A schematic diagram of the structure of a payment processing device for an identity card provided for one or more embodiments of this specification; Figure 13 This is a schematic diagram of the structure of another payment processing device for an identity card provided in one or more embodiments of this specification. Detailed Implementation

[0013] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0014] The payment processing method for identity cards provided in one or more embodiments of this specification is applicable to the implementation environment of identity card payment scenarios. (Refer to...) Figure 1 The implementation environment includes at least: Merchant equipment 101, identification cards 102 for park users, and a server 103 for transaction payment processing; in addition, the implementation environment may also include merchant POS equipment 104 running the merchant system; Merchant device 101 refers to the device or machine deployed by the merchant for cashier payment or transaction payment. Merchant device 101 is equipped with a near-field communication component that can communicate with identity card 102. Identity card 102 refers to a credential card made based on the identity of a user in the park for transaction payment. Correspondingly, identity card 102 has a built-in near-field communication component that communicates with merchant device 101. The merchant POS device 104 is used to support the operation of the merchant system. The merchant system is used to connect to the merchant device 101 and interact with the server 103 through interface calls to realize transaction payment processing.

[0015] In this implementation environment, during the transaction payment process based on the identity card 102 of the park user, the merchant first enters the transaction amount on the merchant device 101. After the transaction amount is entered, the merchant device 101 establishes near-field communication with the identity card 102 of the park user, and performs card verification based on the near-field communication and the identity card 102. After successful verification, the payment voucher of the identity card 102 is read, and the payment voucher is further sent to the merchant system connected to the merchant device 101. The merchant system calls the payment interface to send the payment voucher and transaction information to the server. The server 103, based on the payment voucher and transaction information, performs transaction payment processing through the associated account configured on the identity card 102. In this way, based on the near-field communication established between the identity card 102 of the park user and the merchant device 101, the transaction payment made by the park user using the identity card 102 is realized in the park scenario.

[0016] It should be noted that, considering that the user identity information, name, identification, school, student ID, and other related data involved in this specification may, to some extent, constitute user privacy, authorization from the user must be obtained before collecting such data to ensure that the data collection operation complies with relevant data management regulations. For example, data authorization can be granted during the process of an associated user helping another user in the park apply for an identification card. The specific method of data authorization can be through signing a data authorization agreement or a service agreement, which is not limited in this embodiment.

[0017] Reference Figure 2The payment processing method for identity recognition cards provided in this embodiment can be applied to merchant devices. The method specifically includes steps S202 to S206.

[0018] Step S202: Obtain the transaction amount entered by the merchant and establish near-field communication with the identity card of the park user.

[0019] The park users mentioned in this embodiment refer to users with specific identities within a park, such as student users or teacher users in a school, or users with corresponding specific identities in various park locations such as hospitals, enterprises, public service institutions, and office parks.

[0020] Merchants refer to payment merchants used by users within the park for transactions. Specifically, merchants can be merchants located within the park premises; alternatively, merchants can be authorized merchants located outside the park premises, or authorized merchants that meet specific conditions. For example, stationery stores near schools can become authorized merchants for student transactions after obtaining authorization. Correspondingly, merchant equipment refers to payment devices (POS devices) or payment terminals deployed by merchants for cashiering or payment collection. If the merchant equipment is equipped with near-field communication (NFC) components for near-field communication, it can also be called a near-field interaction device or near-field interaction terminal.

[0021] An identity card is an identity credential used to uniquely identify a user's specific identity within a park. Specifically, the identity card is equipped with a near-field communication (NFC) component to establish NFC communication with merchant devices and conduct corresponding transactions and payments. In addition, the identity card can also be equipped with a processing component (security component or security chip). The processing component works with merchant devices to perform security verification during the transaction and payment process, and can also be used to store transaction records. This improves the traceability of transactions through transaction record storage, thereby enhancing the security of transaction payments.

[0022] The identity card also stores user identity information and / or payment credentials. Specifically, the user identity information and / or payment credentials can be stored in the secure storage area or trusted storage space of the processing component through the processing component, or stored in an encrypted or secret manner.

[0023] Furthermore, to enhance the security of transactions and payments using identity cards in conjunction with merchant devices, data encryption can be employed for data interaction with merchant devices. In this case, the identity card can also store encryption and / or decryption keys. For example, the processing component may also store a private key for encrypting user identity information and / or payment credentials.

[0024] In practice, when park users use their ID cards to interact with merchant devices for transaction payments, they first enter the transaction amount on the merchant device. After entering the transaction amount, the park users bring their ID cards close to the merchant device to establish near-field communication between the merchant device and the ID cards.

[0025] In the actual execution process, the process of inputting the transaction amount on the merchant device and establishing near-field communication between the merchant device and the identity card may vary depending on the model, deployment method, and communication mode of the merchant device in the actual transaction payment scenario. There may also be different ways to input the transaction amount and establish near-field communication in various actual transaction scenarios. The following will provide a detailed explanation of the process of inputting the transaction amount and establishing near-field communication with the identity card in various actual transaction scenarios.

[0026] In real-world scenarios, when a merchant has deployed a POS system, the merchant's staff can enter the transaction amount into the POS system. After receiving the entered transaction amount, the POS system transmits the transaction amount to the merchant's device. Optionally, the transaction amount can be entered through the POS system and transmitted to the merchant's device by the POS system. The POS system can be installed on the merchant's POS device, or it can be installed on the merchant's device in a different way.

[0027] Specifically, the merchant equipment can be deployed in a fixed manner, and the connection between the merchant equipment and the merchant POS equipment can be wired or wireless. In addition, the merchant equipment can be a mobile device or a handheld device. In this case, if the merchant equipment is a mobile device, the connection between the merchant equipment and the merchant POS equipment can be wired or wireless; if the merchant equipment is a handheld device, the connection between the merchant equipment and the merchant POS equipment can be wireless.

[0028] Based on this, when the merchant device is connected to the POS system, during the process of establishing near-field communication between the user's ID card and the merchant device, the merchant device establishes near-field communication with the ID card in card reader mode; specifically, if the merchant device's current near-field communication mode is card reader mode, then it establishes near-field communication with the ID card in card reader mode. If the merchant device's current near-field communication (NFC) mode is card emulation mode, meaning the merchant device acts as a "simulated card" to communicate with the card reader, the NFC mode of the merchant device needs to be switched from card emulation mode to card reader mode. In card reader mode, NFC communication is established with the identification card. Specifically, the merchant device can switch from card emulation mode to card reader mode according to a mode switching command (communication switching command). Optionally, NFC communication is established after the merchant device switches from card emulation mode to card reader mode according to the mode switching command. In card emulation mode, the merchant device is used to cooperate with the user terminal for NFC transaction payments.

[0029] The mode switching command can be sent by the POS system; alternatively, it can be received through the payment page of the merchant's device; or, the mode switching command can be generated after the physical accessories of the merchant's device are operated, such as if the merchant's device is equipped with a physical button for switching near-field communication modes, which the merchant personnel can use to switch near-field communication modes.

[0030] It should be noted that when a merchant device has multiple near-field communication modes, during the transaction payment process in conjunction with an identity card, it needs to switch from card emulation mode to card reader mode according to the mode switching command. After the transaction payment is completed, the near-field communication mode of the merchant device can be switched back to card emulation mode to cooperate with the user terminal in card emulation mode for near-field transaction payment, thereby improving the flexibility of the merchant device to conduct transaction payments through different near-field communication modes.

[0031] In addition, in real-world scenarios, there may be situations where merchants do not deploy a POS system, or where the POS system and the merchant system are the same system, or where the merchant system is installed on the merchant's device. In such cases, transaction amount input and near-field communication can be established based on the merchant's actual deployment. Specifically, if the merchant does not deploy a POS system, the merchant's staff can input the transaction amount on the merchant's device. Optionally, the transaction amount can be input through input components configured on the merchant's device (hardware input components, such as a transaction amount input keyboard). Alternatively, merchant personnel can input the transaction amount through a merchant application installed on the merchant's device. Upon receiving the input transaction amount, the merchant application transmits it to the merchant's device. Optionally, the transaction amount can be input and sent to the merchant device via the merchant application installed on the merchant's device. Here, the merchant application installed on the merchant's device can be replaced by a POS system or a merchant system; or, the merchant application and at least one of the POS system and merchant system can be the same application. Furthermore, the merchant application can be a third-party application provided to the merchant by a third-party application provider, and the merchant system can be a third-party system provided to the merchant by a third-party system provider.

[0032] Based on this, during the process of establishing near-field communication between the ID card and the merchant device, the merchant device also establishes near-field communication with the ID card in card reader mode; if the current merchant device is only configured with card reader mode as the near-field communication mode, then it establishes near-field communication with the ID card in card reader mode. In addition, if the merchant's device is configured with two near-field communication (NFC) modes, the current NFC mode of the merchant's device will be detected. If the current NFC mode of the merchant's device is card reader mode, NFC communication with the identification card will be established in card reader mode. If the current NFC mode of the merchant's device is card emulation mode, the NFC mode of the merchant's device needs to be switched from card emulation mode to card reader mode. Specifically, the merchant's device can switch from card emulation mode to card reader mode according to the mode switching command. Optionally, NFC communication will be established after the merchant's device switches from card emulation mode to card reader mode according to the mode switching command.

[0033] It should be noted that the model, deployment method, communication mode, and other related content of the merchant's equipment in the two actual scenarios provided above can be combined or replaced in any way to form a new implementation method according to the deployment or execution needs of the actual scenario. Furthermore, the process of inputting the transaction amount and establishing near-field communication with the identity card provided in the above actual scenarios can also be combined or replaced in any way to form a new implementation method according to the deployment or execution needs of the actual scenario.

[0034] In practical implementation, based on establishing near-field communication between the merchant device and the identification card, to improve the flexibility of transaction payments and compatibility for various scenarios, corresponding payment applications can be configured in the merchant device for different identification cards. Specifically, in one optional implementation provided in this embodiment, after establishing near-field communication with the identification card of the park user, the payment application for transaction payment on the merchant device is determined according to the identification information sent by the near-field communication component built into the identification card. Here, the payment application refers to the application running on the merchant device and performing subsequent transaction payment-related processing; specifically, subsequent card verification is performed based on near-field communication and the identification card. After successful verification, the payment voucher of the identification card is read and sent to the merchant system connected to the merchant device, which can be executed by the determined payment application. Optionally, the payment application includes the device system configured on the merchant device or the payment application installed on the device system; in addition, the payment application can also be a merchant application or a third-party application installed on the device system.

[0035] The identification information sent by the near-field communication component can be the component identifier of the near-field communication component, or it can be the payment application identifier or field identifier used to identify the payment application; the component identifier, payment application identifier or field identifier can be stored by the processing component of the identity card.

[0036] In this embodiment, the identification card differs from a general physical card. On one hand, the identification card is used to uniquely identify the specific identity of a user in the park. On the other hand, the identification card also has a built-in near-field communication component and can further have a built-in processing component (security component). Based on this, the account corresponding to the identification card is also different from the physical card account of a general physical card. The identification card in this embodiment is configured with an associated account. The following describes the identification card and the associated account configured on the identification card in various practical application scenarios.

[0037] In a real-world scenario, some users within a campus may lack payment permissions. For example, in a school setting, student users may lack user terminals and be unable to directly apply for, configure, or manage identification cards. To address this and improve the convenience of identification card management, a user's associated user can assist with the application and configuration of identification cards. Specifically, in one optional implementation of this embodiment, the identification card is created after the user's associated user accesses the target service to apply for the card. The target service can be a payment application or a service subroutine within the payment application.

[0038] In this scenario, during the configuration of the associated account for the identity card, a sub-account can be created under the associated user's user account based on the associated user's card configuration request. This created sub-account will then be used as the associated account in the identity card configuration. Optionally, the associated account is obtained by creating a sub-account under the associated user's user account based on the associated user's card configuration request.

[0039] After obtaining an identification card, users in the park can use it to make transactions at merchants within the park. In addition, merchants can be authorized for the identification card to expand its payment scope. Specifically, the associated user can configure the merchant authorization for the identification card in the target service to obtain the authorized merchants for the identification card. The authorized merchants can be specific merchants outside the park.

[0040] Optionally, payment merchants for the identity card include: merchants within the park premises, and authorized merchants outside the park configured for the identity card. Authorized merchants are obtained by the associated user after configuring merchant authorization for the identity card in the target service.

[0041] For example, in school settings where students lack a user terminal and cannot directly apply for, configure, or manage identification cards, parents can assist them. Specifically, during the identification card application process, parents access the card information configuration page through a service subroutine. Figure 3 As shown, on the card information configuration page, enter the student user's name, identification information, school, and student ID. After configuration, the parent user can click the "Agree to the Agreement, Next" control to authorize and confirm. After confirmation, a linked sub-account will be created under the parent user's funds account. This linked sub-account is the linked account configured for the student user's identification card. Furthermore, the parent user can... Figure 4 The identity card's funds management page allows for transfers to associated accounts; additionally, the "Receive Payment" control 401 configured on the funds management page can be triggered to receive payments through associated accounts, and the "Automatic Transfer In" control 402 can be triggered to configure an automatic transfer scheme for associated accounts; simultaneously, the "Off-Campus Payment" control 403 can be triggered to configure authorized merchants outside of school premises. The authorized merchant configuration page is shown below. Figure 5 As shown, parents can select one or more merchants from the list of authorized merchants outside the school to authorize payment. After activation, students can use their identity cards to make transactions at authorized off-campus merchants.

[0042] In another practical scenario, there may be situations where users in a park use institutional accounts for transaction payments. For example, in park settings such as hospitals or office parks, when a user in the park makes a transaction payment as a member of an institution, the institution can act on their behalf to make the payment. In this case, the identification card can correspond to the user's status as a member of the institution. Accordingly, the identification card can be a member identification card representing the member's status within the institution or an institutional identification card. In this case, the identification card can be configured and obtained by the institution's management members, for example, by applying for an identification card through the target service and then creating it.

[0043] Based on this, in the process of configuring the associated account of the identity card, the organization account can be configured as the associated account of the identity card according to the card configuration request of the organization's management members. Alternatively, an organization sub-account can be created under the organization account for each organization member as the associated account of the identity card. Furthermore, to prevent institutional members from exceeding payment limits when using institutional accounts or sub-accounts for transactions, their user accounts can be configured together with the institutional account or sub-account as linked accounts configured on the identity card. Optionally, linked accounts include the institutional account of the institution to which the park user belongs and / or the user account of the park user. Here, the payment priority of the institutional account or sub-account is higher than that of the user account.

[0044] In addition, in real-world scenarios, merchants may provide membership cards to their members, who then purchase and use these cards for transactions. In this case, park users can be replaced by the merchant's members. Accordingly, the membership cards include the park users' (members') membership cards at the merchant and are issued to the park users after they purchase the cards. To ensure the security of funds paid by members for purchasing membership cards, these funds can be transferred to an escrow account. This escrow account can be managed by a financial institution or an asset management institution with the appropriate fund management / custody authority. Furthermore, during the configuration of the associated account for the membership card, the escrow account can be configured as the associated account for the membership card. Optionally, the associated account includes an escrow account used to store the funds used by users within the park to purchase cards.

[0045] Step S204: Based on the near-field communication and the identity card, perform identity card verification, and read the payment voucher of the identity card after successful verification.

[0046] In practice, based on the aforementioned establishment of near-field communication between the merchant device and the identification card, in order to ensure the security of transaction payment through the interaction between the identification card and the merchant device, identification card verification can be performed in conjunction with the identification card based on near-field communication, and a payment voucher for the identification card can be obtained after successful verification.

[0047] The payment credential refers to a credential used to identify the payment identifier of an identity card, such as a payment credential code or payment token pre-generated and stored on the identity card. In addition, the payment credential can also be a dynamic payment credential generated during the current transaction payment process, specifically a dynamic payment credential code or a dynamic payment token. In this case, the operation of reading the payment credential of the identity card can be replaced by generating the payment credential of the identity card, or it can be replaced by generating the payment credential of the identity card and sending the payment credential to the identity card to store the payment credential corresponding to the current transaction payment on the identity card.

[0048] In one optional implementation of this embodiment, identification card verification is performed based on near-field communication in conjunction with an identification card, including: The system sends verification information to the identity card via near-field communication and receives the returned encrypted identity information; the encrypted identity information is generated by the processing component built into the identity card. The user identity information and verification information obtained by decrypting the encrypted identity information are used to verify the verification result.

[0049] In practice, verification information can be sent to the identity card via near-field communication. The verification information can be a specific string or a generated random string. After the verification information is sent to the identity card, the processing component built into the identity card reads the stored user identity information and encryption private key, encrypts the user identity information and verification information using the encryption private key to obtain encrypted identity information, and returns the encrypted identity information to the merchant device. After receiving the encrypted identity information, the merchant device decrypts the encrypted identity information using the identity card's public key and compares the decrypted verification information with the previously sent verification information. If they match, the verification is successful; if they do not match, the verification is unsuccessful.

[0050] In this embodiment, to improve the traceability of transactions made using an identity card, thereby indirectly enhancing the security of identity card-based transactions, transaction payment information can be stored in the identity card. Specifically, transaction payment information initiated through the identity card can be stored in the identity card before the transaction is completed. In an optional implementation of this embodiment, after identity card verification is performed using near-field communication (NFC), a transaction record to be paid is created based on the transaction information and sent to the identity card via NFC. The processing component built into the identity card then stores and processes the transaction record to be paid. The transaction information includes the transaction amount, and may also include at least one of the following: transaction time, user identity information, merchant information, and transaction order information.

[0051] Step S206: Send the payment voucher to the merchant system connected to the merchant device, so as to call the payment interface based on the transaction information and the payment voucher to process the transaction payment through the associated account configured on the identity card.

[0052] After obtaining the payment credential from the identity card, the payment credential is sent to the merchant system connected to the merchant device. Based on the transaction information and the payment credential, the payment interface is invoked to process the transaction payment through the associated account configured on the identity card. Here, the merchant system can be the merchant order system that processes orders, and the transaction information can be submitted to the merchant system by the merchant's POS system or merchant application; alternatively, the merchant system can be a POS system or merchant application, and the transaction information can be generated by the merchant system based on the transaction amount. Furthermore, the merchant system can also be a device system or a payment application. In this case, the transaction information can be generated by the device system or payment application based on the transaction amount. Optionally, the device system or payment application is in a system login state or an application login state after logging into the merchant account.

[0053] In practice, during the transaction payment processing via the associated account configured on the identity card, based on transaction information and payment credentials, the transaction information and payment credentials serve as input parameters for the interface call. After the payment interface call is performed based on these parameters, the transaction information and payment credentials are submitted to the server (payment server). Upon receiving the submitted transaction information and payment credentials, the server processes the transaction payment via the associated account configured on the identity card. Optionally, the payment interface may include the payment interface of the payment component configured in the device system, or the payment interface of the payment application.

[0054] In one optional implementation of this embodiment, transaction payment processing is performed through an associated account configured on an identity card, including: The identification card configuration based on the identity card is used to verify payment information for transactions; After verification, the transaction payment is processed based on the associated account. The associated account can be determined based on the payment voucher or the user identity information contained in the transaction information.

[0055] Specifically, in the process of verifying payment information for transaction information based on the identification card configuration, payment verification can be performed by checking whether the merchant is in the payment merchant list configured on the identification card, by checking whether the payment voucher is consistent with the payment voucher corresponding to the user in the park, and by verifying whether the transaction information meets the fee control configuration in the identification card configuration. In one optional implementation provided in this embodiment, verifying payment information for transaction information based on the identification card configuration includes: checking whether the merchant is in the payment merchant list configured on the identification card; if so, verifying whether the transaction information meets the fee control configuration in the identification card configuration; if so, determining that the verification has passed; otherwise, determining that the verification has failed.

[0056] To further enhance the traceability of transactions made using identity cards, thereby indirectly improving the security of identity card transactions, a transaction completion record corresponding to the payment result can be generated and sent to the identity card after the transaction is completed, so that it can be stored and processed by the processing component built into the identity card.

[0057] Specifically, in one optional implementation of this embodiment, after transaction payment is processed through the associated account configured on the identity card, the payment result returned by the interface call or the payment result sent by the merchant system is received; a transaction completion record corresponding to the payment result is generated and sent to the identity card for storage processing by the processing component built into the identity card.

[0058] In summary, the payment processing method for identity cards provided in this embodiment enables park users to conduct transactions using identity cards in conjunction with merchant devices. Based on the transaction amount entered by the merchant, near-field communication (NFC) is established between the merchant device and the identity card. The identity card is then verified using NFC. Upon successful verification, the payment voucher from the identity card is read and sent to the merchant system connected to the merchant device. Based on the transaction information and payment voucher, the payment interface is invoked to process the transaction through the associated account configured on the identity card. This method achieves transaction payment based on NFC communication between the identity card and the merchant device, while ensuring the security of the transaction payment process using the identity card in conjunction with the merchant device.

[0059] It should be noted that steps S202 to S206 provided in this embodiment can be executed by the merchant's device. It should also be noted that steps S202 to S206 executed by the merchant's device can cooperate with steps S902 to S906 executed by the server in the following embodiment. Therefore, when reading this embodiment, please refer to the corresponding content of steps S902 to S906 provided in the following method embodiment. When reading the following method embodiment, please refer to the corresponding content of steps S202 to S206 provided in this embodiment.

[0060] The following example uses the payment processing method for an identification card provided in this embodiment in a payment scenario within a park. Figure 6 The payment processing method for the identity card provided in this embodiment will be further explained below. Figure 6 The payment processing method for identity recognition cards applied to payment scenarios within the park includes the following steps.

[0061] Step S602: Obtain the transaction amount entered by the merchant in the park on the payment device.

[0062] In addition, the operation of obtaining the transaction amount entered by the merchants in the park on the payment device can be replaced by obtaining the transaction amount sent by the merchants' POS system.

[0063] Step S604: Establish near-field communication with the identification cards of users in the park.

[0064] Step S606: Send verification information to the identity card via near-field communication and receive the returned encrypted identity information.

[0065] Step S608: Perform verification processing based on the user identity information and verification information obtained by decrypting the encrypted identity information.

[0066] Step S610: After successful verification, read the payment voucher from the identity card.

[0067] Step S612: Send transaction information and payment vouchers to the merchant system running on the payment receiving device.

[0068] The transaction information can be generated by the payment device or by the POS system of the merchants in the park and submitted to the merchant system. The merchant system can be a merchant order system, a merchant application, or a third-party application. In addition, the merchant system can also be replaced by a device system or a payment application.

[0069] Step S614: Submit transaction information and payment vouchers to the payment server by calling the payment interface through the merchant system.

[0070] Subsequently, after receiving the transaction information and payment voucher sent by the merchant system through the interface call, the payment server processes the transaction payment based on the associated account configured on the identity card.

[0071] Step S616: Generate a transaction completion record based on the payment result returned by the payment server, and send it to the identity card through the payment receiving device.

[0072] Here, after the transaction completion record is sent to the identity card by the payment device, the identity card receives the transaction completion record and stores it through the built-in processing component.

[0073] It should be noted that any one or more steps in steps S602 to S616 can be combined with any one or more steps in steps S202 to S206 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features can be selected in steps S602 to S616 and combined with any one or more technical features provided in steps S202 to S206 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S602 to S616 can be replaced with any one or more technical features provided in steps S202 to S206 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0074] The following example uses the payment processing method for an identification card provided in this embodiment to illustrate the application of payment in an off-site payment scenario within a park. Figure 7 The payment processing method for the identity card provided in this embodiment will be further explained below. Figure 7 The payment processing method for identity recognition cards applied to payment scenarios outside the park includes the following steps.

[0075] Step S702: Obtain the transaction amount sent by the POS system of an authorized merchant outside the park.

[0076] Step S704: Switch the merchant's device from card emulation mode to card reader mode according to the communication switching instruction.

[0077] Step S706: Establish near-field communication with the identification cards of users in the park.

[0078] Step S708: Verify the identification card based on near-field communication in conjunction with the identification card.

[0079] Step S710: After successful verification, read the payment voucher from the identity card.

[0080] Step S712: Send the payment voucher to the authorized merchant's order system.

[0081] After the payment voucher is sent to the merchant's order system, the merchant's order system calls the payment server's payment interface to submit the transaction information and payment voucher to the payment server. Upon receiving the transaction information and payment voucher submitted through the interface call, the payment server processes the transaction payment based on the associated account configured on the identity card and returns the payment result to the merchant's order system. Subsequently, after receiving the payment result returned by the interface call, the merchant's order system sends the payment result to the merchant's terminal. The transaction information can be generated by the POS system based on the transaction amount and submitted to the merchant's order system.

[0082] Step S714: Based on the payment result sent by the merchant order system, switch the merchant device from card reader mode back to card emulation mode.

[0083] It should be noted that any one or more steps in steps S702 to S714 can be combined with any one or more steps in steps S202 to S206 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features in steps S702 to S714 can be selected and combined with any one or more technical features provided in steps S202 to S206 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S702 to S714 can be replaced with any one or more technical features provided in steps S202 to S206 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0084] The following example uses the payment processing method for an identification card provided in this embodiment in an institutional payment scenario, combined with... Figure 8 The payment processing method for the identity card provided in this embodiment will be further explained below. Figure 8 The payment processing method for identity recognition cards applied to payment scenarios in institutional settings includes the following steps.

[0085] Step S802: Obtain the transaction amount entered by the merchant.

[0086] Here, the transaction amount can be entered by the merchant on the near-field interaction device, or it can be received from the merchant's POS system.

[0087] Step S804: Establish near-field communication with the identification cards of the organization members.

[0088] Step S806: Verify the identification card based on near-field communication in conjunction with the identification card.

[0089] Step S808: After successful verification, read the payment voucher from the identity card.

[0090] Step S810: Send payment credentials to the merchant system connected to the near-field interaction device.

[0091] The transaction information can be generated by near-field interaction devices, or by the merchant's POS system and submitted to the merchant system; the merchant system can be a merchant order system, a merchant application, or a third-party application; in addition, the merchant system can also be replaced by a device system or a payment application.

[0092] Step S812: If the merchant system is running on a near-field interaction device, the transaction payment is processed by calling the payment interface through the merchant system based on the institutional account configured on the identity card.

[0093] Step S814: Receive the payment result sent by the merchant system.

[0094] Step S816: If the merchant system is running on the merchant terminal, receive the payment result returned by the merchant system, which is processed through the institutional account configured by the identity card.

[0095] After the merchant system calls the payment interface, the payment server responds to the call by processing the transaction payment based on the transaction information and payment voucher submitted by the interface call, and returns the payment result as the result of the interface call.

[0096] It should be noted that any one or more steps in steps S802 to S816 can be combined with any one or more steps in steps S202 to S206 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features in steps S802 to S816 can be selected and combined with any one or more technical features provided in steps S202 to S206 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S802 to S816 can be replaced with any one or more technical features provided in steps S202 to S206 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0097] Furthermore, it should be noted that the implementation processes of steps S602 to S616, S702 to S716, and S802 to S816 in the different implementation scenarios provided above can be combined, merged, or replaced in any form to form new implementation methods according to the actual execution or deployment needs. For example, one or more steps can be selected from any of the implementation processes of steps S602 to S616, S702 to S716, and S802 to S816 and introduced into other implementation processes, using the selected steps to replace or modify the steps in other implementation processes; or, when selecting one or more steps from any implementation process to introduce into other implementation processes, the selected steps can be adaptively modified according to the scenario of other implementation processes, and then the adaptively modified steps can be combined or replaced with other implementation processes, etc.

[0098] One or more embodiments of another payment processing method for identification cards provided in this specification are as follows: Reference Figure 9 The payment processing method for identity recognition cards provided in this embodiment can be applied to a server (payment server), and the method specifically includes steps S902 to S906.

[0099] Step S902: Receive transaction information submitted by the merchant's system through the payment interface, as well as payment credentials from the park user's identification card.

[0100] The park users mentioned in this embodiment refer to users with specific identities within a park, such as student users or teacher users in a school, or users with corresponding specific identities in various park locations such as hospitals, enterprises, public service institutions, and office parks.

[0101] An identity card is an identity credential carrier used to uniquely identify a user's specific identity within a park. Specifically, the identity card is equipped with a near-field communication (NFC) component to establish NFC communication with merchant devices and conduct transactions and payments based on this NFC communication. In addition, the identity card can be configured with a processing component (security component or security chip). This processing component works with merchant devices to perform security verification during the transaction payment process and can also be used to store transaction records. This transaction record storage enhances the traceability of the identity card's transactions, thereby improving transaction security. The identity card also stores user identity information and / or payment credentials. Specifically, the processing component can store user identity information and / or payment credentials in a secure storage area or trusted storage space, or store them using encryption or encrypted methods. Furthermore, to enhance the security of transactions and payments using identity cards in conjunction with merchant devices, data encryption can be employed for data interaction with merchant devices. In this case, the identity card can also store encryption and / or decryption keys. For example, the processing component may also store a private key for encrypting user identity information and / or payment credentials.

[0102] Merchants refer to payment merchants used by users within the park for transactions. Specifically, merchants can be merchants located within the park premises; alternatively, merchants can be authorized merchants located outside the park premises, or authorized merchants that meet specific conditions. For example, stationery stores near schools can become authorized merchants for student transactions after obtaining authorization. Correspondingly, merchant equipment refers to payment devices (POS devices) or payment terminals deployed by merchants for cashiering or payment collection. If the merchant equipment is equipped with near-field communication (NFC) components for near-field communication, it can also be called a near-field interaction device or near-field interaction terminal.

[0103] Optionally, the payment credential is read from the identity card after the merchant's device establishes near-field communication with the identity card and the identity card is verified.

[0104] The payment credential refers to a credential used to identify the payment identifier of an identity card, such as a payment credential code or payment token pre-generated and stored on the identity card. In addition, the payment credential can also be a dynamic payment credential generated during the current transaction payment process, specifically a dynamic payment credential code or a dynamic payment token. In this case, the operation of reading the payment credential of the identity card can be replaced by generating the payment credential of the identity card, or it can be replaced by generating the payment credential of the identity card and sending the payment credential to the identity card to store the payment credential corresponding to the current transaction payment on the identity card.

[0105] In practice, when park users use their ID cards to interact with merchant devices for transaction payments, they first enter the transaction amount on the merchant device. After entering the transaction amount, the park users bring their ID cards close to the merchant device to establish near-field communication between the merchant device and the ID cards.

[0106] In the actual execution process, the process of inputting the transaction amount on the merchant device and establishing near-field communication between the merchant device and the identity card may vary depending on the model, deployment method, and communication mode of the merchant device in the actual transaction payment scenario. There may also be different ways to input the transaction amount and establish near-field communication in various actual transaction scenarios. The following will provide a detailed explanation of the process of inputting the transaction amount and establishing near-field communication with the identity card in various actual transaction scenarios.

[0107] In real-world scenarios, when a merchant has deployed a POS system, the merchant's staff can enter the transaction amount into the POS system. After receiving the entered transaction amount, the POS system transmits the transaction amount to the merchant's device. Optionally, the transaction amount can be entered through the POS system and transmitted to the merchant's device by the POS system. The POS system can be installed on the merchant's POS device, or it can be installed on the merchant's device in a different way.

[0108] Specifically, the merchant equipment can be deployed in a fixed manner, and the connection between the merchant equipment and the merchant POS equipment can be wired or wireless. In addition, the merchant equipment can be a mobile device or a handheld device. In this case, if the merchant equipment is a mobile device, the connection between the merchant equipment and the merchant POS equipment can be wired or wireless; if the merchant equipment is a handheld device, the connection between the merchant equipment and the merchant POS equipment can be wireless.

[0109] Based on this, when the merchant device is connected to the POS system, during the process of establishing near-field communication (NFC) between the user's ID card and the merchant device, the merchant device establishes NFC with the ID card in reader mode. Specifically, if the merchant device's current NFC mode is reader mode, then NFC is established with the ID card in reader mode. If the merchant device's current NFC mode is card emulation mode, that is, the merchant device acts as a "simulated card" to communicate with the card reader, then the merchant device's NFC mode needs to be switched from card emulation mode to reader mode to establish NFC with the ID card. Specifically, the merchant device can switch from card emulation mode to reader mode according to a mode switching command (communication switching command). Optionally, NFC is established after the merchant device switches from card emulation mode to reader mode according to the mode switching command. In card emulation mode, the merchant device is used to cooperate with the user terminal for NFC transaction payment.

[0110] The mode switching command can be sent by the POS system; alternatively, it can be received through the payment page of the merchant's device; or, the mode switching command can be generated after the physical accessories of the merchant's device are operated, such as if the merchant's device is equipped with a physical button for switching near-field communication modes, which the merchant personnel can use to switch near-field communication modes.

[0111] It should be noted that when a merchant device has multiple near-field communication modes, during the transaction payment process in conjunction with an identity card, it needs to switch from card emulation mode to card reader mode according to the mode switching command. After the transaction payment is completed, the near-field communication mode of the merchant device can be switched back to card emulation mode to cooperate with the user terminal in card emulation mode for near-field transaction payment, thereby improving the flexibility of the merchant device to conduct transaction payments through different near-field communication modes.

[0112] Furthermore, in real-world scenarios, there may be situations where merchants haven't deployed a POS system, or where the POS system and the merchant system are the same system, or where the merchant system is installed on the merchant's device. In these cases, transaction amount input and near-field communication establishment can be implemented based on the merchant's actual deployment. Specifically, if the merchant hasn't deployed a POS system, merchant personnel can input the transaction amount on the merchant's device. Optionally, the transaction amount can be input through an input component configured on the merchant's device (hardware input component, such as a transaction amount input keyboard); alternatively, merchant personnel can input the transaction amount through a merchant application installed on the merchant's device, and the merchant application, upon receiving the input transaction amount, transmits it to the merchant's device; alternatively, the transaction amount can be input through the merchant application installed on the merchant's device and sent to the merchant's device. Here, the merchant application installed on the merchant's device can be replaced by the POS system or the merchant system; or, the merchant application and at least one of the POS system and the merchant system can be the same application. Furthermore, the merchant application can be a third-party application provided to the merchant by a third-party application provider, and the merchant system can also be a third-party system provided to the merchant by a third-party system provider.

[0113] Based on this, during the process of establishing near-field communication between the ID card and the merchant device, the merchant device also establishes near-field communication with the ID card in reader mode. If the merchant device is currently configured with only reader mode as the near-field communication mode, then near-field communication with the ID card is established in reader mode. Otherwise, if the merchant device is configured with two near-field communication modes, the current near-field communication mode of the merchant device is detected. If the current near-field communication mode of the merchant device is reader mode, then near-field communication with the ID card is established in reader mode. If the current near-field communication mode of the merchant device is card emulation mode, then the near-field communication mode of the merchant device needs to be switched from card emulation mode to reader mode. Specifically, the merchant device can switch from card emulation mode to reader mode according to the mode switching command. Optionally, near-field communication is established after the merchant device switches from card emulation mode to reader mode according to the mode switching command.

[0114] It should be noted that the model, deployment method, communication mode, and other related content of the merchant's equipment in the two actual scenarios provided above can be combined or replaced in any way to form a new implementation method according to the deployment or execution needs of the actual scenario. Furthermore, the process of inputting the transaction amount and establishing near-field communication with the identity card provided in the above actual scenarios can also be combined or replaced in any way to form a new implementation method according to the deployment or execution needs of the actual scenario.

[0115] In practical implementation, based on establishing near-field communication between the merchant device and the identification card, to improve the flexibility of transaction payments and compatibility for various scenarios, corresponding payment applications can be configured in the merchant device for different identification cards. Specifically, in one optional implementation provided in this embodiment, after establishing near-field communication with the identification card of the park user, the payment application for transaction payment on the merchant device is determined according to the identification information sent by the near-field communication component built into the identification card. Here, the payment application refers to the application running on the merchant device and performing subsequent transaction payment-related processing; specifically, subsequent card verification is performed based on near-field communication and the identification card. After successful verification, the payment voucher of the identification card is read and sent to the merchant system connected to the merchant device, which can be executed by the determined payment application. Optionally, the payment application includes the device system configured on the merchant device or the payment application installed on the device system; in addition, the payment application can also be a merchant application or a third-party application installed on the device system. The identification information sent by the near-field communication component can be the component identifier of the near-field communication component, or it can be the payment application identifier or field identifier used to identify the payment application; the component identifier, payment application identifier or field identifier can be stored by the processing component of the identity card.

[0116] In this embodiment, the identification card differs from a general physical card. On one hand, the identification card is used to uniquely identify the specific identity of a user in the park. On the other hand, the identification card also has a built-in near-field communication component and can further have a built-in processing component (security component). Based on this, the account corresponding to the identification card is also different from the physical card account of a general physical card. The identification card in this embodiment is configured with an associated account. The following describes the identification card and the associated account configured on the identification card in various practical application scenarios.

[0117] In a real-world scenario, some users within a campus may lack payment permissions. For example, in a school setting, student users may lack user terminals and be unable to directly apply for, configure, or manage identification cards. To address this and improve the convenience of identification card management, a user's associated user can assist with the application and configuration of identification cards. Specifically, in one optional implementation of this embodiment, the identification card is created after the user's associated user accesses the target service to apply for the card. The target service can be a payment application or a service subroutine within the payment application.

[0118] In this scenario, during the configuration of the associated account for the identity card, a sub-account can be created under the associated user's user account based on the associated user's card configuration request. This created sub-account will then be used as the associated account in the identity card configuration. Optionally, the associated account is obtained by creating a sub-account under the associated user's user account based on the associated user's card configuration request.

[0119] After obtaining an identification card, users within the park can use it to make transactions at merchants within the park. Furthermore, they can configure merchant authorization for the identification card to expand its payment scope. Specifically, the associated user can configure merchant authorization for the identification card in the target service to obtain authorized merchants. These authorized merchants can be specific merchants outside the park. Optionally, the payment merchants for the identification card include: merchants within the park and authorized merchants outside the park configured for the identification card. Authorized merchants are obtained by the associated user after configuring merchant authorization for the identification card in the target service.

[0120] In another practical scenario, there may be situations where users in a park use institutional accounts for transaction payments. For example, in park settings such as hospitals or office parks, when a user in the park makes a transaction payment as a member of an institution, the institution can act on their behalf to make the payment. In this case, the identification card can correspond to the user's status as a member of the institution. Accordingly, the identification card can be a member identification card representing the member's status within the institution or an institutional identification card. In this case, the identification card can be configured and obtained by the institution's management members, for example, by applying for an identification card through the target service and then creating it.

[0121] Based on this, during the configuration of associated accounts for identity cards, the organization's account can be configured as the associated account for the identity card configuration based on the card configuration requests of the organization's management members. Alternatively, a sub-account can be created under the organization's account for each organization member as the associated account for the identity card configuration. Furthermore, to prevent organization members from being unable to make payments after exceeding transaction limits using the organization's account or sub-account, the user accounts of organization members can be configured together with the organization's account or sub-account as associated accounts for the identity card configuration. Optionally, associated accounts include the organization's account belonging to the park user and / or the user's account within the park. Here, the payment priority of the organization's account or sub-account is higher than that of the user's account.

[0122] Furthermore, in real-world scenarios, merchants may provide membership cards to their members, who then purchase and use these cards for transactions. In this case, the park user can be considered the merchant's member. The membership card for the park user (member) is issued to the park user after the purchase. To ensure the security of funds paid for the membership card, these funds can be transferred to an escrow account, managed by a financial institution or an asset management institution with appropriate fund management / escrow authority. Furthermore, when configuring the associated account for the membership card, the escrow account can be configured as the associated account for the membership card. Optionally, the associated account includes an escrow account used to store the funds used by the park user to purchase the card.

[0123] Building upon the aforementioned establishment of near-field communication between the merchant device and the identification card, to ensure the security of transaction payments through the interaction between the identification card and the merchant device, identification card verification can be performed in conjunction with near-field communication. Upon successful verification, a payment credential from the identification card is obtained. In one optional implementation of this embodiment, identification card verification based on near-field communication includes: sending verification information to the identification card via near-field communication and receiving the returned encrypted identity information; the encrypted identity information is generated by a processing component built into the identification card; and verification processing is performed based on the user identity information obtained by decrypting the encrypted identity information and the verification information to obtain a verification result.

[0124] In practice, verification information can be sent to the identity card via near-field communication. The verification information can be a specific string or a generated random string. After the verification information is sent to the identity card, the processing component built into the identity card reads the stored user identity information and encryption private key, encrypts the user identity information and verification information using the encryption private key to obtain encrypted identity information, and returns the encrypted identity information to the merchant device. After receiving the encrypted identity information, the merchant device decrypts the encrypted identity information using the identity card's public key and compares the decrypted verification information with the previously sent verification information. If they match, the verification is successful; if they do not match, the verification is unsuccessful.

[0125] In this embodiment, to improve the traceability of transactions made using an identity card, thereby indirectly enhancing the security of identity card-based transactions, transaction payment information can be stored in the identity card. Specifically, transaction payment information initiated through the identity card can be stored in the identity card before the transaction is completed. In an optional implementation of this embodiment, after identity card verification is performed using near-field communication (NFC), a transaction record to be paid is created based on the transaction information and sent to the identity card via NFC. The processing component built into the identity card then stores and processes the transaction record to be paid. The transaction information includes the transaction amount, and may also include at least one of the following: transaction time, user identity information, merchant information, and transaction order information.

[0126] In practice, after obtaining the payment credential from the identity card, the payment credential is sent to the merchant system connected to the merchant device. The merchant system then uses the transaction information and payment credential to call the payment interface and process the transaction payment through the associated account configured on the identity card. Specifically, during the process of calling the payment interface and processing the transaction payment through the associated account configured on the identity card, the transaction information and payment credential serve as input parameters for the interface call. After the payment interface call is performed based on these input parameters, the transaction information and payment credential are submitted to the server (payment server). Here, after receiving the transaction information and payment credential submitted by the interface call, the server processes the transaction payment through the associated account configured on the identity card. Optionally, the payment interface may include the payment interface of the payment component configured in the device system, or the payment interface of the payment application.

[0127] Transaction information can be submitted to the merchant system by the merchant's POS system or merchant application, or the merchant system can be a POS system or merchant application, and the transaction information can be generated by the merchant system based on the transaction amount. Alternatively, the merchant system can also be a device system or payment application. In this case, the transaction information can be generated by the device system or payment application based on the transaction amount. Optionally, the device system or payment application may be in a system login state or an application login state after logging into the merchant account.

[0128] In practice, during the transaction payment process, which involves calling the payment interface based on transaction information and payment vouchers and processing the transaction payment through the associated account configured on the identity card, the transaction information and payment vouchers serve as input parameters for the interface call. After the payment interface call is made based on these input parameters, the transaction information and payment vouchers are submitted to the server (payment server). Upon receiving the transaction information and payment vouchers submitted by the interface call, the server processes the transaction payment through the associated account configured on the identity card based on the transaction information and payment vouchers.

[0129] Step S904: Verify the payment of the transaction information based on the identification card configuration of the identification card.

[0130] After receiving the transaction information and payment voucher submitted by the merchant's system via the payment interface, the system verifies the transaction information based on the identity card's configuration. Specifically, during the payment verification process based on the identity card's configuration, verification can be performed by checking whether the merchant is in the merchant list configured on the identity card, whether the payment voucher matches the payment voucher corresponding to the user in the park, and whether the transaction information meets the fee control configuration in the identity card's configuration. In one optional implementation of this embodiment, the payment verification based on the identity card's configuration includes: checking whether the merchant is in the merchant list configured on the identity card; if so, verifying whether the transaction information meets the fee control configuration in the identity card's configuration; if so, determining that the verification has passed; otherwise, determining that the verification has failed.

[0131] Step S906: After verification, the transaction information is processed for payment based on the associated account configured on the identity card.

[0132] Based on the successful verification of transaction information through the identification card configuration, the transaction payment is processed through the associated account configured with the identification card. Furthermore, after the transaction payment is completed, the payment result can be returned to the merchant system as the result of the interface call.

[0133] In the specific execution process, when processing transaction payment based on the associated account configured by the identity card, funds are first transferred out from the associated account according to the transaction amount contained in the transaction information. During the fund transfer process, funds can be transferred out based on the payment voucher, that is: funds are transferred out from the associated account according to the transaction amount contained in the transaction information based on the payment voucher; after the funds are transferred out, the transferred funds are transferred to the merchant's account.

[0134] In this embodiment, in order to further improve the traceability of transactions based on identity cards, thereby indirectly improving the security of identity card transactions, after the payment result is returned to the merchant system, the merchant system can return the payment result to the merchant device. The merchant device generates a transaction completion record corresponding to the payment result and sends it to the identity card for storage and processing by the processing component built into the identity card.

[0135] The following is an embodiment of a payment processing device for an identity card provided in this specification: In the above embodiments, a payment processing method for an identity card is provided, and correspondingly, a payment processing device for an identity card is also provided, which will be described below with reference to the accompanying drawings.

[0136] Reference Figure 10 This illustration shows a schematic diagram of an embodiment of a payment processing device for an identity card provided in this embodiment.

[0137] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0138] This embodiment provides a payment processing device for an identity card, which operates on a merchant device. The device includes: The near-field communication establishment module 1002 is configured to obtain the transaction amount input by the merchant and establish near-field communication with the identity card of the park user; The identification card verification module 1004 is configured to perform identification card verification in cooperation with the identification card based on the near-field communication, and read the payment voucher of the identification card after successful verification; The payment voucher sending module 1006 is configured to send the payment voucher to the merchant system accessed by the merchant device, so as to call the payment interface based on the transaction information and the payment voucher to perform transaction payment processing through the associated account configured on the identity card.

[0139] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0140] Another embodiment of the payment processing device for an identity card provided in this specification is as follows: In the above embodiments, another payment processing method for identity cards is provided, and correspondingly, another payment processing device for identity cards is also provided, which will be described below with reference to the accompanying drawings.

[0141] Reference Figure 11 This illustration shows a schematic diagram of an embodiment of a payment processing device for an identity card provided in this embodiment.

[0142] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0143] This embodiment provides a payment processing device for an identity card, which runs on a server. The device includes: The receiving module 1102 is configured to receive transaction information submitted by the merchant's system through the payment interface, as well as payment credentials from the identity card of the park user; the payment credentials are read from the identity card after the merchant's device establishes near-field communication with the identity card and the identity card is verified. The payment verification module 1104 is configured to perform payment verification on the transaction information based on the identification card configuration of the identification card; The transaction payment module 1106 is configured to process the transaction information for payment based on the associated account configured on the identity card after verification.

[0144] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0145] The following is an example of a payment processing device based on an identity card provided in this specification: Corresponding to the payment processing method for an identification card described above, based on the same technical concept, one or more embodiments of this specification also provide a payment processing device for an identification card, which is used to execute the payment processing method for an identification card provided above. Figure 12 This is a schematic diagram of the structure of a payment processing device for an identity card provided in one or more embodiments of this specification.

[0146] This embodiment provides a payment processing device for an identity recognition card, comprising: like Figure 12 As shown, device 1200 mainly consists of a communication interface 1202, a user interface 1204, a processor 1206, and a data storage 1208. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 1210. The communication interface 1202 enables device 1200 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, the communication interface 1202 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, the communication interface 1202 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide-area wireless interface (e.g., WiMAX or LTE). Of course, the communication interface 1202 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. The communication interface 1202 may also include multiple physical communication interfaces, such as Wi-Fi, Bluetooth, and wide-area wireless interfaces. The user interface 1204 includes receiving user input and providing output to the user. Therefore, user interface 1204 may include input components such as a keypad, keyboard, touch-sensitive or presence-sensitive panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with a touch-sensitive panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 1204 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 1204 may include software, circuitry, or other forms of logic capable of transmitting data to and receiving data from external user input / output devices. Additionally or alternatively, device 1200 may support remote access from other devices via communication interface 1202 or another physical interface (not shown). User interface 1204 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 1204 may also be configured as a display device for rendering or displaying text fragments.

[0147] Processor 1206 may include one or more general-purpose processors and / or dedicated processors. Data storage 1208 may include one or more volatile and / or non-volatile storage components and may be integrated wholly or partially with processor 1206. Data storage 1208 may include removable and non-removable components.

[0148] Processor 1206 is capable of executing program instructions 1218 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 1208 to perform the various functions described herein. Data storage 1208 may contain a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 1200, enable device 1200 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 1218 by processor 1206 may result in processor 1206 using data 1212. For example, program instructions 1218 may include an operating system 1222 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 1200 and one or more application programs 1220 (e.g., a browser, social application, or game application). Similarly, data 1212 may include operating system data 1216 and application data 1214. Operating system data 1216 is primarily accessible to operating system 1222, while application data 1214 is primarily accessible to one or more application programs 1220. Application data 1214 may reside in a file system visible or hidden from the user of device 1200. Application 1220 may communicate with operating system 1222 via one or more application programming interfaces (APIs). These APIs facilitate application 1220 reading and / or writing application data 1214, transmitting or receiving information via communication interface 1202, receiving or displaying information on user interface 1204, etc. In some terms, application 1220 may be simply referred to as an "app". Furthermore, application 1220 may be downloaded to device 1200 through one or more online app stores or app markets. However, applications may also be installed on device 1200 in other ways, such as through a web browser or a physical interface on device 1200 (e.g., a USB port).

[0149] In one specific embodiment, the payment processing device for the identity card includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the payment processing device for the identity card, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: Obtain the transaction amount entered by the merchant and establish near-field communication with the identification cards of users in the park; The near-field communication is used in conjunction with the identity card to verify the identity card. After successful verification, the payment voucher of the identity card is read. The payment credential is sent to the merchant system connected to the merchant device, so that the payment interface can be invoked based on the transaction information and the payment credential to process the transaction payment through the associated account configured on the identity card.

[0150] Another example of a payment processing device using an identification card provided in this specification is as follows: Corresponding to the other identity card payment processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another identity card payment processing device, which is used to execute the other identity card payment processing method provided above. Figure 13 This is a schematic diagram of the structure of another payment processing device for an identity card provided in one or more embodiments of this specification.

[0151] This embodiment provides a payment processing device for an identity recognition card, comprising: like Figure 13As shown, device 1300 mainly consists of a communication interface 1302, a user interface 1304, a processor 1306, and a data storage 1308. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 1310. The communication interface 1302 enables device 1300 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, the communication interface 1302 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, the communication interface 1302 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide-area wireless interface (e.g., WiMAX or LTE). Of course, the communication interface 1302 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. The communication interface 1302 may also include multiple physical communication interfaces, such as Wi-Fi, Bluetooth, and wide-area wireless interfaces. The user interface 1304 includes receiving user input and providing output to the user. Therefore, user interface 1304 may include input components such as a keypad, keyboard, touch-sensitive or presence-sensitive panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with a touch-sensitive panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 1304 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 1304 may include software, circuitry, or other forms of logic capable of transmitting data to and receiving data from external user input / output devices. Additionally or alternatively, device 1300 may support remote access from other devices via communication interface 1302 or another physical interface (not shown). User interface 1304 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 1304 may also be configured as a display device for rendering or displaying text fragments.

[0152] Processor 1306 may include one or more general-purpose processors and / or special-purpose processors. Data storage 1308 may include one or more volatile and / or non-volatile storage components and may be integrated wholly or partially with processor 1306. Data storage 1308 may include removable and non-removable components.

[0153] Processor 1306 is capable of executing program instructions 1318 (e.g., compiled or uncompiled program logic and / or machine code) stored in data store 1308 to perform the various functions described herein. Data store 1308 may contain a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 1300, enable device 1300 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 1318 by processor 1306 may result in processor 1306 using data 1312. For example, program instructions 1318 may include an operating system 1322 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 1300 and one or more application programs 1320 (e.g., a browser, social application, or game application). Similarly, data 1312 may include operating system data 1316 and application data 1314. Operating system data 1316 is primarily accessible to operating system 1322, while application data 1314 is primarily accessible to one or more application programs 1320. Application data 1314 may reside in a file system visible or hidden to the user of device 1300. Application 1320 may communicate with operating system 1322 via one or more application programming interfaces (APIs). These APIs facilitate application 1320 reading and / or writing application data 1314, transmitting or receiving information via communication interface 1302, receiving or displaying information on user interface 1304, etc. In some terms, application 1320 may be simply referred to as an "app". Furthermore, application 1320 may be downloaded to device 1300 through one or more online app stores or app markets. However, applications may also be installed on device 1300 in other ways, such as through a web browser or a physical interface on device 1300 (e.g., a USB port).

[0154] In one specific embodiment, the payment processing device for the identity card includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the payment processing device for the identity card, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: The system receives transaction information submitted by the merchant's system through a payment interface call, as well as payment credentials from the user's identification card. The payment credentials are read from the identification card after the merchant's device establishes near-field communication with the identification card and the identification card is verified. The transaction information is verified based on the identification card configuration of the identification card. After verification, the transaction information is processed for payment based on the associated account configured on the identity card.

[0155] This specification provides an embodiment of a computer-readable storage medium as follows: Corresponding to the payment processing method for an identity card described above, based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0156] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: Obtain the transaction amount entered by the merchant and establish near-field communication with the identification cards of users in the park; The near-field communication is used in conjunction with the identity card to verify the identity card. After successful verification, the payment voucher of the identity card is read. The payment credential is sent to the merchant system connected to the merchant device, so that the payment interface can be invoked based on the transaction information and the payment credential to process the transaction payment through the associated account configured on the identity card.

[0157] It should be noted that the embodiments of a computer-readable storage medium described in this specification and the embodiments of a payment processing method for an identity card described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0158] Another embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the other payment processing method for identification cards described above, based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0159] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: The system receives transaction information submitted by the merchant's system through a payment interface call, as well as payment credentials from the user's identification card. The payment credentials are read from the identification card after the merchant's device establishes near-field communication with the identification card and the identification card is verified. The transaction information is verified based on the identification card configuration of the identification card. After verification, the transaction information is processed for payment based on the associated account configured on the identity card.

[0160] It should be noted that the embodiments of another computer-readable storage medium described in this specification and the embodiments of another payment processing method for an identity card described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0161] This specification provides an example of a computer program product as follows: Corresponding to the payment processing method for an identity card described above, based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0162] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps: Obtain the transaction amount entered by the merchant and establish near-field communication with the identification cards of users in the park; The near-field communication is used in conjunction with the identity card to verify the identity card. After successful verification, the payment voucher of the identity card is read. The payment credential is sent to the merchant system connected to the merchant device, so that the payment interface can be invoked based on the transaction information and the payment credential to process the transaction payment through the associated account configured on the identity card.

[0163] It should be noted that the embodiments of a computer program product described in this specification and the embodiments of a payment processing method for an identity card described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0164] Another example of a computer program product provided in this specification is as follows: Corresponding to the other payment processing method for identification cards described above, based on the same technical concept, one or more embodiments of this specification also provide another computer program product.

[0165] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps: The system receives transaction information submitted by the merchant's system through a payment interface call, as well as payment credentials from the user's identification card. The payment credentials are read from the identification card after the merchant's device establishes near-field communication with the identification card and the identification card is verified. The transaction information is verified based on the identification card configuration of the identification card. After verification, the transaction information is processed for payment based on the associated account configured on the identity card.

[0166] It should be noted that the embodiments of another computer program product described in this specification and the embodiments of another payment processing method for an identity card described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0167] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments. For example, the device embodiment, equipment embodiment and computer-readable storage medium embodiment are all similar to the method embodiment, so the description is relatively simple. When reading the relevant content of the device embodiment, equipment embodiment and computer-readable storage medium embodiment, please refer to the description of the method embodiment.

[0168] While one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is merely one possible execution order among many steps, and does not represent the only execution order. Therefore, when the claims involve method steps, any changes or adjustments to the order of such steps, or the parallelism between steps, are also within the scope of protection of the claims. This specification uses specific terms to describe embodiments of this specification. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0169] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0170] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0171] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0172] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0173] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0174] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0175] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0176] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0177] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0178] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0179] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0180] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0181] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising at least one…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0182] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0183] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A payment processing method for an identity card, applied to merchant equipment, characterized in that, The method includes: Obtain the transaction amount entered by the merchant and establish near-field communication with the identity credential carrier of the park user with a specific identity. Based on the near-field communication and the identity credential carrier, the identification card is verified, and the payment voucher of the identity credential carrier is read after the verification is successful. The payment credential is sent to the merchant system connected to the merchant device, so that the payment interface can be invoked based on the transaction information and the payment credential to process the transaction payment through the associated account configured by the identity credential carrier.

2. The payment processing method for the identity card according to claim 1, after the steps of obtaining the transaction amount input by the merchant and establishing near-field communication with the identity credential carrier of the specific identity of the park user are executed, and before the steps of performing card verification based on the near-field communication and the identity credential carrier and reading the payment voucher of the identity credential carrier after successful verification are executed, the method further includes: The payment application for making a transaction on the merchant's device is determined based on the identification information sent by the near-field communication component built into the identity credential carrier; wherein, the payment application includes the device system configured on the merchant's device or a payment application installed on the device system.

3. The payment processing method for an identity card according to claim 1, characterized in that, The merchant system includes a POS system installed on the merchant's POS device; the transaction amount is input through the POS system and transmitted to the merchant's device by the POS system.

4. The payment processing method for the identity card according to claim 3, characterized in that, The near-field communication is established after the merchant device switches from card emulation mode to card reader mode according to the mode switching instruction; The mode switching instruction is sent by the POS system, received through the payment page of the merchant device, or generated after the physical accessories of the merchant device are operated.

5. The payment processing method for an identity card according to claim 1, characterized in that, The merchant system includes a merchant application installed on the merchant device; the transaction amount is input through the merchant application and sent to the merchant device. Furthermore, the near-field communication is established in the card reader mode of the merchant device.

6. The payment processing method for an identity card according to claim 1, characterized in that, After the card verification operation based on the near-field communication and the identity credential carrier is performed, and before the operation of reading the payment voucher from the identity credential carrier after successful verification is performed, the method further includes: Based on the transaction information, a transaction record to be paid is created and sent to the identity credential carrier via near-field communication for storage and processing by the processing component built into the identity credential carrier.

7. The payment processing method for an identity card according to claim 2, characterized in that, The merchant system includes the device system or the payment application; the device system or the payment application is in a system login state or an application login state after logging in with a merchant account; The payment interface includes either the payment interface of the payment component configured in the device system or the payment interface of the payment application.

8. The payment processing method for an identity card according to claim 1, characterized in that, The verification of the identification card based on the near-field communication and the identity credential carrier includes: The near-field communication is used to send verification information to the identity credential carrier and receive the returned encrypted identity information; the encrypted identity information is generated by the processing component built into the identity credential carrier. The user identity information and verification information obtained by decrypting the encrypted identity information are used to verify the verification result.

9. The payment processing method for an identity card according to claim 1, characterized in that, The identity credential carrier is created after the associated user of the park applies for an identification card to access the target service. The associated account is obtained by creating a sub-account under the associated user's user account according to the associated user's card configuration request.

10. The payment processing method for an identity card according to claim 9, characterized in that, The payment merchants of the identity credential carrier include: merchants within the park and authorized merchants outside the park configured for the identity credential carrier; The authorized merchant is obtained by the associated user after configuring the merchant authorization of the identity credential carrier in the target service.

11. The payment processing method for an identity card according to claim 1, characterized in that, The identity credential carrier corresponds to the membership status of the park user within their respective organization; The associated accounts include the institutional accounts of the organizations to which the park users belong and / or the user accounts of the park users.

12. The payment processing method for an identity card according to claim 1, characterized in that, The identity credential carrier includes the membership card of the park user at the merchant, and is issued to the park user after the park user makes a card purchase. The associated account includes an escrow account used to store the purchase funds of card users in the park.

13. The payment processing method for an identity card according to claim 1, characterized in that, After the step of sending the payment credential to the merchant system connected to the merchant device, and calling the payment interface of the payment server based on the transaction information and the payment credential to process the transaction payment through the associated account configured on the identity credential carrier, is executed, the method further includes: Receive payment results returned by the interface call or receive payment results sent by the merchant system; A transaction completion record corresponding to the payment result is generated and sent to the identity credential carrier for storage and processing by the processing component built into the identity credential carrier.

14. The payment processing method for an identity card according to claim 1, characterized in that, The transaction payment processing via the associated account configured through the identity credential carrier includes: The transaction information is verified for payment based on the identification card configuration of the identity credential carrier; After verification, the transaction payment is processed based on the associated account.

15. The payment processing method for an identity card according to claim 14, characterized in that, The configuration of the identification card based on the identity credential carrier to perform payment verification of the transaction information includes: Detect whether the merchant is in the payment merchant list configured in the identity credential carrier; If so, verify whether the transaction information meets the fee control configuration in the identification card configuration; if so, confirm that the verification is successful.

16. The payment processing method for an identity card according to claim 4, characterized in that, After the step of sending the payment credential to the merchant system connected to the merchant device, and calling the payment interface of the payment server based on the transaction information and the payment credential to process the transaction payment through the associated account configured on the identity credential carrier, is executed, the method further includes: Switch the merchant device's near-field communication mode back to the card emulation mode, so as to cooperate with the user terminal in the card emulation mode to conduct near-field transaction payments.

17. A payment processing method for an identity card, applied to a payment server, characterized in that, The method includes: The system receives transaction information submitted by the merchant's system through a payment interface call, as well as a payment credential from the identity credential carrier of the park user's specific identity. The payment credential is read from the identity credential carrier after the merchant's device establishes near-field communication with the identity credential carrier and passes the identification card verification. The transaction information is verified for payment based on the identification card configuration of the identity credential carrier; After verification, the transaction information is processed for payment based on the associated account configured on the identity credential carrier.

18. A payment processing device for an identity recognition card, operating on merchant equipment, characterized in that, The device includes: The near-field communication establishment module is configured to obtain the transaction amount input by the merchant and establish near-field communication with the identity credential carrier of the specific identity of the user in the park; The identification card verification module is configured to perform identification card verification based on the near-field communication and the identity credential carrier, and read the payment voucher from the identity credential carrier after successful verification. The payment voucher sending module is configured to send the payment voucher to the merchant system accessed by the merchant device, so as to call the payment interface based on the transaction information and the payment voucher to perform transaction payment processing through the associated account configured by the identity credential carrier.

19. A payment processing device for an identity recognition card, characterized in that, include: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Obtain the transaction amount entered by the merchant and establish near-field communication with the identity credential carrier of the park user with a specific identity. Based on the near-field communication and the identity credential carrier, the identification card is verified, and the payment voucher of the identity credential carrier is read after the verification is successful. The payment credential is sent to the merchant system connected to the merchant device, so that the payment interface can be invoked based on the transaction information and the payment credential to process the transaction payment through the associated account configured by the identity credential carrier.

20. A computer-readable storage medium for storing computer-executable instructions, characterized in that, When executed, the computer-executable instructions perform the steps of the method of claim 1 or claim 17.

Images