WO2023010835A1 - 非卡账户支付方法、设备、系统及存储介质 - Google Patents
非卡账户支付方法、设备、系统及存储介质 Download PDFInfo
- Publication number
- WO2023010835A1 WO2023010835A1 PCT/CN2022/078751 CN2022078751W WO2023010835A1 WO 2023010835 A1 WO2023010835 A1 WO 2023010835A1 CN 2022078751 W CN2022078751 W CN 2022078751W WO 2023010835 A1 WO2023010835 A1 WO 2023010835A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- card account
- card
- payment
- management device
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/342—Cards defining paid or billed services or quantities
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Definitions
- the application belongs to the field of data processing, and in particular relates to a non-card account payment method, device, system and storage medium.
- Card-based payment uses bank cards, prepaid cards and other cards as the main payment tool carrier to realize various payment services.
- the payment acceptor device transmits the collected card information to the card exchange device, and the card exchange device routes the payment information to the corresponding card issuer device based on the card information such as the card number.
- Embodiments of the present application provide a non-card account payment method, device, system, and storage medium, which can reduce development and maintenance costs required for non-card account payment.
- the embodiment of the present application provides a non-card account payment method, which is applied to a card exchange device, and the card exchange device belongs to the card-based payment system.
- the method includes: receiving the first Payment request, the first payment request includes the non-card account number identifier and transaction information, the non-card account number identifier is used to identify the registered account number of the non-card account; use the non-card account number identifier in the first payment request to interact with the non-card account management device, so that The non-card account management device determines the target non-card account corresponding to the non-card account number identifier in the first payment request, so that the card exchange device or the non-card account management device interacts with the target non-card account fund management device corresponding to the target non-card account , to execute the payment, the non-card account management device stores the corresponding relationship between the non-card account ID and the non-card account, and the corresponding relationship between the non-card account and the non-card account fund management device.
- the embodiment of the present application provides a non-card account payment method, which is applied to a non-card account management device.
- the method includes: interacting with the card exchange device using the non-card account number identifier in the first payment request received by the card exchange device, and the first payment request is sent by the payment accepting party device through the first target interface Send to the card exchange device, including the non-card account number identification and transaction information, the card exchange equipment belongs to the card-based payment system; according to the non-card account number identification in the first payment request, determine the non-card account number corresponding to the first payment request The target non-card account; interacting with the target non-card account fund management device corresponding to the target non-card account to perform payment; or interacting with the card exchange device so that the card exchange device interacts with the target non-card account fund management device to perform payment.
- the embodiment of the present application provides a card exchange device, the card exchange device belongs to the card-based payment system, the card exchange device includes an interaction module, and the interaction module includes a receiving unit; the receiving unit is used to receive payment acceptance through the first target interface
- the first payment request sent by the party device, the first payment request includes the non-card account number identification and transaction information, the non-card account number identification is used to identify the registered account number of the non-card account; the interaction module is used to use the non-card account number in the first payment request
- the account identifier interacts with the non-card account management device, so that the non-card account management device determines the target non-card account corresponding to the non-card account identifier in the first payment request, so that the card exchange device or the non-card account management device and the target non-card account
- the target non-card account fund management device corresponding to the account interacts and executes the payment.
- the non-card account management device stores the corresponding relationship between the non-card account ID and the non-card account, and the
- the embodiment of the present application provides a non-card account management device.
- the non-card account management device stores the corresponding relationship between the non-card account ID and the non-card account, and the corresponding relationship between the non-card account and the non-card account fund management device.
- the non-card account management device includes an interaction module and a processing module; the interaction module is used to interact with the card exchange device using the non-card account number identifier in the first payment request received by the card exchange device, and the first payment request is sent by the payment acceptor device Send it to the card exchange device through the first target interface, including the non-card account number identification and transaction information.
- the card exchange device belongs to the card-based payment system; the processing module is used to determine the connection with the first payment request according to the non-card account number identification in the first payment request.
- the non-card account number in the payment request identifies the corresponding target non-card account;
- the interaction module is also used to interact with the target non-card account fund management device corresponding to the target non-card account to perform payment; or interact with the card exchange device to make the card
- the switching device interacts with the target non-card account fund management device to execute the payment.
- the embodiment of the present application provides a card exchange device, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the non-card account payment method of the first aspect is implemented.
- the embodiment of the present application provides a non-card account management device, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the non-card account payment method of the second aspect is implemented.
- the embodiment of the present application provides a non-card account payment system, including the card exchange device of the fifth aspect and the non-card account management device of the sixth aspect.
- the embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the non-card account payment method of the first aspect is implemented.
- the embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the non-card account payment method of the second aspect is implemented.
- Embodiments of the present application provide a non-card account payment method, device, system, and storage medium.
- the card exchange device acquires the non-card account ID and transaction information from the payment accepting party device through a first payment request.
- the card exchange device can use the non-card account number identifier to interact with the non-card account management device used to manage the non-card account, so as to determine the non-card account fund management device corresponding to the non-card account used for payment.
- Card exchange equipment or non-card account management equipment can interact with non-card account fund management equipment through communication to realize non-card account payment.
- the card exchange equipment belongs to the card-based payment system, and the non-card account payment does not need to be separately developed and maintained.
- a new non-card account payment can be made through the card exchange equipment in the existing card-based payment system and the newly added non-card account management equipment , connect non-card accounts to the card-based payment system, realize non-card account payment, and reduce the development cost and maintenance cost required for non-card account payment.
- Fig. 1 is a schematic structural diagram of an example of a card-based payment system
- FIG. 2 is a schematic diagram of an example of an application scenario of the non-card account payment method provided by the embodiment of the present application;
- Fig. 3 is a flow chart of an embodiment of the non-card account payment method provided in the first aspect of the present application
- Fig. 4 is a flow chart of another embodiment of the non-card account payment method provided in the first aspect of the present application.
- Fig. 5 is a flow chart of another embodiment of the non-card account payment method provided in the first aspect of the present application.
- Fig. 6 is a flowchart of another embodiment of the non-card account payment method provided in the first aspect of the present application.
- Fig. 7 is a flowchart of an embodiment of the non-card account payment method provided by the second aspect of the present application.
- Fig. 8 is a flow chart of another embodiment of the non-card account payment method provided by the second aspect of the present application.
- FIG. 9 is a flow chart of an example of a non-card account payment process in the embodiment of the present application.
- FIG. 10 is a flow chart of another example of the non-card account payment process in the embodiment of the present application.
- FIG. 11 is a schematic structural diagram of an embodiment of the card switching device provided by the third aspect of the present application.
- FIG. 12 is a schematic structural diagram of another embodiment of the card switching device provided by the third aspect of the present application.
- Fig. 13 is a schematic structural diagram of an embodiment of a non-card account management device provided in the fourth aspect of the present application.
- Fig. 14 is a schematic structural diagram of another embodiment of the non-card account management device provided in the fourth aspect of the present application.
- Fig. 15 is a schematic structural diagram of another embodiment of the non-card account management device provided in the fourth aspect of the present application.
- Fig. 16 is a schematic structural diagram of yet another embodiment of the non-card account management device provided in the fourth aspect of the present application.
- Fig. 17 is a schematic structural diagram of an embodiment of the card switching device provided by the fifth aspect of the present application.
- Fig. 18 is a schematic structural diagram of an embodiment of a non-card account management device provided in the sixth aspect of the present application.
- Card-based payment is a payment method that uses bank cards, prepaid cards and other cards as the main payment tool carrier to realize various payment services. Card-based payment is realized based on the card-based payment system.
- Fig. 1 is a schematic structural diagram of an example of a card-based payment system.
- the card-based payment system may include a payment acceptor device 11 , a card exchange device 12 and a card account funds management device 13 .
- the payment acceptor device 11 can interact with the card exchange device 12, and the card exchange device 12 can interact with the card account fund management device 13, and the card exchange device 12 forwards the payment request of the payment acceptor device 11 according to the routing mechanism To the corresponding card account fund management device 13 to realize card-based payment.
- the card-based payment system Since the routing mechanism of the card exchange equipment in the card-based payment system is based on the card number and the bank identification number (Bank Identification Number, BIN) of the card, the card-based payment system cannot adapt to the registered account number of the non-card account. Account payments cannot be made directly in the card-based payment system. However, developing and maintaining a new non-card account payment system alone requires a lot of resources and costs.
- This application provides a non-card account payment method, device, system and storage medium, without the need to separately develop and maintain a new non-card account payment system, and can use the card exchange equipment in the card-based payment system for non-card account payment payment, thereby reducing the development cost and maintenance cost of non-card account payment.
- the non-card account payment method in the embodiment of the present application may involve a payment acceptor device, a card exchange device, a non-card account management device, and a non-card account fund management device.
- FIG. 2 is a schematic diagram of an example of an application scenario of the non-card account payment method provided by the embodiment of the present application.
- the non-card account payment system may include a payment acceptor device 21 , a card exchange device 22 , a non-card account management device 23 and a non-card account fund management device 24 .
- the payment acceptor device 21 can communicate with the card exchange device 22 .
- the payment accepting party device 21 may include mobile terminals such as mobile phones, point of sales (POS) equipment, and other devices with payment acceptance functions.
- POS point of sales
- the card exchange device 22 can communicate with the non-card account management device 23 .
- the card exchange device 22 may specifically include equipment such as a server, and the number of card exchange devices 22 in the non-card account payment system is not limited here.
- the card exchange device 22 belongs to the card-based payment system, that is, the card exchange device 22 in the non-card account payment system in the embodiment of the present application can reuse the card exchange device in the card-based payment system.
- the non-card account management device 23 can communicate with the non-card account fund management device 24 .
- One non-card account management device 23 can communicate with one or more than two non-card account fund management devices 24 .
- the non-card account management device 23 may specifically include a server and other devices, and the number of non-card account management devices 23 in the non-card account payment system is not limited here.
- card exchange device 22 may be in communicative interaction with non-card account funds management device 24 .
- One card exchange device 22 can communicate with one or more than two non-card account fund management devices 24 .
- the non-card account fund management device 24 can be a non-card account fund management device, specifically including servers and other devices, and the number of non-card account fund management devices 24 in the non-card account payment system is not limited here.
- the first aspect of the present application provides a non-card account payment method, which can be applied to a card exchange device.
- Fig. 3 is a flowchart of an embodiment of the non-card account payment method provided in the first aspect of the present application. As shown in FIG. 3 , the non-card account payment method may include steps S301 and S302.
- step S301 a first payment request sent by a payment acceptor device is received through a first target interface.
- the first payment request is used for the payment acceptor device to initiate non-card account payment to the card exchange device.
- the first payment request may include a non-card account number identification and transaction information.
- the non-card account identifier is used to identify the registered account number of the non-card account.
- Non-card accounts are accounts other than bank cards, prepaid cards and other cards.
- the non-card account identifier may include a registered account number of the non-card account or a token Token of the registered account.
- a registered account may include a mobile phone number, an email address, a non-card user identity (non-card user identity ID), a payment application identity (payment program ID), etc., which are not limited here.
- the non-card account identifier includes the token of the registered account, the registered account and the token can be converted to each other, and the conversion algorithm between the registered account and the token is not limited here.
- the transaction information may include one or more of payment amount, payment time, merchant ID, and transaction initiator ID, which is not limited here.
- the payment acceptor device can obtain the information in the first payment request through various carriers.
- the payment accepting party device may obtain information such as non-card account ID and transaction information by scanning a code, receiving user input, etc., which is not limited herein.
- the first payment request may be transmitted in the form of a message.
- the first payment request may also include one or more items of message type, message check code and other information, which is not limited here.
- the message verification code in the first payment request can be used to verify the integrity and legitimacy of the first payment request.
- the first payment request is transmitted in the form of a message
- the message may include a message header, a bitmap, and a message body.
- the message body can include message type, bank card number, transaction amount, transaction time, merchant code, transaction initiator, message verification code and other information.
- the following example shows some data fragments in the first payment request:
- Message Head is the message header;
- Message Content is the message body;
- the message body can include 0 to 128 fields, which can be related to the message type, bank card number, transaction amount, transaction time, merchant code, transaction initiator, report Correspondence to information such as text check codes.
- the above-mentioned second field Field 2 may be a non-card account identifier; when card-based payment is performed, the above-mentioned second field Field 2 may be a card number identifier.
- the first payment request in the non-card account payment in the embodiment of this application carries the non-card account identifier, and the payment request in the card-based payment carries the card number identifier.
- the format of the first payment request in the non-card account payment can be the same as the format of the payment request in the card-based payment, so that the non-card account can be connected to the card-based payment system.
- the first target interface is an interface used for interaction between the card exchange device and the payment acceptor device.
- the first target interface may include the first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system, that is, the first target interface may reuse the original interface in the card-based payment system , there is no need to redevelop or define the interface, thereby avoiding a major transformation of the card exchange equipment, and further reducing the development cost and maintenance cost of the non-card account payment method.
- the first interface may specifically be an ISO8583 interface, but it is not limited thereto.
- the first target interface includes the first interface, and the message format of the first payment request may be basically consistent with the message format of the payment request sent by the payment acceptor device to the card exchange device in card-based payment.
- the payment request sent by the payment acceptor device to the card exchange device includes the card number identifier and transaction information, and the card number identifier in the payment request sent by the payment acceptor device to the card exchange device is replaced with a non-card account number identifier, then the first A payment request.
- the first target interface may include a newly added second interface.
- the second interface may include an XML interface, a JSON interface, and the like.
- the format of the newly added second interface can be developed and set according to scenarios and requirements, and is not limited here.
- step S302 use the non-card account number identifier in the first payment request to interact with the non-card account management device, so that the non-card account management device determines the target non-card account corresponding to the non-card account number identifier in the first payment request, to Make the card exchange device or the non-card account management device interact with the target non-card account fund management device corresponding to the target non-card account to execute payment.
- the non-card account management device stores the corresponding relationship between the non-card account ID and the non-card account, and the corresponding relationship between the non-card account and the non-card account fund management device.
- the corresponding relationship between the non-card account identifier and the non-card account is used to represent the corresponding relationship between the registered account number of the non-card account and the non-card account.
- the registered account number has a corresponding relationship with at least one non-card account. That is, a registered account can be bound with one non-card account, or can be bound with two or more non-card accounts.
- a registered account can be bound with one non-card account, or can be bound with two or more non-card accounts.
- one of the two or more non-card accounts that have a corresponding relationship with the registered account can be selected as the default payment account.
- the default payment account of the registered account can be used for payment.
- the corresponding relationship between the non-card account and the non-card account fund management device is used for the non-card account management device to route the payment request, so as to realize the payment.
- the card exchange device may send the non-card account identifier in the first payment request to the non-card account management device, and the non-card account management device determines the target non-card account and the target non-card account according to the corresponding relationship between the non-card account identifier and the non-card account.
- Card account funds management equipment may be used to send the non-card account identifier in the first payment request to the non-card account management device, and the non-card account management device determines the target non-card account and the target non-card account according to the corresponding relationship between the non-card account identifier and the non-card account.
- the non-card account management device can interact with the target non-card account fund management device to realize payment.
- the information sent by the non-card account management device to the target non-card account fund management may include non-card account identification and transaction information, which is not limited here.
- the non-card account management equipment directly interacts with the target non-card account fund management equipment, the process is simpler, and the transformation of the card exchange equipment is relatively small, which can further reduce the development cost and maintenance cost of non-card account payment.
- the non-card account management device determines the target non-card account and the target non-card account fund management device
- the information of the target non-card account such as the target non-card account identification, such as the target non-card account such as the communication address, etc.
- the information of the fund management equipment is sent to the card exchange equipment, and the card exchange equipment interacts with the target non-card account fund management equipment to realize payment.
- the information sent by the card exchange device to the target non-card account fund management device may include non-card account identification and transaction information, etc., which is not limited here.
- the card exchange device can still process card payment requests including card identification and transaction information.
- the card exchange device can determine whether the payment request is a non-card account payment request, that is, the first payment request or a card payment request, according to the content of the received payment request. Specifically, the card exchange device receives the payment request, and identifies the card identifier from the payment request.
- the card identification such as card number or card payment Token
- the payment request is a card payment request, and the information in the card payment request is sent to the card account fund management device to realize card-based payment
- the card identification is not recognized from the payment request
- it is determined that the payment request is a non-card account payment request, that is, the first payment request, and the information in the first payment request is sent to the non-card account management device, and the non-card account management device
- the non-card account management device directly interacts with the non-card account fund management device to realize non-card account payment, or the non-card account management device transmits the information of the non-card account and the information of the non-card account fund management device to the card exchange device,
- the card exchange equipment interacts with the non-card account fund management equipment to realize the non-card account payment.
- the card exchange device acquires the non-card account number identifier and transaction information from the payment acceptor device through the first payment request.
- the card exchange device can use the non-card account number identifier to interact with the non-card account management device used to manage the non-card account, so as to determine the non-card account fund management device corresponding to the non-card account used for payment.
- Card exchange equipment or non-card account management equipment can interact with non-card account fund management equipment through communication to realize non-card account payment.
- the card exchange equipment belongs to the card-based payment system, and the non-card account payment does not need to be separately developed and maintained.
- a new non-card account payment can be made through the card exchange equipment in the existing card-based payment system and the newly added non-card account management equipment , connect non-card accounts to the card-based payment system, realize non-card account payment, and reduce the development cost and maintenance cost required for non-card account payment.
- the non-card account management device can interact with multiple non-card account fund management devices, so the determination of the target non-card account and the target non-card account fund management device can be performed by the non-card account management device.
- non-card account management device For card exchange equipment, all payments indicated by payment requests that do not recognize the card identity can be delivered to non-card account management equipment for processing, and the business of non-card accounts and non-card account fund management equipment can be shielded from card exchange equipment impact, avoid occupying too many operating resources of the card exchange equipment, and avoid the impact on the card-based payment business.
- FIG. 4 is a flow chart of another embodiment of the non-card account payment method provided in the first aspect of the present application. The difference between FIG. 4 and FIG. 3 is that the non-card account payment method in FIG. 4 may further include steps S303 and S304.
- step S303 a first payment response is received.
- the first payment response includes a payment result.
- the first payment response may be sent by the non-card account management device to the card exchange device.
- the first payment response may be sent by the target non-card account funds management device to the card exchange device.
- step S304 the second payment response generated according to the first payment response is sent to the payment acceptor device.
- the second payment response is generated according to the first payment response.
- the second payment response includes a payment result. Send the second payment response to the payment acceptor device, so that the payment acceptor device obtains the payment result.
- the second payment response can be highly similar to the first payment response, where the highly similar means that the information in the second payment response is basically the same as the information in the first payment response, that is, because the sender of the first payment response, The receiver is different from the sender and receiver of the second payment response.
- the content related to the sender and receiver of the second payment response in the second payment response is different from the sender and receiver of the first payment response in the first payment response. Recipient-related content is different.
- the first payment response may include information such as payment result, message type, merchant ID, transaction initiator ID, message verification code, etc.
- the second payment response may include payment result, message type, merchant ID, transaction initiator ID, message verification code and other information; the payment result, message type, merchant ID and transaction initiator ID in the first payment response and the payment result, message type, merchant ID and transaction initiator in the second payment response
- the identification is the same; the message verification code in the first payment response is related to the sender and receiver of the first payment response, and the message verification code in the second payment response is related to the sender and receiver of the second payment response , therefore, the message check code in the first payment response is different from the message check code in the second payment response.
- step S304 may be approximately implemented as forwarding the first payment response to the payment acceptor device, further simplifying the process.
- the payment result and other information can be transmitted to the payment accepting party device, so that the user can obtain the payment result and other information.
- Fig. 5 is a flowchart of another embodiment of the non-card account payment method provided in the first aspect of the present application. The difference between FIG. 5 and FIG. 4 is that step S302 in FIG. 4 can be specifically refined into step S3021 in FIG. 5 , and step S303 in FIG. 4 can be specifically refined into step S3031 in FIG. 5 .
- step S3021 send the second payment request generated according to the first payment request to the non-card account management device through the second target interface, so that the non-card account management device determines the target non-card account, and the target non-card account fund management device Interact and execute payment.
- the second payment request includes the non-card account number identifier and transaction information in the first payment request. Specifically, the second payment request may be transmitted in the form of a message.
- the second payment request may also include one or more items of message type, message check code and other information, which is not limited here.
- the message verification code in the second payment request can be used to verify the integrity and legitimacy of the second payment request.
- the second target interface is an interface for interaction between the card exchange device and the card account management device.
- the second target interface and the first target interface may be the same interface or different interfaces, which is not limited herein.
- the second target interface may include a first interface for card-based interaction between the card exchange system and the payment acceptor device in the card-based payment system.
- the second target interface can reuse the original interface in the card-based payment system without developing a new interface, which can further reduce the development cost and maintenance cost of non-card account payment.
- the second payment request can be highly similar to the first payment request.
- the high similarity means that the information in the second payment request is basically the same as the information in the first payment request, that is, because the sender and receiver of the first payment request are different from the sender and receiver of the second payment request, the second payment request
- the content related to the sender and receiver of the second payment request in the request is different from the content related to the sender and receiver of the first payment request in the first payment request.
- the first payment request may include non-card account ID, transaction information, message type, message verification code and other information
- the second payment request may include non-card account ID, transaction information, message type, message verification code, etc. Code and other information
- the non-card account ID, transaction information, message type and other information in the first payment request are the same as the non-card account ID, transaction information, message type and other information in the second payment request
- the message check code in the first payment request is related to the sender and receiver of the first payment request
- the message check code in the second payment request is related to the sender and receiver of the second payment request. Therefore, the first payment request
- the message check code of is different from the message check code in the second payment request.
- step S3021 may be approximately implemented by forwarding the first payment request to the non-card account management device through the second target interface, further simplifying the process.
- the second target interface may include a newly added third interface.
- the third interface may include an XML interface, a JSON interface, and the like.
- the format of the newly added third interface can be developed and set according to scenarios and requirements, and is not limited here.
- the non-card account management device receives the second payment request through the second target interface, the target non-card account can be determined according to the non-card account number identifier in the second payment request, and the target non-card account can be determined according to the target non-card account.
- the non-card account management device can further interact with the target non-card account fund management device to realize payment.
- step S3031 the first payment response forwarded by the non-card account management device is received.
- the first payment response is sent by the target non-card account fund management device to the non-card account management device.
- the target non-card account fund management device executes the payment
- the target non-card account fund management device sends a first payment response to the non-card account management device.
- the non-card account management device forwards the first payment response to the card exchange device, so as to notify the card exchange device of the payment result, and facilitate the card exchange device to notify the payment accepting party device of the payment result.
- the non-card account management equipment directly interacts with the target non-card account fund management management equipment to execute payment, reduce the transformation of card exchange equipment, and further reduce the development cost and maintenance cost of non-card account payment.
- the non-card account management device directly interacts with the target non-card account fund management device to perform payment, making the process more concise and the non-card account payment more efficient.
- Fig. 6 is a flowchart of another embodiment of the non-card account payment method provided in the first aspect of the present application. The difference between FIG. 6 and FIG. 4 is that step S302 in FIG. 4 can be specifically refined into steps S3022 to S3024 in FIG. 6 , and step S303 in FIG. 4 can be specifically refined into step S3032 in FIG. 6 .
- step S3022 send the third payment request generated according to the first payment request to the non-card account management device through the third target interface, so that the non-card account management device determines the target non-card account and the target non-card account fund management device.
- the third payment request includes the non-card account number identifier and transaction information in the first payment request.
- the third target interface is an interface for interaction between the card exchange device and the non-card account management device.
- the third target interface and the first target interface may be the same interface or different interfaces, which is not limited herein.
- the third target interface may include the first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system.
- the third target interface can reuse the original interface in the card-based payment system without developing a new interface, which can further reduce the development cost and maintenance cost of non-card account payment.
- the third payment request can be highly similar to the first payment request.
- the high similarity means that the information in the third payment request is basically the same as that in the first payment request, that is, because the sender and receiver of the third payment request are different from the sender and receiver of the second payment request, the third payment request.
- the content related to the sender and receiver of the third payment request in the request is different from the content related to the sender and receiver of the first payment request in the first payment request.
- the first payment request may include non-card account ID, transaction information, message type, message verification code and other information
- the third payment request may include non-card account ID, transaction information, message type, message verification code, etc. Code and other information; the non-card account ID, transaction information, message type and other information in the first payment request are the same as the non-card account ID, transaction information, message type and other information in the third payment request;
- the message check code in the first payment request is related to the sender and receiver of the first payment request, and the message check code in the third payment request is related to the sender and receiver of the third payment request. Therefore, the first payment request
- the message check code of is different from the message check code in the third payment request.
- step S3022 can be approximately implemented as forwarding the first payment request to the non-card account management device through the third target interface, which can further simplify the process.
- the third target interface may include a newly added fourth interface.
- the fourth interface may include an XML interface, a JSON interface, and the like.
- the format of the newly added fourth interface can be developed and set according to scenarios and requirements, and is not limited here.
- step S3023 the non-card account feedback message sent by the non-card account management device is received.
- the non-card account management device receives the third payment request, and determines the target non-card account according to the non-card account identifier in the third payment request. According to the target non-card account, determine the target non-card account fund management equipment.
- the non-card account management device may send a non-card account feedback message to the card exchange device.
- the non-card account feedback message is used to indicate the target non-card account and the target non-card account fund management device.
- the target non-card account can be represented by the target non-card account's identification
- the target non-card account fund management device can be represented by the communication address of the target non-card account fund management device, which is not limited herein.
- the non-card account feedback message may include the identification of the target non-card account, the communication address of the target non-card account fund management device, etc., which is not limited here.
- the non-card account feedback message may also include message type, message check code and other information, which is not limited here.
- step S3024 according to the non-card account feedback message, a fourth payment request is sent to the target non-card account fund management device through the fourth target interface.
- the card exchange device can interact with the target non-card account funds management device.
- the card exchange device can determine the target non-card account and the target non-card account fund management device through the non-card account feedback message, thereby interacting with the target non-card account fund management device.
- the fourth payment request instructs the target non-card account funds management device to perform payment using the target non-card account.
- the fourth payment request may include the non-card account number identifier and transaction information, and may also include other information, which is not limited here.
- the fourth target interface is an interface for interaction between the card exchange device and the non-card account fund management device.
- the fourth target interface may include a fifth interface for interaction between the card exchange device and the card account funds management device in the card-based payment system.
- the fourth target interface can reuse the original interface in the card-based payment system without developing a new interface, which can further reduce the development cost and maintenance cost of non-card account payment.
- the fifth interface may specifically be an ISO8583 interface, but it is not limited thereto.
- the fourth target interface may include a newly added sixth interface.
- the sixth interface may include an XML interface, a JSON interface, and the like.
- the format of the newly added sixth interface can be developed and set according to scenarios and requirements, and is not limited here.
- step S3032 the first payment response sent by the fund management device of the target non-card account is received.
- the fund management device of the target non-card account receives the fourth payment request, and may perform payment by using the target non-card account according to the fourth payment request.
- the target non-card account fund management device forwards the first payment response to the card exchange device, so as to notify the card exchange device of the payment result, and facilitate the card exchange device to notify the payment accepting party device of the payment result.
- the card exchange device can also send non-card account general settlement information to the non-card account management device, so that the non-card account management device obtains the respective settlement information of the non-card account according to the non-card account general settlement information.
- the card exchange device performs clearing processing to obtain the general clearing information of non-card accounts.
- the total settlement information of non-card accounts does not distinguish the settlement information of different non-card accounts, but treats all non-card accounts as a whole, and the total settlement information of non-card accounts is the settlement information of this whole.
- the total settlement information of non-card accounts may include total flow information of non-card accounts, general detailed information of non-card accounts, general summary report of non-card accounts, general settlement parameters of non-card accounts, etc., which are not limited here.
- the non-card account general settlement information can be used for non-card account management equipment to perform clearing processing to obtain the respective settlement information of non-card accounts.
- the settlement information of the non-card accounts includes the flow information of the non-card accounts, the detailed information of the non-card accounts, the summary report of the non-card accounts, the settlement parameters of the non-card accounts, etc., which are not limited here.
- the second aspect of the present application provides a non-card account payment method, which can be applied to a non-card account management device.
- the non-card account management device stores the corresponding relationship between the non-card account ID and the non-card account, and the corresponding relationship between the non-card account and the non-card account fund management device.
- the specific content of the corresponding relationship between the non-card account ID and the non-card account and the corresponding relationship between the non-card account and the non-card account fund management device can refer to the relevant description in the above-mentioned embodiments, and will not be repeated here.
- Fig. 7 is a flow chart of an embodiment of the non-card account payment method provided by the second aspect of the present application. As shown in Fig. 7, the non-card account payment method may include step S401, step S402 and step S403, or may include step S401, step S402 and step S404.
- step S401 interact with the card exchange device using the non-card account number identifier in the first payment request received by the card exchange device.
- the first payment request is sent by the payment acceptor device to the card exchange device through the first target interface.
- the first payment request includes the non-card account number identifier and transaction information.
- the card exchange device belongs to the card-based payment system.
- the non-card account identifier may include a registered account or a token Token of the registered account.
- the registered account number has a corresponding relationship with at least one non-card account.
- step S402 according to the non-card account identifier in the first payment request, determine the target non-card account corresponding to the non-card account identifier in the first payment request.
- the non-card account management device may determine the target non-card account corresponding to the non-card account identifier in the first payment request according to the stored correspondence between the non-card account identifier and the non-card account.
- step S403 interact with the target non-card account fund management device corresponding to the target non-card account to execute payment.
- the non-card account management device determines the target non-card account fund management device according to the corresponding relationship between the stored non-card account and the non-card account fund management device.
- the non-card account management device can directly interact with the target non-card account fund management device to execute payment.
- the non-card account management device may send the non-card account ID and transaction information to the target non-card account fund management device, so that the target non-card account fund management device uses the target non-card account for payment.
- the non-card account management equipment directly interacts with the target non-card account fund management equipment, the process is simpler, and the transformation of the card exchange equipment is relatively small, which can further reduce the development cost and maintenance cost of non-card account payment.
- step S404 interact with the card exchange device, so that the card exchange device interacts with the target non-card account fund management device to perform payment.
- the non-card account management device determines the target non-card account fund management device according to the corresponding relationship between the stored non-card account and the non-card account fund management device.
- the non-card account management device may notify the card exchange device of the target non-card account fund management device, so that the card exchange device sends the non-card account ID and transaction information to the target non-card account fund management device, so that the target non-card account fund management device adopts the target non-card account fund management device.
- Non-card account for payment may notify the card exchange device of the target non-card account fund management device, so that the card exchange device sends the non-card account ID and transaction information to the target non-card account fund management device, so that the target non-card account fund management device adopts the target non-card account fund management device.
- Non-card account for payment may notify the card exchange device of the target non-card account fund management device, so that the card exchange device sends the non-card account ID and transaction information to the target non-card account fund management device, so that the target non-card
- the non-card account management device and the card exchange device may interact using the non-card account number identifier in the first payment request received from the payment acceptor device. Determine the target non-card account fund management device corresponding to the non-card account used for payment according to the non-card account identifier in the first payment request.
- the non-card account management device can directly interact with the target non-card account fund management device for payment, or the non-card account management device interacts with the card exchange device so that the card exchange device interacts with the target non-card account fund management device for payment.
- the card exchange equipment belongs to the card-based payment system, and the non-card account payment does not need to be separately developed and maintained.
- a new non-card account payment can be made through the card exchange equipment in the existing card-based payment system and the newly added non-card account management equipment , connect non-card accounts to the card-based payment system, realize non-card account payment, and reduce the development cost and maintenance cost required for non-card account payment.
- the non-card account management device can interact with multiple non-card account fund management devices, so the determination of the target non-card account and the target non-card account fund management device can be performed by the non-card account management device.
- non-card account management device For card exchange equipment, all payments indicated by payment requests that do not recognize card identifiers can be delivered to non-card account management equipment for processing, and the settings of non-card account management equipment can shield non-card accounts and non-card account fund management The impact of the business of the equipment on the card exchange equipment, avoid occupying too many operating resources of the card exchange equipment, and avoid the impact on the card-based payment business.
- the non-card account management device can interact with the target non-card account fund management device to realize payment
- the card exchange device can also interact with the target non-card account fund management device to realize payment
- Fig. 8 is a flow chart of another embodiment of the non-card account payment method provided by the second aspect of the present application. The difference between Fig. 8 and Fig. 7 is that step S402 shown in Fig. 7 may be specifically refined into step S4021 shown in Fig. 8, or may be refined into step S4022 and step S4023 shown in Fig.
- Step S403 can be detailed as step S4031 shown in Figure 8; the non-card account payment method shown in Figure 8 can also include steps S405 and S406; step S404 shown in Figure 7 can be specifically detailed as shown in Figure 8 step S4041 shown.
- step S4021 the second payment request generated according to the first payment request sent by the card exchange device is received through the second target interface.
- the second payment request includes the non-card account number identifier and transaction information in the first payment request.
- the specific content of the second payment request refer to the relevant description in the above embodiment, and details are not repeated here.
- the second target interface includes a first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system.
- the second target interface includes a newly added third interface.
- step S4031 send the fifth payment request generated according to the second payment request to the target non-card account fund management device through the fifth target interface.
- the fifth payment request instructs the target non-card account funds management device to perform payment using the target non-card account.
- the non-card account management device interacts with the target non-card account fund management device through the fifth payment request.
- the fifth payment request may include the non-card account number identifier and transaction information in the first payment request.
- the fifth payment request may specifically be transmitted in the form of a message.
- the fifth payment request may also include one or more items of message type, message check code and other information, which is not limited here.
- the message verification code in the fifth payment request can be used to verify the integrity and legitimacy of the fifth payment request.
- the fifth target interface is an interface for interaction between the non-card account management device and the target non-card account fund management device.
- the fifth target interface may include a fifth interface for interaction between the card exchange device and the card account fund management device in the card-based payment system.
- the fifth target interface can reuse the original interface in the card-based payment system without developing a new interface, which can further reduce the development cost and maintenance cost of non-card account payment .
- the fifth payment request can be highly similar to the second payment request.
- the high similarity means that the information in the fifth payment request is basically the same as the information in the second payment request, that is, because the sender and receiver of the second payment request are different from the sender and receiver of the fifth payment request, the fifth payment request.
- the content related to the sender and receiver of the fifth payment request in the request is different from the content related to the sender and receiver of the second payment request in the second payment request.
- the second payment request may include non-card account ID, transaction information, message type, message verification code and other information
- the fifth payment request may include non-card account ID, transaction information, message type, message verification code, etc. Code and other information
- the non-card account ID, transaction information, message type and other information in the second payment request are the same as the non-card account ID, transaction information, message type and other information in the fifth payment request
- the message check code in the second payment request is related to the sender and receiver of the second payment request
- the message check code in the fifth payment request is related to the sender and receiver of the fifth payment request. Therefore, the second payment request
- the message check code of is different from the message check code in the fifth payment request.
- step S4031 can be approximately implemented as forwarding the second payment request to the non-card account fund management device through the fifth target interface, which can further simplify the process.
- the fifth target interface may include a newly added seventh interface.
- the seventh interface may include an XML interface, a JSON interface, and the like.
- the format of the newly added seventh interface can be developed and set according to scenarios and requirements, and is not limited here.
- step S405 the first payment response sent by the fund management device of the target non-card account is received.
- the first payment response includes a payment result.
- the specific content of the first payment response refer to the relevant descriptions in the foregoing embodiments, and details are not repeated here.
- step S406 the first payment response is forwarded to the card exchange device.
- the non-card account management device forwards the first payment response to the card exchange device to notify the card exchange device of the payment result.
- step S4022 the third payment request generated according to the first payment request and sent by the card exchange device is received through the third target interface.
- the third payment request includes the non-card account number identifier and transaction information in the first payment request.
- the third target interface may include the first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system.
- the third target interface may include a newly added fourth interface.
- step S4023 a non-card account feedback message is generated according to the third payment request.
- the non-card account management device receives the third payment request, and determines the target non-card account according to the non-card account identifier in the third payment request. According to the target non-card account, determine the target non-card account fund management equipment.
- the non-card account management device may send a non-card account feedback message to the card exchange device. The non-card account feedback message is used to indicate the target non-card account and the target non-card account fund management device.
- step S4041 send a non-card account feedback message to the card exchange device, so that the card exchange device sends a fourth payment request to the target non-card account fund management device through the fourth target interface.
- the fourth payment request instructs the target non-card account funds management device to perform payment using the target non-card account.
- the non-card account management device may perform a second clearing process to obtain the respective clearing information of the non-card accounts. Specifically, the non-card account management device receives the non-card account general settlement information sent by the card exchange device. The non-card account management device obtains the respective settlement information of the non-card accounts according to the general settlement information of the non-card accounts.
- the non-card account management device performs secondary clearing to obtain the respective clearing information of the non-card accounts. It can shield the impact of the clearing process of non-card accounts on the card exchange equipment, so as to avoid affecting the card-based payment.
- the non-card account management device may also receive a registration instruction, and the registration instruction may include a registration account number, an identification of the non-card account, an identification of the non-card account fund management device corresponding to the non-card account, and the like.
- the non-card account management device can assign the non-card account identifier to the registered account, establish and store the corresponding relationship between the non-card account identifier and the non-card account, and the corresponding relationship between the non-card account and the non-card account fund management device.
- the non-card account management device can also receive default non-card account settings, thereby setting the default non-card account corresponding to the registered account lock.
- the default non-card account is used for payment associated with the registered account.
- the non-card account management device can also store registered account passwords, non-card account payment interface identifiers, payment authority and other information, which is not limited here.
- the non-card account management device can also provide functions such as verification, inquiry, and cancellation of the non-card account.
- the non-card account management device can verify the registered account number of the non-card account with the non-card account fund management device corresponding to the non-card account, so as to prevent fraudulent use of other people's information for registration. For example, verify the reserved information such as the name, address, ID number, validity period, and password of the non-card account of the non-card account. Verification rules can be set according to scenarios and requirements, and are not limited here. After the verification is passed, the registered account can be used for payment.
- the non-card account management device can also query the registered account number of the fund receiver during the payment process, so as to query the reserved information such as the name, address, certificate number, validity period, non-card account password and other reserved information of the non-card account corresponding to the registered account number, so as to Identify recipients of funds.
- the non-card account management device can also receive a cancellation instruction, cancel the registered account indicated by the cancellation instruction according to the cancellation instruction, and send a cancellation notification to the non-card account fund management device corresponding to the canceled registered account to notify the non-card account fund The non-card account under the registered account of the management device has been cancelled.
- the following examples take the non-card account management device interacting with the target non-card account fund management to complete the non-card account payment and the card exchange device to interact with the target non-card account fund management to complete the non-card account payment as examples. Be explained.
- FIG. 9 is a flow chart of an example of the non-card account payment process in the embodiment of the present application. As shown in FIG. 9 , the non-card account payment process may include steps S501 to S508.
- step S501 the payment acceptor device sends a first payment request to the card exchange device.
- step S502 the card exchange device sends a second payment request to the non-card account management device.
- the non-card account management device determines the target non-card account and the target non-card account fund management device according to the non-card account identifier.
- step S504 the non-card account management device sends a fifth payment request to the target non-card account fund management device.
- step S505 the target non-card account fund management device uses the target non-card account to make payment according to the fifth payment request.
- step S506 the target non-card account fund management device sends a first payment response to the non-card account management device.
- step S507 the non-card account management device sends a first payment response to the card exchange device.
- step S508 the card exchange device sends a second payment response to the payment acceptor device.
- step S501 to step S508 can refer to the relevant part in the above embodiment, which is not limited here.
- FIG. 10 is a flow chart of another example of the non-card account payment process in the embodiment of the present application. As shown in Figure 10, the non-card account payment process may include steps S601 to S6
- step S601 the payment acceptor device sends a first payment request to the card exchange device.
- step S602 the card exchange device sends a third payment request to the non-card account management device.
- step S603 the non-card account management device determines the target non-card account and the target non-card account fund management device according to the non-card account identifier.
- step S604 the non-card account management device sends a non-card account feedback message to the card exchange device.
- step S605 the card exchange device sends a fourth payment request to the target non-card account fund management device.
- step S606 the target non-card account fund management device uses the target non-card account to make payment according to the fourth payment request.
- step S607 the target non-card account fund management device sends a first payment response to the card exchange device.
- step S608 the card exchange device determines the payment acceptor device according to the first payment response and the first payment request.
- step S609 the card exchange device sends a second payment response to the payment acceptor device.
- step S601 to step S609 For the specific content of the above step S601 to step S609, refer to the relevant description in the above embodiment, and details are not repeated here.
- the third aspect of the present application provides a card exchange device, which belongs to the card-based payment system.
- Fig. 11 is a schematic structural diagram of an embodiment of the card switching device provided by the third aspect of the present application.
- the card exchange device 700 includes an interaction module 701 .
- the interaction module 701 may include a receiving unit 7011 .
- the receiving unit 7011 may be configured to receive the first payment request sent by the payment acceptor device through the first target interface.
- the first payment request includes the non-card account number identifier and transaction information.
- the non-card account identifier is used to identify the registered account number of the non-card account.
- the non-card account identifier includes a registered account or a token Token of the registered account.
- the registered account number has a corresponding relationship with at least one non-card account.
- the first target interface includes a first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system.
- the first target interface includes a newly added second interface.
- the interaction module 701 may be used to interact with the non-card account management device by using the non-card account identifier in the first payment request, so that the non-card account management device determines the target non-card account corresponding to the non-card account identifier in the first payment request, so as to Make the card exchange device or the non-card account management device interact with the target non-card account fund management device corresponding to the target non-card account to execute payment.
- the non-card account management device stores the corresponding relationship between the non-card account ID and the non-card account, and the corresponding relationship between the non-card account and the non-card account fund management device.
- the card exchange device acquires the non-card account number identifier and transaction information from the payment acceptor device through the first payment request.
- the card exchange device can use the non-card account number identifier to interact with the non-card account management device used to manage the non-card account, so as to determine the non-card account fund management device corresponding to the non-card account used for payment.
- Card exchange equipment or non-card account management equipment can interact with non-card account fund management equipment through communication to realize non-card account payment.
- the card exchange equipment belongs to the card-based payment system.
- the non-card account payment does not need to be separately developed and maintained.
- a new non-card account payment can be made through the card exchange equipment in the existing card-based payment system and the newly added non-card account management equipment. , connect non-card accounts to the card-based payment system, realize non-card account payment, and reduce the development cost and maintenance cost required for non-card account payment.
- the non-card account management device can interact with multiple non-card account fund management devices, so the determination of the target non-card account and the target non-card account fund management device can be performed by the non-card account management device.
- non-card account management device For card exchange equipment, all payments indicated by payment requests that do not recognize the card identity can be delivered to non-card account management equipment for processing, and the business of non-card accounts and non-card account fund management equipment can be shielded from card exchange equipment impact, avoid occupying too many operating resources of the card exchange equipment, and avoid the impact on the card-based payment business.
- the above-mentioned receiving unit 7011 may also be configured to receive the payment request sent by the payment acceptor device through the first target interface; if the card identification is not recognized from the payment request, confirm that the payment request is the first payment request.
- the interaction module 701 in the above embodiment also has a sending function.
- Fig. 12 is a schematic structural diagram of another embodiment of the card switching device provided by the third aspect of the present application. The difference between FIG. 12 and FIG. 11 is that the interaction module 701 shown in FIG. 12 may further include a sending unit 7012 .
- the sending unit 7012 may be configured to send the second payment request generated according to the first payment request to the non-card account management device through the second target interface, so that the non-card account management device determines the target non-card account, which is different from the target non-card account.
- the card account fund management device interacts and executes the payment.
- the second payment request includes the non-card account number identifier and transaction information in the first payment request.
- the second target interface may include a first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system.
- the second target interface may include a newly added third interface.
- the sending unit 7012 may be configured to send the third payment request generated according to the first payment request to the non-card account management device through the third target interface, so that the non-card account management device determines the target non-card account and the target non-card account management device. Card account funds management equipment.
- the third payment request includes the non-card account number identifier and transaction information in the first payment request.
- the third target interface may include a first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system.
- the third target interface may include a newly added fourth interface.
- the receiving unit 7011 is also configured to receive a non-card account feedback message sent by the non-card account management device.
- the non-card account feedback message is used to indicate the target non-card account and the target non-card account fund management device.
- the sending unit 7012 is also configured to send a fourth payment request to the target non-card account fund management device through the fourth target interface according to the non-card account feedback message.
- the fourth payment request instructs the target non-card account funds management device to perform payment using the target non-card account.
- the fourth target interface may include a fifth interface for interaction between the card exchange device and the card account funds management device in the card-based payment system.
- the fourth target interface may include a newly added sixth interface.
- the receiving unit 7011 is also configured to receive the first payment response.
- the first payment response includes a payment result.
- the sending unit 7012 is further configured to send the second payment response generated according to the first payment response to the payment acceptor device.
- the second payment response includes a payment result.
- the receiving unit 7011 is also configured to receive the first payment response.
- the first payment response includes a payment result.
- the sending unit 7012 is further configured to send the second payment response generated according to the first payment response to the payment acceptor device.
- the second payment response includes a payment result.
- the receiving unit 7011 is further configured to receive the first payment response forwarded by the non-card account management device.
- the first payment response is sent by the target non-card account fund management device to the non-card account management device.
- the receiving unit 7011 is further configured to receive the first payment response sent by the target non-card account fund management device.
- the sending unit 7012 is also configured to send non-card account general settlement information to the non-card account management device, so that the non-card account management device obtains the respective settlement information of the non-card account according to the non-card account general settlement information.
- the fourth aspect of the present application provides a non-card account management device.
- the non-card account management device stores the corresponding relationship between the non-card account identifier and the non-card account, and the corresponding relationship between the non-card account and the non-card account fund management device.
- Fig. 13 is a schematic structural diagram of an embodiment of a non-card account management device provided in the fourth aspect of the present application.
- the non-card account management device 800 may include an interaction module 801 and a processing module 802 .
- the interaction module 801 may be configured to interact with the card exchange device using the non-card account number identifier in the first payment request received by the card exchange device.
- the first payment request is sent by the payment acceptor device to the card exchange device through the first target interface.
- the first payment request includes the non-card account number identifier and transaction information.
- the card exchange device belongs to the card-based payment system.
- the non-card account identifier includes a registered account or a token Token of the registered account.
- the registered account number has a corresponding relationship with at least one non-card account.
- the processing module 802 may be configured to determine a target non-card account corresponding to the non-card account identifier in the first payment request according to the non-card account identifier in the first payment request.
- the interaction module 801 is also used to interact with the target non-card account fund management device corresponding to the target non-card account to perform payment; or interact with the card exchange device so that the card exchange device interacts with the target non-card account fund management device to perform payment .
- the non-card account management device and the card exchange device may interact using the non-card account number identifier in the first payment request received from the payment acceptor device. Determine the target non-card account fund management device corresponding to the non-card account used for payment according to the non-card account identifier in the first payment request.
- the non-card account management device can directly interact with the target non-card account fund management device for payment, or the non-card account management device interacts with the card exchange device so that the card exchange device interacts with the target non-card account fund management device for payment.
- the card exchange equipment belongs to the card-based payment system, and the non-card account payment does not need to be separately developed and maintained.
- a new non-card account payment can be made through the card exchange equipment in the existing card-based payment system and the newly added non-card account management equipment , connect non-card accounts to the card-based payment system, realize non-card account payment, and reduce the development cost and maintenance cost required for non-card account payment.
- the non-card account management device can interact with multiple non-card account fund management devices, so the determination of the target non-card account and the target non-card account fund management device can be performed by the non-card account management device.
- non-card account management device For card exchange equipment, all payments indicated by payment requests that do not recognize card identifiers can be delivered to non-card account management equipment for processing, and the settings of non-card account management equipment can shield non-card accounts and non-card account fund management The impact of the business of the equipment on the card exchange equipment, avoid occupying too many operating resources of the card exchange equipment, and avoid the impact on the card-based payment business.
- the interaction module 801 in the above embodiment has a receiving function and a sending function.
- Fig. 14 is a schematic structural diagram of another embodiment of the non-card account management device provided in the fourth aspect of the present application. The difference between FIG. 14 and FIG. 13 is that the interaction module 801 may include a receiving unit 8011 and a sending unit 8012 .
- the receiving unit 8011 may be configured to receive, through the second target interface, the second payment request generated according to the first payment request and sent by the card exchange device.
- the second payment request includes the non-card account number identifier and transaction information in the first payment request.
- the second target interface may include a first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system.
- the second target interface may include a newly added third interface.
- the sending unit 8012 may be configured to send the fifth payment request generated according to the second payment request to the target non-card account fund management device through the fifth target interface.
- the fifth payment request instructs the target non-card account funds management device to perform payment using the target non-card account.
- the fifth target interface may include a fifth interface for interaction between the card exchange device and the card account fund management device in the card-based payment system.
- the fifth target interface may include a newly added seventh interface.
- Fig. 15 is a schematic structural diagram of another embodiment of the non-card account management device provided in the fourth aspect of the present application.
- the difference between FIG. 15 and FIG. 13 is that the interaction module 801 may include a receiving unit 8011 , a sending unit 8012 and a generating unit 8013 .
- the receiving unit 8011 may be configured to receive the third payment request generated according to the first payment request and sent by the card exchange device through the third target interface.
- the third payment request includes the non-card account number identifier and transaction information in the first payment request.
- the third target interface may include a first interface for card-based interaction between the card exchange device and the payment acceptor device in the card-based payment system.
- the third target interface may include a newly added fourth interface.
- the generating unit 8013 may be configured to generate a non-card account feedback message according to the third payment request.
- the non-card account feedback message is used to indicate the target non-card account and the target non-card account fund management device.
- the sending unit 8012 may be configured to send a non-card account feedback message to the card exchange device, so that the card exchange device sends a fourth payment request to the target non-card account fund management device through the fourth target interface.
- the fourth payment request instructs the target non-card account funds management device to perform payment using the target non-card account.
- the receiving unit 8011 is further configured to receive a first payment response sent by the target non-card account fund management device, where the first payment response includes a payment result.
- the sending unit 8012 is further configured to forward the first payment response to the card exchange device.
- the non-card account management device 800 can also perform clearing processing within the non-card account.
- Fig. 16 is a schematic structural diagram of yet another embodiment of the non-card account management device provided in the fourth aspect of the present application. The difference between FIG. 16 and FIG. 14 is that the non-card account management device 800 may further include a sorting module 803 .
- the receiving unit 8011 can also be used to receive the non-card account general settlement information sent by the card exchange device.
- the sorting module 803 can be used to obtain the respective settlement information of the non-card accounts according to the total settlement information of the non-card accounts.
- the fifth aspect of the present application also provides a card exchange device.
- Fig. 17 is a schematic structural diagram of an embodiment of the card switching device provided in the fifth aspect of the present application.
- the card exchange device 900 includes a memory 901 , a processor 902 and a computer program stored in the memory 901 and operable on the processor 902 .
- the above-mentioned processor 902 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
- CPU central processing unit
- ASIC Application Specific Integrated Circuit
- Memory 901 may include read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk storage medium device, optical storage medium device, flash memory device, electrical, optical or other physical/tangible Memory storage device.
- ROM read-only memory
- RAM random access memory
- disk storage medium device disk storage medium device
- optical storage medium device disk storage medium device
- flash memory device electrical, optical or other physical/tangible Memory storage device.
- memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions, and when the software is executed (e.g., by one or multiple processors), it is operable to perform the operations described with reference to the non-card account payment method according to the first aspect of the present application.
- the processor 902 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 901, so as to implement the non-card account payment method applied to the card exchange device in the above embodiment.
- the card switching device 900 may further include a communication interface 903 and a bus 904 .
- the memory 901 , the processor 902 , and the communication interface 903 are connected through a bus 904 to complete mutual communication.
- the communication interface 903 is mainly used to realize the communication between various modules, devices, units and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through the communication interface 903 .
- the bus 904 includes hardware, software, or both, and couples the components of the card switching device 900 to each other.
- the bus 904 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (Enhanced Industry Standard Architecture, EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, Industry Standard Architecture (ISA) bus, InfiniBand interconnect, Low pin count (Low pin count, LPC) bus, memory bus, MicroChannel Architecture (MicroChannel Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-E) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association local (Video Electronics Standards Association Local Bus, VLB) bus or other suitable bus or a combination of two or more of these.
- Bus 904 may comprise one or more buses, where appropriate. Although the embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.
- the sixth aspect of the present application also provides a non-card account management device.
- Fig. 18 is a schematic structural diagram of an embodiment of a non-card account management device provided in the sixth aspect of the present application.
- the non-card account management 1000 includes a memory 1001 , a processor 1002 and a computer program stored on the memory 1001 and operable on the processor 1002 .
- the above-mentioned processor 1002 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
- CPU central processing unit
- ASIC Application Specific Integrated Circuit
- Memory 1001 may include read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk storage medium device, optical storage medium device, flash memory device, electrical, optical or other physical/tangible Memory storage device.
- ROM read-only memory
- RAM random access memory
- disk storage medium device disk storage medium device
- optical storage medium device disk storage medium device
- flash memory device electrical, optical or other physical/tangible Memory storage device.
- memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions, and when the software is executed (e.g., by one or multiple processors), it is operable to perform the operations described with reference to the non-card account payment method according to the second aspect of the present application.
- the processor 1002 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 1001, so as to implement the non-card account payment method applied to the non-card account management device in the above embodiment.
- the non-card account management device 1000 may further include a communication interface 1003 and a bus 1004 .
- the memory 1001 , the processor 1002 , and the communication interface 1003 are connected through a bus 1004 to complete mutual communication.
- the communication interface 1003 is mainly used to realize the communication between various modules, devices, units and/or devices in the embodiments of the present application. Input devices and/or output devices can also be accessed through the communication interface 1003 .
- the bus 1004 includes hardware, software or both, and couples the components of the non-card account management device 1000 to each other.
- the bus 1004 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (Enhanced Industry Standard Architecture, EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, Industry Standard Architecture (ISA) bus, InfiniBand interconnect, Low pin count (Low pin count, LPC) bus, memory bus, MicroChannel Architecture (MicroChannel Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-E) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association (Video Electronics Standards Association Local Bus, VLB) bus or other suitable bus or a combination of two or more of these.
- Bus 1004 may comprise one or more buses, where appropriate. Although the embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.
- the seventh aspect of the present application provides a non-card account payment system.
- the non-card account payment system may include the card exchange device and the non-card account management system in the above embodiments.
- the card exchange device and the non-card account management system please refer to the relevant descriptions in the above embodiments, which will not be repeated here.
- the non-card account payment system may further include a payment acquirer device and a non-card account funds management device.
- a payment acquirer device for the specific content of the payment acceptor device and the non-card account fund management device, please refer to the relevant descriptions in the above embodiments, and details will not be repeated here.
- the eighth aspect of the present application also provides a computer-readable storage medium, on which computer program instructions are stored.
- the computer program instructions are executed by a processor, the non-standard functions applied to the card exchange device in the above-mentioned embodiments can be implemented.
- Card account payment method and can achieve the same technical effect, in order to avoid repetition, no more details here.
- the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk. etc., are not limited here.
- the ninth aspect of the present application also provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the application in the above-mentioned embodiments to the non-card account management device can be implemented.
- non-card account payment method and can achieve the same technical effect, in order to avoid repetition, no more details here.
- the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk. etc., are not limited here.
- processors may be, but are not limited to, general purpose processors, special purpose processors, application specific processors, or field programmable logic circuits. It can also be understood that each block in the block diagrams and/or flowcharts and combinations of blocks in the block diagrams and/or flowcharts can also be realized by dedicated hardware for performing specified functions or actions, or can be implemented by dedicated hardware and Combination of computer instructions to achieve.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Physics & Mathematics (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Economics (AREA)
- Computer Security & Cryptography (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Computer Networks & Wireless Communication (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
提供了一种非卡账户支付方法、设备、系统及存储介质,涉及数据处理领域。该方法包括:通过第一目标接口接收支付受理方设备(21)发送的第一支付请求,第一支付请求包括非卡账号标识和交易信息,非卡账号标识用于标识非卡账户的注册账号;利用非卡账号标识与非卡账户管理设备(23)交互,使非卡账户管理设备(23)确定与该非卡账号标识对应的目标非卡账户,以使卡交换设备(22)或非卡账户管理设备(23)与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付,非卡账户管理设备(23)存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。
Description
相关申请的交叉引用
本申请要求享有于2021年8月3日提交的名称为“非卡账户支付方法、设备、系统及存储介质”的中国专利申请202110885046.6的优先权,该申请的全部内容通过引用并入本文中。
本申请属于数据处理领域,尤其涉及一种非卡账户支付方法、设备、系统及存储介质。
卡基支付以银行卡、预付卡等卡为主要支付工具载体去实现各种支付服务。在卡基支付系统中,支付受理方设备将采集到的卡信息传输至卡交换设备,由卡交换设备基于卡号等卡信息,将支付信息路由至对应的发卡方设备。
但随着支付技术的发展,出现了非卡账户的支付且非卡账户的支付应用范围越来越广。但单独开发、维护一个新的非卡账户支付系统所需的资源、成本都过于庞大,因此,现阶段亟需一种能够减少开发、维护的资源和成本的非卡账户支付方法。
发明内容
本申请实施例提供一种非卡账户支付方法、设备、系统及存储介质,能够降低非卡账户支付所需的开发成本和维护成本。
第一方面,本申请实施例提供一种非卡账户支付方法,应用于卡交换设备,卡交换设备属于卡基支付系统,该方法包括:通过第一目标接口接收支付受理方设备发送的第一支付请求,第一支付请求包括非卡账号标识 和交易信息,非卡账号标识用于标识非卡账户的注册账号;利用第一支付请求中的非卡账号标识与非卡账户管理设备交互,使非卡账户管理设备确定与第一支付请求中的非卡账号标识对应的目标非卡账户,以使卡交换设备或非卡账户管理设备与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付,非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。
第二方面,本申请实施例提供一种非卡账户支付方法,应用于非卡账户管理设备,非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系,该方法包括:与卡交换设备利用卡交换设备接收到的第一支付请求中的非卡账号标识进行交互,第一支付请求由支付受理方设备通过第一目标接口向卡交换设备发送,包括非卡账号标识和交易信息,卡交换设备属于卡基支付系统;根据第一支付请求中的非卡账号标识,确定与第一支付请求中的非卡账号标识对应的目标非卡账户;与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付;或者,与卡交换设备交互,以使卡交换设备与目标非卡账户资金管理设备交互,执行支付。
第三方面,本申请实施例提供一种卡交换设备,卡交换设备属于卡基支付系统,卡交换设备包括交互模块,交互模块包括接收单元;接收单元,用于通过第一目标接口接收支付受理方设备发送的第一支付请求,第一支付请求包括非卡账号标识和交易信息,非卡账号标识用于标识非卡账户的注册账号;交互模块,用于利用第一支付请求中的非卡账号标识与非卡账户管理设备交互,使非卡账户管理设备确定与第一支付请求中的非卡账号标识对应的目标非卡账户,以使卡交换设备或非卡账户管理设备与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付,非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。
第四方面,本申请实施例提供一种非卡账户管理设备,非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系,非卡账户管理设备包括交互模块和处理模块; 交互模块,用于与卡交换设备利用卡交换设备接收到的第一支付请求中的非卡账号标识进行交互,第一支付请求由支付受理方设备通过第一目标接口向卡交换设备发送,包括非卡账号标识和交易信息,卡交换设备属于卡基支付系统;处理模块,用于根据第一支付请求中的非卡账号标识,确定与第一支付请求中的非卡账号标识对应的目标非卡账户;交互模块还用于与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付;或者,与卡交换设备交互,以使卡交换设备与目标非卡账户资金管理设备交互,执行支付。
第五方面,本申请实施例提供一种卡交换设备,包括:处理器以及存储有计算机程序指令的存储器;处理器执行计算机程序指令时实现第一方面的非卡账户支付方法。
第六方面,本申请实施例提供一种非卡账户管理设备,包括:处理器以及存储有计算机程序指令的存储器;处理器执行计算机程序指令时实现第二方面的非卡账户支付方法。
第七方面,本申请实施例提供一种非卡账户支付系统,包括第五方面的卡交换设备和第六方面的非卡账户管理设备。
第八方面,本申请实施例提供一种计算机可读存储介质,计算机可读存储介质上存储有计算机程序指令,计算机程序指令被处理器执行时实现第一方面的非卡账户支付方法。
第九方面,本申请实施例提供一种计算机可读存储介质,计算机可读存储介质上存储有计算机程序指令,计算机程序指令被处理器执行时实现第二方面的非卡账户支付方法。
本申请实施例提供一种非卡账户支付方法、设备、系统及存储介质,卡交换设备通过第一支付请求从支付受理方设备获取非卡账号标识和交易信息。卡交换设备可利用非卡账号标识与用于管理非卡账户的非卡账户管理设备交互,从而确定支付所采用的非卡账户对应的非卡账户资金管理设备。卡交换设备或非卡账户管理设备可与非卡账户资金管理设备通过通信交互,实现非卡账户支付。卡交换设备属于卡基支付系统,非卡账户支付不需要单独开发、维护一个新的非卡账户支付,可通过现有的卡基支付系 统中的卡交换设备和新增的非卡账户管理设备,将非卡账户接入卡基支付系统,实现非卡账户支付,降低非卡账户支付所需的开发成本和维护成本。
下面将通过参考附图来描述本申请示例性实施例的特征、优点和技术效果。
为了更清楚地说明本申请实施例的技术方案,下面将对本申请实施例中所需要使用的附图作简单的介绍,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为卡基支付系统的一示例的结构示意图;
图2为本申请实施例提供的非卡账户支付方法的应用场景的一示例的示意图;
图3为本申请第一方面提供的非卡账户支付方法的一实施例的流程图;
图4为本申请第一方面提供的非卡账户支付方法的另一实施例的流程图;
图5为本申请第一方面提供的非卡账户支付方法的又一实施例的流程图;
图6为本申请第一方面提供的非卡账户支付方法的再一实施例的流程图;
图7为本申请第二方面提供的非卡账户支付方法的一实施例的流程图;
图8为本申请第二方面提供的非卡账户支付方法的另一实施例的流程图;
图9为本申请实施例中非卡账号支付流程的一示例的流程图;
图10为本申请实施例中非卡账号支付流程的另一示例的流程图;
图11为本申请第三方面提供的卡交换设备的一实施例的结构示意图;
图12为本申请第三方面提供的卡交换设备的另一实施例的结构示意图;
图13为本申请第四方面提供的非卡账户管理设备的一实施例的结构示意图;
图14为本申请第四方面提供的非卡账户管理设备的另一实施例的结构示意图;
图15为本申请第四方面提供的非卡账户管理设备的又一实施例的结构示意图;
图16为本申请第四方面提供的非卡账户管理设备的再一实施例的结构示意图;
图17为本申请第五方面提供的卡交换设备的一实施例的结构示意图;
图18为本申请第六方面提供的非卡账户管理设备的一实施例的结构示意图。
下面将详细描述本申请的各个方面的特征和示例性实施例,为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及具体实施例,对本申请进行进一步详细描述。应理解,此处所描述的具体实施例仅意在解释本申请,而不是限定本申请。对于本领域技术人员来说,本申请可以在不需要这些具体细节中的一些细节的情况下实施。下面对实施例的描述仅仅是为了通过示出本申请的示例来提供对本申请更好的理解。
卡基支付是以银行卡、预付卡等卡为主要支付工具载体去实现各种支付服务的支付方式。卡基支付依托于卡基支付系统实现。图1为卡基支付系统的一示例的结构示意图。如图1所示,卡基支付系统可包括支付受理方设备11、卡交换设备12和卡账户资金管理设备13。其中,支付受理方设备11可与卡交换设备12进行交互,卡交换设备12可与卡账户资金管理设备13进行交互,由卡交换设备12根据路由机制,将支付受理方设备11的支付请求转发给对应的卡账户资金管理设备13,以实现卡基支付。
由于卡基支付系统中的卡交换设备的路由机制是基于卡号、卡的发卡行识别码(Bank Identification Number,BIN)制定的,因此,卡基支付系统无法适应非卡账户的注册账号,非卡账户的支付不能直接在卡基支付系统中进行。而单独开发、维护一个新的非卡账户支付系统需要花费大量的资源和成本。
本申请提供了一种非卡账户支付方法、设备、系统及存储介质,不需单独开发、维护一个新的非卡账户支付系统,能够利用卡基支付系统中的卡交换设备进行非卡账户的支付,从而降低非卡账户支付的开发成本和维护成本。
本申请实施例中的非卡账户支付方法可涉及支付受理方设备、卡交换设备、非卡账户管理设备和非卡账户资金管理设备。图2为本申请实施例提供的非卡账户支付方法的应用场景的一示例的示意图。如图2所示,非卡账户支付系统可包括支付受理方设备21、卡交换设备22、非卡账户管理设备23和非卡账户资金管理设备24。
支付受理方设备21可与卡交换设备22进行通信交互。支付受理方设备21可包括如手机等的移动终端、销售(Point Of Sales,POS)设备等具有支付受理功能的设备。
卡交换设备22可与非卡账户管理设备23进行通信交互。卡交换设备22具体可包括服务器等设备,非卡账户支付系统中的卡交换设备22的数量在此并不限定。卡交换设备22属于卡基支付系统,即本申请实施例中非卡账户支付系统中的卡交换设备22可复用卡基支付系统中的卡交换设备。
非卡账户管理设备23可与非卡账户资金管理设备24进行通信交互。一个非卡账户管理设备23可与一个或两个以上的非卡账户资金管理设备24进行通信交互。非卡账户管理设备23具体可包括服务器等设备,非卡账户支付系统中的非卡账户管理设备23的数量在此并不限定。
在一些示例中,卡交换设备22可与非卡账户资金管理设备24进行通信交互。一个卡交换设备22可与一个或两个以上的非卡账户资金管理设备24进行通信交互。
非卡账户资金管理设备24可为非卡账户的资金管理设备,具体可包括服务器等设备,非卡账户支付系统中非卡账户资金管理设备24的数量在此并不限定。
本申请第一方面提供一种非卡账户支付方法,可应用于卡交换设备。图3为本申请第一方面提供的非卡账户支付方法的一实施例的流程图。如图3所示,该非卡账户支付方法可包括步骤S301和步骤S302。
在步骤S301中,通过第一目标接口接收支付受理方设备发送的第一支付请求。
第一支付请求用于支付受理方设备向卡交换设备发起非卡账户支付。第一支付请求可包括非卡账号标识和交易信息。
非卡账号标识用于标识非卡账户的注册账号。非卡账户为非银行卡、预付卡等卡的账户。在一些示例中,非卡账户标识可包括非卡账户的注册账号或注册账号的令牌Token。注册账号可包括手机号、邮箱地址、非卡用户身份标识即非卡用户身份ID、支付应用程序身份标识即支付程序ID等,在此并不限定。在非卡账户标识包括注册账号的令牌Token的情况下,注册账号与令牌Token之间可相互转换,注册账号与令牌Token之间的转换算法在此并不限定。
交易信息可包括支付金额、支付时间、商户标识、交易发起方标识中的一项或两项以上,在此并不限定。
支付受理方设备可通过各类载体获取第一支付请求中的信息。例如,支付受理方设备可通过扫码、接收用户输入等方式获取到非卡账号标识、交易信息等信息,在此并不限定。
第一支付请求具体可以报文形式传输。第一支付请求还可包括报文类型、报文校验码等信息中的一项或两项以上,在此并不限定。第一支付请求中的报文校验码可用于验证第一支付请求的完整性和合法性。
例如,第一支付请求通过报文形式传输,报文可包括报文头、位图和报文体。报文体可包括报文消息类型、银行卡卡号、交易金额、交易时间、商户代码、交易发起方、报文校验码等信息。为了便于理解,下面举例示出第一支付请求中的部分数据片段:
其中,Message Head为报文头;Message Content为报文体;报文体可包括0至128个域,可与报文消息类型、银行卡卡号、交易金额、交易时间、商户代码、交易发起方、报文校验码等信息对应。在本申请实施例中,在进行非卡账户支付时,上述第2域Field 2可以为非卡账户标识;在进行卡基支付时,上述第2域Field 2可为卡号标识。本申请实施例中的非卡账户支付中的第一支付请求携带非卡账户标识,卡基支付中的支付请求携带卡号标识,除了非卡账户标识和卡号标识的不同以外,本申请实施例中的非卡账户支付中的第一支付请求的格式与卡基支付中的支付请求的格式可相同,从而能够将非卡账户接入卡基支付系统。
第一目标接口为卡交换设备与支付受理方设备用于交互的接口。
在一些示例中,第一目标接口可包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口,即第一目标接口可复用卡基支付系统中原有的接口,不需要重新开发或定义接口,从而避免对卡交换设备进行大的改造,进一步减少非卡账户支付方法的开发成本和维护成本。第一接口可具体为ISO8583接口,但并不限定。
第一目标接口包括该第一接口,第一支付请求的报文格式可与卡基支付中支付受理方设备向卡交换设备发送的支付请求的报文格式基本一致。具体地,支付受理方设备向卡交换设备发送的支付请求包括卡号标识和交 易信息,将支付受理方设备向卡交换设备发送的支付请求中的卡号标识更换为非卡账号标识,则可得到第一支付请求。
在另一些示例中,第一目标接口可包括新增的第二接口。具体地,第二接口可包括XML接口、JSON接口等。新增的第二接口的格式可根据场景和需求开发设定,在此并不限定。
在步骤S302中,利用第一支付请求中的非卡账号标识与非卡账户管理设备交互,使非卡账户管理设备确定与第一支付请求中的非卡账号标识对应的目标非卡账户,以使卡交换设备或非卡账户管理设备与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付。
非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。
非卡账号标识与非卡账户的对应关系用于表征非卡账户的注册账号与非卡账户的对应关系。具体地,注册账号与至少一个非卡账户具有对应关系。即一个注册账号可与一个非卡账户绑定,也可与两个以上的非卡账户绑定。在一些示例中,在注册账号与两个以上的非卡账户具有对应关系的情况下,可在与注册账号具有对应关系的两个以上的非卡账户中选取一个作为默认支付账户,利用该注册账号进行非卡账户支付时,可利用该注册账号的默认支付账户进行支付。
非卡账户与非卡账户资金管理设备的对应关系用于非卡账户管理设备对支付请求进行路由,以实现支付。
卡交换设备可将第一支付请求中的非卡账号标识发送给非卡账户管理设备,由非卡账户管理设备根据非卡账号标识与非卡账户的对应关系,确定目标非卡账户和目标非卡账户资金管理设备。
在一些示例中,非卡账户管理设备确定目标非卡账户和目标非卡账户资金管理设备后,可由非卡账户管理设备与目标非卡账户资金管理设备交互,以实现支付。非卡账户管理设备向目标非卡账户资金管理发送的信息可包括非卡账号标识和交易信息等,在此并不限定。非卡账户管理设备与目标非卡账户资金管理设备直接交互,流程更为简捷,且对卡交换设备的改造也比较小,能够进一步降低非卡账户支付的开发成本和维护成本。
在另一些示例中,非卡账户管理设备确定目标非卡账户和目标非卡账户资金管理设备后,将如目标非卡账户标识等的目标非卡账户的信息、如通信地址等目标非卡账户资金管理设备的信息等向卡交换设备发送,由卡交换设备与目标非卡账户资金管理设备交互,以实现支付。卡交换设备向目标非卡账户资金管理设备发送的信息可包括非卡账号标识和交易信息等,在此并不限定。
在上述实施例中,卡交换设备依然可处理包括卡标识和交易信息的卡支付请求。卡交换设备可根据接收到的支付请求中的内容,确定支付请求是非卡账户支付请求即第一支付请求还是卡支付请求。具体地,卡交换设备接收支付请求,从支付请求中识别卡标识。在从支付请求识别到卡标识如卡号或卡支付Token的情况下,确定该支付请求为卡支付请求,将该卡支付请求中的信息向卡账户资金管理设备发送,以实现卡基支付;在从支付请求未识别到卡标识的情况下,确定该支付请求为非卡账户支付请求即第一支付请求,将第一支付请求中的信息向非卡账户管理设备发送,由管理非卡账户的非卡账户管理设备直接与非卡账户资金管理设备交互,实现非卡账户支付,或者,由非卡账户管理设备将非卡账户的信息和非卡账户资金管理设备的信息传输至卡交换设备,由卡交换设备与非卡账户资金管理设备交互,实现非卡账户支付。
在本申请实施例中,卡交换设备通过第一支付请求从支付受理方设备获取非卡账号标识和交易信息。卡交换设备可利用非卡账号标识与用于管理非卡账户的非卡账户管理设备交互,从而确定支付所采用的非卡账户对应的非卡账户资金管理设备。卡交换设备或非卡账户管理设备可与非卡账户资金管理设备通过通信交互,实现非卡账户支付。卡交换设备属于卡基支付系统,非卡账户支付不需要单独开发、维护一个新的非卡账户支付,可通过现有的卡基支付系统中的卡交换设备和新增的非卡账户管理设备,将非卡账户接入卡基支付系统,实现非卡账户支付,降低非卡账户支付所需的开发成本和维护成本。
而且,非卡账户管理设备可与多个非卡账户资金管理设备交互,因此,目标非卡账户和目标非卡账户资金管理设备的确定可由非卡账户管理 设备进行。对于卡交换设备而言,所有未识别出卡标识的支付请求所指示的支付都可交付给非卡账户管理设备进行处理,可屏蔽非卡账户以及非卡账户资金管理设备的业务对卡交换设备的冲击,避免占用过多的卡交换设备的运行资源,避免对卡基支付业务的影响。
在目标非卡账户资金管理设备执行支付后,目标非卡账户资金管理设备可反馈支付结果。图4为本申请第一方面提供的非卡账户支付方法的另一实施例的流程图。图4与图3的不同之处在于,图4的非卡账户支付方法还可包括步骤S303和步骤S304。
在步骤S303中,接收第一支付应答。
第一支付应答包括支付结果。在一些示例中,第一支付应答可由非卡账户管理设备向卡交换设备发送。在另一些示例中,第一支付应答可由目标非卡账户资金管理设备向卡交换设备发送。
在步骤S304中,向支付受理方设备发送根据第一支付应答生成的第二支付应答。
第二支付应答根据第一支付应答生成。第二支付应答包括支付结果。向支付受理方设备发送第二支付应答,以使支付受理方设备获取支付结果。
在一些示例中,第二支付应答与第一支付应答可高度相似,这里的高度相似指第二支付应答中信息基本与第一支付应答中的信息相同,即由于第一支付应答的发送方、接收方与第二支付应答的发送方、接收方不同,第二支付应答中与第二支付应答的发送方和接收方相关的内容,与第一支付应答中与第一支付应答的发送方和接收方相关的内容不同。
例如,第一支付应答可包括支付结果、报文类型、商户标识、交易发起方标识、报文校验码等信息,第二支付应答可包括支付结果、报文类型、商户标识、交易发起方标识、报文校验码等信息;第一支付应答中的支付结果、报文类型、商户标识和交易发起方标识与第二支付应答中的支付结果、报文类型、商户标识和交易发起方标识相同;第一支付应答中的报文校验码与第一支付应答的发送方和接收方相关,第二支付应答中的报文校验码与第二支付应答的发送方和接收方相关,因此,第一支付应答中 的报文校验码与第二支付应答中的报文校验码不同。在第二支付应答与第一支付应答高度相似的情况下,步骤S304可近似实现为向支付受理方设备转发第一支付应答,进一步简化流程。
通过第一支付应答和第二支付应答,可将支付结果等信息传输至支付受理方设备,以便用户获取支付结果等信息。
在一些实施例中,可由非卡账户管理设备与目标非卡账户资金管理设备交互以实现支付。图5为本申请第一方面提供的非卡账户支付方法的又一实施例的流程图。图5与图4的不同之处在于,图4中的步骤S302可具体细化为图5中的步骤S3021,图4中的步骤S303可具体细化为图5中的步骤S3031。
在步骤S3021中,通过第二目标接口向非卡账户管理设备发送根据第一支付请求生成的第二支付请求,以使非卡账户管理设备确定目标非卡账户,与目标非卡账户资金管理设备交互,执行支付。
第二支付请求包括第一支付请求中的非卡账号标识和交易信息。第二支付请求具体可以报文形式传输。第二支付请求还可包括报文类型、报文校验码等信息中的一项或两项以上,在此并不限定。第二支付请求中的报文校验码可用于验证第二支付请求的完整性和合法性。
第二目标接口为卡交换设备与给卡账户管理设备用于交互的接口。第二目标接口与第一目标接口可为相同的接口或不同的接口,在此并不限定。
在一些示例中,第二目标接口可包括卡基支付系统中卡交换系统与支付受理方设备用于卡基交互的第一接口。为了尽量减少对卡交换设备的改造,第二目标接口可复用卡基支付系统中原有的接口,不需要开发新的接口,从而能够进一步降低非卡账户支付的开发成本和维护成本。
在第二目标接口复用卡基支付系统中的第一接口的情况下,第二支付请求与第一支付请求可高度相似。这里的高度相似指第二支付请求中信息基本与第一支付请求中的信息相同,即由于第一支付请求的发送方、接收方与第二支付请求的发送方、接收方不同,第二支付请求中与第二支付请求的发送方和接收方相关的内容,与第一支付请求中与第一支付请求的发 送方和接收方相关的内容不同。
例如,第一支付请求可包括非卡账号标识、交易信息、报文类型、报文校验码等信息,第二支付请求可包括非卡账号标识、交易信息、报文类型、报文校验码等信息;第一支付请求中的非卡账号标识、交易信息、报文类型等信息与第二支付请求中的非卡账号标识、交易信息、报文类型等信息相同;第一支付请求中的报文校验码与第一支付请求的发送方和接收方相关,第二支付请求中的报文校验码与第二支付请求的发送方和接收方相关,因此,第一支付请求中的报文校验码与第二支付请求中的报文校验码不同。在第二支付请求与第一支付请求高度相似的情况下,步骤S3021可近似实现为通过第二目标接口向非卡账户管理设备转发第一支付请求,进一步简化流程。
在另一些示例中,第二目标接口可包括新增的第三接口。具体地,第三接口可包括XML接口、JSON接口等。新增的第三接口的格式可根据场景和需求开发设定,在此并不限定。
在本申请实施例中,非卡账户管理设备通过第二目标接口接收第二支付请求,根据第二支付请求中的非卡账号标识可确定目标非卡账户,根据目标非卡账户可确定目标非卡账户资金管理设备。非卡账户管理设备可与目标非卡账户资金管理设备进一步交互,实现支付。
在步骤S3031中,接收非卡账户管理设备转发的第一支付应答。
第一支付应答是目标非卡账户资金管理设备向非卡账户管理设备发送的。在目标非卡账户资金管理设备执行支付后,目标非卡账户资金管理设备向非卡账户管理设备发送第一支付应答。非卡账户管理设备向卡交换设备转发该第一支付应答,以通知卡交换设备支付结果,以及便于卡交换设备通知支付受理方设备支付结果。
非卡账户管理设备与目标非卡账户资金管理管理设备直接交互,执行支付,减少对卡交换设备的改造,进一步降低非卡账户支付的开发成本和维护成本。而且,非卡账户管理设备与目标非卡账户资金管理管理设备直接交互,执行支付,使得流程更加简洁,非卡账户支付效率更高。
在一些实施例中,可由卡交换设备与目标非卡账户资金管理设备交互 以实现支付。图6为本申请第一方面提供的非卡账户支付方法的再一实施例的流程图。图6与图4的不同之处在于,图4中的步骤S302可具体细化为图6中的步骤S3022至步骤S3024,图4中的步骤S303可具体细化为图6中的步骤S3032。
在步骤S3022中,通过第三目标接口向非卡账户管理设备发送根据第一支付请求生成的第三支付请求,以使非卡账户管理设备确定目标非卡账户以及目标非卡账户资金管理设备。
第三支付请求包括第一支付请求中的非卡账号标识和交易信息。
第三目标接口为卡交换设备与非卡账户管理设备用于交互的接口。第三目标接口与第一目标接口可为相同的接口或不同的接口,在此并不限定。
在一些示例中,第三目标接口可包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口。为了尽量减少对卡交换设备的改造,第三目标接口可复用卡基支付系统中原有的接口,不需要开发新的接口,从而能够进一步降低非卡账户支付的开发成本和维护成本。
在第三目标接口复用卡基支付系统中的第一接口的情况下,第三支付请求与第一支付请求可高度相似。这里的高度相似指第三支付请求中信息基本与第一支付请求中的信息相同,即由于第三支付请求的发送方、接收方与第二支付请求的发送方、接收方不同,第三支付请求中与第三支付请求的发送方和接收方相关的内容,与第一支付请求中与第一支付请求的发送方和接收方相关的内容不同。
例如,第一支付请求可包括非卡账号标识、交易信息、报文类型、报文校验码等信息,第三支付请求可包括非卡账号标识、交易信息、报文类型、报文校验码等信息;第一支付请求中的非卡账号标识、交易信息、报文类型等信息与第三支付请求中的非卡账号标识、交易信息、报文类型等信息相同;第一支付请求中的报文校验码与第一支付请求的发送方和接收方相关,第三支付请求中的报文校验码与第三支付请求的发送方和接收方相关,因此,第一支付请求中的报文校验码与第三支付请求中的报文校验码不同。在第三支付请求与第一支付请求高度相似的情况下,步骤S3022 可近似实现为通过第三目标接口向非卡账户管理设备转发第一支付请求,可进一步简化流程。
在另一些示例中,第三目标接口可包括新增的第四接口。具体地,第四接口可包括XML接口、JSON接口等。新增的第四接口的格式可根据场景和需求开发设定,在此并不限定。
在步骤S3023中,接收非卡账户管理设备发送的非卡账户反馈消息。
非卡账户管理设备接收第三支付请求,根据第三支付请求中的非卡账号标识,确定目标非卡账户。根据目标非卡账户,确定目标非卡账户资金管理设备。非卡账户管理设备可向卡交换设备发送非卡账户反馈消息。非卡账户反馈消息用于指示目标非卡账户和目标非卡账户资金管理设备。在一些示例中,目标非卡账户可利用目标非卡账户的标识表征,目标非卡账户资金管理设备可利用目标非卡账户资金管理设备的通信地址表征,在此并不限定。即非卡账户反馈消息可包括目标非卡账户的标识、目标非卡账户资金管理设备的通信地址等,在此并不限定。非卡账户反馈消息还可包括报文类型、报文校验码等信息,在此并不限定。
在步骤S3024中,根据非卡账户反馈消息,通过第四目标接口向目标非卡账户资金管理设备发送第四支付请求。
也可由卡交换设备与目标非卡账户资金管理设备进行交互。卡交换设备可通过非卡账户反馈消息确定目标非卡账户以及目标非卡账户资金管理设备,从而与目标非卡账户资金管理设备交互。
第四支付请求指示目标非卡账户资金管理设备利用目标非卡账户执行支付。在一些示例中,第四支付请求可包括非卡账号标识和交易信息,也可包括其他信息,在此并不限定。
第四目标接口为卡交换设备与非卡账户资金管理设备用于交互的接口。
在一些示例中,第四目标接口可包括卡基支付系统中所卡交换设备与卡账户资金管理设备用于交互的第五接口。为了尽量减少对卡交换设备的改造,第四目标接口可复用卡基支付系统中原有的接口,不需要开发新的接口,从而能够进一步降低非卡账户支付的开发成本和维护成本。第五接 口可具体为ISO8583接口,但并不限定。
在另一些示例中,第四目标接口可包括新增的第六接口。具体地,第六接口可包括XML接口、JSON接口等。新增的第六接口的格式可根据场景和需求开发设定,在此并不限定。
在步骤S3032中,接收目标非卡账户资金管理设备发送的第一支付应答。
目标非卡账户资金管理设备接收第四支付请求,可根据第四支付请求,利用目标非卡账户执行支付。目标非卡账户资金管理设备向卡交换设备转发该第一支付应答,以通知卡交换设备支付结果,以及便于卡交换设备通知支付受理方设备支付结果。
在一些实施例中,卡交换设备还可向非卡账户管理设备发送非卡账户总清算信息,以使非卡账户管理设备根据非卡账户总清算信息,获取非卡账户各自的清算信息。
卡交换设备执行清分处理,得到非卡账户总清算信息。非卡账户总清算信息并不区分不同非卡账户的清算信息,而是将所有非卡账户看作一个整体,非卡账户总清算信息是这一个整体的清算信息。具体地,非卡账户总清算信息可包括非卡账户总的流水信息、非卡账户总的明细信息、非卡账户总的汇总报表、非卡账户总的清算参数等,在此并不限定。非卡账户总清算信息可用于非卡账户管理设备进行清分处理得到非卡账户各自的清算信息。非卡账户各自的清算信息包括非卡账户各自的流水信息、非卡账户各自的明细信息、非卡账户各自的汇总报表、非卡账户各自的清算参数等,在此并不限定。
对卡交换设备而言,不需进行非卡账户各自的清算信息,只需得到所有非卡账户总的清算信息,可屏蔽非卡账户的清分处理等对卡交换设备的冲击,从而避免影响卡基支付。
本申请第二方面提供一种非卡账户支付方法,可应用于非卡账户管理设备。非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系的具体内容 可参见上述实施例中的相关说明,在此不再赘述。图7为本申请第二方面提供的非卡账户支付方法的一实施例的流程图。如图7所示,非卡账户支付方法可包括步骤S401、步骤S402和步骤S403,或者,包括步骤S401、步骤S402和步骤S404。
在步骤S401中,与卡交换设备利用卡交换设备接收到的第一支付请求中的非卡账号标识进行交互。
第一支付请求由支付受理方设备通过第一目标接口向卡交换设备发送。第一支付请求包括非卡账号标识和交易信息。卡交换设备属于卡基支付系统。
在一些示例中,非卡账号标识可包括注册账号或注册账号的令牌Token。注册账号与至少一个非卡账户具有对应关系。
第一支付请求、非卡账号标识、交易信息和卡交换设备的具体内容可参见上述实施例中的相关说明,在此不再赘述。
在步骤S402中,根据第一支付请求中的非卡账号标识,确定与第一支付请求中的非卡账号标识对应的目标非卡账户。
非卡账户管理设备可根据存储的非卡账号标识与非卡账户的对应关系,确定与第一支付请求中的非卡账号标识对应的目标非卡账户。
在步骤S403中,与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付。
非卡账户管理设备根据存储非卡账户与非卡账户资金管理设备的对应关系,确定目标非卡账户资金管理设备。非卡账户管理设备可直接与目标非卡账户资金管理设备交互,执行支付。例如,非卡账户管理设备可向目标非卡账户资金管理设备发送非卡账号标识和交易信息,以使目标非卡账户资金管理设备采用目标非卡账户进行支付。
非卡账户管理设备与目标非卡账户资金管理设备直接交互,流程更为简捷,且对卡交换设备的改造也比较小,能够进一步降低非卡账户支付的开发成本和维护成本。
在步骤S404中,与卡交换设备交互,以使卡交换设备与目标非卡账户资金管理设备交互,执行支付。
非卡账户管理设备根据存储非卡账户与非卡账户资金管理设备的对应关系,确定目标非卡账户资金管理设备。非卡账户管理设备可通知卡交换设备目标非卡账户资金管理设备,以使卡交换设备向目标非卡账户资金管理设备发送非卡账号标识和交易信息,使得目标非卡账户资金管理设备采用目标非卡账户进行支付。
在本申请实施例中,非卡账户管理设备与卡交换设备可利用从支付受理方设备接收到的第一支付请求中非卡账号标识进行交互。根据第一支付请求中非卡账号标识确定支付所采用的非卡账户对应的目标非卡账户资金管理设备。非卡账户管理设备可直接与目标非卡账户资金管理设备通过交互进行支付,或者,非卡账户管理设备与卡交换设备交互,使卡交换设备与目标非卡账户资金管理设备通过交互进行支付。卡交换设备属于卡基支付系统,非卡账户支付不需要单独开发、维护一个新的非卡账户支付,可通过现有的卡基支付系统中的卡交换设备和新增的非卡账户管理设备,将非卡账户接入卡基支付系统,实现非卡账户支付,降低非卡账户支付所需的开发成本和维护成本。
而且,非卡账户管理设备可与多个非卡账户资金管理设备交互,因此,目标非卡账户和目标非卡账户资金管理设备的确定可由非卡账户管理设备进行。对于卡交换设备而言,所有未识别出卡标识的支付请求所指示的支付都可交付给非卡账户管理设备进行处理,非卡账户管理设备的设置可屏蔽非卡账户以及非卡账户资金管理设备的业务对卡交换设备的冲击,避免占用过多的卡交换设备的运行资源,避免对卡基支付业务的影响。
在本申请实施例中,可由非卡账户管理设备与目标非卡账户资金管理设备交互以实现支付,也可由卡交换设备与目标非卡账户资金管理设备交互以实现支付。图8为本申请第二方面提供的非卡账户支付方法的另一实施例的流程图。图8与图7的不同之处在于,图7所示的步骤S402可具体细化为图8所示的步骤S4021,或者细化为图8所示的步骤S4022和步骤S4023;图7所示的步骤S403可具体细化为图8所示的步骤S4031;图8所示的非卡账户支付方法还可包括步骤S405和步骤S406;图7所示的步骤S404可具体细化为图8所示的步骤S4041。
在步骤S4021中,通过第二目标接口接收卡交换设备发送的根据第一支付请求生成的第二支付请求。
第二支付请求包括第一支付请求中的非卡账号标识和交易信息。第二支付请求的具体内容可参见上述实施例中的相关说明,在此不再赘述。
在一些示例中,第二目标接口包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口。
在另一些示例中,第二目标接口包括新增的第三接口。
第二目标接口、第一接口、第三接口等具体内容可参见上述实施例中的相关说明,在此不再赘述。
在步骤S4031中,通过第五目标接口向目标非卡账户资金管理设备发送根据第二支付请求生成的第五支付请求。
第五支付请求指示目标非卡账户资金管理设备利用目标非卡账户执行支付。非卡账户管理设备通过第五支付请求与目标非卡账户资金管理设备进行交互。在一些示例中,第五支付请求可包括第一支付请求中的非卡账号标识和交易信息。第五支付请求具体可以报文形式传输。第五支付请求还可包括报文类型、报文校验码等信息中的一项或两项以上,在此并不限定。第五支付请求中的报文校验码可用于验证第五支付请求的完整性和合法性。
第五目标接口为非卡账户管理设备与目标非卡账户资金管理设备用于交互的接口。
在一些示例中,第五目标接口可包括卡基支付系统中卡交换设备与卡账户资金管理设备用于交互的第五接口。为了尽量减少非卡账户支付中新开发的部分,第五目标接口可复用卡基支付系统中原有的接口,不需要开发新的接口,从而能够进一步降低非卡账户支付的开发成本和维护成本。
在第五目标接口复用卡基支付系统中的第五接口的情况下,第五支付请求与第二支付请求可高度相似。这里的高度相似指第五支付请求中信息基本与第二支付请求中的信息相同,即由于第二支付请求的发送方、接收方与第五支付请求的发送方、接收方不同,第五支付请求中与第五支付请求的发送方和接收方相关的内容,与第二支付请求中与第二支付请求的发 送方和接收方相关的内容不同。
例如,第二支付请求可包括非卡账号标识、交易信息、报文类型、报文校验码等信息,第五支付请求可包括非卡账号标识、交易信息、报文类型、报文校验码等信息;第二支付请求中的非卡账号标识、交易信息、报文类型等信息与第五支付请求中的非卡账号标识、交易信息、报文类型等信息相同;第二支付请求中的报文校验码与第二支付请求的发送方和接收方相关,第五支付请求中的报文校验码与第五支付请求的发送方和接收方相关,因此,第二支付请求中的报文校验码与第五支付请求中的报文校验码不同。在第五支付请求与第二支付请求高度相似的情况下,步骤S4031可近似实现为通过第五目标接口向非卡账户资金管理设备转发第二支付请求,可进一步简化流程。
在另一些示例中,第五目标接口可包括新增的第七接口。具体地,第七接口可包括XML接口、JSON接口等。新增的第七接口的格式可根据场景和需求开发设定,在此并不限定。
在步骤S405中,接收目标非卡账户资金管理设备发送的第一支付应答。
第一支付应答包括支付结果。第一支付应答的具体内容可参见上述实施例中的相关说明,在此不再赘述。
在步骤S406中,向卡交换设备转发第一支付应答。
非卡账户管理设备向卡交换设备转发第一支付应答,以通知卡交换设备该支付结果。
在步骤S4022中,通过第三目标接口接收卡交换设备发送的根据第一支付请求生成的第三支付请求。
第三支付请求包括第一支付请求中的非卡账号标识和交易信息。
在一些示例中,第三目标接口可包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口。
在另一些示例中,第三目标接口可包括新增的第四接口。
第三支付请求、第三目标接口、第一接口、第四接口的具体内容可参见上述实施例中的相关说明,在此不再赘述。
在步骤S4023中,根据第三支付请求,生成非卡账户反馈消息。
非卡账户管理设备接收第三支付请求,根据第三支付请求中的非卡账号标识,确定目标非卡账户。根据目标非卡账户,确定目标非卡账户资金管理设备。非卡账户管理设备可向卡交换设备发送非卡账户反馈消息。非卡账户反馈消息用于指示目标非卡账户和目标非卡账户资金管理设备。
非卡账户反馈消息的具体内容可参见上述实施例中的相关说明,在此不再赘述。
在步骤S4041中,向卡交换设备发送非卡账户反馈消息,以使卡交换设备通过第四目标接口向目标非卡账户资金管理设备发送第四支付请求。
第四支付请求指示目标非卡账户资金管理设备利用目标非卡账户执行支付。
卡交换设备向目标非卡账户资金管理设备发送第四支付请求的具体内容可参见上述实施例中的相关说明,在此不再赘述。
在一些实施例中,在卡交换设备进行清分处理后,非卡账户管理设备可进行二次清分处理,以得到非卡账户各自的清算信息。具体地,非卡账户管理设备接收卡交换设备发送的非卡账户总清算信息。非卡账户管理设备根据非卡账户总清算信息,获取非卡账户各自的清算信息。
非卡账户总清算信息、非卡账户各自的清算信息的具体内容可参见上述实施例中的相关说明,在此不再赘述。
对于卡交换设备而言,所有非卡账户均视为同一账户,不会增加卡交换设备的额外清分处理。在卡交换设备进行清分处理的情况下,非卡账户管理设备再进行二次清分,以得到非卡账户各自的清算信息。可屏蔽非卡账户的清分处理等对卡交换设备的冲击,从而避免影响卡基支付。
在一些实施例中,非卡账户管理设备还可接收注册指令,注册指令可包括注册账号、非卡账户的标识、非卡账户对应的非卡账户资金管理设备的标识等。非卡账户管理设备可为注册账号分配非卡账号标识,建立并存储非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。
非卡账户管理设备还可接收默认非卡账户设置,从而设置注册账号锁 对应的默认非卡账户。默认非卡账户用于进行该注册账号关联的支付。
非卡账户管理设备还可存储注册账号密码、非卡账户支付接口标识、支付权限等信息,在此并不限定。
非卡账户管理设备除了上述非卡账户的注册以外,还可提供非卡账户的验证、查询、注销等功能。
例如,非卡账户管理设备在进行非卡账户的注册过程中,可与非卡账户对应的非卡账户资金管理设备对非卡账户的注册账号进行验证,以防止冒用他人信息进行注册。如对非卡账户的姓名、地址、证件号、有效期、非卡账户密码等预留信息进行验证。验证规则可根据场景和需求设定,在此并不限定。验证通过后,该注册账号可被使用进行支付。
非卡账户管理设备还可在支付过程中,查询资金接收方的注册账号,从而查询该注册账号对应的非卡账户的姓名、地址、证件号、有效期、非卡账户密码等预留信息,以确定资金接收方。
非卡账户管理设备还可接收注销指令,根据该注销指令,注销该注销指令指示的注册账号,并向被注销的注册账号对应的非卡账户资金管理设备发起注销通知,以通知非卡账户资金管理设备该注册账号下的非卡账户已注销。
为了便于说明,下面以由非卡账户管理设备与目标非卡账户资金管理进行交互以完成非卡账户支付和由卡交换设备与目标非卡账户资金管理进行交互以完成非卡账户支付为例分别进行说明。
在一些示例中,由非卡账户管理设备与目标非卡账户资金管理进行交互以完成非卡账户支付。图9为本申请实施例中非卡账号支付流程的一示例的流程图。如图9所示,该非卡账号支付流程可包括步骤S501至步骤S508。
在步骤S501中,支付受理方设备向卡交换设备发送第一支付请求。
在步骤S502中,卡交换设备向非卡账户管理设备发送第二支付请求。
在步骤S503中,非卡账户管理设备根据非卡账号标识,确定目标非卡账户和目标非卡账户资金管理设备。
在步骤S504中,非卡账户管理设备向目标非卡账户资金管理设备发送第五支付请求。
在步骤S505中,目标非卡账户资金管理设备根据第五支付请求,利用目标非卡账户进行支付。
在步骤S506中,目标非卡账户资金管理设备向非卡账户管理设备发送第一支付应答。
在步骤S507中,非卡账户管理设备向卡交换设备发送第一支付应答。
在步骤S508中,卡交换设备向支付受理方设备发送第二支付应答。
上述步骤S501至步骤S508的具体内容可参见上述实施例中的相关部分,在此并不限定。
在另一些示例中,由卡交换设备与目标非卡账户资金管理进行交互以完成非卡账户支付。图10为本申请实施例中非卡账号支付流程的另一示例的流程图。如图10所示,该非卡账号支付流程可包括步骤S601至步骤S6
在步骤S601中,支付受理方设备向卡交换设备发送第一支付请求。
在步骤S602中,卡交换设备向非卡账户管理设备发送第三支付请求。
在步骤S603中,非卡账户管理设备根据非卡账号标识,确定目标非卡账户和目标非卡账户资金管理设备。
在步骤S604中,非卡账户管理设备向卡交换设备发送非卡账户反馈消息。
在步骤S605中,卡交换设备向目标非卡账户资金管理设备发送第四支付请求。
在步骤S606中,目标非卡账户资金管理设备根据第四支付请求,利用目标非卡账户进行支付。
在步骤S607中,目标非卡账户资金管理设备向卡交换设备发送第一支付应答。
在步骤S608中,卡交换设备根据第一支付应答和第一支付请求,确 定支付受理方设备。
在步骤S609中,卡交换设备向支付受理方设备发送第二支付应答。
上述步骤S601至步骤S609的具体内容可参见上述实施例中的相关说明,在此不再赘述。
本申请第三方面提供一种卡交换设备,该卡交换设备属于卡基支付系统。图11为本申请第三方面提供的卡交换设备的一实施例的结构示意图。如图11所示,该卡交换设备700包括交互模块701。该交互模块701可包括接收单元7011。
接收单元7011可用于通过第一目标接口接收支付受理方设备发送的第一支付请求。
第一支付请求包括非卡账号标识和交易信息。非卡账号标识用于标识非卡账户的注册账号。
在一些示例中,非卡账号标识包括注册账号或注册账号的令牌Token。注册账号与至少一个非卡账户具有对应关系。
在一些示例中,第一目标接口包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口。
在另一些示例中,第一目标接口包括新增的第二接口。
交互模块701可用于利用第一支付请求中的非卡账号标识与非卡账户管理设备交互,使非卡账户管理设备确定与第一支付请求中的非卡账号标识对应的目标非卡账户,以使卡交换设备或非卡账户管理设备与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付。
非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。
在本申请实施例中,卡交换设备通过第一支付请求从支付受理方设备获取非卡账号标识和交易信息。卡交换设备可利用非卡账号标识与用于管理非卡账户的非卡账户管理设备交互,从而确定支付所采用的非卡账户对应的非卡账户资金管理设备。卡交换设备或非卡账户管理设备可与非卡账户资金管理设备通过通信交互,实现非卡账户支付。卡交换设备属于卡基支付系统,非卡账户支付不需要单独开发、维护一个新的非卡账户支付, 可通过现有的卡基支付系统中的卡交换设备和新增的非卡账户管理设备,将非卡账户接入卡基支付系统,实现非卡账户支付,降低非卡账户支付所需的开发成本和维护成本。
而且,非卡账户管理设备可与多个非卡账户资金管理设备交互,因此,目标非卡账户和目标非卡账户资金管理设备的确定可由非卡账户管理设备进行。对于卡交换设备而言,所有未识别出卡标识的支付请求所指示的支付都可交付给非卡账户管理设备进行处理,可屏蔽非卡账户以及非卡账户资金管理设备的业务对卡交换设备的冲击,避免占用过多的卡交换设备的运行资源,避免对卡基支付业务的影响。
在一些示例中,上述接收单元7011还可用于通过第一目标接口接收支付受理方设备发送的支付请求;在从支付请求中未识别到卡标识的情况下,确认支付请求为第一支付请求。
上述实施例中的交互模块701还具有发送功能。图12为本申请第三方面提供的卡交换设备的另一实施例的结构示意图。图12与图11的不同之处在于,图12所示的交互模块701还可包括发送单元7012。
在一些示例中,发送单元7012可用于通过第二目标接口向非卡账户管理设备发送根据第一支付请求生成的第二支付请求,以使非卡账户管理设备确定目标非卡账户,与目标非卡账户资金管理设备交互,执行支付。
第二支付请求包括第一支付请求中的非卡账号标识和交易信息。
具体地,第二目标接口可包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口。或者,第二目标接口可包括新增的第三接口。
在另一些示例中,发送单元7012可用于通过第三目标接口向非卡账户管理设备发送根据第一支付请求生成的第三支付请求,以使非卡账户管理设备确定目标非卡账户以及目标非卡账户资金管理设备。
第三支付请求包括第一支付请求中的非卡账号标识和交易信息。
具体地,第三目标接口可包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口。或者,第三目标接口可包括新增的第四接口。
接收单元7011还可用于接收非卡账户管理设备发送的非卡账户反馈消息。
非卡账户反馈消息用于指示目标非卡账户和目标非卡账户资金管理设备。
发送单元7012还可用于根据非卡账户反馈消息,通过第四目标接口向目标非卡账户资金管理设备发送第四支付请求。
第四支付请求指示目标非卡账户资金管理设备利用目标非卡账户执行支付。
具体地,第四目标接口可包括卡基支付系统中卡交换设备与卡账户资金管理设备用于交互的第五接口。第四目标接口可包括新增的第六接口。
在一些实施例中,接收单元7011还可用于接收第一支付应答。
第一支付应答包括支付结果。
发送单元7012还可用于向支付受理方设备发送根据第一支付应答生成的第二支付应答。
第二支付应答包括支付结果。
在一些示例中,接收单元7011还可用于接收第一支付应答。
第一支付应答包括支付结果。
发送单元7012还可用于向支付受理方设备发送根据第一支付应答生成的第二支付应答。
第二支付应答包括支付结果。
具体地,在一些示例中,接收单元7011还可用于接收非卡账户管理设备转发的第一支付应答。
第一支付应答是目标非卡账户资金管理设备向非卡账户管理设备发送的。
在另一些示例中,接收单元7011还可用于接收目标非卡账户资金管理设备发送的第一支付应答。
在一些实施例中,发送单元7012还可用于向非卡账户管理设备发送非卡账户总清算信息,以使非卡账户管理设备根据非卡账户总清算信息,获取非卡账户各自的清算信息。
本申请第四方面提供一种非卡账户管理设备,非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。图13为本申请第四方面提供的非卡账户管理设备的一实施例的结构示意图。如图13所示,非卡账户管理设备800可包括交互模块801和处理模块802。
交互模块801可用于与卡交换设备利用卡交换设备接收到的第一支付请求中的非卡账号标识进行交互。
第一支付请求由支付受理方设备通过第一目标接口向卡交换设备发送。第一支付请求包括非卡账号标识和交易信息。卡交换设备属于卡基支付系统。
在一些示例中,非卡账号标识包括注册账号或注册账号的令牌Token。注册账号与至少一个非卡账户具有对应关系。
处理模块802可用于根据第一支付请求中的非卡账号标识,确定与第一支付请求中的非卡账号标识对应的目标非卡账户。
交互模块801还用于与目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付;或者,与卡交换设备交互,以使卡交换设备与目标非卡账户资金管理设备交互,执行支付。
在本申请实施例中,非卡账户管理设备与卡交换设备可利用从支付受理方设备接收到的第一支付请求中非卡账号标识进行交互。根据第一支付请求中非卡账号标识确定支付所采用的非卡账户对应的目标非卡账户资金管理设备。非卡账户管理设备可直接与目标非卡账户资金管理设备通过交互进行支付,或者,非卡账户管理设备与卡交换设备交互,使卡交换设备与目标非卡账户资金管理设备通过交互进行支付。卡交换设备属于卡基支付系统,非卡账户支付不需要单独开发、维护一个新的非卡账户支付,可通过现有的卡基支付系统中的卡交换设备和新增的非卡账户管理设备,将非卡账户接入卡基支付系统,实现非卡账户支付,降低非卡账户支付所需的开发成本和维护成本。
而且,非卡账户管理设备可与多个非卡账户资金管理设备交互,因此,目标非卡账户和目标非卡账户资金管理设备的确定可由非卡账户管理 设备进行。对于卡交换设备而言,所有未识别出卡标识的支付请求所指示的支付都可交付给非卡账户管理设备进行处理,非卡账户管理设备的设置可屏蔽非卡账户以及非卡账户资金管理设备的业务对卡交换设备的冲击,避免占用过多的卡交换设备的运行资源,避免对卡基支付业务的影响。
上述实施例中的交互模块801具有接收功能和发送功能。图14为本申请第四方面提供的非卡账户管理设备的另一实施例的结构示意图。图14与图13的不同之处在于,交互模块801可包括接收单元8011和发送单元8012。
在一些示例中,接收单元8011可用于通过第二目标接口接收卡交换设备发送的根据第一支付请求生成的第二支付请求。
第二支付请求包括第一支付请求中的非卡账号标识和交易信息。
具体地,第二目标接口可包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口。或者,第二目标接口可包括新增的第三接口。
发送单元8012可用于通过第五目标接口向目标非卡账户资金管理设备发送根据第二支付请求生成的第五支付请求。
第五支付请求指示目标非卡账户资金管理设备利用目标非卡账户执行支付。
具体地,第五目标接口可包括卡基支付系统中卡交换设备与卡账户资金管理设备用于交互的第五接口。或者,第五目标接口可包括新增的第七接口。
图15为本申请第四方面提供的非卡账户管理设备的又一实施例的结构示意图。图15与图13的不同之处在于,交互模块801可包括接收单元8011、发送单元8012和生成单元8013。
接收单元8011可用于通过第三目标接口接收卡交换设备发送的根据第一支付请求生成的第三支付请求。
第三支付请求包括第一支付请求中的非卡账号标识和交易信息。
具体地,第三目标接口可包括卡基支付系统中卡交换设备与支付受理方设备用于卡基交互的第一接口。或者,第三目标接口可包括新增的第四 接口。
生成单元8013可用于根据第三支付请求,生成非卡账户反馈消息。
非卡账户反馈消息用于指示目标非卡账户和目标非卡账户资金管理设备。
发送单元8012可用于向卡交换设备发送非卡账户反馈消息,以使卡交换设备通过第四目标接口向目标非卡账户资金管理设备发送第四支付请求。
第四支付请求指示目标非卡账户资金管理设备利用目标非卡账户执行支付。
在一些实施例中,接收单元8011还可用于接收目标非卡账户资金管理设备发送的第一支付应答,第一支付应答包括支付结果。
发送单元8012还可用于向卡交换设备转发第一支付应答。
在一些实施例中,非卡账户管理设备800还可进行非卡账户内部的清分处理。图16为本申请第四方面提供的非卡账户管理设备的再一实施例的结构示意图。图16与图14的不同之处在于,非卡账户管理设备800还可包括清分模块803。
接收单元8011还可用于接收卡交换设备发送的非卡账户总清算信息。
清分模块803可用于根据非卡账户总清算信息,获取非卡账户各自的清算信息。
本申请第五方面还提供了一种卡交换设备。图17为本申请第五方面提供的卡交换设备的一实施例的结构示意图。如图17所示,卡交换设备900包括存储器901、处理器902及存储在存储器901上并可在处理器902上运行的计算机程序。
在一个示例中,上述处理器902可以包括中央处理器(CPU),或者特定集成电路(Application Specific Integrated Circuit,ASIC),或者可以被配置成实施本申请实施例的一个或多个集成电路。
存储器901可包括只读存储器(Read-Only Memory,ROM),随机存取存储器(Random Access Memory,RAM),磁盘存储介质设备,光存 储介质设备,闪存设备,电气、光学或其他物理/有形的存储器存储设备。因此,通常,存储器包括一个或多个编码有包括计算机可执行指令的软件的有形(非暂态)计算机可读存储介质(例如,存储器设备),并且当该软件被执行(例如,由一个或多个处理器)时,其可操作来执行参考根据本申请第一方面中非卡账户支付方法所描述的操作。
处理器902通过读取存储器901中存储的可执行程序代码来运行与可执行程序代码对应的计算机程序,以用于实现上述实施例中应用于卡交换设备的非卡账户支付方法。
在一个示例中,卡交换设备900还可包括通信接口903和总线904。其中,如图17所示,存储器901、处理器902、通信接口903通过总线904连接并完成相互间的通信。
通信接口903,主要用于实现本申请实施例中各模块、装置、单元和/或设备之间的通信。也可通过通信接口903接入输入设备和/或输出设备。
总线904包括硬件、软件或两者,将卡交换设备900的部件彼此耦接在一起。举例来说而非限制,总线904可包括加速图形端口(Accelerated Graphics Port,AGP)或其他图形总线、增强工业标准架构(Enhanced Industry Standard Architecture,EISA)总线、前端总线(Front Side Bus,FSB)、超传输(HyperTransport,HT)互连、工业标准架构(Industry Standard Architecture,ISA)总线、无限带宽互连、低引脚数(Low pin count,LPC)总线、存储器总线、微信道架构(MicroChannel Architecture,MCA)总线、外围组件互连(Peripheral Component Interconnect,PCI)总线、PCI-Express(PCI-E)总线、串行高级技术附件(Serial Advanced Technology Attachment,SATA)总线、视频电子标准协会局部(Video Electronics Standards Association Local Bus,VLB)总线或其他合适的总线或者两个或更多个以上这些的组合。在合适的情况下,总线904可包括一个或多个总线。尽管本申请实施例描述和示出了特定的总线,但本申请考虑任何合适的总线或互连。
本申请第六方面还提供了一种非卡账户管理设备。图18为本申请第六方面提供的非卡账户管理设备的一实施例的结构示意图。如图18所 示,非卡账户管理1000包括存储器1001、处理器1002及存储在存储器1001上并可在处理器1002上运行的计算机程序。
在一个示例中,上述处理器1002可以包括中央处理器(CPU),或者特定集成电路(Application Specific Integrated Circuit,ASIC),或者可以被配置成实施本申请实施例的一个或多个集成电路。
存储器1001可包括只读存储器(Read-Only Memory,ROM),随机存取存储器(Random Access Memory,RAM),磁盘存储介质设备,光存储介质设备,闪存设备,电气、光学或其他物理/有形的存储器存储设备。因此,通常,存储器包括一个或多个编码有包括计算机可执行指令的软件的有形(非暂态)计算机可读存储介质(例如,存储器设备),并且当该软件被执行(例如,由一个或多个处理器)时,其可操作来执行参考根据本申请第二方面中非卡账户支付方法所描述的操作。
处理器1002通过读取存储器1001中存储的可执行程序代码来运行与可执行程序代码对应的计算机程序,以用于实现上述实施例中应用于非卡账户管理设备的非卡账户支付方法。
在一个示例中,非卡账户管理设备1000还可包括通信接口1003和总线1004。其中,如图18所示,存储器1001、处理器1002、通信接口1003通过总线1004连接并完成相互间的通信。
通信接口1003,主要用于实现本申请实施例中各模块、装置、单元和/或设备之间的通信。也可通过通信接口1003接入输入设备和/或输出设备。
总线1004包括硬件、软件或两者,将非卡账户管理设备1000的部件彼此耦接在一起。举例来说而非限制,总线1004可包括加速图形端口(Accelerated Graphics Port,AGP)或其他图形总线、增强工业标准架构(Enhanced Industry Standard Architecture,EISA)总线、前端总线(Front Side Bus,FSB)、超传输(HyperTransport,HT)互连、工业标准架构(Industry Standard Architecture,ISA)总线、无限带宽互连、低引脚数(Low pin count,LPC)总线、存储器总线、微信道架构(MicroChannel Architecture,MCA)总线、外围组件互连(Peripheral Component Interconnect,PCI)总线、PCI-Express(PCI-E)总线、串行高级技术附件(Serial Advanced Technology Attachment,SATA)总线、视频电子标准协会局部(Video Electronics Standards Association Local Bus,VLB)总线或其他合适的总线或者两个或更多个以上这些的组合。在合适的情况下,总线1004可包括一个或多个总线。尽管本申请实施例描述和示出了特定的总线,但本申请考虑任何合适的总线或互连。
本申请第七方面提供一种非卡账户支付系统。该非卡账户支付系统可包括上述实施例中的卡交换设备和非卡账户管理系统。卡交换设备和非卡账户管理系统的具体内容可参见上述实施例中的相关说明,在此不再赘述。
在一些示例中,该非卡账户支付系统还可包括支付受理方设备和非卡账户资金管理设备。支付受理方设备和非卡账户资金管理设备的具体内容可参见上述实施例中的相关说明,在此不再赘述。
本申请第八方面还提供一种计算机可读存储介质,该计算机可读存储介质上存储有计算机程序指令,该计算机程序指令被处理器执行时可实现上述实施例中应用于卡交换设备的非卡账户支付方法,且能达到相同的技术效果,为避免重复,这里不再赘述。其中,上述计算机可读存储介质可包括非暂态计算机可读存储介质,如只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等,在此并不限定。
本申请第九方面还提供一种计算机可读存储介质,该计算机可读存储介质上存储有计算机程序指令,该计算机程序指令被处理器执行时可实现上述实施例中应用于非卡账户管理设备的非卡账户支付方法,且能达到相同的技术效果,为避免重复,这里不再赘述。其中,上述计算机可读存储介质可包括非暂态计算机可读存储介质,如只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等,在此并不限定。
需要明确的是,本说明书中的各个实施例均采用递进的方式描述,各个实施例之间相同或相似的部分互相参见即可,每个实施例重点说明的都 是与其他实施例的不同之处。对于设备实施例、系统实施例、计算机可读存储介质实施例而言,相关之处可以参见方法实施例的说明部分。本申请并不局限于上文所描述并在图中示出的特定步骤和结构。本领域的技术人员可以在领会本申请的精神之后,作出各种改变、修改和添加,或者改变步骤之间的顺序。并且,为了简明起见,这里省略对已知方法技术的详细描述。
上面参考根据本申请的实施例的方法、装置(系统)和计算机程序产品的流程图和/或框图描述了本申请的各方面。应当理解,流程图和/或框图中的每个方框以及流程图和/或框图中各方框的组合可以由计算机程序指令实现。这些计算机程序指令可被提供给通用计算机、专用计算机、或其它可编程数据处理装置的处理器,以产生一种机器,使得经由计算机或其它可编程数据处理装置的处理器执行的这些指令使能对流程图和/或框图的一个或多个方框中指定的功能/动作的实现。这种处理器可以是但不限于是通用处理器、专用处理器、特殊应用处理器或者现场可编程逻辑电路。还可理解,框图和/或流程图中的每个方框以及框图和/或流程图中的方框的组合,也可以由执行指定的功能或动作的专用硬件来实现,或可由专用硬件和计算机指令的组合来实现。
本领域技术人员应能理解,上述实施例均是示例性而非限制性的。在不同实施例中出现的不同技术特征可以进行组合,以取得有益效果。本领域技术人员在研究附图、说明书及权利要求书的基础上,应能理解并实现所揭示的实施例的其他变化的实施例。在权利要求书中,术语“包括”并不排除其他装置或步骤;数量词“一个”不排除多个;术语“第一”、“第二”用于标示名称而非用于表示任何特定的顺序。权利要求中的任何附图标记均不应被理解为对保护范围的限制。权利要求中出现的多个部分的功能可以由一个单独的硬件或软件模块来实现。某些技术特征出现在不同的从属权利要求中并不意味着不能将这些技术特征进行组合以取得有益效果。
Claims (26)
- 一种非卡账户支付方法,应用于卡交换设备,所述卡交换设备属于卡基支付系统,所述方法包括:通过第一目标接口接收支付受理方设备发送的第一支付请求,所述第一支付请求包括非卡账号标识和交易信息,所述非卡账号标识用于标识非卡账户的注册账号;利用所述第一支付请求中的所述非卡账号标识与非卡账户管理设备交互,使所述非卡账户管理设备确定与所述第一支付请求中的所述非卡账号标识对应的目标非卡账户,以使所述卡交换设备或所述非卡账户管理设备与所述目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付,所述非卡账户管理设备存储有所述非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。
- 根据权利要求1所述的方法,其中,所述通过第一目标接口接收支付受理方设备发送的第一支付请求,包括:通过所述第一目标接口接收支付受理方设备发送的支付请求;在从所述支付请求中未识别到卡标识的情况下,确认所述支付请求为所述第一支付请求。
- 根据权利要求1所述的方法,其中,所述利用所述第一支付请求中的所述非卡账号标识与非卡账户管理设备交互,包括:通过第二目标接口向所述非卡账户管理设备发送根据所述第一支付请求生成的第二支付请求,以使所述非卡账户管理设备确定所述目标非卡账户,与所述目标非卡账户资金管理设备交互,执行支付,所述第二支付请求包括所述第一支付请求中的所述非卡账号标识和所述交易信息。
- 根据权利要求1所述的方法,其中,所述利用所述第一支付请求中的所述非卡账号标识与非卡账户管理设备交互,包括:通过第三目标接口向所述非卡账户管理设备发送根据所述第一支付请求生成的第三支付请求,以使所述非卡账户管理设备确定所述目标非卡账户以及所述目标非卡账户资金管理设备,所述第三支付请求包括所述第一 支付请求中的所述非卡账号标识和所述交易信息;接收所述非卡账户管理设备发送的非卡账户反馈消息,所述非卡账户反馈消息用于指示所述目标非卡账户和所述目标非卡账户资金管理设备;根据所述非卡账户反馈消息,通过第四目标接口向所述目标非卡账户资金管理设备发送第四支付请求,所述第四支付请求指示所述目标非卡账户资金管理设备利用所述目标非卡账户执行支付。
- 根据权利要求1所述的方法,还包括:接收第一支付应答,所述第一支付应答包括支付结果;向所述支付受理方设备发送根据所述第一支付应答生成的第二支付应答,所述第二支付应答包括所述支付结果。
- 根据权利要求5所述的方法,其中,所述接收第一支付应答,包括:接收所述非卡账户管理设备转发的所述第一支付应答,所述第一支付应答是所述目标非卡账户资金管理设备向所述非卡账户管理设备发送的;或者,接收所述目标非卡账户资金管理设备发送的所述第一支付应答。
- 根据权利要求1所述的方法,其中,所述非卡账号标识包括所述注册账号或所述注册账号的令牌Token;所述注册账号与至少一个非卡账户具有对应关系。
- 根据权利要求1所述的方法,其中,所述第一目标接口包括:所述卡基支付系统中所述卡交换设备与支付受理方设备用于卡基交互的第一接口;或者,新增的第二接口。
- 根据权利要求3所述的方法,其中,所述第二目标接口包括:所述卡基支付系统中所述卡交换设备与支付受理方设备用于卡基交互的第一接口;或者,新增的第三接口。
- 根据权利要求4所述的方法,其中,所述第三目标接口包括:所述卡基支付系统中所述卡交换设备与支付受理方设备用于卡基交互的第一接口;或者,新增的第四接口;所述第四目标接口包括:所述卡基支付系统中所述卡交换设备与卡账户资金管理设备用于交互的第五接口;或者,新增的第六接口。
- 根据权利要求1所述的方法,还包括:向所述非卡账户管理设备发送非卡账户总清算信息,以使所述非卡账户管理设备根据所述非卡账户总清算信息,获取所述非卡账户各自的清算信息。
- 一种非卡账户支付方法,应用于非卡账户管理设备,所述非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系,所述方法包括:与卡交换设备利用所述卡交换设备接收到的第一支付请求中的非卡账号标识进行交互,所述第一支付请求由支付受理方设备通过第一目标接口向所述卡交换设备发送,包括所述非卡账号标识和交易信息,所述卡交换设备属于卡基支付系统;根据所述第一支付请求中的所述非卡账号标识,确定与所述第一支付请求中的所述非卡账号标识对应的目标非卡账户;与所述目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付;或者,与所述卡交换设备交互,以使所述卡交换设备与所述目标非卡账户资金管理设备交互,执行支付。
- 根据权利要求12所述的方法,其中,所述与卡交换设备利用所述卡交换设备接收到的第一支付请求中的非卡账号标识进行交互,包括:通过第二目标接口接收所述卡交换设备发送的根据所述第一支付请求生成的第二支付请求,所述第二支付请求包括所述第一支付请求中的所述非卡账号标识和所述交易信息;所述与所述目标非卡账户对应的目标非卡账户资金管理设备交互,执 行支付,包括:通过第五目标接口向所述目标非卡账户资金管理设备发送根据所述第二支付请求生成的第五支付请求,所述第五支付请求指示所述目标非卡账户资金管理设备利用所述目标非卡账户执行支付。
- 根据权利要求12所述的方法,其中,所述与卡交换设备利用所述卡交换设备接收到的第一支付请求中的非卡账号标识进行交互,包括:通过第三目标接口接收所述卡交换设备发送的根据所述第一支付请求生成的第三支付请求,所述第三支付请求包括所述第一支付请求中的所述非卡账号标识和所述交易信息;根据所述第三支付请求,生成非卡账户反馈消息,所述非卡账户反馈消息用于指示所述目标非卡账户和所述目标非卡账户资金管理设备;所述与所述卡交换设备交互,以使所述卡交换设备与所述目标非卡账户资金管理设备交互,执行支付,包括:向所述卡交换设备发送所述非卡账户反馈消息,以使所述卡交换设备通过第四目标接口向所述目标非卡账户资金管理设备发送第四支付请求,所述第四支付请求指示所述目标非卡账户资金管理设备利用所述目标非卡账户执行支付。
- 根据权利要求12所述的方法,还包括:接收所述目标非卡账户资金管理设备发送的第一支付应答,所述第一支付应答包括支付结果;向所述卡交换设备转发所述第一支付应答。
- 根据权利要求12所述的方法,其中,所述非卡账号标识包括所述注册账号或所述注册账号的令牌Token;所述注册账号与至少一个非卡账户具有对应关系。
- 根据权利要求13所述的方法,其中,所述第二目标接口包括:所述卡基支付系统中所述卡交换设备与支付受理方设备用于卡基交互的第一接口;或者,新增的第三接口;所述第五目标接口包括:所述卡基支付系统中所述卡交换设备与卡账户资金管理设备用于交互的第五接口;或者,新增的第七接口。
- 根据权利要求13所述的方法,其中,所述第三目标接口包括:所述卡基支付系统中所述卡交换设备与支付受理方设备用于卡基交互的第一接口;或者,新增的第四接口。
- 根据权利要求11所述的方法,还包括:接收所述卡交换设备发送的非卡账户总清算信息;根据所述非卡账户总清算信息,获取所述非卡账户各自的清算信息。
- 一种卡交换设备,所述卡交换设备属于卡基支付系统,所述卡交换设备包括交互模块,所述交互模块包括接收单元;所述接收单元,用于通过第一目标接口接收支付受理方设备发送的第一支付请求,所述第一支付请求包括非卡账号标识和交易信息,所述非卡账号标识用于标识非卡账户的注册账号;所述交互模块,用于利用所述第一支付请求中的所述非卡账号标识与非卡账户管理设备交互,使所述非卡账户管理设备确定与所述第一支付请求中的所述非卡账号标识对应的目标非卡账户,以使所述卡交换设备或所述非卡账户管理设备与所述目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付,所述非卡账户管理设备存储有所述非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系。
- 一种非卡账户管理设备,所述非卡账户管理设备存储有非卡账号标识与非卡账户的对应关系以及非卡账户与非卡账户资金管理设备的对应关系,所述非卡账户管理设备包括交互模块和处理模块;交互模块,用于与卡交换设备利用所述卡交换设备接收到的第一支付请求中的非卡账号标识进行交互,所述第一支付请求由支付受理方设备通过第一目标接口向所述卡交换设备发送,包括所述非卡账号标识和交易信息,所述卡交换设备属于卡基支付系统;处理模块,用于根据所述第一支付请求中的所述非卡账号标识,确定 与所述第一支付请求中的所述非卡账号标识对应的目标非卡账户;所述交互模块还用于与所述目标非卡账户对应的目标非卡账户资金管理设备交互,执行支付;或者,与所述卡交换设备交互,以使所述卡交换设备与所述目标非卡账户资金管理设备交互,执行支付。
- 一种卡交换设备,包括:处理器以及存储有计算机程序指令的存储器;所述处理器执行所述计算机程序指令时实现如权利要求1至11中任意一项所述的非卡账户支付方法。
- 一种非卡账户管理设备,包括:处理器以及存储有计算机程序指令的存储器;所述处理器执行所述计算机程序指令时实现如权利要求12至19中任意一项所述的非卡账户支付方法。
- 一种非卡账户支付系统,包括如权利要求22所述的卡交换设备和如权利要求23所述的非卡账户管理设备。
- 一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机程序指令,所述计算机程序指令被处理器执行时实现如权利要求1至11中任意一项所述的非卡账户支付方法。
- 一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机程序指令,所述计算机程序指令被处理器执行时实现如权利要求12至19中任意一项所述的非卡账户支付方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110885046.6A CN113657887B (zh) | 2021-08-03 | 2021-08-03 | 非卡账户支付方法、设备、系统及存储介质 |
| CN202110885046.6 | 2021-08-03 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023010835A1 true WO2023010835A1 (zh) | 2023-02-09 |
Family
ID=78478294
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/078751 Ceased WO2023010835A1 (zh) | 2021-08-03 | 2022-03-02 | 非卡账户支付方法、设备、系统及存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113657887B (zh) |
| WO (1) | WO2023010835A1 (zh) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113657887B (zh) * | 2021-08-03 | 2024-08-16 | 中国银联股份有限公司 | 非卡账户支付方法、设备、系统及存储介质 |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104715360A (zh) * | 2013-12-16 | 2015-06-17 | 中国银联股份有限公司 | 无卡支付收款系统以及无卡支付收款方法 |
| CN104732382A (zh) * | 2015-04-03 | 2015-06-24 | 深圳市淘淘谷信息技术有限公司 | 一种支付管理方法及支付管理系统 |
| CN106372871A (zh) * | 2016-08-29 | 2017-02-01 | 成都支付通卡友电子商务有限公司 | 全兼容支付结算系统 |
| CN107111810A (zh) * | 2014-10-13 | 2017-08-29 | 万事达卡国际股份有限公司 | 用于直接运营商计费的方法和系统 |
| US20190392446A1 (en) * | 2018-06-26 | 2019-12-26 | Mastercard Asia/Pacific Pte. Ltd. | Computer system and computer-implemented method for authenticating a card-not-present transaction |
| CN110659896A (zh) * | 2018-06-28 | 2020-01-07 | 万事达卡亚太私人有限公司 | 聚合的交易处理 |
| CN113657887A (zh) * | 2021-08-03 | 2021-11-16 | 中国银联股份有限公司 | 非卡账户支付方法、设备、系统及存储介质 |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1389812A (zh) * | 2001-06-01 | 2003-01-08 | 陆杨 | 综合业务数据网信用卡网上支付结算系统 |
| CN1758276A (zh) * | 2004-10-10 | 2006-04-12 | 中国银联股份有限公司 | 一种支付服务管理系统及方法 |
| KR20080052726A (ko) * | 2006-12-08 | 2008-06-12 | 주식회사 신한은행 | 지급 가상계좌를 이용한 출금(또는 이체) 거래 처리 방법및 시스템과 이를 위한 프로그램 기록매체 |
| CN101515387A (zh) * | 2008-12-31 | 2009-08-26 | 候万春 | 一种基于支付桥实现非接触支付的系统和方法 |
| CN103413216B (zh) * | 2013-05-16 | 2018-02-09 | 深圳市淘淘谷信息技术有限公司 | 一种多账户管理支付方法 |
| CN104504565A (zh) * | 2015-01-16 | 2015-04-08 | 上海浩恺信息科技有限公司 | 一种基于银行虚拟卡号的移动支付系统和方法 |
| CN111476578A (zh) * | 2020-04-09 | 2020-07-31 | 王海刚 | Nfc支付方法及系统、圈存方法及系统 |
| CN112308558A (zh) * | 2020-10-27 | 2021-02-02 | 支付宝(杭州)信息技术有限公司 | 语音交互的支付方法、服务器、装置、设备及系统 |
-
2021
- 2021-08-03 CN CN202110885046.6A patent/CN113657887B/zh active Active
-
2022
- 2022-03-02 WO PCT/CN2022/078751 patent/WO2023010835A1/zh not_active Ceased
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104715360A (zh) * | 2013-12-16 | 2015-06-17 | 中国银联股份有限公司 | 无卡支付收款系统以及无卡支付收款方法 |
| CN107111810A (zh) * | 2014-10-13 | 2017-08-29 | 万事达卡国际股份有限公司 | 用于直接运营商计费的方法和系统 |
| CN104732382A (zh) * | 2015-04-03 | 2015-06-24 | 深圳市淘淘谷信息技术有限公司 | 一种支付管理方法及支付管理系统 |
| CN106372871A (zh) * | 2016-08-29 | 2017-02-01 | 成都支付通卡友电子商务有限公司 | 全兼容支付结算系统 |
| US20190392446A1 (en) * | 2018-06-26 | 2019-12-26 | Mastercard Asia/Pacific Pte. Ltd. | Computer system and computer-implemented method for authenticating a card-not-present transaction |
| CN110659896A (zh) * | 2018-06-28 | 2020-01-07 | 万事达卡亚太私人有限公司 | 聚合的交易处理 |
| CN113657887A (zh) * | 2021-08-03 | 2021-11-16 | 中国银联股份有限公司 | 非卡账户支付方法、设备、系统及存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113657887B (zh) | 2024-08-16 |
| CN113657887A (zh) | 2021-11-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20250328880A1 (en) | Mobile services remote deposit capture | |
| US11676138B2 (en) | Multi-network tokenization processing | |
| US10901818B2 (en) | System and method for common request processing | |
| US20140067661A1 (en) | Virtual check system and method | |
| WO2012142315A2 (en) | Message routing using logically independent recipient identifiers | |
| EP4625291A1 (en) | Digital payment processing method and apparatus, and device, system and medium | |
| CN112085531B (zh) | 资源处理方法、服务器、终端、设备、系统及存储介质 | |
| CN114207652B (zh) | 非本地账户处理 | |
| WO2021005269A1 (en) | Blockchain-based transaction from offline wallet | |
| WO2018129035A2 (en) | Merchant enrollment for reverse payments | |
| CN113519003B (zh) | 直接扩展覆盖系统和方法 | |
| WO2022222581A1 (zh) | 支付方法、平台设备、系统及存储介质 | |
| TWI888097B (zh) | 支付增強驗證的方法、裝置、伺服器、系統及介質 | |
| CN112669062A (zh) | 电子卡券管理方法、服务器、系统及存储介质 | |
| TWI839875B (zh) | 支付方法、使用者終端、裝置、設備、系統及介質 | |
| WO2023010835A1 (zh) | 非卡账户支付方法、设备、系统及存储介质 | |
| CN106855974A (zh) | 一种移动支付方法及装置 | |
| CN114529285B (zh) | 数字货币支付方法、服务器、系统及介质 | |
| CN118941283A (zh) | 基于多业务系统的交易转接方法、装置、设备及介质 | |
| CN114897524A (zh) | 数字货币跨境支付方法、装置、设备、系统及介质 | |
| CN114461117A (zh) | 数据处理方法、装置、设备及计算机存储介质 | |
| TWI858507B (zh) | 網路支付業務開通方法、裝置、設備、系統及介質 | |
| EP4636672A1 (en) | Open loop transaction system and method | |
| KR101021604B1 (ko) | 은행 웹망을 이용한 수입신용장의 전산 관리 시스템 | |
| CN117793691A (zh) | 一种网卡管理方法、装置、设备及存储介质 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22851562 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2401000674 Country of ref document: TH |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 22851562 Country of ref document: EP Kind code of ref document: A1 |

