WO2022222581A1 - 支付方法、平台设备、系统及存储介质 - Google Patents

支付方法、平台设备、系统及存储介质 Download PDF

Info

Publication number
WO2022222581A1
WO2022222581A1 PCT/CN2022/075806 CN2022075806W WO2022222581A1 WO 2022222581 A1 WO2022222581 A1 WO 2022222581A1 CN 2022075806 W CN2022075806 W CN 2022075806W WO 2022222581 A1 WO2022222581 A1 WO 2022222581A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
platform
account
request message
information
Prior art date
Application number
PCT/CN2022/075806
Other languages
English (en)
French (fr)
Inventor
袁成凤
佟志臣
闵勇
孙纲
赵恒�
冯俊
缪晖
胡新松
周敏
Original Assignee
中国银联股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国银联股份有限公司 filed Critical 中国银联股份有限公司
Publication of WO2022222581A1 publication Critical patent/WO2022222581A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems

Definitions

  • the present application belongs to the field of data processing, and in particular relates to a payment method, platform device, system and storage medium.
  • employees in the organization need to travel to complete the work delivered by the organization, or they need to help the organization purchase supplies needed by the organization.
  • the employee needs to pay for the resource expenses generated therein first, and then apply to the organization. to reimburse.
  • the circulation process of payment resources is more complicated, the circulation time is longer, and the execution efficiency is low.
  • the embodiments of the present application provide a payment method, a platform device, a system, and a storage medium, which can improve the efficiency of resource flow and execution.
  • an embodiment of the present application provides a payment method, which is applied to a transfer platform.
  • the method includes: receiving a payment request message sent by an agency platform, where the payment request message includes a payer organization identifier and payment information, and the payer organization identifier Used to indicate the account of the payer's organization; forward the payment request message to the third-party platform, and the payment request message is used to instruct the third-party platform to send a service acquisition request message to the service provider platform according to the payer's organization identification and payment information;
  • the identification and payment information of the payer's organization, and the payment resources of the third-party platform are transferred to the account of the service provider's platform.
  • an embodiment of the present application provides a payment method, which is applied to a third-party platform.
  • the method includes: receiving a payment request message sent by a transfer platform, where the payment request message includes a payer organization identifier and payment information, and the payer organization The identifier is used to indicate the account of the payer organization; according to the payer organization identifier and payment information, a service acquisition request message is sent to the service provider platform; wherein, in the case that the service provider platform provides services in response to the service acquisition request message, the first The payment resources of the third-party platform are controlled by the transfer platform and transferred to the account of the service provider platform.
  • an embodiment of the present application provides a switching platform device, including: a receiving module configured to receive a payment request message sent by an agency platform, where the payment request message includes a payer organization identifier and payment information, and the payer organization identifier It is used to indicate the account of the payer's organization; the sending module is used to forward the payment request message to the third-party platform, and the payment request message is used to instruct the third-party platform to send the service to the service provider platform according to the payer's organization identification and payment information.
  • the request message is used to transfer the payment resources of the third-party platform to the account of the service provider platform according to the identifier of the payer's organization and payment information.
  • an embodiment of the present application provides a third-party platform device, including: a receiving module configured to receive a payment request message sent by a transfer platform, where the payment request message includes a payer organization identifier and payment information, and the payer organization The identifier is used to indicate the account of the payer organization; the sending module is used to send a service acquisition request message to the service provider platform according to the payer organization identifier and payment information; wherein, the service providing platform provides services in response to the service acquisition request message
  • the payment resources of the third-party platform corresponding to the third-party platform device are controlled by the transfer platform and transferred to the account of the service provider platform.
  • an embodiment of the present application provides a switching platform device, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the payment method of the first aspect is implemented.
  • an embodiment of the present application provides a third-party platform device, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the payment method of the second aspect is implemented.
  • an embodiment of the present application provides a payment system, including the switching platform device of the fifth aspect and the third-party platform device of the sixth aspect.
  • an embodiment of the present application provides a computer-readable storage medium, where computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the payment method of the first aspect or the payment of the second aspect is realized method.
  • the present application provides a payment method, platform device, system and storage medium.
  • the agency platform, the transfer platform and the third-party platform can request the service provider platform through a payment request message including the payment party organization identification and payment information.
  • service and can directly transfer the payment resources corresponding to the payment information in the third-party platform to the account of the service provider platform, the payment resources do not need to flow out of the user's personal account, and the payment resources do not need to flow into the personal account again in the subsequent process.
  • which can quickly complete the transfer of payment resources between payer organizations, third-party platforms and service provider platforms, simplifying the transfer process of payment resources, reducing transfer time, and improving execution efficiency.
  • FIG. 1 is a schematic diagram of an example of a scenario architecture of a payment method provided by an embodiment of the present application
  • FIG. 2 is a flowchart of an embodiment of the payment method provided by the first aspect of the present application
  • FIG. 3 is a flowchart of another embodiment of the payment method provided by the first aspect of the present application.
  • FIG. 5 is a flowchart of still another embodiment of the payment method provided by the first aspect of the present application.
  • FIG. 6 is a flowchart of an embodiment of the payment method provided by the second aspect of the present application.
  • FIG. 9 is a flowchart of still another embodiment of the payment method provided by the second aspect of the present application.
  • FIG. 10 is a flowchart of an example of a payment process provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of an embodiment of the switching platform device provided by the third aspect of the application.
  • FIG. 12 is a schematic structural diagram of an embodiment of a third-party platform device provided by the fourth aspect of the application.
  • FIG. 13 is a schematic diagram of the hardware structure of an embodiment of the switching platform device provided by the fifth aspect of the application.
  • FIG. 14 is a schematic diagram of a hardware structure of an embodiment of a third-party platform device provided by the sixth aspect of the application.
  • the employees in the organization need to travel to complete the work delivered by the organization, or they need to help the organization purchase the supplies needed by the organization.
  • Employees need to pay for the resource costs incurred, and then apply to the organization for reimbursement.
  • Resources flow from employees to intermediary accounts, and then from intermediary accounts to service providers.
  • resources also need to be transferred from the organization to which the employee belongs to the employee to realize the reimbursement process.
  • the following takes the travel expenses incurred by employees of an organization on business trips as an example.
  • the employees book air tickets with the airline through an online travel agent (OTA), and the ticket purchase funds are transferred from the employee's account to the account of the online travel agent, and then from the online travel agent.
  • the account of the travel agent is transferred to the account of the airline.
  • the ticket purchase funds flow from the organization's account to the employee's account.
  • the resource transfer process is more complicated, and the transfer time is long, which reduces the execution efficiency of resource transfer.
  • the present application provides a payment method, platform, system and storage medium. Through the interaction of a payment request message including the identifier of the payer's organization and payment information on the agency platform, the transfer platform and the third-party platform, resources can be transferred from the organization's organization.
  • the account is directly transferred to the account of the service provider, thereby simplifying the resource transfer process, reducing the resource transfer time, and improving the execution efficiency of resource transfer.
  • the payment in the embodiment of the present application refers to the payment initiated by the user but the final resource payer is the payer organization.
  • the proxy platform, transfer platform, third-party platform, and service provider platform can be implemented by servers, terminal devices, etc., which are not limited here.
  • the agency platform may be a service agency platform for customers.
  • the agency platform may be an online travel agency platform, which is not limited herein.
  • the transfer platform is a platform for monitoring the process of resource flow, and the resource authority is higher than that of the agency platform, third-party platform and service provider platform.
  • the third-party platform may be a third-party payment platform with payment qualification certification. Specifically, the payment qualification of the third-party platform can be authenticated by the transfer platform.
  • a service provider platform is a platform that provides users with purchased services.
  • the service provider platform can be the platform of an airline, railway company, bus company, or other transportation company, which is not limited here.
  • FIG. 1 is a schematic diagram of an example of a scenario architecture of a payment method provided by an embodiment of the present application.
  • the user can interact with the proxy platform 12 through the terminal device 11, the proxy platform 12 and the transfer platform 13 can interact, and the proxy platform 12 and the service provider platform 14 can interact, and the transfer
  • the platform 13 and the third-party platform 15 can interact, and the third-party platform 15 and the service provider platform 14 can interact.
  • FIG. 2 is a flowchart of an embodiment of the payment method provided by the first aspect of the present application. As shown in FIG. 2, the payment method may include steps S201 to S203.
  • step S201 a payment request message sent by the agency platform is received.
  • the user can initiate a payment request to the agent platform through the terminal device.
  • the agency platform sends a payment request message to the transfer platform in response to the payment request.
  • the agent platform can host the account of the payer organization.
  • the payment request message includes the identifier of the payer's organization and payment information.
  • the payer organization ID is used to indicate the account of the payer organization.
  • the payer organization is the organization that is the payer. Organizations may specifically include enterprises, institutions, social groups, institutions, etc., which are not limited here.
  • One account corresponds to one payer organization, that is, one payer organization uses the account of the payer organization to pay by using the payment method in the embodiment of the present application.
  • a payer organization may include at least one payment user, that is, a payer organization has a payment association relationship with at least one payment user. The payment association relationship can be established in advance. Payment users in the payer organization share the account of the payer organization. For example, when a payer organization includes multiple payment users, multiple users in the payer organization can use the account of the payment organization to make payments.
  • Payment information includes information required to make a payment.
  • the payment information may include payment user information, payment content information, etc., which are not limited herein.
  • the payment user information is used to indicate the payment user, for example, the payment user information may include the user's name, the user's mobile phone number, the user's ID number, etc., which is not limited herein.
  • Payment content information may be used to indicate payment resources.
  • the payment content information can also be used to indicate payment for commodities, etc., which is not limited here.
  • the payment content information may include payment commodity information, payment resource information, etc., which is not limited herein.
  • the proxy platform may also send a service request to the service provider platform in response to the user initiating a payment request to the proxy platform through the terminal device.
  • the service request may include the payer organization identification and payment information for requesting the service.
  • the agency platform sends a ticket purchase request to the airline in response to a payment request initiated by the user to the agency platform through the terminal device.
  • step S202 the payment request message is forwarded to the third-party platform.
  • the payment request message is used to instruct the third-party platform to send a service acquisition request message to the service provider platform according to the payer's organization identifier and payment information.
  • the third-party platform can store account information of the payer organization, user information of users in the payer organization, etc., which is not limited herein.
  • the payer organization's account may be allocated by the third-party platform.
  • the third-party platform may correspond to the accounts of one or more payer organizations.
  • the third-party platform may send a service acquisition request message to the service provider platform.
  • the service acquisition request message is used to request the service from the service provider platform.
  • the service may correspond to the application scenario of the payment method, and may include physical goods or services, which are not limited here.
  • the service requested by the service acquisition request message to the service provider platform may include travel tickets, travel tickets, accommodation reservations, etc., which are not limited herein.
  • the payment request message may be used to instruct the third-party platform to send a service acquisition request message requesting a ticket to the airline platform.
  • the payment request message may be used to instruct the third-party platform to send a service acquisition request message for requesting accommodation reservations to the service platform of the hotel.
  • the requested service may include the specific purchased common items, which is not limited herein.
  • the third-party platform may also receive a payment request message for the personal account.
  • the third-party platform can determine whether the payment account is an account of the payer organization or an individual account through the account identifier in the payment request message.
  • the payer organization identifier may have a type identifier
  • the personal account identifier may also have a type identifier.
  • the type identification bit may include a single character or a multi-character character, which is not limited herein.
  • the type identifier of the payer organization identifier is different from the type identifier of the personal account.
  • the identifier of the payer organization may be the card number of the virtual card corresponding to the account of the payer organization
  • the identifier of the personal account may be the card number of the bank card of the personal account.
  • the identifier of the payer's organization includes the issuer identification number (IIN) with a prefix of 2, and the identity of the personal account includes an issuer identification code with a prefix of 2.
  • the issuer identification code can be used as the type identifier, or the prefix of the issuer identification code can be used as the type identifier.
  • the third-party platform can determine whether the account identifier in the payment request message is the payer organization identifier or the personal account identifier by identifying the type identifier of the account identifier. In the case where it is determined that the account identifier in the payment request message is the identifier of the payer organization, the payment request message is forwarded to the third-party platform. When it is determined that the account identifier in the payment request message is the personal account identifier, the payment request message is forwarded to a personal account management platform such as a bank platform.
  • step S203 the payment resources of the third-party platform are transferred to the account of the service provider platform according to the identifier of the payer's organization and the payment information.
  • the transfer platform can transfer the payment resources corresponding to the payment information in the account of the payer organization indicated by the payer organization identifier in the third-party platform to the account of the service provider platform to complete the payment.
  • the payer organization can realize the resource transfer between the payer organization and the third-party platform according to the invoice provided by the user in the payer organization and the reconciliation information provided by the third-party platform.
  • the resource transfer between the payer organization and the third-party platform refers to the transfer of resources to be returned from the account of the payer organization to the third-party platform.
  • the resources to be returned include the payment resources of the same amount as the payment resources transferred from the third-party platform to the account of the service provider platform.
  • the time for the transfer platform to transfer the payment resources of the third-party platform to the account of the service provider platform is not limited.
  • the transfer platform's transfer of the payment resources of the third-party platform to the account of the service provider's platform can be performed on the second day of payment, or on the same day of payment.
  • the agency platform, the transfer platform, and the third-party platform can request services from the service provider platform through a payment request message including the payer's organization identifier and payment information, and can transfer the third-party platform to the service provider platform.
  • the payment resources corresponding to the payment information are directly transferred to the account of the service provider platform, and the payment resources do not need to flow out of the user's personal account, and the payment resources do not need to flow into the personal account again in the subsequent process, which can quickly complete the payment of the payment resources.
  • the circulation between party organizations, third-party platforms and service provider platforms simplifies the circulation process of payment resources, reduces circulation time, and improves execution efficiency.
  • the interaction process between the proxy platform and the service provider platform does not change, which can reduce the cost of transforming the existing architecture.
  • the payment resources do not need to go through the agency platform, which reduces the circulation links of the payment resources, reduces the risk in the process of the payment resources circulation, and improves the security and reliability of the payment.
  • FIG. 3 is a flowchart of another embodiment of the payment method provided by the first aspect of the present application. The difference between FIG. 3 and FIG. 2 is that the payment method shown in FIG. 3 may further include steps S204 and S205.
  • step S204 reconciliation information is generated according to the identifier of the payer's organization and the payment information.
  • the transfer platform may periodically perform the transfer of the payment resources of the third-party platform to the account of the service provider platform according to the identifier of the payer's organization and payment information. For example, the transferable platform can settle settlements on a daily basis, and calculate the payment resources that the third-party platform needs to transfer to the account of the service provider platform within one day.
  • the transfer platform can determine the payment resources, the first and third payment resources that should be transferred to the account of each payer organization according to the identification and payment information of the payer organization obtained from the payment request message.
  • the account of each payer organization corresponding to the three-party platform should transfer the total payment resources, etc., to generate reconciliation information.
  • the reconciliation information may include details and total amount of payment resources, etc., which are not limited here.
  • step S205 the reconciliation information is sent to the third-party platform and the service provider platform respectively.
  • Third-party platforms and service provider platforms can perform reconciliation based on reconciliation information to ensure the accuracy of payment resource transfer.
  • the payer organization identification includes the issuer identification identification.
  • the issuer identifier is used to identify the third-party platform that generates and issues the account of the payer organization. Through the issuer identifier, the transfer platform can forward the payment request message to the accurate third-party platform.
  • FIG. 4 is a flowchart of another embodiment of the payment method provided by the first aspect of the present application. The difference between FIG. 4 and FIG. 2 is that step S202 in FIG. 2 can be specifically refined into step S2021 and step S2022 in FIG. 4 .
  • step S2021 the issuer identifier in the payer organization identifier is identified, and the third-party platform corresponding to the issuer identifier is determined.
  • the third-party platform that generates and issues the account of the payer organization may be one or more than two, which is not limited here.
  • the transfer platform can identify the issuer's identity in the payer's organization identity, and determine the third party that generates and issues the payer's organization's account according to the issuer's identity. platform in order to forward the payment request message to the third-party platform.
  • the issuer identification bits may include issuer identification codes or other codes, etc., which are not limited herein.
  • issuer identification codes or other codes, etc., which are not limited herein.
  • step S2022 the payment request message is forwarded to the third-party platform corresponding to the issuer identifier.
  • FIG. 5 is a flowchart of still another embodiment of the payment method provided by the first aspect of the present application. The difference between FIG. 5 and FIG. 2 is that the payment method shown in FIG. 5 may further include steps S206 and S207.
  • step S206 a permission request message sent by the third-party platform to issue an account is received.
  • the permission request message issued by the account includes the institution qualification information of the third-party platform.
  • the institutional qualification information of the third-party platform is used to characterize the conditions, qualifications, and capabilities of the third-party platform.
  • the transfer platform can determine whether to activate the authority to generate and issue the account of the payer organization for the third-party platform according to the institution qualification information of the third-party platform included in the authorization request message issued by the account.
  • step S207 if the institution qualification information of the third-party platform satisfies the preset permission activation conditions, a permission activation success message is sent to the third-party platform.
  • Permission activation conditions can be set according to specific scenarios and needs, and are not limited here. If the institution qualification information of the third-party platform satisfies the permission activation conditions, it means that the third-party platform has the qualification to generate and issue the account of the payer's organization, and send the permission activation success message to the third-party platform.
  • the permission activation success message indicates that the third-party platform has the permission to generate and issue the account of the payer organization.
  • the institution qualification information of the third-party platform does not meet the permission activation conditions, which means that the third-party platform does not have the qualifications to generate and issue the account of the payer's organization.
  • Activation failure message indicates that the third-party platform does not have the permission to generate and issue the account of the payer organization.
  • FIG. 6 is a flowchart of an embodiment of the payment method provided by the second aspect of the present application. As shown in FIG. 6 , the payment method may include steps S301 and S302.
  • step S301 a payment request message sent by the transfer platform is received.
  • the payment request message includes the identifier of the payer's organization and payment information.
  • the payer organization ID is used to indicate the account of the payer organization.
  • the payer organization identifier may include the issuer identifier identifier.
  • the issuer identifier is used to identify the third-party platform that generates and issues the account of the payer organization.
  • For the specific content of the identifier of the issuer reference may be made to the relevant descriptions in the foregoing embodiments, which will not be repeated here.
  • payment information may include payment user information and payment content information.
  • the payment user information is used to indicate the payment user.
  • the payment content information is used to indicate payment resources.
  • an account of a payer organization has a payment association relationship with at least one payer user.
  • a payment user who has a payment association relationship with the account of the payer organization can initiate payment by using the account of the payer organization.
  • the account of one payer organization has a payment association relationship with two or more payment users
  • the two or more payment users can initiate payment by using the account of the payer organization.
  • step S302 a service acquisition request message is sent to the service provider platform according to the payer organization identifier and payment information.
  • the service acquisition request message may include the payer organization identification and payment information.
  • the service provider platform may provide the service requested by the service acquisition request message.
  • the service provider platform is an airline platform
  • the airline company can receive the service request initiated by the agency platform.
  • the airline platform receives the service acquisition request message, it can check whether the payer organization identification and payment information in the service acquisition request message are consistent with the payer organization identification and payment information carried in the service request initiated by the agency platform. . If the payer organization identifier and payment information in the service acquisition request message are consistent with the payer organization identifier and payment information carried in the service request initiated by the agency platform, the airline platform provides the corresponding service, that is, the ticket is issued.
  • the payment resources of the third-party platform are controlled and transferred to the account of the service provider platform by the transfer platform.
  • the account of the third-party platform can be managed by the transfer platform, and the transfer platform transfers the payment resources in the account of the third-party platform to the account of the service provider platform, that is, the payment resources are transferred from the third-party platform to the service provider platform to realize The flow of payment resources.
  • the third-party platform can verify the payment user information in the payment information. Specifically, it can be verified whether the account of the payer organization indicated by the payer organization identifier has a payment association relationship with the payment user indicated by the payment user information in the payment information. In the case that the verification is successful, that is, the account of the payer organization indicated by the payer organization identifier has a payment association relationship with the payment user indicated by the payment user information in the payment information, a service acquisition request message is sent to the service provider platform.
  • the service acquisition request message is refused to be sent to the service provider platform.
  • the agency platform, the transfer platform, and the third-party platform can request services from the service provider platform through a payment request message including the payer's organization identifier and payment information, and can transfer the third-party platform to the service provider platform.
  • the payment resources corresponding to the payment information are directly transferred to the account of the service provider platform, and the payment resources do not need to flow out of the user's personal account, and the payment resources do not need to flow into the personal account again in the subsequent process, which can quickly complete the payment of the payment resources.
  • the circulation between party organizations, third-party platforms and service provider platforms simplifies the circulation process of payment resources, reduces circulation time, and improves execution efficiency.
  • the payment resources do not need to go through the agency platform, which reduces the circulation links of the payment resources, reduces the risk in the process of the payment resources circulation, and improves the security and reliability of the payment.
  • FIG. 7 is a flowchart of another embodiment of the payment method provided by the second aspect of the present application. The difference between FIG. 7 and FIG. 6 is that the payment method shown in FIG. 7 may further include step S303.
  • step S303 the reconciliation information sent by the transfer platform is received.
  • the reconciliation information is generated by the transfer platform according to the payer's organization identification and payment information.
  • the reconciliation information for the specific content of the reconciliation information, reference may be made to the relevant descriptions in the foregoing embodiments, and details are not repeated here.
  • the third-party platform can reconcile with the service provider platform, so as to ensure the accuracy and reliability of the payment.
  • the third-party platform may also request permission from the transit platform to generate and issue the account of the payer organization. Only when the third-party platform has the authority to generate and distribute the account of the payer organization can the third-party platform generate and distribute the account of the payer organization and manage the account of the payer organization.
  • FIG. 8 is a flowchart of still another embodiment of the payment method provided by the second aspect of the present application. The difference between FIG. 8 and FIG. 6 is that the payment method shown in FIG. 8 may further include steps S304 and S305.
  • step S304 a request message is sent to the transfer platform for the permission to issue the account.
  • the account issuing authority request message includes the institution qualification information of the third-party platform, and is used to request the transfer platform for the authority to generate and issue the account of the payer's organization.
  • step S305 a permission activation success message sent by the transfer platform is received.
  • the permission activation success message is sent by the transfer platform when the institution qualification information of the third-party platform meets the preset permission activation conditions.
  • the permission activation success message indicates that the third-party platform has the permission to generate and issue the account of the payer organization. That is, only when the institutional qualification information of the third-party platform satisfies the permission activation conditions, the third-party platform has the authority to generate and issue the account of the payer's organization. In the event that the institutional qualification information of the third-party platform does not meet the conditions for permission activation, the third-party platform does not have the authority to generate and issue the account of the payer's organization.
  • the authority of the transfer platform is higher than that of the third-party platform, and the third-party platform can be managed.
  • the transfer platform has the authority to create and issue the account of the payer organization for the third-party platform.
  • the authorization of the third-party platform by the transfer platform facilitates the standardized management of the third-party platform, and can prevent the third-party platform that is not qualified enough to perform the above payment method from participating in the payment process in the embodiment of the present application, thereby improving the security and safety of payment. reliability.
  • FIG. 9 is a flowchart of still another embodiment of the payment method provided by the second aspect of the present application. The difference between FIG. 9 and FIG. 6 is that the payment method shown in FIG. 9 may further include steps S306 to S308.
  • step S306 the account application message sent by the payer organization through the terminal device is received.
  • the account application message includes the qualification information of the payer organization, and is used to apply for the account of the payer organization.
  • the qualification information of the payer organization is used to characterize the payer organization's other conditions, qualifications, capabilities, etc.
  • step S307 in response to the account application message, an account is allocated to the payer organization.
  • the transfer platform assigns different accounts to different payer organizations. Specifically, the transfer screen can assign an account number to the payer organization. For example, the transit platform may assign the payer organization a 16-digit to 19-digit account number that includes a 2-prefixed issuer identification code.
  • step S308 an account credit authority is set for the account of the payer organization according to the qualification information of the payer organization.
  • Account credit authority may include authority content possessed by the account, and the authority content is related to qualification information and the like.
  • account credit rights may include resource transfer time limits and credit resource amounts.
  • the resource transfer time limit can indicate the time limit for the account of the payer organization to transfer the resources to be returned to the third-party platform. For example, if the resource transfer time is limited to 5 days, within 5 days after the third-party platform transfers the payment resources to the service provider's platform, the account of the payer's organizational structure needs to transfer the resources to be returned to the third-party platform.
  • the conditions, qualifications, and abilities of the payer organization represented by the qualification information are positively correlated.
  • the amount of credit resources can indicate the amount of credit resources set by the third-party platform for the payer organization. In the case that the amount of resources to be returned between the account of the payer organization and the third-party platform exceeds the amount of credit resources, the third-party platform refuses to execute the payment related to the account of the payer organization.
  • the resources to be returned include the payment resources of the same amount as the payment resources transferred from the third-party platform to the account of the service provider platform.
  • the higher the condition, qualification, and capability of the payer organization represented by the qualification information of the payer organization the greater the amount of credit resources indicated by the amount of credit resources, that is, the amount of credit resources indicated by the amount of credit resources.
  • the amount is positively related to the conditions, qualifications and capabilities of the payer organization represented by the qualification information.
  • the payment resources in the above embodiments may include payment funds, payment points, payment virtual currency, etc., which are not limited herein.
  • FIG. 10 is a flowchart of an example of a payment process provided by an embodiment of the present application. As shown in FIG. 10 , the payment method may include steps S401 to S414.
  • step S401 the third-party platform sends an account-issued permission request message to the transfer platform.
  • step S402 when the institution qualification information of the third-party platform satisfies the preset permission activation conditions, the transfer platform sends a permission activation success message to the third-party platform.
  • step S403 the terminal device sends an account application message to the third-party platform.
  • step S404 the third-party platform allocates an account to the payer organization in response to the account application message.
  • step S405 the account credit authority is set for the account of the payer organization according to the qualification information of the payer organization.
  • step S406 the terminal device sends a payment request to the agency platform in response to the user's input operation.
  • step S407 the proxy platform sends a service request to the service provider platform in response to the payment request.
  • step S408 the agency platform sends a payment request message to the transfer platform in response to the payment request.
  • step S409 the transfer platform forwards the payment request message to the third-party platform.
  • step S410 the third-party platform sends a service acquisition request message to the service provider platform according to the payer organization identifier and payment information in the payment request message.
  • step S411 the service provider platform provides the service in response to the service acquisition request message.
  • step S412 at the end of the settlement period, the transfer platform sends the generated reconciliation information to the third-party platform.
  • step S413 at the end of the settlement period, the transfer platform sends the generated reconciliation information to the service provider platform.
  • step S414 within the first time period after the settlement period ends, the transfer platform transfers the payment resources of the third-party platform to the account of the service provider platform.
  • FIG. 11 is a schematic structural diagram of an embodiment of the switching platform device provided by the third aspect of the application.
  • the switching platform device 500 may include a receiving module 501 , a sending module 502 and a resource transfer module 503 .
  • the receiving module 501 may be configured to receive a payment request message sent by the agency platform.
  • the payment request message includes the identifier of the payer's organization and payment information.
  • the payer organization ID is used to indicate the account of the payer organization.
  • the payment information includes payment user information and payment content information.
  • the payment user information is used to indicate the payment user.
  • the payment content information is used to indicate payment resources.
  • an account of a payer organization has a payout relationship with at least one payer user.
  • the sending module 502 may be configured to forward the payment request message to the third-party platform.
  • the payment request message is used to instruct the third-party platform to send a service acquisition request message to the service provider platform according to the payer's organization identifier and payment information.
  • the resource transfer module 503 can be configured to transfer the payment resources of the third-party platform to the account of the service provider platform according to the identifier of the payer's organization and the payment information.
  • the agency platform, the transfer platform corresponding to the transfer platform device, and the third-party platform may request services from the service provider platform through a payment request message including the payer organization identifier and payment information, and
  • the payment resources corresponding to the payment information in the third-party platform can be directly transferred to the account of the service provider platform.
  • the payment resources do not need to flow out of the user's personal account, and the payment resources do not need to flow into the personal account again in the subsequent process, which can quickly It completes the transfer of payment resources between payer organizations, third-party platforms and service provider platforms, simplifies the transfer process of payment resources, reduces transfer time, and improves execution efficiency.
  • the interaction process between the proxy platform and the service provider platform does not change, which can reduce the cost of transforming the existing architecture.
  • the payment resources do not need to go through the agency platform, which reduces the circulation links of the payment resources, reduces the risk in the process of the payment resources circulation, and improves the security and reliability of the payment.
  • the transit platform device may further include a reconciliation information generation module.
  • the reconciliation information generation module can be used to generate reconciliation information according to the identifier of the payer's organization and payment information.
  • the sending module 502 in the above embodiment can also be used to send the reconciliation information to the third-party platform and the service provider platform respectively.
  • the payer organization identification includes the issuer identification identification.
  • the issuer identifier is used to identify the third-party platform that generates and issues the account of the payer organization.
  • the switching platform device 500 in the above embodiment may further include an identification module.
  • the identification module can be used to identify the identity of the issuer in the organizational identity of the payer, and to determine the third-party platform corresponding to the identity of the issuer.
  • the sending module 502 in the above embodiment may be configured to forward the payment request message to the third-party platform corresponding to the issuer identifier.
  • the receiving module 501 in the above-mentioned embodiment may also be configured to receive an account-issued permission request message sent by a third-party platform.
  • the permission request message issued by the account includes the institution qualification information of the third-party platform.
  • the sending module 502 in the above embodiment can also be configured to send a permission activation success message to the third-party platform when the institution qualification information of the third-party platform satisfies a preset permission activation condition.
  • the permission activation success message indicates that the third-party platform has the permission to generate and issue the account of the payer organization.
  • FIG. 12 is a schematic structural diagram of an embodiment of a third-party platform device provided by the fourth aspect of the application.
  • the third-party platform device 600 may include a receiving module 601 and a sending module 602 .
  • the receiving module 601 may be configured to receive a payment request message sent by the transfer platform.
  • the payment request message includes the identifier of the payer's organization and payment information.
  • the payer organization ID is used to indicate the account of the payer organization.
  • the payment information includes payment user information and payment content information.
  • the payment user information is used to indicate the payment user.
  • the payment content information is used to indicate payment resources.
  • an account of a payer organization has a payment association relationship with at least one payer user.
  • the sending module 602 may be configured to send a service acquisition request message to the service provider platform according to the payer organization identifier and payment information.
  • the service providing platform provides the service in response to the service acquisition request message
  • the payment resources of the third-party platform corresponding to the third-party platform device are controlled and transferred to the account of the service provider platform by the transfer platform.
  • the agency platform, the transfer platform, and the third-party platform can request services from the service provider platform through a payment request message including the payer's organization identifier and payment information, and can transfer the third-party platform to the service provider platform.
  • the payment resources corresponding to the payment information are directly transferred to the account of the service provider platform, and the payment resources do not need to flow out of the user's personal account, and the payment resources do not need to flow into the personal account again in the subsequent process, which can quickly complete the payment of the payment resources.
  • the circulation between party organizations, third-party platforms and service provider platforms simplifies the circulation process of payment resources, reduces circulation time, and improves execution efficiency.
  • the payment resources do not need to go through the agency platform, which reduces the circulation links of the payment resources, also reduces the risks in the process of the payment resources circulation, and improves the security and reliability of the payment.
  • the sending module 602 in the above-mentioned embodiment can also be used to send payment to the account of the payer organization indicated by the payer organization identifier and the payment user indicated by the payment user information in the payment information.
  • the service provider platform sends a service acquisition request message.
  • the receiving module 601 in the above-mentioned embodiments may also be configured to receive reconciliation information sent by the transfer platform, where the reconciliation information is generated by the transfer platform according to the payer's organization identification and payment information.
  • the sending module 602 in the above-mentioned embodiment may also be configured to send an account-issued permission request message to the transfer platform, where the account-issued permission request message includes the institution qualification information of the third-party platform.
  • the receiving module 601 in the above embodiment can also be configured to receive a permission activation success message sent by the transfer platform.
  • the permission activation success message is sent by the transfer platform when the institution qualification information of the third-party platform meets the preset permission activation conditions.
  • the permission activation success message indicates that the third-party platform has the permission to generate and issue the account of the payer organization.
  • the receiving module 601 in the above embodiment may also be used to receive an account application message sent by the payer organization through the terminal device.
  • the account application message includes the qualification information of the payer organization
  • the third-party platform device 600 may also include an account assignment module and a permission setting module.
  • the account allocation module may be configured to allocate an account to the payer organization in response to the account application message.
  • the authority setting module can be used to set account credit authority for the account of the payer organization according to the qualification information of the payer organization.
  • the payer organization identification includes the issuer identification identification.
  • the issuer identifier is used to identify the third-party platform that generates and issues the account of the payer organization.
  • FIG. 13 is a schematic diagram of the hardware structure of an embodiment of the switching platform device provided in the fifth aspect of the application.
  • the switching platform device 700 includes a memory 701 , a processor 702 , and a computer program stored on the memory 701 and executable on the processor 702 .
  • the above-mentioned processor 702 may include a central processing unit (CPU), or a 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 701 may include Read-Only Memory (ROM), Random Access Memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical/tangible memory storage device.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • magnetic disk storage media devices typically, magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical/tangible memory storage device.
  • a memory typically, includes one or more tangible (non-transitory) computer-readable storage media (eg, memory devices) encoded with software including computer-executable instructions, and when the software is executed (eg, by a or multiple processors), it is operable to perform the operations described with reference to the payment method according to the first aspect of the present application.
  • the processor 702 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 701, so as to implement the payment method of the first aspect in the above embodiment.
  • the transit platform device 700 may also include a communication interface 703 and a bus 704 .
  • the memory 701 , the processor 702 , and the communication interface 703 are connected through the bus 704 and complete the communication with each other.
  • the communication interface 703 is mainly used to implement communication between modules, apparatuses, units and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through communication interface 703 .
  • the bus 704 includes hardware, software, or both, coupling the components of the switch platform device 700 to each other.
  • the bus 704 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), Hyper Transport (HT) interconnect, Industry Standard Architecture (ISA) bus, Infiniband interconnect, Low pin count (LPC) bus, memory bus, Micro Channel Architecture (Micro Channel) Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-E) bus, Serial Advanced Technology Attachment (Serial Advanced Technology Attachment, SATA) bus, Video Electronics Standards Association Part ( Video Electronics Standards Association Local Bus (VLB) bus or other suitable bus or a combination of two or more of these.
  • Bus 704 may include one or more buses, where appropriate. Although embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.
  • FIG. 14 is a schematic diagram of a hardware structure of an embodiment of a third-party platform device provided by the sixth aspect of the application.
  • the third-party platform device 800 includes a memory 801 , a processor 802 , and a computer program stored on the memory 801 and executable on the processor 802 .
  • the above-mentioned processor 802 may include a central processing unit (CPU), or a 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 801 may include Read-Only Memory (ROM), Random Access Memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical/tangible memory storage device.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • magnetic disk storage media devices typically, magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical/tangible memory storage device.
  • a memory typically, includes one or more tangible (non-transitory) computer-readable storage media (eg, memory devices) encoded with software including computer-executable instructions, and when the software is executed (eg, by a or multiple processors), it is operable to perform the operations described with reference to the payment method according to the second aspect of the present application.
  • the processor 802 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 801, so as to implement the payment method of the second aspect in the above embodiment.
  • the third-party platform device 800 may also include a communication interface 803 and a bus 804 .
  • the memory 801 , the processor 802 , and the communication interface 803 are connected through the bus 804 and complete the communication with each other.
  • the communication interface 803 is mainly used to implement communication between modules, apparatuses, units and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through communication interface 803 .
  • the bus 804 includes hardware, software, or both, coupling the components of the third-party platform device 800 to each other.
  • the bus 804 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), Hyper Transport (HT) interconnect, Industry Standard Architecture (ISA) bus, Infiniband interconnect, Low pin count (LPC) bus, memory bus, Micro Channel Architecture (Micro Channel) Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-E) bus, Serial Advanced Technology Attachment (Serial Advanced Technology Attachment, SATA) bus, Video Electronics Standards Association Part ( Video Electronics Standards Association Local Bus (VLB) bus or other suitable bus or a combination of two or more of these.
  • Bus 804 may include one or more buses, where appropriate. Although embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.
  • a seventh aspect of the present application provides a payment system.
  • the payment system may include the switching platform device and the third-party platform device in the above-mentioned embodiment, that is, the payment system may include the switching platform and the third-party platform in the above-mentioned embodiment.
  • the above-mentioned payment system may further include one or more than two types of agent platform equipment, service provider platform equipment, and terminal equipment, that is, the above-mentioned payment system may further include agent platform, service provider platform, and terminal equipment.
  • agent platform service provider platform
  • terminal equipment One type or two or more types are not limited here.
  • Embodiments of the present application further provide a computer-readable storage medium, where computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the payment method of the first aspect in the foregoing embodiments or The payment method of the second aspect can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), magnetic disk or 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 will also be understood that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can also be implemented by special purpose hardware for performing the specified functions or actions, or by special purpose hardware and/or A combination of computer instructions is implemented.

Landscapes

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

Abstract

一种支付方法、平台设备、系统及存储介质，属于数据处理领域。该方法应用于转接平台，包括：接收代理平台发送的支付请求消息，支付请求消息包括支付方组织机构标识和支付信息，支付方组织机构标识用于指示支付方组织机构的账户；将支付请求消息向第三方平台转发，支付请求消息用于指示第三方平台根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息；根据支付方组织机构标识和支付信息，将第三方平台的支付资源转移至服务提供方平台的账户。

Description

支付方法、平台设备、系统及存储介质
相关申请的交叉引用
本申请要求享有于2021年4月21日提交的名称为“支付方法、平台设备、系统及存储介质”的中国专利申请202110429874.9的优先权，该申请的全部内容通过引用并入本文中。
技术领域
本申请属于数据处理领域，尤其涉及一种支付方法、平台设备、系统及存储介质。
背景技术
随着电子信息技术的不断发展，电子信息技术被应用在越来越多的业务领域中，如购物领域、出行领域等，为人们的生活、工作和学习带来了极大的便利。
在工作过程中，组织机构中的员工需要出差完成组织机构交付的工作，或者，需要帮组织机构购买组织机构所需的用品，员工需要先行支付其中产生的资源花销，之后再向组织机构申请报销。支付资源的流转过程较为复杂，且流转时间较长，执行效率较低。
发明内容
本申请实施例提供一种支付方法、平台设备、系统及存储介质，能够提高资源流转执行效率。
第一方面，本申请实施例提供一种支付方法，应用于转接平台，方法包括：接收代理平台发送的支付请求消息，支付请求消息包括支付方组织机构标识和支付信息，支付方组织机构标识用于指示支付方组织机构的账户；将支付请求消息向第三方平台转发，支付请求消息用于指示第三方平 台根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息；根据支付方组织机构标识和支付信息，将第三方平台的支付资源转移至服务提供方平台的账户。
第二方面，本申请实施例提供一种支付方法，应用于第三方平台，方法包括：接收转接平台发送的支付请求消息，支付请求消息包括支付方组织机构标识和支付信息，支付方组织机构标识用于指示支付方组织机构的账户；根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息；其中，在服务提供平台响应于服务获取请求消息提供服务的情况下，第三方平台的支付资源由转接平台控制转移至服务提供方平台的账户。
第三方面，本申请实施例提供一种转接平台设备，包括：接收模块，用于接收代理平台发送的支付请求消息，支付请求消息包括支付方组织机构标识和支付信息，支付方组织机构标识用于指示支付方组织机构的账户；发送模块，用于将支付请求消息向第三方平台转发，支付请求消息用于指示第三方平台根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息；资源转移模块，用于根据支付方组织机构标识和支付信息，将第三方平台的支付资源转移至服务提供方平台的账户。
第四方面，本申请实施例提供一种第三方平台设备，包括：接收模块，用于接收转接平台发送的支付请求消息，支付请求消息包括支付方组织机构标识和支付信息，支付方组织机构标识用于指示支付方组织机构的账户；发送模块，用于根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息；其中，在服务提供平台响应于服务获取请求消息提供服务的情况下，第三方平台设备对应的第三方平台的支付资源由转接平台控制转移至服务提供方平台的账户。
第五方面，本申请实施例提供一种转接平台设备，包括：处理器以及存储有计算机程序指令的存储器；处理器执行计算机程序指令时实现第一方面的支付方法。
第六方面，本申请实施例提供一种第三方平台设备，包括：处理器以及存储有计算机程序指令的存储器；处理器执行计算机程序指令时实现第 二方面的支付方法。
第七方面，本申请实施例提供一种支付系统，包括第五方面的转接平台设备和第六方面的第三方平台设备。
第八方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序指令，计算机程序指令被处理器执行时实现第一方面的支付方法或第二方面的支付方法。
本申请提供一种支付方法、平台设备、系统及存储介质，代理平台、转接平台和第三方平台之间可通过包括支付方组织机构标识和支付信息的支付请求消息，向服务提供方平台请求服务，并可将第三方平台中与支付信息对应的支付资源直接转移至服务提供方平台的账户中，支付资源不需从用户的个人账户流出，后续过程中支付资源也不需要再次流入个人账户，能够快速地完成支付资源在支付方组织机构、第三方平台和服务提供方平台之间的流转，简化了支付资源的流转过程，减少了流转时间，提高了执行效率。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例中所需要使用的附图作简单的介绍，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的支付方法的场景架构的一示例的示意图；
图2为本申请第一方面提供的支付方法的一实施例的流程图；
图3为本申请第一方面提供的支付方法的另一实施例的流程图；
图4为本申请第一方面提供的支付方法的又一实施例的流程图；
图5为本申请第一方面提供的支付方法的再一实施例的流程图；
图6为本申请第二方面提供的支付方法的一实施例的流程图；
图7为本申请第二方面提供的支付方法的另一实施例的流程图；
图8为本申请第二方面提供的支付方法的又一实施例的流程图；
图9为本申请第二方面提供的支付方法的再一实施例的流程图；
图10为本申请实施例提供的支付流程的一示例的流程图；
图11为本申请第三方面提供的转接平台设备的一实施例的结构示意图；
图12为本申请第四方面提供的第三方平台设备的一实施例的结构示意图；
图13为本申请第五方面提供的转接平台设备的一实施例的硬件结构示意图；
图14为本申请第六方面提供的第三方平台设备的一实施例的硬件结构示意图。
具体实施方式
下面将详细描述本申请的各个方面的特征和示例性实施例，为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及具体实施例，对本申请进行进一步详细描述。应理解，此处所描述的具体实施例仅意在解释本申请，而不是限定本申请。对于本领域技术人员来说，本申请可以在不需要这些具体细节中的一些细节的情况下实施。下面对实施例的描述仅仅是为了通过示出本申请的示例来提供对本申请更好的理解。
在工作过程中，组织机构中的员工需要出差完成组织机构交付的工作，或者，需要帮组织机构购买组织机构所需的用品。员工需要先行支付其中产生的资源花销，之后再向组织机构申请报销。资源从员工处流转到中间代理商户，再从中间代理商户流转到服务提供方，在后续报销过程中，资源还需要从员工所属的组织机构流转到员工，实现报销流程。下面以组织机构的员工出差产生的差旅费为例，员工通过线上旅游代理(Online Travel Agent，OTA)在航空公司预定机票，购票资金从员工账户流转至线上旅游代理的账户，再从线上旅游代理的账户流转至航空公司的账户。在后续报销过程中，购票资金从组织机构的账户流转到员工的账户。在支付到报销的整个过程中，资源流转过程较为复杂，且流转时间较长，降低了资源流转的执行效率。
本申请提供一种支付方法、平台、系统及存储介质，通过包括支付方组织机构标识和支付信息的支付请求消息在代理平台、转接平台和第三方 平台的交互，能够使资源从组织机构的账户直接流转至服务提供方的账户，从而简化资源流转过程，减少资源流转时间，提高资源流转的执行效率。需要说明的是，本申请实施例中的支付指的是由用户发起但最终的资源支付方为支付方组织机构的支付。
代理平台、转接平台、第三方平台、服务提供方平台可由服务器、终端设备等实现，在此并不限定。代理平台可为服务的代理商户平台，例如，若在差旅场景中，代理平台可为线上旅游代理的平台，在此并不限定。转接平台是监控资源流转过程的平台，资源权限高于代理平台、第三方平台和服务提供方平台。第三方平台可为具有支付资质认证的第三方支付平台。具体地，第三方平台的支付资质可由转接平台进行认证。服务提供方平台为为用户提供购买的服务的平台，例如，若在差旅场景中，服务提供方平台可为航空公司、铁路公司、公交公司等交通出行公司的平台，在此并不限定。
图1为本申请实施例提供的支付方法的场景架构的一示例的示意图。如图1所示，用户可通过终端设备11与代理平台12进行交互，代理平台12与转接平台13之间可进行交互，代理平台12与服务提供方平台14之间可进行交互，转接平台13与第三方平台15之间可进行交互，第三方平台15与服务提供方平台14之间可进行交互。
本申请第一方面提供一种支付方法，可应用于转接平台。图2为本申请第一方面提供的支付方法的一实施例的流程图。如图2所示，该支付方法可包括步骤S201至步骤S203。
在步骤S201中，接收代理平台发送的支付请求消息。
用户可通过终端设备向代理平台发起支付请求。对应地，代理平台响应于该支付请求，向转接平台发送支付请求消息。代理平台可托管支付方组织机构的账户。支付请求消息包括支付方组织机构标识和支付信息。
支付方组织机构标识用于指示支付方组织机构的账户。支付方组织机构为作为支付方的组织机构。组织机构具体可包括企业、事业单位、社会团体、机关等，在此并不限定。一个账户对应一个支付方组织机构，即一个支付方组织机构使用该支付方组织机构的账户，利用本申请实施例中的 支付方法进行支付。一个支付方组织机构可包括至少一个支付用户，即一个支付方组织机构与至少一个支付用户具有支付关联关系。该支付关联关系可预先建立。支付方组织机构中的支付用户共享支付方组织机构的账户。例如，在一个支付方组织机构包括多个支付用户的情况下，支付方组织机构中的多个用户均可使用该支付组织机构的账户进行支付。
支付信息包括进行支付所需的信息。在一些示例中，支付信息可包括支付用户信息、支付内容信息等，在此并不限定。支付用户信息用于指示支付用户，如支付用户信息可包括用户姓名、用户手机号、用户身份证号等，在此并不限定。支付内容信息可用于指示支付资源。支付内容信息还可用于指示支付商品等，在此并不限定。例如，支付内容信息可包括支付商品信息、支付资源信息等，在此并不限定。
在一些示例中，代理平台响应于用户通过终端设备向代理平台发起支付请求，还可向服务提供方平台发送服务请求。服务请求可包括支付方组织机构标识和支付信息，用于请求服务。例如，在差旅机票支付的场景中，代理平台响应于用户通过终端设备向代理平台发起的支付请求，向航空公司发送机票购票请求。
在步骤S202中，将支付请求消息向第三方平台转发。
支付请求消息用于指示第三方平台根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息。第三方平台可存储支付方组织机构的账户信息、支付方组织机构中用户的用户信息等，在此并不限定。在一些示例中，支付方组织机构的账户可由第三方平台分配。第三方平台可与一个或两个以上的支付方组织机构的账户对应。
第三方平台响应于支付请求消息，可向服务提供方平台发送服务获取请求消息。服务获取请求消息用于向服务提供方平台请求服务。服务可与支付方法的应用场景对应，可包括实体商品或服务等，在此并不限定。在一些示例中，在差旅支付的场景中，服务获取请求消息向服务提供方平台请求的服务可包括出行机票、出行车票、住宿预订等，在此并不限定。例如，在差旅机票支付的场景中，支付请求消息可用于指示第三方平台向航空公司平台发送请求机票的服务获取请求消息。又例如，在差旅住宿支付 的场景中，支付请求消息可用于指示第三方平台向酒店的服务平台发送请求预定住宿的服务获取请求消息。在另一些示例中，在公用物品购买支付的场景中，请求的服务可包括具体购买的公用物品，在此并不限定。
在一些示例中，第三方平台还可接收到个人账户的支付请求消息。第三方平台可通过支付请求消息中的账户标识来确定支付账户为支付方组织机构的账户还是个人账户。支付方组织机构标识可具有类型标识位，个人账户标识也可具有类型标识位。类型标识位可包括单位字符，也可包括多位字符，在此并不限定。支付方组织机构标识的类型标识位和个人账户的类型标识位不同。例如，支付方组织机构标识可为支付方组织机构的账户对应的虚拟卡的卡号，个人账户标识为个人账户的银行卡的卡号。支付方组织机构标识包括2字头的发行者标识代码(Issuer Identification Number，IIN)，个人账户标识包括非2字头的发行者标识代码。发行者标识代码可作为类型标识位，或者发行者标识代码的字头可作为类型标识位。
第三方平台可通过对账户标识的类型标识位的识别，确定支付请求消息中的账户标识是支付方组织机构标识还是个人账户标识。在确定支付请求消息中的账户标识为支付方组织机构标识的情况下，将支付请求消息向第三方平台转发。在确定支付请求消息中的账户标识为个人账户标识的情况下，将支付请求消息向个人账户管理平台如银行平台等转发。
在步骤S203中，根据支付方组织机构标识和支付信息，将第三方平台的支付资源转移至服务提供方平台的账户。
在支付成功的情况下，转接平台可将第三方平台中支付方组织机构标识指示的支付方组织机构的账户中与支付信息对应的支付资源转移至服务提供方平台的账户，以完成支付。在后续过程中，支付方组织机构可根据支付方组织机构内用户提供的发票、第三方平台提供的对账信息等，实现支付方组织机构与第三方平台之间的资源转移，具体地，这里的支付方组织机构与第三方平台之间的资源转移指支付方组织结构的账户向第三方平台转移待返还资源。待返还资源包括与第三方平台转移至服务提供方平台的账户的支付资源同等量的支付资源。
转接平台将第三方平台的支付资源转移至服务提供方平台的账户的时间并不限定。例如，转接平台将第三方平台的支付资源转移至服务提供方平台的账户可在支付的第二天执行，也可在支付的当天执行。
在本申请实施例中，代理平台、转接平台和第三方平台之间可通过包括支付方组织机构标识和支付信息的支付请求消息，向服务提供方平台请求服务，并可将第三方平台中与支付信息对应的支付资源直接转移至服务提供方平台的账户中，支付资源不需从用户的个人账户流出，后续过程中支付资源也不需要再次流入个人账户，能够快速地完成支付资源在支付方组织机构、第三方平台和服务提供方平台之间的流转，简化了支付资源的流转过程，减少了流转时间，提高了执行效率。
在本申请实施例中，代理平台与服务提供方平台之间的交互流程并未发生改变，能够降低现有架构的改造成本。在本申请实施例中，支付资源不需经过代理平台，减少了支付资源的流转环节，也降低了支付资源流转过程中的风险，提高了支付的安全性和可靠性。
在一些示例中，转接平台还可为第三方平台和服务提供方平台提供对账信息，以保证支付资源转移的准确性。图3为本申请第一方面提供的支付方法的另一实施例的流程图。图3与图2的不同之处在于，图3所示的支付方法还可包括步骤S204和步骤S205。
在步骤S204中，根据支付方组织机构标识和支付信息，生成对账信息。
为了简化流程，转接平台可周期性地根据支付方组织机构标识和支付信息，执行第三方平台的支付资源至服务提供方平台的账户的转移。例如，可转接平台可一天一结算，计算第三方平台一天内需要转移至服务提供方平台的账户的支付资源。为了方便第三方平台和服务提供方平台对账，转接平台可根据从支付请求消息中获取的支付方组织机构标识和支付信息，确定每个支付方组织机构的账户应转移的支付资源、第三方平台对应的各支付方组织机构的账户应转移的总的支付资源等，生成对账信息。对账信息可包括支付资源的明细、总量等，在此并不限定。
在步骤S205中，将对账信息分别向第三方平台和服务提供方平台发 送。
第三方平台和服务提供方平台可根据对账信息进行对账，以保证支付资源转移的准确性。
在一些示例中，支付方组织机构标识包括发行方标识位。发行方标识位用于标识生成并下发支付方组织机构的账户的第三方平台。通过发行方标识位，转接平台可将支付请求消息转发至准确的第三方平台。图4为本申请第一方面提供的支付方法的又一实施例的流程图。图4与图2的不同之处在于，图2中的步骤S202可具体细化为图4中的步骤S2021和步骤S2022。
在步骤S2021中，识别支付方组织机构标识中发行方标识位，确定发行方标识位对应的第三方平台。
具有生成并下发支付方组织机构的账户的第三方平台可为一个，也可为两个以上，在此并不限定。在具有两个以上的第三方平台的情况下，转接平台可在支付方组织机构标识中识别发行方标识位，根据发行方标识位，确定生成及下发支付方组织机构的账户的第三方平台，以便于将支付请求消息转发给该第三方平台。
在一些示例中，发行方标识位可包括发行者标识代码或其他代码等，在此并不限定。发行方标识位的具体内容可参见上述实施例中的相关说明，在此不再赘述。
在步骤S2022中，将支付请求消息向发行方标识位对应的第三方平台转发。
在一些示例中，转接平台还可确定第三方平台是否具有生成及下发支付方组织机构的账户的权限。图5为本申请第一方面提供的支付方法的再一实施例的流程图。图5与图2的不同之处在于，图5所示的支付方法还可包括步骤S206和步骤S207。
在步骤S206中，接收第三方平台发送的账户下发权限请求消息。
账户下发权限请求消息包括第三方平台的机构资质信息。第三方平台的机构资质信息用于表征第三方平台具备的条件、资格、能力等。转接平台可根据账户下发权限请求消息包括的第三方平台的机构资质信息，确定 是否为第三方平台开通生成及下发支付方组织机构的账户的权限。
在步骤S207中，在第三方平台的机构资质信息满足预设的权限开通条件的情况下，向第三方平台发送权限开通成功消息。
权限开通条件可根据具体场景和需求设定，在此并不限定。第三方平台的机构资质信息满足权限开通条件，表示第三方平台具有能够生成及下发支付方组织机构的账户的资质，向第三方平台发送权限开通成功消息。权限开通成功消息表征第三方平台具有生成及下发支付方组织机构的账户的权限。
第三方平台的机构资质信息不满足权限开通条件，表示第三方平台没有能够生成及下发支付方组织机构的账户的资质，可不向第三方平台发送权限开通成功消息，或向第三方平台发送权限开通失败消息。权限开通失败消息表征第三方平台不具有生成及下发支付方组织机构的账户的权限。
本申请第二方面提供一种支付方法，可应用于第三方平台。图6为本申请第二方面提供的支付方法的一实施例的流程图。如图6所示，该支付方法可包括步骤S301和步骤S302。
在步骤S301中，接收转接平台发送的支付请求消息。
支付请求消息包括支付方组织机构标识和支付信息。支付方组织机构标识用于指示支付方组织机构的账户。
在一些示例中，支付方组织机构标识可包括发行方标识位。发行方标识位用于标识生成及下发支付方组织机构的账户的第三方平台。发行方标识位的具体内容可参见上述实施例中的相关说明，在此不再赘述。
在一些示例中，支付信息可包括支付用户信息和支付内容信息。支付用户信息用于指示支付用户。支付内容信息用于指示支付资源。
在一些示例中，一个支付方组织机构的账户与至少一个支付用户具有支付关联关系。与支付方组织机构的账户具有支付关联关系的支付用户可利用该支付方组织机构的账户发起支付。在一个支付方组织机构的账户与两个以上的支付用户具有支付关联关系的情况下，这两个以上的支付用户均可利用该支付方组织机构的账户发起支付。
支付请求消息、支付方组织机构标识、支付信息可参见上述实施例中 的相关说明，在此不再赘述。
在步骤S302中，根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息。
服务获取请求消息可包括支付方组织机构标识和支付信息。服务提供方平台响应于该服务获取请求消息，可提供服务获取请求消息请求的服务。例如，服务提供方平台为航空公司平台，在第三方平台向航空公司平台发送服务获取请求消息之前，航空公司可接收代理平台发起的服务请求。航空公司平台在接收到服务获取请求消息的情况下，可核对服务获取请求消息中的支付方组织机构标识和支付信息，与代理平台发起的服务请求携带的支付方组织机构标识和支付信息是否一致。在服务获取请求消息中的支付方组织机构标识和支付信息，与代理平台发起的服务请求携带的支付方组织机构标识和支付信息一致的情况下，航空公司平台提供对应的服务即出票。
其中，在服务提供平台响应于服务获取请求消息提供服务的情况下，第三方平台的支付资源由转接平台控制转移至服务提供方平台的账户。第三方平台的账户可受转接平台管理，转接平台将第三方平台的账户中的支付资源转移至服务提供方平台的账户，即支付资源从第三方平台流转至服务提供方平台，以实现支付资源的流转。
在一些示例中，为了避免没有支付方组织机构的账户的使用权限的用户利用支付方组织机构的账户进行支付。第三方平台可对支付信息中的支付用户信息进行验证。具体地，可验证支付方组织机构标识指示的支付方组织机构的账户与支付信息中支付用户信息指示的支付用户是否具有支付关联关系。在验证成功即在支付方组织机构标识指示的支付方组织机构的账户与支付信息中支付用户信息指示的支付用户具有支付关联关系的情况下，向服务提供方平台发送服务获取请求消息。在验证失败即在支付方组织机构标识指示的支付方组织机构的账户与支付信息中支付用户信息指示的支付用户不具有支付关联关系的情况下，拒绝向服务提供方平台发送服务获取请求消息。通过对支付用户信息进行验证，能够避免非法支付，从而提高支付的安全性和可靠性。
在本申请实施例中，代理平台、转接平台和第三方平台之间可通过包括支付方组织机构标识和支付信息的支付请求消息，向服务提供方平台请求服务，并可将第三方平台中与支付信息对应的支付资源直接转移至服务提供方平台的账户中，支付资源不需从用户的个人账户流出，后续过程中支付资源也不需要再次流入个人账户，能够快速地完成支付资源在支付方组织机构、第三方平台和服务提供方平台之间的流转，简化了支付资源的流转过程，减少了流转时间，提高了执行效率。
在本申请实施例中，支付资源不需经过代理平台，减少了支付资源的流转环节，也降低了支付资源流转过程中的风险，提高了支付的安全性和可靠性。
在一些示例中，第三方平台还可与服务提供方平台进行对账。图7为本申请第二方面提供的支付方法的另一实施例的流程图。图7与图6的不同之处在于，图7所示的支付方法还可包括步骤S303。
在步骤S303中，接收转接平台发送的对账信息。
对账信息由转接平台根据支付方组织机构标识和支付信息生成。对账信息的具体内容可参见上述实施例中的相关说明，在此不再赘述。
通过对账信息，第三方平台可与服务提供方平台进行对账，从而能够保证支付的准确性和可靠性。
在一些示例中，第三方平台还可向转接平台请求生成及下发支付方组织机构的账户的权限。在第三方平台具有生成及下发支付方组织机构的账户的权限的情况下，第三方平台才能够生成及下发支付方组织机构的账户，才能够对支付方组织机构的账户进行管理。图8为本申请第二方面提供的支付方法的又一实施例的流程图。图8与图6的不同之处在于，图8所示的支付方法还可包括步骤S304和步骤S305。
在步骤S304中，向转接平台发送账户下发权限请求消息。
账户下发权限请求消息包括第三方平台的机构资质信息，用于向转接平台请求生成及下发支付方组织机构的账户的权限。
在步骤S305中，接收转接平台发送的权限开通成功消息。
权限开通成功消息由转接平台在第三方平台的机构资质信息满足预设 的权限开通条件的情况下发送。权限开通成功消息表征第三方平台具有生成及下发支付方组织机构的账户的权限。即在第三方平台的机构资质信息满足权限开通条件的情况下，第三方平台才具有生成及下发支付方组织机构的账户的权限。在第三方平台的机构资质信息不满足权限开通条件的情况下，第三方平台不具有生成及下发支付方组织机构的账户的权限。
转接平台的权限高于第三方平台，可对第三方平台进行管理。转接平台具有为第三方平台开通生成及下发支付方组织机构的账户的权限的权限。通过转接平台对第三方平台的授权，便于对第三方平台进行规范化管理，且能够避免资质不足以进行上述支付方法的第三方平台参与本申请实施例中的支付过程，提高支付的安全性和可靠性。
在一些示例中，在第三方平台具有生成及下发支付方组织机构的账户的权限的情况下，第三方平台可为支付方组织机构生成及下发账户。图9为本申请第二方面提供的支付方法的再一实施例的流程图。图9与图6的不同之处在于，图9所示的支付方法还可包括步骤S306至步骤S308。
在步骤S306中，接收支付方组织机构通过终端设备发送的账户申请消息。
账户申请消息包括支付方组织机构的资质信息，用于申请支付方组织机构的账户。支付方组织机构的资质信息用于表征支付方组织机构就别的条件、资格、能力等。
在步骤S307中，响应于账户申请消息，为支付方组织机构分配账户。
转接平台为不同的支付方组织机构分配不同的账户。具体地，转接屏体可为支付方组织机构分配账户号码。例如，转接平台可为支付方组织机构分配16位至19位包括2字头的发行者标识代码的账户号码。
在步骤S308中，根据支付方组织机构的资质信息，为支付方组织机构的账户设置账户信用权限。
账户信用权限可包括账户所具有的权限内容，该权限内容与资质信息等相关。在一些示例中，账户信用权限可包括资源转移时间限制和信用资源量。资源转移时间限制可指示支付方组织机构的账户将待返还资源转移 至第三方平台的时间限制。例如，资源转移时间限制为5天，则在第三方平台将支付资源转移至服务方提供平台后的5天内，支付方组织结构的账户需要将待返还资源转移至第三方平台。在一些示例中，支付方组织机构的资质信息表征的支付方组织机构具备的条件、资格、能力越高，资源转移时间限制所指示的时长可越长，即资源转移时间限制所指示的时长与资质信息表征的支付方组织机构具备的条件、资格、能力的高低正相关。信用资源量可指示第三方平台为支付方组织机构设置的授信资源量。在支付方组织机构的账户与第三方平台之间的待返还资源的量超过信用资源量的情况下，第三方平台拒绝执行与该支付方组织机构的账户相关的支付。待返还资源包括与第三方平台转移至服务提供方平台的账户的支付资源同等量的支付资源。在一些示例中，支付方组织机构的资质信息表征的支付方组织机构具备的条件、资格、能力越高，信用资源量所指示的授信资源量可越大，即信用资源量所指示的授信资源量与资质信息表征的支付方组织机构具备的条件、资格、能力的高低正相关。
上述实施例中的支付资源可包括支付资金、支付积分、支付虚拟货币等，在此并不限定。
下面一具体示例说明应用于终端设备、代理平台、转接平台、第三方平台、服务提供方平台的本申请实施例中的支付方法。图10为本申请实施例提供的支付流程的一示例的流程图。如图10所示，该支付方法可包括步骤S401至步骤S414。
在步骤S401中，第三方平台向转接平台发送账户下发权限请求消息。
在步骤S402中，在第三方平台的机构资质信息满足预设的权限开通条件的情况下，转接平台向第三方平台发送权限开通成功消息。
在步骤S403中，终端设备向第三方平台发送账户申请消息。
在步骤S404中，第三方平台响应于账户申请消息，为支付方组织机构分配账户。
在步骤S405中，根据支付方组织机构的资质信息，为支付方组织机构的账户设置账户信用权限。
在步骤S406中，终端设备响应于用户的输入操作，向代理平台发送支付请求。
在步骤S407中，代理平台响应于支付请求，向服务提供方平台发送服务请求。
在步骤S408中，代理平台响应于支付请求，向转接平台发送支付请求消息。
在步骤S409中，转接平台将支付请求消息向第三方平台转发。
在步骤S410中，第三方平台根据支付请求消息中的支付方组织机构标识和支付信息，向服务提供方平台发送服务获取请求消息。
在步骤S411中，服务提供方平台响应于服务获取请求消息，提供服务。
在步骤S412中，在结算周期结束时，转接平台将生成的对账信息向第三方平台发送。
在步骤S413中，在结算周期结束时，转接平台将生成的对账信息向服务提供方平台发送。
在步骤S414中，在结算周期结束后的第一时间段内，转接平台将第三方平台的支付资源转移至服务提供方平台的账户。
在转接平台将第三方平台的支付资源转移至服务提供方平台的账户后的第二时间段内，与支付资源等量的资源从支付组织机构的账户转移至第三方平台。
本申请第三方面提供一种转接平台设备。图11为本申请第三方面提供的转接平台设备的一实施例的结构示意图。如图11所示，该转接平台设备500可包括接收模块501、发送模块502和资源转移模块503。
接收模块501可用于接收代理平台发送的支付请求消息。
支付请求消息包括支付方组织机构标识和支付信息。支付方组织机构标识用于指示支付方组织机构的账户。
在一些示例中，支付信息包括支付用户信息和支付内容信息。支付用户信息用于指示支付用户。支付内容信息用于指示支付资源。
在一些示例中，一个支付方组织机构的账户与至少一个支付用户具有 支付关联关系。
发送模块502可用于将支付请求消息向第三方平台转发。
支付请求消息用于指示第三方平台根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息。
资源转移模块503可用于根据支付方组织机构标识和支付信息，将第三方平台的支付资源转移至服务提供方平台的账户。
在本申请实施例中，代理平台、转接平台设备对应的转接平台和第三方平台之间可通过包括支付方组织机构标识和支付信息的支付请求消息，向服务提供方平台请求服务，并可将第三方平台中与支付信息对应的支付资源直接转移至服务提供方平台的账户中，支付资源不需从用户的个人账户流出，后续过程中支付资源也不需要再次流入个人账户，能够快速地完成支付资源在支付方组织机构、第三方平台和服务提供方平台之间的流转，简化了支付资源的流转过程，减少了流转时间，提高了执行效率。
在本申请实施例中，代理平台与服务提供方平台之间的交互流程并未发生改变，能够降低现有架构的改造成本。在本申请实施例中，支付资源不需经过代理平台，减少了支付资源的流转环节，也降低了支付资源流转过程中的风险，提高了支付的安全性和可靠性。
在一些示例中，转接平台设备还可包括对账信息生成模块。对账信息生成模块可用于根据支付方组织机构标识和支付信息，生成对账信息。
上述实施例中的发送模块502还可用于将对账信息分别向第三方平台和服务提供方平台发送。
在一些示例中，支付方组织机构标识包括发行方标识位。发行方标识位用于标识生成并下发支付方组织机构的账户的第三方平台。
上述实施例中的转接平台设备500还可包括识别模块。识别模块可用于识别支付方组织机构标识中发行方标识位，确定发行方标识位对应的第三方平台。
上述实施例中的发送模块502可用于将支付请求消息向发行方标识位对应的第三方平台转发。
在一些示例中，上述实施例中的接收模块501还可用于接收第三方平 台发送的账户下发权限请求消息。账户下发权限请求消息包括第三方平台的机构资质信息。
上述实施例中的发送模块502还可用于在第三方平台的机构资质信息满足预设的权限开通条件的情况下，向第三方平台发送权限开通成功消息。权限开通成功消息表征第三方平台具有生成及下发支付方组织机构的账户的权限。
本申请第四方面提供一种第三方平台设备。图12为本申请第四方面提供的第三方平台设备的一实施例的结构示意图。如图12所示，第三方平台设备600可包括接收模块601和发送模块602。
接收模块601可用于接收转接平台发送的支付请求消息。
支付请求消息包括支付方组织机构标识和支付信息。支付方组织机构标识用于指示支付方组织机构的账户。
在一些示例中，支付信息包括支付用户信息和支付内容信息。支付用户信息用于指示支付用户。支付内容信息用于指示支付资源。
在一些示例中，一个支付方组织机构的账户与至少一个支付用户具有支付关联关系。
发送模块602可用于根据支付方组织机构标识和支付信息向服务提供方平台发送服务获取请求消息。
其中，在服务提供平台响应于服务获取请求消息提供服务的情况下，第三方平台设备对应的第三方平台的支付资源由转接平台控制转移至服务提供方平台的账户。
在本申请实施例中，代理平台、转接平台和第三方平台之间可通过包括支付方组织机构标识和支付信息的支付请求消息，向服务提供方平台请求服务，并可将第三方平台中与支付信息对应的支付资源直接转移至服务提供方平台的账户中，支付资源不需从用户的个人账户流出，后续过程中支付资源也不需要再次流入个人账户，能够快速地完成支付资源在支付方组织机构、第三方平台和服务提供方平台之间的流转，简化了支付资源的流转过程，减少了流转时间，提高了执行效率。
在本申请实施例中，支付资源不需经过代理平台，减少了支付资源的 流转环节，也降低了支付资源流转过程中的风险，提高了支付的安全性和可靠性。
在一些示例中，上述实施例中的发送模块602还可用于在支付方组织机构标识指示的支付方组织机构的账户与支付信息中支付用户信息指示的支付用户具有支付关联关系的情况下，向服务提供方平台发送服务获取请求消息。
在一些示例中，上述实施例中的接收模块601还可用于接收转接平台发送的对账信息，对账信息由转接平台根据支付方组织机构标识和支付信息生成。
在一些示例中，上述实施例中的发送模块602还可用于向转接平台发送账户下发权限请求消息，账户下发权限请求消息包括第三方平台的机构资质信息。
上述实施例中的接收模块601还可用于接收转接平台发送的权限开通成功消息。权限开通成功消息由转接平台在第三方平台的机构资质信息满足预设的权限开通条件的情况下发送。权限开通成功消息表征第三方平台具有生成及下发支付方组织机构的账户的权限。
在一些示例中，上述实施例中的接收模块601还可用于接收支付方组织机构通过终端设备发送的账户申请消息。账户申请消息包括支付方组织机构的资质信息
第三方平台设备600还可包括账户分配模块和权限设置模块。账户分配模块可用于响应于账户申请消息，为支付方组织机构分配账户。权限设置模块可用于根据支付方组织机构的资质信息，为支付方组织机构的账户设置账户信用权限。
在一些示例中，支付方组织机构标识包括发行方标识位。发行方标识位用于标识生成及下发支付方组织机构的账户的第三方平台。
本申请第五方面提供一种转接平台设备。图13为本申请第五方面提供的转接平台设备的一实施例的硬件结构示意图。如图13所示，转接平台设备700包括存储器701、处理器702及存储在存储器701上并可在处理器702上运行的计算机程序。
在一个示例中，上述处理器702可以包括中央处理器(CPU)，或者特定集成电路(Application Specific Integrated Circuit，ASIC)，或者可以被配置成实施本申请实施例的一个或多个集成电路。
存储器701可包括只读存储器(Read-Only Memory，ROM)，随机存取存储器(Random Access Memory，RAM)，磁盘存储介质设备，光存储介质设备，闪存设备，电气、光学或其他物理/有形的存储器存储设备。因此，通常，存储器包括一个或多个编码有包括计算机可执行指令的软件的有形(非暂态)计算机可读存储介质(例如，存储器设备)，并且当该软件被执行(例如，由一个或多个处理器)时，其可操作来执行参考根据本申请第一方面的支付方法所描述的操作。
处理器702通过读取存储器701中存储的可执行程序代码来运行与可执行程序代码对应的计算机程序，以用于实现上述实施例中第一方面的支付方法。
在一个示例中，转接平台设备700还可包括通信接口703和总线704。其中，如图13所示，存储器701、处理器702、通信接口703通过总线704连接并完成相互间的通信。
通信接口703，主要用于实现本申请实施例中各模块、装置、单元和/或设备之间的通信。也可通过通信接口703接入输入设备和/或输出设备。
总线704包括硬件、软件或两者，将转接平台设备700的部件彼此耦接在一起。举例来说而非限制，总线704可包括加速图形端口(Accelerated Graphics Port，AGP)或其他图形总线、增强工业标准架构(Enhanced Industry Standard Architecture，EISA)总线、前端总线(Front Side Bus，FSB)、超传输(Hyper Transport，HT)互连、工业标准架构(Industry Standard Architecture，ISA)总线、无限带宽互连、低引脚数(Low pin count，LPC)总线、存储器总线、微信道架构(Micro Channel Architecture，MCA)总线、外围组件互连(Peripheral Component Interconnect，PCI)总线、PCI-Express(PCI-E)总线、串行高级技术附件(Serial Advanced Technology Attachment，SATA)总线、视频电子标准协会局部(Video Electronics Standards Association Local Bus，VLB)总线或 其他合适的总线或者两个或更多个以上这些的组合。在合适的情况下，总线704可包括一个或多个总线。尽管本申请实施例描述和示出了特定的总线，但本申请考虑任何合适的总线或互连。
本申请第六方面提供一种第三方平台设备。图14为本申请第六方面提供的第三方平台设备的一实施例的硬件结构示意图。如图14所示，第三方平台设备800包括存储器801、处理器802及存储在存储器801上并可在处理器802上运行的计算机程序。
在一个示例中，上述处理器802可以包括中央处理器(CPU)，或者特定集成电路(Application Specific Integrated Circuit，ASIC)，或者可以被配置成实施本申请实施例的一个或多个集成电路。
存储器801可包括只读存储器(Read-Only Memory，ROM)，随机存取存储器(Random Access Memory，RAM)，磁盘存储介质设备，光存储介质设备，闪存设备，电气、光学或其他物理/有形的存储器存储设备。因此，通常，存储器包括一个或多个编码有包括计算机可执行指令的软件的有形(非暂态)计算机可读存储介质(例如，存储器设备)，并且当该软件被执行(例如，由一个或多个处理器)时，其可操作来执行参考根据本申请第二方面的支付方法所描述的操作。
处理器802通过读取存储器801中存储的可执行程序代码来运行与可执行程序代码对应的计算机程序，以用于实现上述实施例中第二方面的支付方法。
在一个示例中，第三方平台设备800还可包括通信接口803和总线804。其中，如图14所示，存储器801、处理器802、通信接口803通过总线804连接并完成相互间的通信。
通信接口803，主要用于实现本申请实施例中各模块、装置、单元和/或设备之间的通信。也可通过通信接口803接入输入设备和/或输出设备。
总线804包括硬件、软件或两者，将第三方平台设备800的部件彼此耦接在一起。举例来说而非限制，总线804可包括加速图形端口(Accelerated Graphics Port，AGP)或其他图形总线、增强工业标准架构(Enhanced Industry Standard Architecture，EISA)总线、前端总线(Front  Side Bus，FSB)、超传输(Hyper Transport，HT)互连、工业标准架构(Industry Standard Architecture，ISA)总线、无限带宽互连、低引脚数(Low pin count，LPC)总线、存储器总线、微信道架构(Micro Channel Architecture，MCA)总线、外围组件互连(Peripheral Component Interconnect，PCI)总线、PCI-Express(PCI-E)总线、串行高级技术附件(Serial Advanced Technology Attachment，SATA)总线、视频电子标准协会局部(Video Electronics Standards Association Local Bus，VLB)总线或其他合适的总线或者两个或更多个以上这些的组合。在合适的情况下，总线804可包括一个或多个总线。尽管本申请实施例描述和示出了特定的总线，但本申请考虑任何合适的总线或互连。
本申请第七方面提供一种支付系统，该支付系统可包括上述实施例中的转接平台设备和第三方平台设备，即该支付系统可包括上述实施例中的转接平台和第三方平台。
在一些示例中，上述支付系统还可包括代理平台设备、服务提供方平台设备、终端设备中的一类或两类以上，即上述支付系统还可包括代理平台、服务提供方平台、终端设备中的一类或两类以上，在此并不限定。
支付系统中代理平台、终端设备、转接平台、第三方平台、服务提供方平台的具体内容可参见上述实施例中的相关说明，在此不再赘述。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序指令，该计算机程序指令被处理器执行时可实现上述实施例中的第一方面的支付方法或第二方面的支付方法，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，上述计算机可读存储介质可包括非暂态计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等，在此并不限定。
需要明确的是，本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同或相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。对于平台设备实施例、系统实施例、计算机可读存储介质实施例而言，相关之处可以参见方法实施例的说明部分。本 申请并不局限于上文所描述并在图中示出的特定步骤和结构。本领域的技术人员可以在领会本申请的精神之后，作出各种改变、修改和添加，或者改变步骤之间的顺序。并且，为了简明起见，这里省略对已知方法技术的详细描述。
上面参考根据本申请的实施例的方法、装置(系统)和计算机程序产品的流程图和/或框图描述了本申请的各方面。应当理解，流程图和/或框图中的每个方框以及流程图和/或框图中各方框的组合可以由计算机程序指令实现。这些计算机程序指令可被提供给通用计算机、专用计算机、或其它可编程数据处理装置的处理器，以产生一种机器，使得经由计算机或其它可编程数据处理装置的处理器执行的这些指令使能对流程图和/或框图的一个或多个方框中指定的功能/动作的实现。这种处理器可以是但不限于是通用处理器、专用处理器、特殊应用处理器或者现场可编程逻辑电路。还可理解，框图和/或流程图中的每个方框以及框图和/或流程图中的方框的组合，也可以由执行指定的功能或动作的专用硬件来实现，或可由专用硬件和计算机指令的组合来实现。
本领域技术人员应能理解，上述实施例均是示例性而非限制性的。在不同实施例中出现的不同技术特征可以进行组合，以取得有益效果。本领域技术人员在研究附图、说明书及权利要求书的基础上，应能理解并实现所揭示的实施例的其他变化的实施例。在权利要求书中，术语“包括”并不排除其他装置或步骤；数量词“一个”不排除多个；术语“第一”、“第二”用于标示名称而非用于表示任何特定的顺序。权利要求中的任何附图标记均不应被理解为对保护范围的限制。权利要求中出现的多个部分的功能可以由一个单独的硬件或软件模块来实现。某些技术特征出现在不同的从属权利要求中并不意味着不能将这些技术特征进行组合以取得有益效果。

Claims (20)

  1. 一种支付方法，应用于转接平台，所述方法包括：
    接收代理平台发送的支付请求消息，所述支付请求消息包括支付方组织机构标识和支付信息，所述支付方组织机构标识用于指示支付方组织机构的账户；
    将所述支付请求消息向第三方平台转发，所述支付请求消息用于指示所述第三方平台根据所述支付方组织机构标识和所述支付信息向服务提供方平台发送服务获取请求消息；
    根据所述支付方组织机构标识和支付信息，将第三方平台的支付资源转移至所述服务提供方平台的账户。
  2. 根据权利要求1所述的方法，其中，所述支付信息包括支付用户信息和支付内容信息，所述支付用户信息用于指示支付用户，所述支付内容信息用于指示支付资源。
  3. 根据权利要求2所述的方法，其中，一个所述支付方组织机构的账户与至少一个所述支付用户具有支付关联关系。
  4. 根据权利要求1所述的方法，在所述将所述支付请求消息向第三方平台转发之后，还包括：
    根据所述支付方组织机构标识和所述支付信息，生成对账信息；
    将所述对账信息分别向第三方平台和服务提供方平台发送。
  5. 根据权利要求1所述的方法，其中，所述支付方组织机构标识包括发行方标识位，所述发行方标识位用于标识生成并下发所述支付方组织机构的账户的所述第三方平台；
    所述将所述支付请求消息向第三方平台转发，包括：
    识别所述支付方组织机构标识中所述发行方标识位，确定所述发行方标识位对应的所述第三方平台；
    将所述支付请求消息向所述发行方标识位对应的所述第三方平台转发。
  6. 根据权利要求1所述的方法，还包括：
    接收所述第三方平台发送的账户下发权限请求消息，所述账户下发权限请求消息包括所述第三方平台的机构资质信息；
    在所述第三方平台的机构资质信息满足预设的权限开通条件的情况下，向所述第三方平台发送权限开通成功消息，所述权限开通成功消息表征所述第三方平台具有生成及下发支付方组织机构的账户的权限。
  7. 一种支付方法，应用于第三方平台，所述方法包括：
    接收转接平台发送的支付请求消息，所述支付请求消息包括支付方组织机构标识和支付信息，所述支付方组织机构标识用于指示支付方组织机构的账户；
    根据所述支付方组织机构标识和所述支付信息向服务提供方平台发送服务获取请求消息；
    其中，在所述服务提供平台响应于所述服务获取请求消息提供服务的情况下，所述第三方平台的支付资源由转接平台控制转移至所述服务提供方平台的账户。
  8. 根据权利要求7所述的方法，其中，所述支付信息包括支付用户信息和支付内容信息，所述支付用户信息用于指示支付用户，所述支付内容信息用于指示支付资源。
  9. 根据权利要求8所述的方法，其中，一个所述支付方组织机构的账户与至少一个所述支付用户具有支付关联关系。
  10. 根据权利要求9所述的方法，其中，所述根据所述支付方组织机构标识和所述支付信息向服务提供方平台发送服务获取请求消息，包括：
    在所述支付方组织机构标识指示的支付方组织机构的账户与所述支付信息中所述支付用户信息指示的支付用户具有所述支付关联关系的情况下，向所述服务提供方平台发送所述服务获取请求消息。
  11. 根据权利要求7所述的方法，在所述根据所述支付方组织机构标识和所述支付信息向服务提供方平台发送服务获取请求消息之后，还包括：
    接收所述转接平台发送的对账信息，所述对账信息由所述转接平台根据所述支付方组织机构标识和所述支付信息生成。
  12. 根据权利要求7所述的方法，还包括：
    向所述转接平台发送账户下发权限请求消息，所述账户下发权限请求消息包括所述第三方平台的机构资质信息；
    接收所述转接平台发送的权限开通成功消息，所述权限开通成功消息由所述转接平台在所述第三方平台的机构资质信息满足预设的权限开通条件的情况下发送，所述权限开通成功消息表征所述第三方平台具有生成及下发支付方组织机构的账户的权限。
  13. 根据权利要求7所述的方法，还包括：
    接收支付方组织机构通过终端设备发送的账户申请消息，所述账户申请消息包括支付方组织机构的资质信息；
    响应于所述账户申请消息，为支付方组织机构分配账户；
    根据支付方组织机构的资质信息，为支付方组织机构的账户设置账户信用权限。
  14. 根据权利要求7所述的方法，其中，所述支付方组织机构标识包括发行方标识位，所述发行方标识位用于标识生成及下发所述支付方组织机构的账户的所述第三方平台。
  15. 一种转接平台设备，包括：
    接收模块，用于接收代理平台发送的支付请求消息，所述支付请求消息包括支付方组织机构标识和支付信息，所述支付方组织机构标识用于指示支付方组织机构的账户；
    发送模块，用于将所述支付请求消息向第三方平台转发，所述支付请求消息用于指示所述第三方平台根据所述支付方组织机构标识和所述支付信息向服务提供方平台发送服务获取请求消息；
    资源转移模块，用于根据所述支付方组织机构标识和支付信息，将第三方平台的支付资源转移至所述服务提供方平台的账户。
  16. 一种第三方平台设备，包括：
    接收模块，用于接收转接平台发送的支付请求消息，所述支付请求消息包括支付方组织机构标识和支付信息，所述支付方组织机构标识用于指示支付方组织机构的账户；
    发送模块，用于根据所述支付方组织机构标识和所述支付信息向服务提供方平台发送服务获取请求消息；
    其中，在所述服务提供平台响应于所述服务获取请求消息提供服务的情况下，所述第三方平台设备对应的第三方平台的支付资源由转接平台控制转移至所述服务提供方平台的账户。
  17. 一种转接平台设备，包括：处理器以及存储有计算机程序指令的存储器；
    所述处理器执行所述计算机程序指令时实现如权利要求1至6中任意一项所述的支付方法。
  18. 一种第三方平台设备，包括：处理器以及存储有计算机程序指令的存储器；
    所述处理器执行所述计算机程序指令时实现如权利要求7至14中任意一项所述的支付方法。
  19. 一种支付系统，包括如权利要求17所述的转接平台设备和如权利要求18所述的第三方平台设备。
  20. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序指令，所述计算机程序指令被处理器执行时实现如权利要求1至14中任意一项所述的支付方法。
PCT/CN2022/075806 2021-04-21 2022-02-10 支付方法、平台设备、系统及存储介质 WO2022222581A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110429874.9A CN113222570B (zh) 2021-04-21 2021-04-21 支付方法、平台设备、系统及存储介质
CN202110429874.9 2021-04-21

Publications (1)

Publication Number Publication Date
WO2022222581A1 true WO2022222581A1 (zh) 2022-10-27

Family

ID=77088192

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/075806 WO2022222581A1 (zh) 2021-04-21 2022-02-10 支付方法、平台设备、系统及存储介质

Country Status (2)

Country Link
CN (1) CN113222570B (zh)
WO (1) WO2022222581A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113222570B (zh) * 2021-04-21 2024-02-23 中国银联股份有限公司 支付方法、平台设备、系统及存储介质
CN114707976A (zh) * 2022-03-24 2022-07-05 中国银联股份有限公司 支付方法、用户终端、装置、设备、系统及介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007010353A1 (en) * 2005-07-15 2007-01-25 Donald, Heather, June A system to enable a user to effect a payment to a third party and a method of operating the system
CN109801049A (zh) * 2017-11-15 2019-05-24 腾讯科技（深圳）有限公司 资源转移方法和装置、计算机设备和存储介质
CN110782320A (zh) * 2019-10-25 2020-02-11 上海燕汐软件信息科技有限公司 一种订单处理方法、装置、订单报消系统及存储介质
US20200126052A1 (en) * 2018-10-17 2020-04-23 American Express Travel Related Services Company, Inc. Transfers using credit accounts
CN112669042A (zh) * 2021-03-15 2021-04-16 中国银联股份有限公司 支付方法、服务器、用户终端、系统及存储介质
CN113222570A (zh) * 2021-04-21 2021-08-06 中国银联股份有限公司 支付方法、平台设备、系统及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007010353A1 (en) * 2005-07-15 2007-01-25 Donald, Heather, June A system to enable a user to effect a payment to a third party and a method of operating the system
CN109801049A (zh) * 2017-11-15 2019-05-24 腾讯科技（深圳）有限公司 资源转移方法和装置、计算机设备和存储介质
US20200126052A1 (en) * 2018-10-17 2020-04-23 American Express Travel Related Services Company, Inc. Transfers using credit accounts
CN110782320A (zh) * 2019-10-25 2020-02-11 上海燕汐软件信息科技有限公司 一种订单处理方法、装置、订单报消系统及存储介质
CN112669042A (zh) * 2021-03-15 2021-04-16 中国银联股份有限公司 支付方法、服务器、用户终端、系统及存储介质
CN113222570A (zh) * 2021-04-21 2021-08-06 中国银联股份有限公司 支付方法、平台设备、系统及存储介质

Also Published As

Publication number Publication date
CN113222570B (zh) 2024-02-23
CN113222570A (zh) 2021-08-06

Similar Documents

Publication Publication Date Title
JP6926271B2 (ja) 既存の支払ネットワーク上でブロックチェーンを基礎としたトランザクションを処理する方法及びシステム
US10942918B2 (en) Self-cleaning token vault
CN109196535B (zh) 电子支付系统及其方法
WO2022222581A1 (zh) 支付方法、平台设备、系统及存储介质
US20170091759A1 (en) Token provisioning for non-account holder use with limited transaction functions
US20160119296A1 (en) Token Enrollment System and Method
JP2018518758A (ja) ブロックチェーンを基礎としたトランザクションのために交換処理とイシュア処理とを統合する方法及びシステム
JP2018518759A (ja) ブロックチェーンを基礎とした資産を不換通貨アカウントへリンクさせる方法及びシステム
US11087312B2 (en) Account tokenization for virtual currency resources
CN107204957B (zh) 一种账号绑定和业务处理的方法及装置
CN103975352A (zh) 可安全充值的电子钱包
CN108140181B (zh) 管理令牌化系统中的客户唯一性
WO2022222808A1 (zh) 基于报销码的数据处理的方法及装置
JP2019520658A (ja) 注文情報処理方法、装置およびシステム
WO2022052894A1 (zh) 资源处理方法、服务器、终端、设备、系统及存储介质
US20190362348A1 (en) Merchant enrollment for reverse payments
TW201535292A (zh) 用於促進金融貸款之系統及方法
WO2023178924A1 (zh) 支付方法、用户终端、装置、设备、系统及介质
WO2019242342A1 (zh) 一种信用退税方法、装置、系统及电子设备
CN111784347B (zh) 一种资源转移方法及装置
CN110400139B (zh) 基于对公数字钱包的支付方法、装置及系统
CN105931035A (zh) 一种支付标记生成方法及装置
CN112074835A (zh) 执行安全操作的技术
TW201606678A (zh) 用以提供信貸之系統及方法
TWI528302B (zh) System and Method of Application for Wallet

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: 22790691

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22790691

Country of ref document: EP

Kind code of ref document: A1