Payment management and control method, system and device for product modification, medium and program product

Abstract

The invention provides a payment management and control method, system and device for product resigning, a medium and a program product. The payment management and control method comprises the steps of obtaining resigning related information of a product; according to the employee poor bidding information and the predetermined payment information, judging whether the resigning application meets a preset travel-on-business standard or not; if yes, obtaining a corresponding first endorsement strategy according to the endorsement payment information, and realizing product endorsement according to the first endorsement strategy; and if not, obtaining a corresponding second alteration strategy according to the alteration payment information, and realizing product alteration according to the second alteration strategy. Through the first alteration strategy and the second alteration strategy, the problem of inflexible payment mode switching is solved, loss caused by public account payment of a company for product alteration is avoided, and management and control of business travel budget of the company are enhanced.

Description

[0001] This disclosure claims priority from Chinese patent application CN2024115456684, filed November 1, 2024. This disclosure incorporates the entire text of the aforementioned Chinese patent application. Technical Field

[0002] The present disclosure relates to the field of computer technology, and in particular to a payment control method, system, device, medium, and program product for product reissue. Background Art

[0003] With the continuous development of online ticketing, more and more users are accustomed to booking travel products through travel platforms. In the existing travel platform's ticket change process, when a company account payment is placed, the company account payment can be changed; when a personal payment is placed, the personal payment can be changed; and when a mixed payment (company account and personal payment) is placed, the mixed payment (company account and personal payment) can be changed or the company account payment can be changed. In other words, when a company account payment is placed, the personal payment cannot be changed; when a company account payment is placed, the mixed payment (company account and personal payment) cannot be changed; and when a mixed payment (company account and personal payment) is placed, the personal payment cannot be changed.

[0004] The above-mentioned product change payment method, on the one hand, limits the employees' range of choices; on the other hand, it makes it impossible for the company to effectively control the payment methods used by employees when changing products; on the other hand, when the product change level has already restricted travel standards, the fees paid to external applications from the company account are not effectively controlled. The additional fees incurred by employees when changing to the same product will cause the company's travel expenses to overspend. Summary of the Invention

[0005] The technical problem to be solved by the present disclosure is to overcome the defects of the existing technology in that the payment method switching during the product re-issuance process is inflexible and the losses caused by the company's public account payments for product re-issuance cannot be controlled, and a payment control method, system, equipment, medium and program product for product re-issuance is provided.

[0006] The present disclosure solves the above technical problems through the following technical solutions:

[0007] In a first aspect, the present disclosure provides a payment management method for product reissue, the payment management method comprising:

[0008] Obtain product change-related information; the change-related information includes employee discount information, reservation payment information, and change payment information;

[0009] Determining whether the change request meets the preset travel standards based on the employee's travel standard information and the scheduled payment information;

[0010] If the conditions are met, the corresponding first ticket change strategy is obtained according to the ticket change payment information, and the product ticket is changed according to the first ticket change strategy; the first ticket change strategy includes a company account payment strategy, a personal account payment strategy, and a company or personal account payment strategy;

[0011] If it does not comply, the corresponding second change strategy will be obtained based on the change payment information, and the product change will be implemented according to the second change strategy; the second change strategy includes the over-standard control company account payment strategy, the over-standard control personal account payment strategy and the over-standard control unrestricted account payment strategy for change.

[0012] Preferably, the steps of obtaining a corresponding first ticket change strategy based on the ticket change payment information, and implementing the product ticket change based on the first ticket change strategy include:

[0013] If the first ticket change policy is the company account payment policy, checking whether the ticket change payment information satisfies the public account payment requirement under the ticket change fee collection scenario;

[0014] If the conditions are met, the public account payment is confirmed to implement the change operation;

[0015] If not, when the ticket change operation does not require payment of a ticket change fee to an external application, it is determined that the ticket change operation is implemented through public account payment; or when the ticket change operation requires payment of a ticket change fee to an external application, it is determined that no account payment is available to implement the ticket change operation;

[0016] and / or,

[0017] If the first ticket change strategy is the personal account payment strategy, determining personal payment to implement the ticket change operation;

[0018] and / or,

[0019] If the first ticket change policy is the company or personal account payment policy, checking whether the ticket change payment information satisfies the public account payment requirement for charging the ticket change fee;

[0020] If the conditions are met, the public account payment or personal payment is confirmed to implement the ticket change operation;

[0021] If not met, when the ticket change operation does not require payment of a ticket change fee to an external application, then public account payment or personal payment is determined to implement the ticket change operation; or when the ticket change operation requires payment of a ticket change fee to an external application, then personal payment is determined to implement the ticket change operation.

[0022] Preferably, the step of obtaining a corresponding second ticket change policy according to the ticket change payment information, and implementing the product ticket change according to the second ticket change policy includes:

[0023] If the second ticket change strategy is the over-limit control corporate account payment strategy, checking whether the ticket change payment information satisfies the over-limit control that prohibits corporate account payment;

[0024] If the conditions are met, it is determined that there is no available account to pay for the ticket change operation;

[0025] If not, continue to check whether the change payment information meets the control of excessive mixed payment; if so, determine that there is no available account payment to implement the change operation; if not, continue to check whether the change payment information meets the control of excessive unreservable;

[0026] If it meets the requirements, it is determined that the ticket change operation cannot be carried out because the difference standard is exceeded; if it does not meet the requirements, check whether the ticket change payment information meets the requirements of mixed payment or the over-standard control of the reason for exceeding the standard. If it meets the requirements, continue to check whether the ticket change payment information meets the requirements of public account payment in the scenario of charging ticket change fees. If it does not meet the requirements, when the ticket change operation requires payment of the ticket change fee to an external application, it is determined that there is no available account payment to realize the ticket change operation, or when the ticket change operation does not require payment of the ticket change fee to an external application, then after collecting the reason for exceeding the standard, it is determined that the ticket change operation is realized through public account payment.

[0027] Preferably, the step of obtaining a corresponding second ticket change policy according to the ticket change payment information, and implementing the product ticket change according to the second ticket change policy, further includes:

[0028] If the second ticket change policy is the excessive control personal account payment policy, checking whether the ticket change payment information satisfies the excessive control that prohibits corporate account payment;

[0029] If the conditions are met, the personal account payment is confirmed to implement the ticket change operation;

[0030] If not, continue to check whether the payment information for the ticket change meets the standard control of mixed payment; if so, determine that the personal payment has been changed; if not, continue to check whether the payment information for the ticket change meets the standard control of mixed payment or the reason for the selection of the standard;

[0031] If the requirements are met, the reason for the excess will be collected, and personal payment will be determined to implement the ticket change operation; if the requirements are not met, the ticket change payment information will be checked to see if it meets the non-bookable excess control. If it does, it will be determined that the ticket change operation cannot be carried out due to the excess.

[0032] Preferably, the step of obtaining a corresponding second ticket change policy according to the ticket change payment information, and implementing the product ticket change according to the second ticket change policy, further includes:

[0033] If the second ticket change policy is the policy of not restricting account payment under the over-limit control, checking whether the ticket change payment information satisfies the over-limit control that prohibits corporate account payment;

[0034] If the conditions are met, the personal payment is confirmed to implement the ticket change operation;

[0035] If not, continue to check whether the change payment information meets the excessive control of mixed payment; if satisfied, continue to check whether the change payment information meets the public account payment in the scenario of charging change fees.

[0036] If the conditions are met, personal payment or hybrid payment is determined to implement the ticket change operation. If the conditions are not met, when the ticket change operation requires payment of a ticket change fee to an external application, personal payment is determined to implement the ticket change operation. Alternatively, when the ticket change operation does not require payment of a ticket change fee to an external application, hybrid payment or personal payment is determined to implement the ticket change operation. If the conditions are not met, further verification is performed to determine whether the ticket change payment information meets the control requirements for excess bookings that cannot be made.

[0037] If the conditions are met, it is determined that the difference exceeds the standard and the ticket cannot be changed;

[0038] If not, continue to check whether the change payment information meets the requirements of mixed payment or over-limit control based on the reason for over-limit; if satisfied, continue to check whether the change payment information meets the requirements of public account payment under the scenario of charging change fees;

[0039] If the conditions are met, a mixed payment method is determined, or after collecting the reason for the excess, a public account payment method is determined to implement the ticket change operation; if the conditions are not met, when the ticket change operation does not require payment of a ticket change fee to an external application, a mixed payment method is determined, or after collecting the reason for the excess, a public account payment method is determined to implement the ticket change operation; or when the ticket change operation requires payment of a ticket change fee to an external application, after collecting the reason for the excess, a personal payment method is determined to implement the ticket change operation;

[0040] If it is not satisfied, continue to check whether the change payment information meets the over-standard control with priority selection of the over-standard control reason; if it is satisfied, continue to check whether the change payment information meets the public account payment in the scenario of charging the change fee corresponding to the company account; if it is satisfied, select the over-standard reason and determine whether the public account payment or personal payment is used to realize the change operation. If it is not satisfied, when the change operation requires payment of the change fee to an external application, select the over-standard reason and determine that only personal payment is used to realize the change operation.

[0041] Preferably, the step of determining whether the ticket change application meets the preset travel standards based on the employee's travel standard information and the scheduled payment information includes:

[0042] Determining whether the scheduled payment information is for a public account payment and the travel is for official business;

[0043] If so, continue to determine whether the employee's change information meets the optional product level corresponding to the employee level and the price of the changed product does not exceed the price threshold; if it does, determine that the change application meets the preset travel standards.

[0044] In a second aspect, the present disclosure provides a payment control system for product reissue, the payment control system comprising:

[0045] An acquisition module is used to obtain product change-related information; the change-related information includes employee discount information, scheduled payment information, and change payment information;

[0046] A difference standard prediction module is used to determine whether the ticket change application meets the preset travel standards based on the employee difference standard information and the scheduled payment information; if so, call the first strategy module; if not, call the second strategy module;

[0047] The first policy module is configured to obtain a corresponding first ticket change policy based on the ticket change payment information, and implement a product ticket change based on the first ticket change policy; the first ticket change policy includes a company account payment policy, a personal account payment policy, and a company or personal account payment policy;

[0048] The second strategy module is used to obtain the corresponding second change strategy based on the change payment information, and to implement product change according to the second change strategy; the second change strategy includes the over-standard control company account payment strategy, the over-standard control personal account payment strategy and the over-standard control unrestricted account payment strategy for change.

[0049] Preferably, the first policy module includes:

[0050] A first policy unit is configured to, if the first ticket change policy is the company account payment policy, verify whether the ticket change payment information satisfies the public account payment requirement in the ticket change fee collection scenario;

[0051] If the conditions are met, the public account payment is confirmed to implement the change operation;

[0052] If not, when the ticket change operation does not require payment of a ticket change fee to an external application, it is determined that the ticket change operation is implemented through public account payment; or when the ticket change operation requires payment of a ticket change fee to an external application, it is determined that no account payment is available to implement the ticket change operation;

[0053] and / or,

[0054] A second strategy unit is configured to determine that a personal payment is used to implement a ticket change operation if the first ticket change strategy is the personal account payment strategy;

[0055] and / or,

[0056] A third policy unit is configured to, if the first ticket change policy is the company or personal account payment policy, verify whether the ticket change payment information satisfies the requirement for public account payment for ticket change fees;

[0057] If the conditions are met, the public account payment or personal payment is confirmed to implement the ticket change operation;

[0058] If not met, when the ticket change operation does not require payment of a ticket change fee to an external application, then public account payment or personal payment is determined to implement the ticket change operation; or when the ticket change operation requires payment of a ticket change fee to an external application, then personal payment is determined to implement the ticket change operation.

[0059] Preferably, the second policy module includes:

[0060] A fourth strategy unit is configured to, if the second ticket change strategy is the over-limit control corporate account payment strategy, verify whether the ticket change payment information satisfies the over-limit control of not allowing corporate account payment;

[0061] If the conditions are met, it is determined that there is no available account to pay for the ticket change operation;

[0062] If not, continue to check whether the change payment information meets the control of excessive mixed payment; if so, determine that there is no available account payment to implement the change operation; if not, continue to check whether the change payment information meets the control of excessive unreservable;

[0063] If it meets the requirements, it is determined that the ticket change operation cannot be carried out because the difference standard is exceeded; if it does not meet the requirements, check whether the ticket change payment information meets the requirements of mixed payment or the over-standard control of the reason for exceeding the standard. If it meets the requirements, continue to check whether the ticket change payment information meets the requirements of public account payment in the scenario of charging ticket change fees. If it does not meet the requirements, when the ticket change operation requires payment of the ticket change fee to an external application, it is determined that there is no available account payment to realize the ticket change operation, or when the ticket change operation does not require payment of the ticket change fee to an external application, then after collecting the reason for exceeding the standard, it is determined that the ticket change operation is realized through public account payment.

[0064] Preferably, the second policy module further includes:

[0065] A fifth strategy unit is configured to, if the second ticket change strategy is the excessive payment control strategy for personal accounts, verify whether the ticket change payment information satisfies the excessive payment control requirement that corporate account payments are not permitted;

[0066] If the conditions are met, the personal account payment is confirmed to implement the ticket change operation;

[0067] If not, continue to check whether the payment information for the ticket change meets the standard control of mixed payment; if so, determine that the personal payment has been changed; if not, continue to check whether the payment information for the ticket change meets the standard control of mixed payment or the reason for the selection of the standard;

[0068] If the requirements are met, the reason for the excess will be collected, and personal payment will be determined to implement the ticket change operation; if the requirements are not met, the ticket change payment information will be checked to see if it meets the non-bookable excess control. If it does, it will be determined that the ticket change operation cannot be carried out due to the excess.

[0069] Preferably, the second policy module further includes:

[0070] a sixth strategy unit, configured to, if the second ticket change strategy is the strategy for not restricting account payment under the over-limit control, verify whether the ticket change payment information satisfies the over-limit control that prohibits corporate account payment; and if so, determine that the ticket change operation is implemented through personal payment;

[0071] If not, continue to check whether the payment change information meets the excessive control of mixed payment;

[0072] If the conditions are met, continue to check whether the ticket change payment information satisfies the public account payment in the scenario of charging the ticket change fee; if the conditions are met, determine whether the ticket change operation is implemented by personal payment or hybrid payment; if the conditions are not met, when the ticket change operation requires payment of the ticket change fee to an external application, determine whether the ticket change operation is implemented by personal payment, or when the ticket change operation does not require payment of the ticket change fee to an external application, determine whether the ticket change operation is implemented by hybrid payment or personal payment; if the conditions are not met, continue to check whether the ticket change payment information satisfies the control of exceeding the standard that cannot be booked; if the conditions are met, determine that the ticket change operation cannot be implemented due to exceeding the standard;

[0073] If not, continue to check whether the payment information for the ticket change meets the requirements of mixed payment or the over-limit control based on the reason for the over-limit;

[0074] If satisfied, then continue to check whether the ticket change payment information satisfies the public account payment in the scenario of charging ticket change fees; if satisfied, determine mixed payment, or after collecting the reason for the excess, determine public account payment to implement the ticket change operation; if not satisfied, when the ticket change operation does not require payment of the ticket change fee to an external application, determine mixed payment, or after collecting the reason for the excess, determine public account payment to implement the ticket change operation, or when the ticket change operation requires payment of the ticket change fee to an external application, determine personal payment to implement the ticket change operation after collecting the reason for the excess;

[0075] If it is not satisfied, continue to check whether the change payment information meets the over-standard control with priority selection of the over-standard control reason; if it is satisfied, continue to check whether the change payment information meets the public account payment in the scenario of charging the change fee corresponding to the company account; if it is satisfied, select the over-standard reason and determine whether the public account payment or personal payment is used to realize the change operation. If it is not satisfied, when the change operation requires payment of the change fee to an external application, select the over-standard reason and determine that only personal payment is used to realize the change operation.

[0076] Preferably, the difference standard prediction module is specifically used to:

[0077] The first pre-judgment unit is configured to determine whether the predetermined payment information is a public account payment and the payment is for official travel; if so, the second pre-judgment unit is invoked;

[0078] The second pre-judgment unit is used to continue to judge whether the employee's change information meets the optional product level corresponding to the employee level and the price of the changed product does not exceed the price threshold; if so, it is determined that the change application meets the preset travel standards.

[0079] In a third aspect, the present disclosure further provides an electronic device comprising a processor, a memory, and a computer program stored on the memory and executable on the processor, wherein when the computer program is executed by the processor, the payment control method for product reissue as described in the first aspect is implemented.

[0080] In a fourth aspect, the present disclosure further provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the payment control method for product reissue as described in the first aspect.

[0081] In a fifth aspect, the present disclosure further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the payment control method for product reissue as described in the first aspect.

[0082] On the basis of conforming to the common sense in this field, the above-mentioned preferred conditions can be arbitrarily combined to obtain the preferred embodiments of the present disclosure.

[0083] The positive progress of the present disclosure is that it provides a payment control method, system, device, medium and program product for product rebooking, which determines whether the rebooking application meets the preset travel standards based on the employee's travel standard information and the scheduled payment information; if it meets the requirements, obtain the corresponding first rebooking strategy including the company account payment strategy, the personal account payment strategy and the company or personal account payment strategy for rebooking; if it does not meet the requirements, obtain the corresponding second rebooking strategy including the over-standard control company account payment strategy, the over-standard control personal account payment strategy and the over-standard control unrestricted account payment strategy for rebooking. The present disclosure solves the problem of inflexible payment method switching through the first rebooking strategy and the second rebooking strategy, avoids the losses caused by the company's public account payment for product rebooking, and strengthens the control of the company's travel budget. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] Figure 1 This is a first flow chart of the payment control method for product reissue according to Example 1 of the present disclosure.

[0085] Figure 2This is a second flow chart of the payment control method for product reissue according to embodiment 1 of the present disclosure.

[0086] Figure 3 This is a first flow chart of step S14 of the payment control method for product reissue in Example 1 of the present disclosure.

[0087] Figure 4 This is a second flow chart of step S14 of the payment control method for product reissue in embodiment 1 of the present disclosure.

[0088] Figure 5 This is a third flow chart of step S14 of the payment control method for product reissue in Example 1 of the present disclosure.

[0089] Figure 6 This is a schematic diagram of the first module of the payment control system for product reissue according to Example 2 of the present disclosure.

[0090] Figure 7 This is a schematic diagram of the second module of the payment control system for product reissue according to Example 2 of the present disclosure.

[0091] Figure 8 This is a schematic diagram of the hardware structure of the electronic device of Example 3 of the present disclosure. DETAILED DESCRIPTION

[0092] The present disclosure is further illustrated below by way of examples, but the present disclosure is not limited to the scope of the examples.

[0093] In the embodiments of the present disclosure, prefixes such as "first" and "second" are used only to distinguish different description objects, and have no limiting effect on the position, order, priority, quantity or content of the described objects. In the embodiments of the present disclosure, the use of prefixes such as ordinal numbers to distinguish description objects does not constitute a limitation on the described objects. For the statement of the described objects, please refer to the description in the context of the claims or embodiments, and no unnecessary limitations should be constituted due to the use of such prefixes. In addition, in the description of this embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

[0094] In the embodiments of the present disclosure, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0095] Example 1

[0096] This embodiment provides a payment control method for product reissue, such as Figure 1 As shown, the payment control method includes:

[0097] S11. Obtain product change information; the change information includes employee discount information, reservation payment information, and change payment information;

[0098] S12. Determine whether the change request meets the preset travel standards based on the employee's travel standard information and the scheduled payment information; if so, proceed to step S13; if not, proceed to step S14;

[0099] S13. Obtaining a corresponding first ticket change strategy based on the ticket change payment information, and implementing a product ticket change based on the first ticket change strategy; the first ticket change strategy includes a company account payment strategy, a personal account payment strategy, and a company or personal account payment strategy;

[0100] S14. Obtain the corresponding second change strategy based on the change payment information, and implement the product change according to the second change strategy; the second change strategy includes the over-standard control company account payment strategy, the over-standard control personal account payment strategy and the over-standard control unrestricted account payment strategy for change.

[0101] In this embodiment, the product change scenario includes multiple payment methods such as personal payment, public account payment, mixed payment and unrestricted payment (personal payment or public account payment). The scheduled payment information and the change payment information can include any one or more of the four payment methods.

[0102] Product changes are classified into three types according to price ranges: low-price changes to high-price changes, high-price changes to low-price changes, and other types of changes. In the case of low-price changes to high-price changes, additional fees need to be paid to external applications on the basis of the original ticket price. In the case of public account payments, the company needs to control this.

[0103] If the payment is made from a public account and the travel is official, and the rebooking request meets the preset travel standards, the company account payment policy corresponding to the public account payment method will be applied; if the payment is made from a personal account, the personal account payment policy will be applied; and if the payment is made from a public account, the company or personal account payment policy corresponding to the unrestricted payment method will be applied. If the payment is made from a public account and the travel is official, and the rebooking request does not meet the preset travel standards, the company account payment policy for the public account payment method will be applied; if the payment is made from a personal account, the personal account payment policy for the unrestricted payment method will be applied; and if the payment is made from an unrestricted payment method, the unrestricted account payment policy for the unrestricted payment method will be applied.

[0104] In one embodiment, if Figure 2 As shown, step S12 specifically includes:

[0105] S121, determining whether the scheduled payment information is a public account payment and the traveler is on official business; if so, executing step S122;

[0106] S122. Continue to determine whether the employee's travel change information meets the optional product level corresponding to the employee level and whether the price of the changed product does not exceed the price threshold; if so, determine that the change application meets the preset travel standards.

[0107] In this embodiment, when payment is made through a public account and the business trip meets the prerequisites of the preset travel standards, it is necessary to determine again based on the employee level whether the optional product level corresponding to the employee level in the corresponding employee difference standard information meets the conditions, and further determine whether the price of the rebooked product does not exceed the price threshold (for example, 100 yuan). If it exceeds, the rebooking application does not meet the preset travel standards.

[0108] In one embodiment, step S13 specifically includes:

[0109] If the first ticket change policy is the company account payment policy, check whether the ticket change payment information satisfies the public account payment requirement for the ticket change fee collection scenario;

[0110] If the conditions are met, the public account payment is confirmed to implement the change operation;

[0111] If not satisfied, when the ticket change operation does not require payment of a ticket change fee to an external application, it is determined that the ticket change operation is implemented through public account payment; or when the ticket change operation requires payment of a ticket change fee to an external application, it is determined that no account payment is available to implement the ticket change operation.

[0112] In one embodiment, step S13 specifically includes:

[0113] If the first ticket change strategy is the personal account payment strategy, personal payment is determined to implement the ticket change operation.

[0114] In one embodiment, step S13 specifically includes:

[0115] If the first ticket change policy is a company or personal account payment policy, check whether the ticket change payment information satisfies the public account payment requirement for ticket change fees.

[0116] If the conditions are met, the public account payment or personal payment is confirmed to implement the ticket change operation;

[0117] If not met, when the ticket change operation does not require payment of a ticket change fee to an external application, then public account payment or personal payment is determined to implement the ticket change operation; or when the ticket change operation requires payment of a ticket change fee to an external application, then personal payment is determined to implement the ticket change operation.

[0118] In this embodiment, product changes are made through company account payment strategies, personal account payment strategies, and company or personal account payment strategies, which solves the problem of inflexible payment method switching, avoids losses caused by the company's public account payments for product changes, and strengthens the management and control of the company's travel budget.

[0119] In one embodiment, Figure 3 As shown, step S14 specifically includes:

[0120] S1411. If the second ticket change policy is the over-limit control corporate account payment policy, check whether the ticket change payment information satisfies the over-limit control that prohibits corporate account payment; if so, determine that no account payment is available to implement the ticket change operation; if not, execute step S1412;

[0121] S1412. Check whether the ticket change payment information meets the excessive control requirements for mixed payment. If so, determine that no account is available for payment to implement the ticket change operation. If not, execute step S1413.

[0122] S1413. Check whether the change payment information meets the control requirements for non-bookable excess tickets. If so, determine that the change is not allowed due to the excess difference. If not, proceed to step S1414.

[0123] S1414: Check whether the payment information for the ticket change satisfies mixed payment or over-limit control for the selected over-limit reason. If so, check whether the payment information for the ticket change satisfies public account payment in the scenario of charging a ticket change fee. If not, proceed to step S1415.

[0124] S1415. When the ticket change operation requires payment of a ticket change fee to an external application, it is determined that there is no available account to pay for the ticket change operation; or when the ticket change operation does not require payment of a ticket change fee to an external application, after collecting the reason for the excess, it is determined that the public account payment is used to implement the ticket change operation.

[0125] In this embodiment, when checking that the changed payment information does not meet the mixed payment or the over-limit control with the reason of exceeding the limit is selected, the changed payment information is finally checked again to see whether it meets the over-limit control with the reason of exceeding the limit being selected first. If it meets the requirement, the changed payment information is continued to be checked to see whether it meets the public account payment in the scenario of charging the change fee. If it meets the requirement, the specific implementation steps are the same as S1415.

[0126] When the company account payment strategy is selected, the payment information for the rebooking will be sequentially checked to see if it meets one of the following control modes: non-company account payment (excess control), mixed payment (excess control applicable to both personal and public account payments), non-bookable (excess control), mixed payment or select excess reason (excess control), and priority (excess control). The target rebooking action corresponding to the satisfied excess control mode will be determined. This approach enriches the standard control mode for rebooking company account payments that exceed travel standards, enhances the flexibility of rebooking payment methods, and effectively controls the company's losses caused by public account payments for product rebooking.

[0127] In one embodiment, Figure 4 As shown, step S14 specifically includes:

[0128] S1421. If the second ticket change policy is the excess control personal account payment policy, check whether the ticket change payment information satisfies the excess control that prohibits corporate account payment; if so, determine that the ticket change operation is implemented through personal account payment; if not, execute step S1422;

[0129] S1422. Check whether the payment information for ticket change meets the requirements for excessive control of mixed payment. If so, determine that the personal payment is allowed to change the ticket. If not, proceed to step S1423.

[0130] S1423. Check whether the payment information for ticket change satisfies the mixed payment or the over-limit control for the selected over-limit reason. If so, collect the over-limit reason and determine the personal payment to implement the ticket change operation. If not, execute step S1424.

[0131] S1424. Check whether the payment information for ticket change meets the control requirements for excess booking. If so, determine that the ticket change operation is not allowed due to excess difference.

[0132] In this embodiment, when the check of the payment information for the ticket change does not meet the over-limit control of non-reservable, the payment information for the ticket change is checked again to see whether it meets the over-limit control with priority selection of the reason for the over-limit. If it meets the requirement, it is determined that only personal payment is used to realize the ticket change.

[0133] When selecting the strategy for exceeding standards for personal account payments, the payment information for rebooking is sequentially checked to see if it meets one of the following standards: exceeding standards for non-company account payments, exceeding standards for mixed payments that can be applied to both personal and public account payments, exceeding standards for mixed payments or selecting the reason for exceeding standards, exceeding standards for non-bookable travel, and exceeding standards for prioritizing the reason for exceeding standards. The target rebooking action corresponding to the exceeding standards control mode is then determined. This approach enriches the standard control modes for personal account payments that exceed business travel standards, enhances the flexibility of rebooking payment methods, and effectively manages losses caused by public account payments for product rebooking.

[0134] In one embodiment, Figure 5 As shown, step S14 specifically includes:

[0135] S1431. If the second ticket change policy is an over-limit control policy with no account payment restrictions, check whether the ticket change payment information satisfies the over-limit control policy that prohibits corporate account payments; if so, determine that personal payment is used to implement the ticket change operation; if not, execute step S1432.

[0136] S1432: Check whether the payment information for the ticket change meets the requirements for the over-limit control of mixed payment; if so, proceed to step S1433; if not, proceed to step S1434;

[0137] S1433. Continue to check whether the ticket change payment information satisfies the public account payment requirement for the ticket change fee charging scenario; if so, determine whether personal payment or hybrid payment is used to implement the ticket change operation; if not, if the ticket change operation requires payment of a ticket change fee to an external application, determine whether personal payment is used to implement the ticket change operation; or if the ticket change operation does not require payment of a ticket change fee to an external application, determine whether hybrid payment or personal payment is used to implement the ticket change operation;

[0138] S1434. Continue to check whether the change payment information meets the control requirements for exceeding the limit that cannot be booked; if so, determine that the change operation cannot be performed due to exceeding the limit; if not, execute step S1435;

[0139] S1435. Check whether the payment information for the ticket change satisfies the mixed payment or the over-limit control for the selected over-limit reason; if so, proceed to step S1436; if not, proceed to step S1437;

[0140] S1436. Check whether the ticket change payment information satisfies the requirement for public account payment in a ticket change fee charging scenario; if so, determine mixed payment, or collect the reason for the excess and determine public account payment to implement the ticket change operation; if not, if the ticket change operation does not require payment of the ticket change fee to an external application, determine mixed payment, or collect the reason for the excess and determine public account payment to implement the ticket change operation; if the ticket change operation requires payment of the ticket change fee to an external application, determine personal payment to implement the ticket change operation after collecting the reason for the excess;

[0141] S1437. Check whether the payment information for ticket change satisfies the over-limit control with priority given to the reason for over-limit control; if so, continue to check whether the payment information for ticket change satisfies the public account payment in the scenario of charging ticket change fees corresponding to the company account; if so, select the reason for over-limit and determine whether the ticket change operation is realized by public account payment or personal payment; if not, when the ticket change operation requires payment of the ticket change fee to an external application, select the reason for over-limit and determine that only personal payment is realized to realize the ticket change operation.

[0142] In this embodiment, when the policy of unrestricted account payment is selected for over-the-limit control, the payment information for rebooking is sequentially checked to see if it satisfies one of the following over-the-limit control modes: over-the-limit control for non-company account payments, over-the-limit control for mixed payments applicable to both personal and public account payments, over-the-limit control for non-reservable items, over-the-limit control for mixed payments, over-the-limit control based on selected over-the-limit reasons, or over-the-limit control with priority given to over-the-limit control reasons. The target rebooking operation corresponding to the satisfied over-the-limit control mode is then determined. This approach enriches the standard control modes for unrestricted account payments (e.g., personal or company account payments) that exceed travel standards, enhances the flexibility of rebooking payment methods, and effectively manages losses caused by the company's public account payments for product rebooking.

[0143] By implementing the company account payment strategy for exceeding the standard control, the personal account payment strategy for exceeding the standard control, and the unrestricted account payment strategy for exceeding the standard control to change products, the problem of inflexible payment method switching is solved, the company avoids losses caused by public account payments for product changes, and strengthens the control of the company's travel budget.

[0144] In this embodiment, a payment control method for product rebooking is provided. Through the first rebooking strategy and the second rebooking strategy, the problem of inflexible payment method switching is solved, the losses caused by the company's public account payments for product rebooking are avoided, and the control of the company's travel budget is strengthened.

[0145] Example 2

[0146] This embodiment provides a payment control system for product reissue, such as Figure 6 As shown, the payment control system includes:

[0147] Acquisition module 210, for acquiring product change related information; the change related information includes employee difference information, scheduled payment information and change payment information;

[0148] The difference standard prediction module 220 is used to determine whether the ticket change application meets the preset travel standards based on the employee difference standard information and the scheduled payment information; if it does, the first strategy module 230 is called; if it does not, the second strategy module 240 is called;

[0149] The first policy module 230 is used to obtain a corresponding first change policy based on the change payment information and implement the product change according to the first change policy; the first change policy includes a company account payment policy, a personal account payment policy, and a company or personal account payment policy;

[0150] The second strategy module 240 is used to obtain the corresponding second change strategy based on the change payment information, and to implement product change according to the second change strategy; the second change strategy includes the over-standard control company account payment strategy, the over-standard control personal account payment strategy and the over-standard control unrestricted account payment strategy for change.

[0151] In this embodiment, the product change scenario includes multiple payment methods such as personal payment, public account payment, mixed payment and unrestricted payment (personal payment or public account payment). The scheduled payment information and the change payment information can include any one or more of the four payment methods.

[0152] Product changes are classified into three types according to price ranges: low-price changes to high-price changes, high-price changes to low-price changes, and other types of changes. In the case of low-price changes to high-price changes, additional fees need to be paid to external applications on the basis of the original ticket price. In the case of public account payments, the company needs to control this.

[0153] If the travel is on official business and the payment is made through a public account, and the rebooking request meets the preset travel standards, the first policy module 230 will adopt the company account payment policy corresponding to the public account payment method, the personal account payment policy corresponding to the personal account payment method, or the company or personal account payment policy corresponding to the unrestricted payment method when rebooking. If the travel is on official business and the payment is made through a public account, and the rebooking request does not meet the preset travel standards, the second policy module 240 will adopt the excess control company account payment policy corresponding to the public account payment method, the excess control personal account payment policy corresponding to the personal account payment method, or the excess control unrestricted account payment policy corresponding to the unrestricted payment method when rebooking.

[0154] In one embodiment, if Figure 7 As shown, the difference standard prediction module 220 specifically includes:

[0155] The first pre-judgment unit 221 is used to determine whether the scheduled payment information is a public account payment and the payment is for official travel; if so, the second pre-judgment unit 222 is called;

[0156] The second pre-judgment unit 222 is used to continue to determine whether the employee's change information meets the optional product level corresponding to the employee level and the price of the changed product does not exceed the price threshold; if so, it is determined that the change application meets the preset travel standards.

[0157] In this embodiment, after the first prediction unit 221 determines that the payment is made from a public account and the business trip meets the prerequisites of the preset travel standards, it is necessary to determine again based on the employee level whether the optional product level corresponding to the employee level of the corresponding employee difference information meets the conditions, and further determine whether the price of the rebooked product does not exceed the price threshold (for example, 100 yuan). If it exceeds, the rebooking application does not meet the preset travel standards.

[0158] In one embodiment, the first policy module 230 specifically includes:

[0159] The first policy unit 231 is used to check whether the ticket change payment information satisfies the public account payment requirement in the ticket change fee collection scenario if the first ticket change policy is the company account payment policy;

[0160] If the conditions are met, the public account payment is confirmed to implement the change operation;

[0161] If not, when the ticket change operation does not require payment of a ticket change fee to an external application, it is determined that the ticket change operation is implemented through public account payment; or when the ticket change operation requires payment of a ticket change fee to an external application, it is determined that no account payment is available to implement the ticket change operation;

[0162] In one embodiment, the first policy module 230 specifically includes:

[0163] The second strategy unit 232 is configured to determine personal payment to implement the ticket change operation if the first ticket change strategy is a personal account payment strategy.

[0164] In one embodiment, the first policy unit 230 specifically includes:

[0165] The third policy unit 233 is configured to verify whether the ticket change payment information satisfies the requirement of paying the ticket change fee through a public account if the first ticket change policy is the company or personal account payment policy;

[0166] If the conditions are met, the public account payment or personal payment is confirmed to implement the ticket change operation;

[0167] If not met, when the ticket change operation does not require payment of a ticket change fee to an external application, then public account payment or personal payment is determined to implement the ticket change operation; or when the ticket change operation requires payment of a ticket change fee to an external application, then personal payment is determined to implement the ticket change operation.

[0168] In this embodiment, the problem of inflexible payment method switching is solved by changing the payment method through company account payment strategy, personal account payment strategy and company or personal account payment strategy, avoiding the losses caused by the company's public account payment for product changes and strengthening the management and control of the company's travel budget.

[0169] In one embodiment, the second policy module 240 specifically includes:

[0170] The fourth policy unit 241 is configured to check whether the rebooking payment information satisfies the over-limit control of not allowing corporate account payment if the second rebooking policy is the over-limit control corporate account payment policy;

[0171] If the conditions are met, it is determined that there is no available account to pay for the ticket change operation;

[0172] If not, continue to check whether the payment information for the ticket change meets the control of excessive mixed payment standards; if so, determine that there is no available account payment to implement the ticket change operation; if not, continue to check whether the payment information for the ticket change meets the control of excessive unreservable payment standards;

[0173] If the requirements are met, it is determined that the ticket change operation cannot be carried out because the difference standard is exceeded; if the requirements are not met, check whether the ticket change payment information meets the requirements of mixed payment or select the excess control of the reason for exceeding the standard. If the requirements are met, continue to check whether the ticket change payment information meets the requirements of public account payment in the scenario of charging ticket change fees. If the requirements are not met, when the ticket change operation requires payment of the ticket change fee to an external application, it is determined that there is no available account payment to realize the ticket change operation, or when the ticket change operation does not require payment of the ticket change fee to an external application, then after collecting the reason for exceeding the standard, it is determined that the ticket change operation is realized through public account payment.

[0174] In this embodiment, when checking that the changed payment information does not meet the mixed payment or the over-limit control with the reason of exceeding the limit is selected, the changed payment information is finally checked again to see whether it meets the over-limit control with the reason of exceeding the limit being selected first. If it meets the requirement, the changed payment information is continued to be checked to see whether it meets the public account payment in the scenario of charging the change fee. If it meets the requirement, the specific implementation steps are the same as S1415.

[0175] When the company account payment strategy is selected, the payment information for the rebooking will be sequentially checked to see if it meets one of the following control modes: non-company account payment (excess control), mixed payment (excess control applicable to both personal and public account payments), non-bookable (excess control), mixed payment or select excess reason (excess control), and priority (excess control). The target rebooking action corresponding to the satisfied excess control mode will be determined. This approach enriches the standard control mode for rebooking company account payments that exceed travel standards, enhances the flexibility of rebooking payment methods, and effectively controls the company's losses caused by public account payments for product rebooking.

[0176] In one embodiment, the second policy module 240 specifically includes:

[0177] The fifth policy unit 242 is configured to verify whether the payment information for the rebooking satisfies the over-limit control requirement that company account payments are not permitted when the second rebooking policy is the over-limit control policy for personal account payments.

[0178] If the conditions are met, the personal account payment is confirmed to implement the ticket change operation;

[0179] If not, continue to check whether the payment information for the changed ticket meets the over-limit control of mixed payment; if it meets the requirements, determine whether the personal payment can be changed; if not, continue to check whether the payment information for the changed ticket meets the over-limit control of mixed payment or the reason for the over-limit;

[0180] If the requirements are met, the reason for the excess will be collected, and personal payment will be determined to implement the ticket change operation; if the requirements are not met, the ticket change payment information will be checked to see if it meets the non-bookable excess control. If it does, it will be determined that the ticket change operation cannot be carried out due to the excess.

[0181] In this embodiment, when the check of the payment information for the ticket change does not meet the over-limit control of non-reservable, the payment information for the ticket change is checked again to see whether it meets the over-limit control with priority selection of the reason for the over-limit. If it meets the requirement, it is determined that only personal payment is used to realize the ticket change.

[0182] When selecting the strategy for exceeding standards for personal account payments, the payment information for rebooking is sequentially checked to see if it meets one of the following standards: exceeding standards for non-company account payments, exceeding standards for mixed payments that can be applied to both personal and public account payments, exceeding standards for mixed payments or those that select the reason for exceeding standards, exceeding standards for non-bookable items, or exceeding standards for those that prioritize the reason for exceeding standards. The target rebooking action corresponding to the exceeding standards control mode is then determined. This approach enriches the standard control modes for personal account payments that exceed business travel standards, enhances the flexibility of rebooking payment methods, and effectively manages losses caused by public account payments for product rebooking.

[0183] In one embodiment, the second policy module 240 specifically includes:

[0184] The sixth policy unit 243 is configured to, if the second ticket change policy is an over-limit control policy with no account payment restrictions, check whether the ticket change payment information satisfies the over-limit control requirement that prohibits corporate account payments; if so, determine that the ticket change operation is implemented through personal payment;

[0185] If not, continue to check whether the payment information for the changed ticket meets the excessive control requirements for mixed payments;

[0186] If the conditions are met, the process continues to check whether the ticket change payment information satisfies the public account payment requirement for the ticket change fee charging scenario. If the conditions are met, personal payment or hybrid payment is determined to implement the ticket change operation. If the conditions are not met, if the ticket change operation requires payment of a ticket change fee to an external application, personal payment is determined to implement the ticket change operation. If the ticket change operation does not require payment of a ticket change fee to an external application, hybrid payment or personal payment is determined to implement the ticket change operation.

[0187] If not, continue to check whether the change payment information meets the control of excessive booking that cannot be booked; if it does, it is determined that the change operation cannot be performed due to exceeding the difference standard;

[0188] If not, continue to check whether the payment information for the changed ticket meets the requirements for mixed payment or select the excess control based on the reason for the excess;

[0189] If the conditions are met, the system will continue to check whether the ticket change payment information satisfies the public account payment in the scenario of charging ticket change fees. If the conditions are met, a mixed payment method will be determined, or after collecting the reason for the excess, a public account payment method will be determined to implement the ticket change operation. If the conditions are not met, when the ticket change operation does not require payment of the ticket change fee to an external application, a mixed payment method will be determined, or after collecting the reason for the excess, a public account payment method will be determined to implement the ticket change operation. If the ticket change operation requires payment of the ticket change fee to an external application, a personal payment method will be determined to implement the ticket change operation after collecting the reason for the excess.

[0190] If it is not satisfied, continue to check whether the change payment information meets the over-standard control with priority given to the over-standard control reason; if it is satisfied, continue to check whether the change payment information meets the public account payment in the scenario of charging change fees corresponding to the company account; if it is satisfied, select the over-standard reason and determine whether the change operation is realized by public account payment or personal payment. If it is not satisfied, when the change operation requires payment of the change fee to an external application, select the over-standard reason and determine that only personal payment is realized to realize the change operation.

[0191] In this embodiment, when the policy of unrestricted account payment is selected for over-the-limit control, the payment information for rebooking is sequentially checked to see if it satisfies one of the following over-the-limit control modes: over-the-limit control for non-company account payments, over-the-limit control for mixed payments applicable to both personal and public account payments, over-the-limit control for non-reservable items, over-the-limit control for mixed payments, over-the-limit control based on selected over-the-limit reasons, or over-the-limit control with priority given to over-the-limit control reasons. The target rebooking operation corresponding to the satisfied over-the-limit control mode is then determined. This approach enriches the standard control modes for unrestricted account payments (e.g., personal or company account payments) that exceed travel standards, enhances the flexibility of rebooking payment methods, and effectively manages losses caused by the company's public account payments for product rebooking.

[0192] By implementing the company account payment strategy for exceeding the standard control, the personal account payment strategy for exceeding the standard control, and the unrestricted account payment strategy for exceeding the standard control to change products, the problem of inflexible payment method switching is solved, the company avoids losses caused by public account payments for product changes, and strengthens the control of the company's travel budget.

[0193] In this embodiment, the problem of inflexible payment method switching is solved by changing the payment method through company account payment strategy, personal account payment strategy and company or personal account payment strategy, avoiding the losses caused by the company's public account payment for product changes and strengthening the management and control of the company's travel budget.

[0194] Since the system embodiments generally correspond to the method embodiments, reference will be made to the description of the method embodiments for relevant details. The system embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components of the units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the disclosed solution.

[0195] Example 3

[0196] Figure 8This is a hardware structure diagram of an electronic device provided in this embodiment. The water heater includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the payment control method for product reissue in embodiment 1 is implemented. Figure 8 The electronic device 60 shown is only an example and should not limit the functionality and scope of use of the embodiments of the present disclosure.

[0197] The electronic device 60 may be a general-purpose computing device, such as a server device. Components of the electronic device 60 may include, but are not limited to, the at least one processor 61, the at least one memory 62, and a bus 63 connecting different system components (including the memory 62 and the processor 61).

[0198] The bus 63 includes a data bus, an address bus, and a control bus.

[0199] The memory 62 may include a volatile memory, such as a random access memory (RAM) 621 and / or a cache memory 622 , and may further include a read-only memory (ROM) 623 .

[0200] The memory 62 may also include a program / utility 625 having a set (at least one) of program modules 624, such program modules 624 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0201] The processor 61 executes various functional applications and data processing by running the computer programs stored in the memory 62, such as the payment control method for product reissue in Example 1 of the present disclosure.

[0202] The electronic device 60 can also communicate with one or more external devices 64 (e.g., a keyboard, pointing device, etc.). This communication can occur via an input / output (I / O) interface 65. Furthermore, the model-generating electronic device 60 can also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 66. As shown, the network adapter 66 communicates with other modules of the model-generating electronic device 60 via a bus 63. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the model-generating electronic device 60, including but not limited to microcode, device drivers, redundant processors, external disk drive arrays, RAID (RAID) systems, tape drives, and data backup storage systems.

[0203] It should be noted that although the above detailed description refers to several units / modules or sub-units / modules of the water heater, this division is merely exemplary and not mandatory. In fact, according to embodiments of the present disclosure, the features and functions of two or more units / modules described above may be embodied in a single unit / module. Conversely, the features and functions of a single unit / module described above may be further divided and embodied by multiple units / modules.

[0204] Example 4

[0205] This embodiment provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the steps of the payment control method for product reissue according to embodiment 1 are implemented.

[0206] The readable storage medium may include, but is not limited to, a portable disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0207] In a possible implementation, the present disclosure can also be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps of the payment control method for product reissue in Example 1.

[0208] The program code for executing the present disclosure may be written in any combination of one or more programming languages, and may be executed entirely on the user device, partially on the user device, as a standalone software package, partially on the user device and partially on a remote device, or entirely on the remote device.

[0209] Example 5

[0210] This embodiment also provides a computer program product, including a computer program, which, when executed by a processor, implements the payment control method for product reissue described in any one of the above items.

[0211] The program code for executing the computer program product of the present disclosure may be written in any combination of one or more programming languages, and the program code may be executed entirely on the user device, partially on the user device, as a standalone software package, partially on the user device and partially on a remote device, or entirely on the remote device.

[0212] While specific embodiments of the present disclosure have been described above, those skilled in the art will appreciate that these are merely illustrative and that the scope of protection of the present disclosure is defined by the appended claims. Those skilled in the art may make various changes or modifications to these embodiments without departing from the principles and essence of the present disclosure, and such changes and modifications are intended to fall within the scope of protection of the present disclosure.

Claims

1. A payment control method for product rebooking, characterized in that: The payment control method includes: Obtain product change-related information; the change-related information includes employee discount information, reservation payment information, and change payment information; Determining whether the change request meets the preset travel standards based on the employee's travel standard information and the scheduled payment information; If the conditions are met, the corresponding first ticket change strategy is obtained according to the ticket change payment information, and the product ticket is changed according to the first ticket change strategy; the first ticket change strategy includes a company account payment strategy, a personal account payment strategy, and a company or personal account payment strategy; If it does not comply, the corresponding second change strategy will be obtained based on the change payment information, and the product change will be implemented according to the second change strategy; the second change strategy includes the over-standard control company account payment strategy, the over-standard control personal account payment strategy and the over-standard control unrestricted account payment strategy for change.

2. The payment control method for product reissue according to claim 1, characterized in that: The step of obtaining a corresponding first ticket change strategy according to the ticket change payment information, and implementing the product ticket change according to the first ticket change strategy includes: If the first ticket change policy is the company account payment policy, checking whether the ticket change payment information satisfies the public account payment requirement under the ticket change fee collection scenario; If the conditions are met, the public account payment is confirmed to implement the change operation; If not, when the ticket change operation does not require payment of a ticket change fee to an external application, it is determined that the ticket change operation is implemented through public account payment; or when the ticket change operation requires payment of a ticket change fee to an external application, it is determined that no account payment is available to implement the ticket change operation; and / or, If the first ticket change strategy is the personal account payment strategy, determining personal payment to implement the ticket change operation; and / or, If the first ticket change policy is the company or personal account payment policy, checking whether the ticket change payment information satisfies the public account payment requirement for charging the ticket change fee; If the conditions are met, the public account payment or personal payment is confirmed to implement the ticket change operation; If not met, when the ticket change operation does not require payment of a ticket change fee to an external application, then public account payment or personal payment is determined to implement the ticket change operation; or when the ticket change operation requires payment of a ticket change fee to an external application, then personal payment is determined to implement the ticket change operation.

3. The payment control method for product reissue according to claim 1, characterized in that: The step of obtaining a corresponding second ticket change policy according to the ticket change payment information, and implementing the product ticket change according to the second ticket change policy includes: If the second ticket change strategy is the over-limit control corporate account payment strategy, checking whether the ticket change payment information satisfies the over-limit control that prohibits corporate account payment; If the conditions are met, it is determined that there is no available account to pay for the ticket change operation; If not, continue to check whether the change payment information meets the control of excessive mixed payment; if so, determine that no available account payment is available to implement the change operation; if not, continue to check whether the change payment information meets the control of excessive unreservable; If it meets the requirements, it is determined that the ticket change operation cannot be carried out because the difference standard is exceeded; if it does not meet the requirements, check whether the ticket change payment information meets the requirements of mixed payment or the over-standard control of the reason for exceeding the standard. If it meets the requirements, continue to check whether the ticket change payment information meets the requirements of public account payment in the scenario of charging ticket change fees. If it does not meet the requirements, when the ticket change operation requires payment of the ticket change fee to an external application, it is determined that there is no available account payment to realize the ticket change operation, or when the ticket change operation does not require payment of the ticket change fee to an external application, then after collecting the reason for exceeding the standard, it is determined that the ticket change operation is realized through public account payment.

4. The payment control method for product reissue according to claim 1, characterized in that: The step of obtaining a corresponding second ticket change policy according to the ticket change payment information, and implementing the product ticket change according to the second ticket change policy includes: If the second ticket change policy is the excessive control personal account payment policy, checking whether the ticket change payment information satisfies the excessive control that prohibits corporate account payment; If the conditions are met, the personal account payment is confirmed to implement the ticket change operation; If not, continue to check whether the payment information for the ticket change meets the standard control of mixed payment; if so, determine that the personal payment has been changed; if not, continue to check whether the payment information for the ticket change meets the standard control of mixed payment or the reason for the selection of the standard; If the requirements are met, the reason for the excess will be collected, and personal payment will be determined to implement the ticket change operation; if the requirements are not met, the ticket change payment information will be checked to see if it meets the non-bookable excess control. If it does, it will be determined that the ticket change operation cannot be carried out due to the excess.

5. The payment control method for product reissue according to claim 1, characterized in that: The step of obtaining a corresponding second ticket change policy according to the ticket change payment information, and implementing the product ticket change according to the second ticket change policy includes: If the second ticket change policy is the policy of not restricting account payment under the excess control, checking whether the ticket change payment information satisfies the excess control that prohibits corporate account payment; if so, determining that personal payment is used to implement the ticket change operation; If not, continue to check whether the payment change information meets the excessive control of mixed payment; If satisfied, continue to check whether the ticket change payment information satisfies the public account payment in the scenario of charging a ticket change fee; if satisfied, determine whether personal payment or hybrid payment is used to implement the ticket change operation; if not satisfied, when the ticket change operation requires payment of a ticket change fee to an external application, determine whether personal payment is used to implement the ticket change operation; or when the ticket change operation does not require payment of a ticket change fee to an external application, determine whether hybrid payment or personal payment is used to implement the ticket change operation; If not, continue to check whether the change payment information meets the control of exceeding the limit that cannot be booked; if it does, determine that the change operation is not allowed due to exceeding the limit; If not, continue to check whether the payment information for the ticket change meets the requirements of mixed payment or the over-limit control based on the reason for the over-limit; If satisfied, then continue to check whether the ticket change payment information satisfies the public account payment in the scenario of charging ticket change fees; if satisfied, determine mixed payment, or after collecting the reason for the excess, determine public account payment to implement the ticket change operation; if not satisfied, when the ticket change operation does not require payment of the ticket change fee to an external application, determine mixed payment, or after collecting the reason for the excess, determine public account payment to implement the ticket change operation, or when the ticket change operation requires payment of the ticket change fee to an external application, determine personal payment to implement the ticket change operation after collecting the reason for the excess; If it is not satisfied, continue to check whether the change payment information meets the over-standard control with priority selection of the over-standard control reason; if it is satisfied, continue to check whether the change payment information meets the public account payment in the scenario of charging the change fee corresponding to the company account; if it is satisfied, select the over-standard reason and determine whether the public account payment or personal payment is used to realize the change operation. If it is not satisfied, when the change operation requires payment of the change fee to an external application, select the over-standard reason and determine that only personal payment is used to realize the change operation.

6. The payment control method for product reissue according to claim 1, characterized in that: The step of determining whether the ticket change application meets the preset travel standards based on the employee travel standard information and the scheduled payment information includes: Determining whether the scheduled payment information is for a public account payment and the travel is for official business; If so, continue to determine whether the employee's change information meets the optional product level corresponding to the employee level and the price of the changed product does not exceed the price threshold; if it does, determine that the change application meets the preset travel standards.

7. A payment control system for product reissue, characterized in that: The payment control system includes: An acquisition module is used to obtain product change-related information; the change-related information includes employee discount information, scheduled payment information, and change payment information; A difference standard prediction module is used to determine whether the ticket change application meets the preset travel standards based on the employee difference standard information and the scheduled payment information; if so, call the first strategy module; if not, call the second strategy module; The first policy module is configured to obtain a corresponding first ticket change policy based on the ticket change payment information, and implement a product ticket change based on the first ticket change policy; the first ticket change policy includes a company account payment policy, a personal account payment policy, and a company or personal account payment policy; The second strategy module is used to obtain the corresponding second change strategy based on the change payment information, and to implement product change according to the second change strategy; the second change strategy includes the over-standard control company account payment strategy, the over-standard control personal account payment strategy and the over-standard control unrestricted account payment strategy for change.

8. An electronic device, characterized in that: The invention comprises a processor, a memory and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the payment control method for product reissue according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, it implements the payment control method for product reissue according to any one of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the payment control method for product reissue according to any one of claims 1 to 6 is implemented.

Images