CN113222570B - Payment method, platform device, system and storage medium - Google Patents

Abstract

This application discloses a payment method, platform equipment, system and storage medium, which belongs to the field of data processing. The method is applied to the transfer platform and includes: receiving a payment request message sent by the agency platform. The payment request message includes the payer organization identification and payment information. The payer organization identification is used to indicate the account of the payer organization; sending the payment request The message is forwarded 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 based on the payer's organization identification and payment information; based on the payer's organization identification and payment information, the third-party platform The payment resources are transferred to the account of the service provider platform. According to the embodiments of the present application, the efficiency of resource transfer execution can be improved.

Description

Payment methods, platform equipment, systems and storage media

Technical field

This application belongs to the field of data processing, and in particular relates to a payment method, platform equipment, system and storage medium.

Background technique

With the continuous development of electronic information technology, electronic information technology is being used in more and more business fields, such as shopping and travel, etc., which has brought great convenience to people's life, work and study.

In the course of work, employees in the organization need to travel to complete work delivered by the organization, or need to help the organization purchase supplies needed by the organization. Employees need to pay the resource costs incurred first, and then apply to the organization. to reimburse. The transfer process of payment resources is complex, takes a long time, and has low execution efficiency.

Contents of the invention

The embodiments of this application provide a payment method, platform equipment, system and storage medium, which can improve the efficiency of resource transfer execution.

In the first aspect, embodiments of this application provide a payment method, which is applied to the transfer platform. The method includes: receiving a payment request message sent by the agency platform. The payment request message includes the payer organization identifier and payment information. The payer organization identifier Used to indicate the account of the payer 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 based on the payer organization identification and payment information; according to The payer's organization identification and payment information are used to transfer the payment resources of the third-party platform to the account of the service provider platform.

In the second aspect, embodiments of this application provide a payment method, which is applied to a third-party platform. The method includes: receiving a payment request message sent by the transfer platform. The payment request message includes the payer organization identification and payment information. The payer organization The identifier is used to indicate the account of the payer organization; a service acquisition request message is sent to the service provider platform according to the payer organization identifier and payment information; wherein, in the case where 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 transferred to the account of the service provider platform under the control of the transfer platform.

In the third aspect, embodiments of the present application provide a transfer platform device, including: a receiving module, configured to receive a payment request message sent by the agency platform. The payment request message includes the payer organization identification and payment information. The payer organization identification Used to indicate the account of the payer organization; the sending module is used 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 services to the service provider platform based on the payer organization identification and payment information. Obtain the request message; the resource transfer module is used to transfer the payment resources of the third-party platform to the account of the service provider platform based on the payer's organizational identification and payment information.

In the fourth aspect, embodiments of the present application provide a third-party platform device, including: a receiving module for receiving a payment request message sent by the transfer platform. The payment request message includes the payer organization identification and payment information. 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 provider platform provides services in response to the service acquisition request message In this case, the payment resources of the third-party platform corresponding to the third-party platform device are transferred to the account of the service provider platform under the control of the transfer platform.

In a fifth aspect, embodiments of the present application provide a transfer 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.

In a sixth aspect, embodiments of the present application provide 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.

In a seventh aspect, embodiments of the present application provide a payment system, including the transfer platform device of the fifth aspect and the third-party platform device of the sixth aspect.

In an eighth aspect, embodiments of the present application provide a computer-readable storage medium. Computer program instructions are stored on the computer-readable storage medium. 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 implemented. method.

This application provides a payment method, platform equipment, system and storage medium. The agent platform, transfer platform and third-party platform can request the service provider platform through a payment request message including the payer's organization identification and payment information. services, 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. , 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.

Description of drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the drawings required to be used in the embodiments of the present application will be briefly introduced below. For those of ordinary skill in the art, without exerting creative efforts, they can also Additional drawings can be obtained from these drawings.

Figure 1 is a schematic diagram of an example of the scenario architecture of the payment method provided by the embodiment of the present application;

Figure 2 is a flow chart of an embodiment of the payment method provided in the first aspect of this application;

Figure 3 is a flow chart of another embodiment of the payment method provided in the first aspect of this application;

Figure 4 is a flow chart of another embodiment of the payment method provided in the first aspect of this application;

Figure 5 is a flow chart of yet another embodiment of the payment method provided in the first aspect of this application;

Figure 6 is a flow chart of an embodiment of the payment method provided in the second aspect of this application;

Figure 7 is a flow chart of another embodiment of the payment method provided in the second aspect of this application;

Figure 8 is a flow chart of yet another embodiment of the payment method provided in the second aspect of this application;

Figure 9 is a flow chart of yet another embodiment of the payment method provided in the second aspect of this application;

Figure 10 is a flow chart of an example of the payment process provided by the embodiment of the present application;

Figure 11 is a schematic structural diagram of an embodiment of the transfer platform device provided in the third aspect of the present application;

Figure 12 is a schematic structural diagram of an embodiment of a third-party platform device provided in the fourth aspect of this application;

Figure 13 is a schematic diagram of the hardware structure of an embodiment of the transfer platform device provided in the fifth aspect of the present application;

FIG. 14 is a schematic diagram of the hardware structure of an embodiment of the third-party platform device provided in the sixth aspect of this application.

Detailed ways

Features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be described in further detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described here are only intended to explain the application, but not to limit the application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of embodiments is merely intended to provide a better understanding of the present application by illustrating examples thereof.

In the course of their work, employees in the organization need to travel to complete work delivered by the organization, or need to help the organization purchase supplies needed by the organization. Employees need to pay the resource expenses incurred first and then apply for reimbursement from the organization. Resources flow from employees to intermediary accounts, and then from intermediary accounts to service providers. In the subsequent reimbursement process, resources also need to flow from the organization to which the employee belongs to the employee to implement the reimbursement process. The following takes the travel expenses incurred by employees of an organization on business trips as an example. Employees book air tickets with an airline through an Online Travel Agent (OTA). The purchase funds flow from the employee's account to the online travel agent's account, and then from the online travel agent. The travel agent's account is transferred to the airline's account. During the subsequent reimbursement process, the ticket purchase funds flow from the organization's account to the employee's account. In the entire process from payment to reimbursement, the resource transfer process is relatively complex and takes a long time, which reduces the execution efficiency of resource transfer.

This application provides a payment method, platform, system and storage medium, which enables resources to be transferred from the organization through the interaction of payment request messages including the payer's organizational identity and payment information on the agency platform, transfer platform and third-party platform. The account is directly transferred to the service provider's account, thereby simplifying the resource transfer process, reducing resource transfer time, and improving the execution efficiency of resource transfer. It should be noted that payment in the embodiment of this application refers to payment initiated by a user but where the final resource payer is the payer organization.

The agent platform, transfer platform, third-party platform, and service provider platform can be implemented by servers, terminal devices, etc., and are not limited here. The agency platform can be a service agent platform. For example, in a business travel scenario, the agency platform can be an online travel agency platform, which is not limited here. The transfer platform is a platform that monitors the resource transfer process. Its 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 certified by the transfer platform. The service provider platform is a platform that provides users with purchased services. For example, in a business travel scenario, the service provider platform can be the platform of transportation companies such as airlines, railway companies, bus companies, etc., which is not limited here.

Figure 1 is a schematic diagram of an example of the scenario architecture of the payment method provided by the embodiment of the present application. As shown in Figure 1, users can interact with the agent platform 12 through the terminal device 11, the agent platform 12 and the transfer platform 13 can interact, the agent 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.

The first aspect of this application provides a payment method that can be applied to the transfer platform. Figure 2 is a flow chart of an embodiment of the payment method provided in the first aspect of this application. As shown in Figure 2, the payment method may include steps S201 to S203.

In step S201, receive the payment request message sent by the agency platform.

Users can initiate payment requests to the agency platform through terminal devices. Correspondingly, in response to the payment request, the agency platform sends a payment request message to the transfer platform. Agency platforms host accounts for payer organizations. The payment request message includes the payer's organization identification and payment information.

The payer organization ID is used to indicate the account of the payer organization. Payor Organization is the organization that is the payer. Organizational structures may specifically include enterprises, institutions, social groups, agencies, etc., and are not limited here. An account corresponds to a payer organization, that is, a payer organization uses the payer organization's account to make payments using the payment method in the embodiment of this application. A payer organization may include at least one payment user, that is, a payer organization has a payment association with at least one payment user. The payment association relationship can be established in advance. Paying users in the payer organization share the payer organization's account. For example, in the case where a payer organization includes multiple payment users, multiple users in the payer organization can make payments using the payment organization's account.

Payment information includes information required to make a payment. In some examples, payment information may include payment user information, payment content information, etc., which is not limited here. The payment user information is used to indicate the payment user. For example, the payment user information may include the user's name, user's mobile phone number, user's ID number, etc., which is not limited here. Payment content information may be used to indicate payment resources. The payment content information can also be used to instruct payment for goods, etc., but is not limited here. For example, the payment content information may include payment product information, payment resource information, etc., which is not limited here.

In some examples, the agent platform may also send a service request to the service provider platform in response to the user initiating a payment request to the agent platform through the terminal device. The service request may include the payer organization identification and payment information used to request the service. For example, in the scenario of travel ticket payment, the agency platform responds to the payment request initiated by the user to the agency platform through the terminal device and sends a ticket purchase request to the airline.

In 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 based on the payer's organization identification and payment information. The third-party platform can store the account information of the payer organization, the user information of the users in the payer organization, etc., which is not limited here. In some examples, the payer organization's account may be assigned by the third-party platform. The third-party platform can correspond to the accounts of one or more payer organizations.

In response to the payment request message, 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 services from the service provider platform. The service can correspond to the application scenario of the payment method, and can include physical goods or services, etc., which is not limited here. In some examples, in the scenario of business travel payment, the services requested by the service acquisition request message from the service provider platform may include travel tickets, travel tickets, accommodation reservations, etc., which are not limited here. For example, in the scenario of travel ticket payment, the payment request message can be used to instruct the third-party platform to send a service acquisition request message requesting the ticket to the airline platform. For another example, in the scenario of travel and accommodation payment, the payment request message can be used to instruct the third-party platform to send a service acquisition request message for booking accommodation to the hotel's service platform. In other examples, in the scenario of purchasing and paying for public goods, the requested service may include specific purchased public goods, which is not limited here.

In some examples, the third-party platform may also receive payment request messages for personal accounts. The third-party platform can determine whether the payment account is the account of the payer's organization or a personal account through the account identifier in the payment request message. The payer organization identifier can have a type identifier, and the individual account identifier can also have a type identifier. The type identification bit may include a single character or multiple characters, which is not limited here. The type identifier of the payer's organization identifier is different from the type identifier of the personal account. For example, the payer organization identifier may be the card number of the virtual card corresponding to the payer organization's account, and the personal account identifier may be the card number of the bank card of the personal account. The payer's organizational identification includes an Issuer Identification Number (IIN) that begins with a 2, and the personal account identification includes an issuer identification code that does not begin with a 2. The issuer identification code can be used as the type identification bit, or the prefix of the issuer identification code can be used as the type identification bit.

The third-party platform can determine whether the account identifier in the payment request message is the payer's organization identifier or an individual account identifier by identifying the type identifier of the account identifier. When it is determined that the account identifier in the payment request message is the payer's organization identifier, 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 a personal account identifier, the payment request message is forwarded to a personal account management platform such as a bank platform.

In step S203, the payment resources of the third-party platform are transferred to the account of the service provider platform according to the payer's organizational identification and payment information.

If the payment is successful, 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 identification in the third-party platform to the account of the service provider platform to complete the payment. In the follow-up process, the payer organization can realize resource transfer between the payer organization and the third-party platform based on the invoices provided by users within the payer organization, reconciliation information provided by the third-party platform, etc. Specifically, here The transfer of resources 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 same amount of payment resources as those 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. For example, a transfer platform that transfers the payment resources of a third-party platform to the account of the service provider platform can be executed on the second day of payment or on the same day of payment.

In the embodiment of this application, 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 organizational identity and payment information, and can transfer the services to the third-party platform. The payment resources corresponding to the payment information are 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. In the subsequent process, the payment resources do not need to flow into the personal account again, and the payment resources can be quickly completed. The transfer between party organizations, third-party platforms and service provider platforms simplifies the transfer process of payment resources, reduces transfer time, and improves execution efficiency.

In the embodiment of this application, the interaction process between the agent platform and the service provider platform has not changed, which can reduce the cost of transforming the existing architecture. In the embodiment of this application, payment resources do not need to go through the agency platform, which reduces the circulation of payment resources, reduces risks in the circulation process of payment resources, and improves the security and reliability of payment.

In some examples, the transfer platform can also provide reconciliation information to the third-party platform and the service provider platform to ensure the accuracy of the transfer of payment resources. Figure 3 is a flow chart of another embodiment of the payment method provided in the first aspect of this application. The difference between Figure 3 and Figure 2 is that the payment method shown in Figure 3 may also include step S204 and step S205.

In step S204, reconciliation information is generated based on the payer's organizational identification and payment information.

In order to simplify the process, the transfer platform can periodically transfer the payment resources of the third-party platform to the account of the service provider platform based on the payer's organizational identification and payment information. For example, the transferable platform can settle accounts 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 a day. In order to facilitate reconciliation between the third-party platform and the service provider platform, the transfer platform can determine the payment resources that should be transferred from the account of each payer organization based on the payer organization identification and payment information obtained from the payment request message. The total payment resources that should be transferred to the accounts of each payer organization corresponding to the third-party platform are generated to generate reconciliation information. The reconciliation information may include the details and total amount of payment resources, etc., which is not limited here.

In 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 reconciliations based on reconciliation information to ensure the accuracy of payment resource transfers.

In some examples, the payer organization identification includes an issuer identification bit. The issuer identification bit is used to identify the third-party platform that generates and issues the account of the payer organization. Through the issuer identification bit, the transfer platform can forward the payment request message to the accurate third-party platform. Figure 4 is a flow chart of yet another embodiment of the payment method provided in the first aspect of this application. The difference between Figure 4 and Figure 2 is that step S202 in Figure 2 can be specifically detailed into step S2021 and step S2022 in Figure 4 .

In step S2021, the issuer identification bit in the payer organization identification is identified, and the third-party platform corresponding to the issuer identification bit is determined.

There can be one third-party platform that generates and issues the account of the payer organization, or there can be two or more, which is not limited here. In the case of more than two third-party platforms, the transfer platform can identify the issuer identifier in the payer organization identifier, and determine the third party that generates and issues the payer organization's account based on the issuer identifier. platform to forward the payment request message to the third-party platform.

In some examples, the issuer identification bit may include an issuer identification code or other codes, etc., which is not limited here. For the specific content of the issuer identification bit, please refer to the relevant descriptions in the above embodiments and will not be described again here.

In step S2022, the payment request message is forwarded to the third-party platform corresponding to the issuer identification bit.

In some examples, the transfer platform may also determine whether the third-party platform has the authority to generate and issue the payer organization's account. Figure 5 is a flow chart of yet another embodiment of the payment method provided in the first aspect of this application. The difference between Figure 5 and Figure 2 is that the payment method shown in Figure 5 may also include step S206 and step S207.

In step S206, the account issuance permission request message sent by the third-party platform is received.

The permission request message issued by the account includes the institutional qualification information of the third-party platform. The institutional qualification information of the third-party platform is used to characterize the conditions, qualifications, capabilities, etc. possessed by the third-party platform. The transfer platform can determine whether to provide the third-party platform with the authority to generate and issue the account of the payer organization based on the institutional qualification information of the third-party platform included in the account issuance permission request message.

In step S207, when the institutional qualification information of the third-party platform meets the preset permission activation conditions, a permission activation success message is sent to the third-party platform.

The permission activation conditions can be set according to specific scenarios and needs, and are not limited here. The institutional qualification information of the third-party platform meets the permission activation conditions, which means that the third-party platform has the qualifications to generate and issue the account of the payer organization, and sends a permission activation success message to the third-party platform. The message of successful permission activation indicates that the third-party platform has the permission to generate and issue the account of the payer organization.

The institutional qualification information of the third-party platform does not meet the conditions for permission activation, which means that the third-party platform does not have the qualifications to generate and issue the account of the payer organization. It does not need to send a permission activation success message to the third-party platform, or send permissions to the third-party platform. Activation failure message. The permission activation failure message indicates that the third-party platform does not have the permission to generate and issue the account of the payer organization.

The second aspect of this application provides a payment method that can be applied to third-party platforms. Figure 6 is a flow chart of an embodiment of the payment method provided in the second aspect of this application. As shown in Figure 6, the payment method may include step S301 and step S302.

In step S301, receive the payment request message sent by the transfer platform.

The payment request message includes the payer's organization identification and payment information. The payer organization ID is used to indicate the account of the payer organization.

In some examples, the payer organization identification may include an issuer identification bit. The issuer identification bit is used to identify the third-party platform that generates and issues the account of the payer organization. For the specific content of the issuer identification bit, please refer to the relevant descriptions in the above embodiments and will not be described again here.

In some examples, payment information may include payment user information and payment content information. The payment user information is used to indicate the payment user. Payment content information is used to indicate payment resources.

In some examples, a payer organization's account has a payment association with at least one payment user. A payment user who has a payment association with the account of the payer organization can initiate payment using the account of the payer organization. When the account of a payer organization has a payment association with more than two payment users, both of the two or more payment users can use the account of the payer organization to initiate payment.

For the payment request message, payer organization identifier, and payment information, please refer to the relevant descriptions in the above embodiments and will not be described again here.

In 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, in response to the service get request message, may provide the service requested by the service get request message. For example, the service provider platform is an airline platform. Before the third-party platform sends a service acquisition request message to the airline platform, the airline can receive the service request initiated by the agent platform. When the airline platform receives a 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. . When 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, the airline platform provides the corresponding service and issues a ticket.

Among them, when the service providing platform provides services in response to the service acquisition request message, the payment resources of the third-party platform are transferred to the account of the service provider platform under the control of the transfer platform. The account of the third-party platform can be managed by the transfer platform. 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 Transfer of payment resources.

In some examples, to prevent users who do not have access to the payer organization's account from making payments using the payer organization's account. 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 and the payment user indicated by the payment user information in the payment information have a payment association. If the verification is successful, that is, if the account of the payer organization indicated by the payer organization identifier has a payment association 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. If the verification fails, that is, if the account of the payer organization indicated by the payer organization identifier does not have a payment association with the payment user indicated by the payment user information in the payment information, the service acquisition request message shall be refused to be sent to the service provider platform. By verifying payment user information, illegal payments can be avoided, thereby improving the security and reliability of payments.

In the embodiment of this application, 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 organizational identity and payment information, and can transfer the services to the third-party platform. The payment resources corresponding to the payment information are 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. In the subsequent process, the payment resources do not need to flow into the personal account again, and the payment resources can be quickly completed. The transfer between party organizations, third-party platforms and service provider platforms simplifies the transfer process of payment resources, reduces transfer time, and improves execution efficiency.

In the embodiment of this application, payment resources do not need to go through the agency platform, which reduces the circulation of payment resources, reduces risks in the circulation process of payment resources, and improves the security and reliability of payment.

In some examples, the third-party platform may also reconcile with the service provider platform. Figure 7 is a flow chart of another embodiment of the payment method provided in the second aspect of this application. The difference between Figure 7 and Figure 6 is that the payment method shown in Figure 7 may also include step S303.

In step S303, the reconciliation information sent by the transfer platform is received.

Reconciliation information is generated by the transfer platform based on the payer's organizational identification and payment information. For the specific content of the reconciliation information, please refer to the relevant descriptions in the above embodiments and will not be described again here.

Through reconciliation information, the third-party platform can reconcile with the service provider platform, thereby ensuring the accuracy and reliability of payment.

In some examples, the third-party platform may also request permission from the transfer platform to generate and issue the payer organization's account. Only when the third-party platform has the authority to generate and issue the account of the payer organization, can the third-party platform generate and issue the account of the payer organization and manage the account of the payer organization. Figure 8 is a flow chart of yet another embodiment of the payment method provided in the second aspect of this application. The difference between Figure 8 and Figure 6 is that the payment method shown in Figure 8 may also include step S304 and step S305.

In step S304, an account delivery permission request message is sent to the transfer platform.

The account issuance permission request message includes the institutional qualification information of the third-party platform and is used to request the transfer platform for permission to generate and issue the account of the payer organization.

In step S305, receive a permission activation success message sent by the transfer platform.

The permission activation success message is sent by the transfer platform when the institutional qualification information of the third-party platform meets the preset permission activation conditions. The message of successful permission activation 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 meets the conditions for permission activation, the third-party platform has the authority to generate and issue the account of the payer organization. If 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 accounts for the payer organization.

The transfer platform has higher authority than the third-party platform and can manage the third-party platform. The transfer platform has the authority to create and issue accounts for payer organizations to third-party platforms. Authorization of third-party platforms by the transfer platform facilitates standardized management of third-party platforms, and can prevent third-party platforms that are not qualified to carry out the above payment methods from participating in the payment process in the embodiments of this application, improving the security and safety of payments. reliability.

In some examples, if the third-party platform has the authority to generate and issue accounts for the payer organization, the third-party platform can generate and issue accounts for the payer organization. Figure 9 is a flow chart of yet another embodiment of the payment method provided in the second aspect of this application. The difference between Fig. 9 and Fig. 6 is that the payment method shown in Fig. 9 may also include steps S306 to S308.

In 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 an account of the payer organization. The qualification information of the payer organization is used to characterize the other conditions, qualifications, capabilities, etc. of the payer organization.

In step S307, in response to the account application message, an account is assigned to the payer organization.

The routing platform allocates different accounts to different payer organizations. Specifically, the transfer screen may assign an account number to the payer organization. For example, the routing platform may assign a payer organization a 16- to 19-digit account number that includes a 2-digit issuer identification code.

In step S308, account credit permissions are set for the account of the payer organization based on the qualification information of the payer organization.

Account credit permissions may include permissions owned by the account, which are related to qualification information, etc. In some examples, account credit permissions may include resource transfer time limits and credit resource amounts. The resource transfer time limit can indicate the time limit for the payor organization's account to transfer the resources to be returned to the third-party platform. For example, if the resource transfer time is limited to 5 days, then within 5 days after the third-party platform transfers the payment resources to the platform provided by the service provider, the account of the payer's organizational structure needs to transfer the resources to be returned to the third-party platform. In some examples, the higher the conditions, qualifications, and abilities of the payer organization represented by the payer organization's qualification information, the longer the resource transfer time limit may indicate, that is, the resource transfer time limit indicates the same time period as the payer organization's qualification information. Qualification information represents a positive correlation with the conditions, qualifications, and capabilities of the payer organization. The amount of credit resources can indicate the amount of credit resources set by the third-party platform for the payer organization. When 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 same amount of payment resources as those transferred from the third-party platform to the account of the service provider platform. In some examples, the higher the conditions, qualifications, and capabilities of the payer organization represented by the payer organization's qualification information, 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 quantity 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 here.

The following specific example illustrates the payment method in the embodiment of the present application applied to terminal equipment, agency platforms, transfer platforms, third-party platforms, and service provider platforms. Figure 10 is a flow chart of an example of the payment process provided by the embodiment of the present application. As shown in Figure 10, the payment method may include steps S401 to S414.

In step S401, the third-party platform sends an account delivery permission request message to the transfer platform.

In step S402, when the institutional qualification information of the third-party platform meets the preset permission activation conditions, the transfer platform sends a permission activation success message to the third-party platform.

In step S403, the terminal device sends an account application message to the third-party platform.

In step S404, the third-party platform responds to the account application message and allocates an account to the payer organization.

In step S405, account credit permissions are set for the account of the payer organization based on the qualification information of the payer organization.

In step S406, the terminal device responds to the user's input operation and sends a payment request to the agent platform.

In step S407, the agency platform sends a service request to the service provider platform in response to the payment request.

In step S408, the agency platform responds to the payment request and sends a payment request message to the transfer platform.

In step S409, the transfer platform forwards the payment request message to the third-party platform.

In step S410, the third-party platform sends a service acquisition request message to the service provider platform based on the payer organization identifier and payment information in the payment request message.

In step S411, the service provider platform provides the service in response to the service acquisition request message.

In step S412, at the end of the settlement cycle, the transfer platform sends the generated reconciliation information to the third-party platform.

In step S413, at the end of the settlement cycle, the transfer platform sends the generated reconciliation information to the service provider platform.

In step S414, within the first period of time after the settlement cycle ends, the transfer platform transfers the payment resources of the third-party platform to the account of the service provider platform.

In the second period after the transfer platform transfers the payment resources of the third-party platform to the account of the service provider platform, resources equal to the payment resources are transferred from the payment organization's account to the third-party platform.

The third aspect of this application provides a transfer platform device. Figure 11 is a schematic structural diagram of an embodiment of the transfer platform device provided in the third aspect of this application. As shown in Figure 11, the transfer platform device 500 may include a receiving module 501, a sending module 502 and a resource transfer module 503.

The receiving module 501 can be used to receive the payment request message sent by the agent platform.

The payment request message includes the payer's organization identification and payment information. The payer organization ID is used to indicate the account of the payer organization.

In some examples, the payment information includes payment user information and payment content information. The payment user information is used to indicate the payment user. Payment content information is used to indicate payment resources.

In some examples, a payer organization's account has a payment association with at least one payment user.

The sending module 502 may be used 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 based on the payer's organization identification and payment information.

The resource transfer module 503 can be used to transfer the payment resources of the third-party platform to the account of the service provider platform based on the payer's organizational identification and payment information.

In the embodiment of this application, the agency platform, the transfer platform corresponding to the transfer platform device, 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 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 from 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 be quickly Easily 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.

In the embodiment of this application, the interaction process between the agent platform and the service provider platform has not changed, which can reduce the cost of transforming the existing architecture. In the embodiment of this application, payment resources do not need to go through the agency platform, which reduces the circulation of payment resources, reduces risks in the circulation process of payment resources, and improves the security and reliability of payment.

In some examples, the transfer platform device may also include a reconciliation information generation module. The reconciliation information generation module can be used to generate reconciliation information based on the payer's organizational identification 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.

In some examples, the payer organization identification includes an issuer identification bit. The issuer identification bit is used to identify the third-party platform that generates and issues the account of the payer organization.

The transfer platform device 500 in the above embodiment may also include an identification module. The identification module can be used to identify the issuer identification bit in the payer's organizational identification and determine the third-party platform corresponding to the issuer identification bit.

The sending module 502 in the above embodiment can be used to forward the payment request message to the third-party platform corresponding to the issuer identifier.

In some examples, the receiving module 501 in the above embodiment can also be used to receive an account issuance permission request message sent by a third-party platform. The permission request message issued by the account includes the institutional qualification information of the third-party platform.

The sending module 502 in the above embodiment can also be used to send a permission activation success message to the third-party platform when the institutional qualification information of the third-party platform meets the preset permission activation conditions. The message of successful permission activation indicates that the third-party platform has the permission to generate and issue the account of the payer organization.

The fourth aspect of this application provides a third-party platform device. Figure 12 is a schematic structural diagram of an embodiment of a third-party platform device provided in the fourth aspect of this application. As shown in Figure 12, the third-party platform device 600 may include a receiving module 601 and a sending module 602.

The receiving module 601 can be used to receive the payment request message sent by the transfer platform.

The payment request message includes the payer's organization identification and payment information. The payer organization ID is used to indicate the account of the payer organization.

In some examples, the payment information includes payment user information and payment content information. The payment user information is used to indicate the payment user. Payment content information is used to indicate payment resources.

In some examples, a payer organization's account has a payment association with at least one payment user.

The sending module 602 may be used to send a service acquisition request message to the service provider platform according to the payer organization identification and payment information.

Wherein, when 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 transferred to the account of the service provider platform under the control of the transfer platform.

In the embodiment of this application, 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 organizational identity and payment information, and can transfer the services to the third-party platform. The payment resources corresponding to the payment information are 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. In the subsequent process, the payment resources do not need to flow into the personal account again, and the payment resources can be quickly completed. The transfer between party organizations, third-party platforms and service provider platforms simplifies the transfer process of payment resources, reduces transfer time, and improves execution efficiency.

In the embodiment of this application, payment resources do not need to go through the agency platform, which reduces the circulation of payment resources, reduces risks in the circulation process of payment resources, and improves the security and reliability of payment.

In some examples, the sending module 602 in the above embodiment can also be used to send a message to the payer organization when the account of the payer organization indicated by the payer organization identification has a payment association with the payment user indicated by the payment user information in the payment information. The service provider platform sends a service acquisition request message.

In some examples, the receiving module 601 in the above embodiment can also be used to receive reconciliation information sent by the transfer platform. The reconciliation information is generated by the transfer platform based on the payer's organizational identity and payment information.

In some examples, the sending module 602 in the above embodiment can also be used to send an account-issued permission request message to the transfer platform, where the account-issued permission request message includes the institutional qualification information of the third-party platform.

The receiving module 601 in the above embodiment can also be used to receive the permission activation success message sent by the transfer platform. The permission activation success message is sent by the transfer platform when the institutional qualification information of the third-party platform meets the preset permission activation conditions. The message of successful permission activation indicates that the third-party platform has the permission to generate and issue the account of the payer organization.

In some examples, the receiving module 601 in the above embodiment can 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 allocation module and a permission setting module. The account allocation module may be used to allocate an account to the payor organization in response to the account request message. The permission setting module can be used to set account credit permissions for the payer organization's account based on the payer organization's qualification information.

In some examples, the payer organization identification includes an issuer identification bit. The issuer identification bit is used to identify the third-party platform that generates and issues the account of the payer organization.

A fifth aspect of this application provides a transfer platform device. FIG. 13 is a schematic diagram of the hardware structure of an embodiment of the transfer platform device provided in the fifth aspect of the present application. As shown in Figure 13, the transfer 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.

In one example, the above-mentioned processor 702 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 embodiments of the present application.

The memory 701 may include read-only memory (ROM), random access memory (RandomAccess Memory, RAM), magnetic disk storage media device, optical storage media device, flash memory device, electrical, optical or other physical/tangible memory storage device. Thus, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including 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 payment method according to the first aspect of the present application.

The processor 702 reads the executable program code stored in the memory 701 to run the computer program corresponding to the executable program code, so as to implement the payment method of the first aspect in the above embodiment.

In one example, transit platform device 700 may also include communication interface 703 and bus 704. Among them, as shown in Figure 13, the memory 701, the processor 702, and the communication interface 703 are connected through the bus 704 and complete communication with each other.

The communication interface 703 is mainly used to implement communication between modules, devices, units and/or equipment in the embodiments of this application. Input devices and/or output devices may also be accessed through the communication interface 703.

Bus 704 includes hardware, software, or both, coupling the components of switching platform device 700 to one another. By way of example, but not limitation, 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, Industrial Standard Architecture (ISA) bus, infinite bandwidth interconnect, low pin count (LPC) bus, memory bus, Micro Channel Architecture , MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, 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. Where appropriate, bus 704 may include one or more buses. Although the embodiments of this application describe and illustrate a specific bus, this application contemplates any suitable bus or interconnection.

A sixth aspect of this application provides a third-party platform device. FIG. 14 is a schematic diagram of the hardware structure of an embodiment of the third-party platform device provided in the sixth aspect of this application. As shown in Figure 14, 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.

In one example, the above-mentioned processor 802 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 embodiments of the present application.

Memory 801 may include read-only memory (ROM), random access memory (RandomAccess Memory, RAM), magnetic disk storage media device, optical storage media device, flash memory device, electrical, optical or other physical/tangible memory storage device. Thus, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including 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 payment method according to the second aspect of the present application.

The processor 802 reads the executable program code stored in the memory 801 to run the computer program corresponding to the executable program code, so as to implement the payment method of the second aspect in the above embodiment.

In one example, the third-party platform device 800 may also include a communication interface 803 and a bus 804. Among them, as shown in Figure 14, the memory 801, the processor 802, and the communication interface 803 are connected through the bus 804 and complete communication with each other.

The communication interface 803 is mainly used to implement communication between modules, devices, units and/or equipment in the embodiments of this application. Input devices and/or output devices may also be accessed through the communication interface 803.

Bus 804 includes hardware, software, or both, coupling the components of third-party platform device 800 to each other. By way of example, but not limitation, 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, Industrial Standard Architecture (ISA) bus, infinite bandwidth interconnect, low pin count (LPC) bus, memory bus, Micro Channel Architecture , MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, 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. Where appropriate, bus 804 may include one or more buses. Although the embodiments of this application describe and illustrate a specific bus, this application contemplates any suitable bus or interconnection.

The seventh aspect of this application provides a payment system. The payment system may include the transfer platform device and the third-party platform device in the above embodiment. That is, the payment system may include the transfer platform and the third-party platform in the above embodiment.

In some examples, the above-mentioned payment system may also include one or more types of agent platform equipment, service provider platform equipment, and terminal equipment. That is, the above-mentioned payment system may also include an agent platform, a service provider platform, and terminal equipment. One or more categories are not limited here.

The specific contents of the agency platform, terminal equipment, transfer platform, third-party platform, and service provider platform in the payment system can be found in the relevant descriptions in the above embodiments, and will not be described again here.

Embodiments of the present application also provide a computer-readable storage medium. Computer program instructions are stored on the computer-readable storage medium. When executed by a processor, the computer program instructions can implement the first aspect of the payment method in the above embodiments or The second payment method can achieve the same technical effect. To avoid duplication, it will not be described again here. Wherein, the above-mentioned computer-readable storage media may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical disks. etc. are not limited here.

It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. place. For platform device embodiments, system embodiments, and computer-readable storage medium embodiments, relevant information may be found in the description of the method embodiments. This application is not limited to the specific steps and structures described above and illustrated in the drawings. Those skilled in the art can make various changes, modifications and additions, or change the order between steps after understanding the spirit of the present application. Also, for the sake of brevity, detailed descriptions of known method techniques are omitted here.

Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that execution of the instructions via the processor of the computer or other programmable data processing apparatus enables Implementation of the functions/actions specified in one or more blocks of a flowchart and/or block diagram. Such a processor may be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It will also be understood that each block in 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 that performs the specified functions or actions, or can be implemented by special purpose hardware and A combination of computer instructions.

Those skilled in the art should understand that the above embodiments are illustrative rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Those skilled in the art should be able to understand and implement other modified embodiments of the disclosed embodiments based on studying the drawings, description and claims. In the claims, the term "comprising" does not exclude other means or steps; the quantifier "a" does not exclude a plurality; the terms "first" and "second" are used to indicate names rather than to indicate any specific order. . Any reference signs in the claims shall not be construed as limiting the scope. The functions of several parts appearing in the claims may be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims (20)

1. A payment method, characterized in that it is applied to a transfer platform, and the method includes: Receive a payment request message sent by the agency platform. The payment request message includes the payer organization identifier and payment information. The payer organization identifier is used to indicate the account of the payer organization. The agency platform is an agent account for services. platform; Forwarding the payment request message to a 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 organization identifier and the payment information, so The above service acquisition request message is used to request physical goods or services from the service provider platform; Transfer the payment resources of the third-party platform to the account of the service provider platform according to the payer's organizational identification and payment information. 2. The method according to claim 1, characterized in that the payment information includes payment user information and payment content information, the payment user information is used to indicate a paying user, and the payment content information is used to indicate payment resources. 3. The method according to claim 2, characterized in that an account of one of the payer organizations has a payment association relationship with at least one of the paying users. 4. The method according to claim 1, characterized in that, after forwarding the payment request message to a third-party platform, it further includes: Generate reconciliation information based on the payer organizational identifier and the payment information; Send the reconciliation information to the third-party platform and the service provider platform respectively. 5. The method according to claim 1, characterized in that the payer organization identifier includes an issuer identification bit, and the issuer identification bit is used to identify the generation and issuance of the account of the payer organization. The third-party platform; The forwarding of the payment request message to the third-party platform includes: Identify the issuer identifier in the payer organization identifier, and determine the third-party platform corresponding to the issuer identifier; Forward the payment request message to the third-party platform corresponding to the issuer identification bit. 6. The method of claim 1, further comprising: Receive an account-issued permission request message sent by the third-party platform, where the account-issued permission request message includes the institutional qualification information of the third-party platform; When the institutional qualification information of the third-party platform meets the preset permission activation conditions, a permission activation success message is sent to the third-party platform. The permission activation success message indicates that the third-party platform has the ability to generate and deliver Permissions for the payer organization's account. 7. A payment method, characterized in that it is applied to a third-party platform, and the method includes: Receive a payment request message sent by the transfer platform. The payment request message is sent by the agency platform to the transfer platform and includes the payer organization identification and payment information. The payer organization identification is used to indicate the payer organization. account, the agent platform is the agent account platform of the service; Send a service acquisition request message to the service provider platform according to the payer organization identifier and the payment information, where the service acquisition request message is used to request physical goods or services from the service provider platform; Wherein, when the service providing platform provides physical goods or services in response to the service acquisition request message, the payment resources of the third-party platform are transferred to the account of the service provider platform under the control of the transfer platform. 8. The method according to claim 7, wherein the payment information includes payment user information and payment content information, the payment user information is used to indicate a paying user, and the payment content information is used to indicate payment resources. 9. The method according to claim 8, characterized in that an account of one of the payer organizations has a payment association relationship with at least one of the paying users. 10. The method according to claim 9, wherein sending a service acquisition request message to the service provider platform based on the payer organization identifier and the payment information includes: In the case where the account of the payer organization indicated by the payer organization identification and the payment user indicated by the payment user information in the payment information have the payment association relationship, send the payment association to the service provider platform. The above service gets the request message. 11. The method according to claim 7, characterized in that after sending a service acquisition request message to the service provider platform according to the payer organization identifier and the payment information, it further includes: Receive reconciliation information sent by the transfer platform, where the reconciliation information is generated by the transfer platform based on the payer organization identifier and the payment information. 12. The method of claim 7, further comprising: Send an account-issued permission request message to the transfer platform, where the account-issued permission request message includes the institutional qualification information of the third-party platform; Receive a permission activation success message sent by the transfer platform. The permission activation success message is sent by the transfer platform when the institutional qualification information of the third-party platform meets the preset permission activation conditions. The successful activation message indicates that the third-party platform has the authority to generate and issue the account of the payer organization. 13. The method of claim 7, further comprising: Receive an account application message sent by the payer organization through the terminal device, where the account application message includes the qualification information of the payer organization; Allocate an account to the payer organization in response to the account application message; Set account credit permissions for the payer organization's account based on the payer organization's qualification information. 14. The method according to claim 7, characterized in that the payer organization identifier includes an issuer identification bit, and the issuer identification bit is used to identify the generation and issuance of the account of the payer organization. The third-party platform. 15. A transfer platform device, characterized by including: A receiving module, configured to receive a payment request message sent by the agency platform. The payment request message includes a payer organization identifier and payment information. The payer organization identifier is used to indicate the account of the payer organization. The agency platform An agent account platform for services; A sending module, configured to forward the payment request message to a third-party platform, where the payment request message is used to instruct the third-party platform to send services to the service provider platform based on the payer organization identifier and the payment information. Acquisition request message, the service acquisition request message is used to request physical goods or services from the service provider platform; The resource transfer module is used to transfer the payment resources of the third-party platform to the account of the service provider platform based on the payer's organizational identification and payment information. 16. A third-party platform device, characterized by including: The receiving module is used to receive the payment request message sent by the transfer platform. The payment request message is sent by the agency platform to the transfer platform and includes the payer organization identifier and payment information. The payer organization identifier is used to Indicate the account of the payer organization, and the agent platform is the agent account platform of the service; A sending module, configured to send a service acquisition request message to the service provider platform according to the payer organization identifier and the payment information, where the service acquisition request message is used to request physical goods or services from the service provider platform; Wherein, when the service providing platform provides physical goods or 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 transferred to the service provider under the control of the transfer platform account on the party platform. 17. A transfer platform device, characterized in that it includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the payment method according to any one of claims 1 to 6 is implemented. 18. A third-party platform device, characterized by including: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the payment method according to any one of claims 7 to 14 is implemented. 19. A payment system, characterized by comprising the transfer platform device as claimed in claim 17 and the third-party platform device as claimed in claim 18. 20. A computer-readable storage medium, characterized in that computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the computer program instructions of any one of claims 1 to 14 are implemented. payment method described above.