TWM630213U - Dynamic stored-value processing system - Google Patents

Abstract

A processing system for dynamic stored value includes a point ticket card, a front-end sales device and a server side. The point ticket card has first characteristic information; the front-end sales device has a front-end input unit and a front-end communication unit, the front-end input unit receives the first characteristic information and the point stored value request, and the front-end communication unit transmits the first characteristic information and the point stored value Requirements: The server side has a back-end communication unit, a back-end storage unit and a back-end processing unit, the back-end storage unit has a ticket card database, the ticket card database stores a plurality of ticket card information, and each ticket card information stores the first Feature information and stored point information, the back-end processing unit finds out the corresponding ticket card information according to the received first feature information, and the back-end processing unit adds the point stored value request to the stored value of the found ticket card information. Point information.

Description

Dynamic Stored Value Processing System

An online data processing system, especially a dynamic stored value processing system.

The current telecommunications prepaid card or game credit card purchase is widely used and can be purchased at the channel, direct sales store or supermarket. Since the current point cards only provide a fixed amount of points, consumers can only purchase point cards that exceed the budgeted amount. Although the remaining points can be stored in the background server, the remaining small points for many times will cause inconvenience to consumers in management.

In view of this, in some embodiments, the dynamic stored value processing system includes a point ticket card, a front-end sales device, and a server side. The point ticket card has first characteristic information; the front-end sales device has a front-end input unit and a front-end communication unit, the front-end input unit is electrically connected to the front-end communication unit, and the front-end input unit receives a point stored value request, and the point stored value request includes the first Characteristic information and stored value points, the front-end communication unit transmits point stored value requirements; the server side has a back-end communication unit, a back-end storage unit and a back-end processing unit, and the back-end processing unit is electrically connected to the back-end communication unit and the back-end processing unit. The back-end storage unit, the back-end storage unit has a ticket card database and a user database, the ticket card database stores a plurality of ticket card information, each ticket card information stores the first feature information and the stored point information, and the user database Stores a plurality of user information, the user information includes user account and ticket card related information, the back-end communication unit receives the point stored value request or the ticket card return request, and the ticket card return request includes the first feature information and the target account number; wherein, The back-end processing unit searches for the corresponding ticket card information according to the first characteristic information of the point stored value request, and the back-end processing unit adds the stored value points required by the point stored value request to the stored points of the found ticket card information. information; the back-end processing unit searches for the corresponding ticket information from the ticket database according to the first feature information required for the return of the ticket, and the back-end processing unit searches for the corresponding user from the user database according to the target account required for the return of the ticket information, the back-end processing unit returns the found ticket card information to the ticket card associated information of the target account. The dynamic stored-value processing system provides flexible stored-value channels, and users can further determine the stored-value points (or stored-value amount) of each stored-value ticket card according to different needs.

In some embodiments, the point ticket card further has second characteristic information, the front-end input unit receives the second characteristic information, and the front-end communication unit transmits the second characteristic information to the server.

In some embodiments, the ticket information further stores second feature information and additional information, the back-end processing unit searches for corresponding ticket information and additional information according to the second feature information, the back-end processing unit generates a response message according to the additional information, and then The terminal communication unit transmits the response message to the front-end sales equipment.

The dynamic stored value processing system can provide a flexible stored value method, and the user decides the stored value points (or stored value amount) for the selected ticket card according to different needs. And each time the stored-value processing of the ticket card is one-time, so the security of the stored-value transaction is also guaranteed at the same time.

Please refer to FIG. 1A and FIG. 1B , which are a schematic diagram of an application scenario and a schematic block diagram of an architecture of a processing system for dynamic stored value according to an embodiment, respectively. The dynamic stored value processing system 100 includes a point ticket card 110 , a front-end sales device 120 , a server end 130 and a user equipment end 140 . The point ticket 110 may be a physical ticket or a virtual ticket. The point ticket card 110 has first characteristic information 111 . The first feature information 111 can be printed on either side of the point ticket card 110 . The first feature information 111 is a one-dimensional barcode (barcode), a two-dimensional barcode (QR code) or a clear code. Taking the physical credit card 110 as an example, the first feature information 111 of the two-dimensional barcode can be set on the credit card 110 .

The front-end sales device 120 has a front-end input unit 121 and a front-end communication unit 122 . The front-end input unit 121 is connected to the front-end communication unit 122 . The front-end sales device 120 may be a physical point of sale (POS) or a self-service machine (Kiosk), or may be a virtual online shopping platform. The front-end input unit 121 acquires the point ticket card 110 and the point stored value request 211 . The front-end input unit 121 may be a barcode scanner, a keyboard, a camera, or the like. If it is a virtual point ticket card 110, the front-end input unit 121 can be implemented by means of character reading, Optical Character Recognition (OCR), or a decoding program.

In addition, the front-end input unit 121 can also receive the point stored value request 211 . Points stored value request 211 includes stored value points. Stored value points can be not only cash points, but also bonus points, telecom points or game points. In addition to the pre-set amount, the amount of stored value points can also be determined by consumers. The front-end communication unit 122 transmits the first characteristic information 111 to the server end 130 , or the front-end communication unit 122 receives the message from the server end 130 .

The server side 130 has a back-end communication unit 131 , a back-end storage unit 132 and a back-end processing unit 133 . The back-end processing unit 133 is electrically connected to the back-end communication unit 131 and the back-end storage unit 132 . The back-end storage unit 132 has a ticket database 134 and a user database 135 , and the ticket database 134 records a plurality of ticket information 136 . Each ticket information 136 stores the first feature information 111 and the stored point information 137 , please refer to the dotted frame in the ticket database 134 in FIG. 1B . The user database 135 stores user information 138 . The user information 138 at least includes the user account 151 , the ticket-card associated information 152 and the stored-value account information 153 . In general, the user account 151 and the user information 138 have a one-to-one relationship.

The ticket-card-related information 152 records the point-ticket cards currently owned by the user account 151 . The stored value account information 153 is used to record the stored points of the user account 151 . The stored value account information 153 may correspond to a number of different types of points, such as game points, telecommunication points or supermarket points. When the user acquires a new point ticket card, the user can add the point ticket card to the ticket card related information 152 to record the ownership of the point ticket card by the user. At the same time, the points of the counting ticket need to be returned to the account, so that the points of the counting ticket can be added to the stored-value accounting information 153 .

The back-end communication unit 131 receives the first feature information 111 from the front-end sales equipment 120 . The back-end processing unit 133 generates the identification result 241 according to the first characteristic information 111 , and the back-end communication unit 131 transmits the identification result 241 to the front-end sales device 120 . The identification result 241 is used to confirm whether the point card 110 is legitimate. In addition, the back-end processing unit 133 finds out the corresponding ticket information 136 according to the received first feature information 111 , and the back-end processing unit 133 adds the point storage request 211 to the stored points of the found ticket information 136 Number Information 137.

The user equipment end 140 has a user input unit 141 , a user communication unit 142 , a user storage unit 144 and a user processing unit 143 . The user processing unit 143 is electrically connected to the user input unit 141 and the user communication unit 142 . The user equipment 140 may be, but not limited to, a mobile phone, a personal computer, a notebook computer, or a tablet computer.

The user input unit 141 can be used for receiving the first feature information 111 of the point ticket card 110 and receiving a user selection request. The user selection request may be used to select the user account 151 in the user equipment side 140 . The user input unit 141 acquires the first feature information 111 by means of photographing or typing. The user communication unit 142 is connected to the front-end sales equipment 120 or the server 130 via the network, or communicates with the front-end sales equipment 120 through near-field communication (Near-field communication, NFC).

The user processing unit 143 generates a ticket card return request 221 according to the first feature information 111 and the user selection request. The user selection requirement includes at least an originating account 441 and a target account 431 . Generally speaking, the originating account 441 may be the user of the user equipment 140 and the corresponding user account. In addition to other user accounts 151, the target account 431 can also be the originating account 441 of the aforementioned user equipment 140. In other words, the target account 431 may be the originating account 441 itself, or other user accounts 151 .

The user communication unit 142 is network-connected to the server end 130 . The user communication unit 142 transmits the ticket card return request 221 to the server 130 . The user communication unit 142 transmits the ticket card return request 221 to the server 130 . The user storage unit 144 stores the address book program 145 , and the address book program 145 records a plurality of user accounts 151 . The user account 151 not only corresponds to the owner of the user equipment 140 , but also may be related persons such as relatives and friends of the user equipment 140 . The user account 151 may be an email, a phone number, or a username, or the like. The user processing unit 143 selects one of the user accounts 151 as the target account 431 according to the user selection requirement. And for the convenience of describing the operating device of the target account 431, it is hereinafter referred to as the target device end 432. The owner of the user equipment 140 is called the originating account 441 . In addition, the target device side 432 may also be the user equipment side 140 itself.

To further illustrate the overall operation of this embodiment, please also refer to FIG. 2A , which is a schematic diagram of an operation flow of a processing system for dynamic stored value according to an embodiment. The dynamic stored value processing system 100 performs the following steps: Step S210: the server side receives a point stored value request or a ticket card return request, the point stored value request includes the first feature information and the stored value points, and the ticket card return request includes the first feature information and the target account number; Step S220: the server side searches for the corresponding ticket information according to the first characteristic information required for the stored value of points; Step S230: If the ticket card information corresponding to the first feature information exists in the server, the server adds the stored value points required for point storage to the stored points information of the found ticket card information; Step S240: the server side searches for the corresponding ticket information according to the first characteristic information required for the return of the ticket card; Step S250: If the ticket information corresponding to the first feature information exists in the server, the server returns the found ticket information to the ticket associated information of the target account; and Step S260: If the ticket information corresponding to the first feature information does not exist in the server, the server sends a prompt message to the front-end sales device.

First, the consumer selects any point ticket card 110 and goes to the front-end sales device 120 to open the card. The card opening is to add stored value points to the point ticket card 110 . The front-end sales equipment 120 reads the first characteristic information 111 of the point ticket card 110 . The front-end sales device 120 receives the customer's stored value amount, and generates a corresponding point stored value request 211 according to the stored value amount. The front-end sales device 120 sends the point storage request 211 to the server 130 . The point stored value request 211 includes the first characteristic information 111 and the stored value point.

The server 130 generates the identification result 241 according to the first characteristic information 111 . The identification result 241 further includes legal results and illegal results. The legal result is that the ticket information 136 corresponding to the first feature information 111 exists in the server 130 . The illegal result is that the ticket information 136 corresponding to the first feature information 111 does not exist in the server 130 .

When the identification result 241 is invalid, the server 130 will send a prompt message to the front-end sales device 120 so that the operator of the front-end sales device 120 can confirm the point ticket card 110 . If the identification result 241 is valid, the server 130 obtains the corresponding ticket information 136 according to the first feature information 111 . The server 130 obtains the stored point information 137 from the ticket information 136 . The server 130 adds the stored points of the point storage request 211 to the stored points information 137 of the found ticket information 136 . After completing the storage of the stored point information 137 , the server 130 sends a confirmation message to the front-end sales device 120 .

In addition to the above-mentioned point stored value request, the server 130 may also receive a ticket card return request 221 . The ticket card return request 221 includes the first characteristic information 111 and the target account number 431 . When the server side 130 receives the ticket card return request 221 , the back-end processing unit 133 searches for the corresponding user information 138 and ticket card information 136 respectively according to the ticket card return request 221 . In other words, the backend processing unit 133 searches the user database 135 with the target account 431 . The back-end processing unit 133 searches the ticket database 134 with the first feature information 111 . If the back-end processing unit 133 does not find the target account 431 or the first feature information 111 , the back-end processing unit 133 drives the back-end communication unit 131 to send a prompt message to the user equipment 140 . The ticket return request 221 may be issued by the front-end sales equipment 120 or the user equipment side 140 .

When the back-end processing unit 133 finds the user information 138 and the ticket-card information 136 corresponding to the ticket-card return request 221 , the back-end processing unit 133 adds the stored point information 137 of the ticket-card information 136 to the storage of the user information 138 . Value accounting information 153. To put it simply, the user equipment 140 can select any user account 151 , and the server 130 can transfer the stored value card 110 to the selected user account 151 . And any user account 151 includes the originating account 441 of the user equipment 140 , and may also be any user account 151 in the address book program 145 . After the server 130 completes the transfer of the points, the server 130 sends a notification message 231 to the user equipment 140 and the target equipment 432 respectively.

In some embodiments, the point ticket card 110 further has the second characteristic information 112 , please refer to FIG. 2B and FIG. 3 . FIG. 3 is a schematic diagram showing the relationship between the appearance of the point ticket card and the server side according to an embodiment. The second feature information 112 may be a one-dimensional barcode, a two-dimensional barcode, a plaintext code, or the like. The front-end input unit 121 receives the second characteristic information 112 , and the front-end communication unit 122 transmits the second characteristic information 112 to the server end 130 . In this embodiment, the ticket information 136 of the server side 130 is further provided with two sets of fields, which respectively record the second characteristic information 112 and the additional information 311 , as shown in FIG. 3 . The additional information 311 is used to record points, commodities or gifts corresponding to the second feature information 112 .

The front-end input unit 121 reads the second characteristic information 112 of the point ticket card 110 , and the front-end communication unit 122 sends a redemption request (without a label) to the server 130 according to the second characteristic information 112 . The back-end processing unit 133 searches whether there is corresponding ticket information 136 according to the second characteristic information 112 of the exchange request. If the server 130 has the ticket information 136 corresponding to the exchange request, the back-end processing unit 133 generates a response message (without a label) from the additional information 311 in the ticket information 136 , and sends the response message to the front-end sales device 120 .

In one embodiment, after the back-end processing unit 133 completes the search process of the user information 138 and the ticket information 136 , the back-end processing unit 133 returns the point ticket card 110 to the target account 431 . The home-return process is to transfer the authority of the ownership of the point card 110 from the originating account 441 to the target account 431 . As mentioned above, the ownership of the point card 110 can be sent to the target account 431 by way of forwarding. Although the target account 431 accepts the point card 110 , the stored point information 137 is not added to the stored value accounting information 153 of the target account 431 . After the server 130 completes the home registration, the server 130 sends a notification message 231 to the user equipment 140 and the target equipment 432 respectively.

If the target device 432 receives the notification message 231 , the user of the target device 432 can not only consume points through the target device 432 , but also synchronize the Smart Card with the server 130 . The smart card may be, but not limited to, an iCash card, an EasyCard or a credit card.

Generally, the smart card stores stored value accounting information 153 of user information 138 . The user equipment 140 can bind the smart card through Near Field Communication (NFC), flash chip or ZigBee, etc., so that the user account 151 of the user equipment 140 is linked. Alternatively, the consumer interacts with the smart card through the front-end sales device 120, so that the front-end sales device 120 sends the new stored value accounting information 153 to the smart card.

Therefore, the target device 432 receives the notification message 231 of the bonus point, and the consumer can handshake the smart card with the front-end sales device 120 to synchronize the smart card with the stored point information 137 of the server 130 . For example, the iCash smart card can communicate via NFC in addition to its associated card number. Therefore, when the recipient consumer receives the notification message 231 of the stored-value account information 153, the recipient consumer can take the iCash smart card to the physical store, and hold the iCash smart card with the front-end sales device 120 to complete the points purpose of home.

In some embodiments, the front-end sales device 120 may generate a bonus information according to the stored value points. The front-end sales device 120 adds the bonus information to the point stored value request 211 , so that the summed result is a new point stored value request 211 . The front-end sales device 120 sends the new point stored value request 211 to the server 130 . The server 130 adjusts the stored point information 137 of the ticket information 136 according to the new point stored value request 211 . Please refer to FIG. 4 , which is an operation of adjusting bonus information and stored value points in an embodiment. Schematic.

For example, the point stored value requirement A1 has the stored value point B1. The front-end sales equipment 120 generates bonus information C1 according to the stored value points B1. The front-end sales device 120 adds the stored value point B1 and the bonus information C1 to obtain a new stored value point B2 (ie, B2=B1+C1), and encapsulates it as a new stored value request A2. The front-end sales device 120 sends the point storage request A2 to the server 130 . The server 130 adds the stored value point B2 of the point stored value request A2 to the corresponding ticket card information 136 .

In some embodiments, the server 130 generates reward points according to the ticket card return request 221, please refer to FIG. 5A. The server 130 adds the reward points to the stored value account information 153 of the target account 431 . For example, when the value is stored during the event, the server 130 may provide the reward point D1 according to the stored value point B3. Suppose that the initiating account 441 sends a point stored value request 211 and a ticket return request 221 to the server 130, wherein the stored value point is B3, and the object of the ticket return request 221 is the target account 431. When the server side 130 receives the point stored value request 211 , the server side 130 adds up the stored value point B3 and the reward point D1 , and adds the total result to the stored point information of the corresponding ticket information 136 137(B4=B3+D1).

Next, the server 130 obtains the stored-value account information B4 of the target account 431 according to the ticket card return request 221 . The server 130 adds the stored point information 137 of the point ticket card 110 into the stored value accounting information B4 of the target account 431 . Finally, the server end 130 sends a notification message 231 to the target device end 432 . Please refer to FIG. 5A , which is a schematic diagram of processing feedback points at the target device side according to an embodiment.

In some embodiments, the server-side 130 generates reward points according to the card return request 221 . The server 130 adds the reward points to the stored value account information B4 of the originating account 441 . Following the previous example, when storing value during the event, the server 130 may provide the reward point D1 according to the stored value point B3. Suppose that the initiating account 441 sends a point stored value request A3 and a ticket return request 221 to the server 130, the stored value point is B3, and the object of the ticket return request 221 is the originating account 441.

Next, the server 130 obtains the stored-value account information B4 of the originating account 441 according to the ticket card return request 221 . The server 130 adds the stored point information 137 of the point ticket card 110 into the stored value account information B4 of the originating account 441 . Finally, the server 130 sends a notification message 231 to the user equipment 140 that initiated the account 441 . Please refer to FIG. 5B , which is a schematic diagram of processing feedback points at the user equipment side according to an embodiment.

In addition, when the initiating account 441 generates the ticket card return request 221 , the aforementioned iCash smart card card number can also be added to the ticket card return request 221 . The server 130 handshakes the stored point information 137 of the gifted consumer according to the iCash smart card number, thereby saving the corresponding processing time of the gifted consumer to the physical store.

In addition to being a physical ticket card, the point ticket card 110 can also be a virtual ticket card. Further, in the physical store, a virtual shopping platform (ie, corresponding to the front-end sales equipment 120 ) can be set in the automatic service machine. And a virtual point ticket card 110 is provided on the shopping platform. Correspondingly, the virtual point ticket card 110 also has the first characteristic information 111 . When the consumer purchases the credit card 110 through the automatic service machine, the front-end sales device 120 also reads the first characteristic information 111 of the credit card 110 .

Next, the consumer decides the point stored value request 211 , and the front-end sales device 120 sends the point stored value request 211 to the server 130 . The server 130 adds the stored value points to the stored point information 137 of the point ticket card 110 according to the point storage value request 211 . The consumer selects the address book program 145 to which the individual belongs through the front-end sales device 120 , and selects the target account 431 from the address book program 145 . The server 130 stores the value of the point ticket card 110 into the stored value account information of the target account 431 .

The dynamic stored value processing system 100 provides flexible point stored value processing. The point card 110 can determine the denomination of the stored value according to the needs of the consumer. For individual users who do not have a credit card or do not want to use online cash flow payment, it is inconvenient to purchase a point ticket card 110 and give gifts online. Through the processing system 100 for dynamic stored value, after purchasing the point ticket card 110 in a physical store by cash or other methods, it can be transferred to a personal account to give a virtual gift card as a gift. Or transfer it for self-consumption. For enterprise users, the manufacturer can provide point ticket cards 110 with different denominations according to activity requirements. Further, additional activities (such as lottery, company introduction, product introduction, shopping bonus, etc.) can be embedded in the second feature information 112 of the point ticket card 110 to provide more feedback and attract users to buy point tickets Card 110. In addition, different reward amounts or bonuses can be added in accordance with the consumption activities when redeeming the point ticket card 110 .

100: Handling Systems 110: Point Ticket Card 111: First feature information 112: Second feature information 120: Front-end sales equipment 121: Front input unit 122: Front-end communication unit 130: server side 131: Back-end communication unit 132: rear storage unit 133: Back-end processing unit 134: Ticket database 135:User database 136: Ticket Information 137: Stored Points Information 138: User Information 140: User equipment side 141: User input unit 142: User communication unit 143: User processing unit 144: User storage unit 145: Address Book Program 151: User account 152: Ticket card related information 153. B4: Stored value accounting information 211, A1, A2, A3: Points stored value requirements 221: Requirement for return of ticket card 231: Notification message 241: Recognition result 311: Additional Information 431: target account 432: target device side 441: Create account B1, B2, B3: Stored value points C1: Bonus Information D1: Reward Points S210, S220, S230, S240, S250, S260: Steps

[ Fig. 1A ] This is a schematic diagram of an application scenario of the processing system for dynamic stored value of this embodiment. [FIG. 1B] This is a schematic block diagram of the structure of a processing system for dynamic stored value of this embodiment. [ FIG. 2A ] A schematic diagram of an operation flow of a processing system for dynamic stored value according to an embodiment. [ FIG. 2B ] A sequence diagram of a processing system for dynamic stored value according to an embodiment. FIG. 3 is a schematic diagram of the relationship between the appearance of the point ticket card and the server side according to an embodiment. FIG. 4 is a schematic diagram of the operation of adjusting bonus information and stored value points according to an embodiment. FIG. 5A is a schematic diagram of processing feedback points on the target device side according to an embodiment. [ FIG. 5B ] A schematic diagram of reward point processing at the user equipment side according to an embodiment.

100: Handling Systems

110: Point Ticket Card

111: First feature information

120: Front-end sales equipment

130: server side

211: Points Stored Value Requirements

Claims (12)

A processing system for dynamic stored value, comprising: a one-point ticket card, having a first characteristic information; A front-end sales device has a front-end input unit and a front-end communication unit, the front-end input unit is electrically connected to the front-end communication unit, the front-end input unit receives a point stored value request, and the point stored value request includes the first feature information and a stored value point, the front-end communication unit transmits the point stored value request; and A server end has a back-end communication unit, a back-end storage unit and a back-end processing unit, the back-end processing unit is electrically connected to the back-end communication unit and the back-end storage unit, the back-end storage unit There is a ticket card database and a user database, the ticket card database stores a plurality of ticket card information, each of the ticket card information stores the first feature information and a stored point information, the user database stores a plurality of ticket card information User information, the user information includes a user account and a ticket card associated information, the back-end communication unit receives the point stored value request or a ticket card return request, the ticket card return request includes the first feature information with a target account; Wherein, the back-end processing unit searches the corresponding ticket card information according to the first characteristic information of the point-stored value request, and the back-end processing unit adds the stored-value points requested by the point-stored value to the searched-out The stored point information of the ticket card information; the back-end processing unit searches the ticket card database for the corresponding ticket card information according to the first feature information requested by the ticket card return home, and the back-end processing unit searches for the corresponding ticket card information According to the target account required for the return of the ticket, the corresponding user information is searched from the user database, and the back-end processing unit returns the found ticket information to the ticket associated information of the target account. The processing system for dynamic stored value according to claim 1, wherein the point ticket card is a physical ticket card or a virtual ticket card. The processing system for dynamic stored value according to claim 1, wherein the first characteristic information is a one-dimensional barcode, a two-dimensional barcode or a plaintext code. The processing system for dynamic stored value according to claim 1, wherein the point ticket card further has a second characteristic information, the front-end input unit receives the second characteristic information, and the front-end communication unit transmits the second characteristic information to the server side. The processing system for dynamic stored value according to claim 4, wherein the ticket information further stores the second characteristic information and an additional information, and the back-end processing unit searches for the corresponding ticket information and additional information according to the second characteristic information. For the additional information, the back-end processing unit generates a response message according to the additional information, and the back-end communication unit transmits the response message to the front-end sales equipment. The processing system for dynamic stored value according to claim 1, wherein the front-end sales device adds a bonus information to the point stored value request, and the front-end sales device transmits the aggregated point stored value request to the server side. The processing system for dynamic stored value according to claim 1, wherein the user information has a stored value account information, and the server side finds out the corresponding user information and the ticket card information according to the point stored value request. , the server side adds the found stored point information to the stored value account information of the user information. The processing system for dynamic stored value according to claim 7, wherein the server generates a reward point according to the point stored value request, and the server adds the reward point to the stored value account of the target account service information. The processing system for dynamic stored value according to claim 7, wherein the server generates a reward point according to the point stored value request, and the server adds the reward point to the stored value account of an originating account service information. The processing system for dynamic stored value according to claim 7, wherein the server sends a notification message to a target device according to the ticket card return request, the target device selects a smart card according to the notification message, and the The front-end sales equipment sends the stored value accounting information to the smart card. The processing system for dynamic stored value according to claim 1, further comprising a user equipment end having a user input unit, a user communication unit, a user storage unit and a user processing unit, the user processing unit being electrically connected In the user input unit, the user storage unit and the user communication unit, the user storage unit stores an address book program, the address book program records at least one user account, the user input unit receives the first feature information, the user The processing unit selects one of the user accounts as the target account, the user processing unit generates the ticket card return request according to the target account and the first feature information, and the user communication unit transmits the ticket card return request to the server side. The processing system for dynamic stored value according to claim 1, wherein the front-end sales device receives the target account number and the first characteristic information to generate the ticket card return request, and the front-end sales device transmits the ticket card return request to the server side.

Images