WO2024041316A1 - 支付处理方法及装置 - Google Patents

支付处理方法及装置 Download PDF

Info

Publication number
WO2024041316A1
WO2024041316A1 PCT/CN2023/110186 CN2023110186W WO2024041316A1 WO 2024041316 A1 WO2024041316 A1 WO 2024041316A1 CN 2023110186 W CN2023110186 W CN 2023110186W WO 2024041316 A1 WO2024041316 A1 WO 2024041316A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
type
order
user
target
Prior art date
Application number
PCT/CN2023/110186
Other languages
English (en)
French (fr)
Inventor
王峰
Original Assignee
支付宝（中国）网络技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 支付宝（中国）网络技术有限公司 filed Critical 支付宝（中国）网络技术有限公司
Publication of WO2024041316A1 publication Critical patent/WO2024041316A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102—Bill distribution or payments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635—Processing of requisition or of purchase orders

Definitions

  • This document relates to the field of payment technology, and in particular to a payment processing method and device.
  • One or more embodiments of this specification provide a payment processing method, including: determining the obtained payment classification label of the user's payment order. Match the payment classification tag with a payment type in a payment type set. If the matching is successful, the payment channel configuration set by the user for the target payment type is read according to the target payment type carried in the matching result. Payment processing of the payment order is performed based on the payment channel configuration.
  • One or more embodiments of this specification provide a payment processing device, including: a determination module configured to determine the acquired payment classification label of the user's payment order.
  • a matching module configured to match the payment classification tag with the payment type in the payment type set. If the match is successful, run the configuration reading module.
  • the configuration reading module is configured to read the payment channel configuration set by the user for the target payment type according to the target payment type carried in the matching result.
  • the payment module is configured to perform payment processing of the payment order based on the payment channel configuration.
  • One or more embodiments of the present specification provide a payment processing device, including: a processor; and, a memory configured to store computer-executable instructions that, when executed, cause the processor to: Determine the payment category label of the obtained user's payment order. Match the payment classification tag with a payment type in a payment type set. If the matching is successful, the payment channel configuration set by the user for the target payment type is read according to the target payment type carried in the matching result. Payment processing of the payment order is performed based on the payment channel configuration.
  • One or more embodiments of this specification provide a storage medium for storing computer-executable instructions.
  • the computer-executable instructions When executed by a processor, the computer-executable instructions implement the following process: determine the acquired payment classification label of the user's payment order. . Match the payment classification tag with a payment type in a payment type set. If the matching is successful, the payment channel configuration set by the user for the target payment type is read according to the target payment type carried in the matching result. Payment processing of the payment order is performed based on the payment channel configuration.
  • Figure 1 is an execution flow chart of a payment processing method provided by one or more embodiments of this specification
  • Figure 2 is a schematic diagram of a payment settings page provided by one or more embodiments of this specification.
  • Figure 3 is a schematic diagram of a tab page provided by one or more embodiments of this specification.
  • Figure 4 is a schematic diagram of a settings sub-page provided by one or more embodiments of this specification.
  • Figure 5 is a schematic diagram of a payment channel adding page provided by one or more embodiments of this specification.
  • Figure 6 is an execution flow chart of a payment processing method applied to the first payment scenario provided by one or more embodiments of this specification;
  • Figure 7 is an execution flow chart of a payment processing method applied to the second payment scenario provided by one or more embodiments of this specification;
  • Figure 8 is a schematic diagram of a payment processing device provided by one or more embodiments of this specification.
  • Figure 9 is a schematic structural diagram of a payment processing device provided by one or more embodiments of this specification.
  • An embodiment of a payment processing method provided in this specification is based on setting corresponding payment channel configurations for payment channels of different payment types.
  • the payment classification label of the user's payment order matches the payment classification label with the payment type in the payment type set composed of payment types, obtains the target payment type that matches the payment classification label, and further reads the payment set for the target payment type Channel configuration, and payment processing of payment orders based on payment channel configuration, in order to perform personalized payment processing for different types of payment orders, thereby meeting the payment needs of different users for different payment types and increasing the flexibility of payment processing. , improving the convenience of user payment.
  • this embodiment provides a payment processing method, which specifically includes steps S102 to S108.
  • Step S102 Determine the obtained payment classification label of the user's payment order.
  • the payment classification label in this embodiment refers to the label used to identify the order type of the payment order.
  • the payment classification label of the payment order generated by the user for online shopping is “online shopping”
  • the payment classification label of the payment order generated by the user for offline shopping is “offline shopping”
  • the payment classification label of the payment order generated by the user for bank transfer is "transfer”.
  • This embodiment provides two optional implementation methods for determining payment classification labels. The two methods for determining payment classification labels will be described in detail below.
  • the payment classification label is determined in the following manner: reading the order classification label recorded in the payment order as the payment classification label.
  • the payment classification label is determined in the following manner: the payment classification label is determined based on the order data carried in the payment order.
  • the order classification label recorded in the payment order can be read; for example, the order type of the payment order record generated by the user for online shopping If the label is "Online Shopping", then the label "Online Shopping" is read and the payment classification label of the payment order is determined; in addition, if the payment order does not record an order classification label, the payment order label can be determined according to the order classification label.
  • the order data carried by the payment order determines the payment classification label; the order data includes the merchant name, merchant type and/or account type; for example, the payment order generated by the user for offline shopping carries a scan code payment mark. According to the Scan code to pay
  • the payment tag can determine that the payment category label of the payment order is "offline shopping".
  • the label input by the user for the payment order can also be collected as the payment classification label to determine the payment classification label of the payment order. For example, when a user watches a live broadcast and rewards an anchor for a payment order, he or she can enter a label "live broadcast reward”. In this case, the collected user-entered "live broadcast reward" label will be used as the reward for the anchor.
  • the payment classification label of the generated payment order when a user watches a live broadcast and rewards an anchor for a payment order, he or she can enter a label "live broadcast reward".
  • the collected user-entered "live broadcast reward" label will be used as the reward for the anchor.
  • Step S104 Match the payment classification label with the payment type in the payment type set.
  • the payment type described in this embodiment refers to the payment scenario or payment environment for processing payment orders, such as the payment scenario for paying for orders generated by online shopping, and the payment scenario for paying for orders generated by offline store payment. , the payment scenario where the order generated by the red envelope transfer is paid.
  • the payment type set in this embodiment refers to a set of at least one payment type, such as a payment type set consisting of online payment, offline payment, and red envelope payment.
  • the payment classification tag is matched with the payment types in the payment type set, and after matching, a matching result of successful matching or failed matching is obtained; in the case of successful matching, the following step S106 is executed; in the case of failed matching In this case, a matching failure reminder is sent to the user, or the payment priority of the global payment channel is read, and the payment processing of the payment order is performed according to the payment order in which the payment priority of the global payment channel is read.
  • the payment classification label in the process of matching the payment classification label with the payment types in the payment type set, can be compared with each payment type in the payment type set, and the payment types can be calculated respectively. Based on the similarity between the payment classification tag and each payment type in the payment type set, select a payment type with a higher similarity as the target payment type to accurately classify payment orders and help users arrange consumption reasonably. For example, if the payment category label of the payment order is "online shopping", then it is compared with the payment types in the payment type set. If it matches the payment type of online shopping, it is determined that the payment type of this payment is online shopping.
  • the payment types in the payment type set are respectively set with respective payment channel configurations; wherein the payment channel configuration of the payment type includes: at least one payment channel for order payment settings under the payment type. , and the payment priority of at least one payment channel.
  • the payment priority refers to the priority of selecting payment channels when making payment, that is, the payment order of payment channels.
  • the payment channel configuration set for this payment type includes three payment channels: account balance payment, debit card payment, and credit payment, as well as the payment sequence of these three payment channels, as shown in Figure 4 shown.
  • a recommendation list is provided to the user. , enabling users to customize the priority of payment channels. For example, at least one payment channel corresponding to the payment order generated by the user's payment in an offline store is account balance payment, and the payment priority order from high to low is account balance payment. ->Credit payment->Credit card payment->Debit card payment.
  • the payment priority is determined in the following manner: based on the user's preference data, the payment priority of the payment channels in the recommendation list is determined; the recommendation list is determined by the It consists of at least one payment channel mentioned above.
  • At least one payment channel is obtained A recommended list.
  • the payment priority of the payment channels in the recommended list is determined based on the user's preference data.
  • the order of the payment channels in the recommended list is adjusted according to the user's adjustment instructions to obtain The adjusted recommendation list, the payment priority of the payment channels in the adjusted recommendation list is determined based on the order of the user's adjusted payment channels.
  • the payment types in the payment type set are set with their own payment channel configurations.
  • the order of the recommended list determined based on the user's preference data is: credit payment, debit card payment,
  • the user's adjusted payment order is account balance payment, debit card payment, and credit payment, and the adjusted payment order will be regarded as the payment priority.
  • the recommended list of any one of the at least one payment type is displayed through the settings sub-page of any one of the payment types, and the user enters the tab page by triggering the settings entry configured on the settings page of the application. , the user enters the setting sub-page of the corresponding payment type by triggering the type tag entry configured on the tag page.
  • the user enters the tab page shown in Figure 3 by triggering the "payment personality configuration" setting entry configured on the settings page of the application shown in Figure 2, where the available status of the payment personality configuration can be set through the status control 302; Enter the setting subpage shown in Figure 4 by triggering the "offline shopping" type tag entrance 304 configured on the tag page; to adjust the order of the payment channels for "offline shopping”; wherein, the user can set the online shopping mode through the status control 402
  • the available state for shopping is lowered; the payment sequence of the payment channel is adjusted by triggering the adjustment control 404 of "Credit Payment".
  • the payment type setting sub-page is provided with a type control corresponding to the payment type. If the control status of the type control is on, then the type control to which the type control belongs The payment status of the payment type is Available.
  • a type control corresponding to the payment type can also be set on the payment type setting sub-page. If the control status of the type control is on, then the The payment status of the payment type to which the above type control belongs is available.
  • a type control corresponding to the payment type can be set on the payment type setting sub-page. If the control state of the trigger control is on, then The payment status of all payment types in the payment type set is the available status. If the control status of the type control is the open status, the payment status of the payment type to which the type control belongs is the available status.
  • online payment setting subpage For example, if the online payment setting subpage is set with an online payment type control and is turned on, then online payment is available.
  • the payment classification tag is matched with the payment type in the payment type set. If the matching is successful, the following step S106 is executed, and the user's request for the payment type is read according to the target payment type carried in the matching result.
  • the payment processing of the payment order is performed based on the global payment channel configuration. Realize reading the payment order of the payment priority of the global payment channel and retrograde payment processing of the payment order; specifically, in an optional implementation provided by this embodiment, all the steps are performed based on the global payment channel configuration.
  • the payment processing of the payment order includes: reading the payment priority of the global payment channel, and performing the payment processing of the payment order according to the payment sequence of reading the payment priority of the global payment channel.
  • the matching The similarity is used as the basis for judging the matching results.
  • the payment priority of the global payment channel is read, and then the target payment channel with the highest payment priority is selected, and the target payment channel is used for payment to ensure that the user's payment is successfully completed; if the payment If it fails, the payment channel with the next payment priority will be selected for payment until the payment is completed.
  • the settings sub-page shows the payment order of the payment priority of the user's global payment channel.
  • the account balance payment channel is the first choice. If the payment fails, the next payment priority is selected. Make the payment through the payment channel of debit card payment, and so on until the payment is successful.
  • Payment types with a similarity higher than the threshold can meet the payment needs of different users; for example, when a user rewards an anchor while watching a live broadcast, and no payment type is matched in the payment type set, online shopping can be recommended as a highly similar payment type.
  • Payment Type As the target payment type, read the list of payment channels for the payment type of online shopping.
  • Step S106 According to the target payment type carried in the matching result, read the payment channel configuration set by the user for the target payment type.
  • the payment channel configuration set by the user for the target payment type is read.
  • the payment type of the payment order is recorded in the matching result, and the payment channel list set by the user for the payment type is read.
  • the classification label corresponding to the user's payment order based on red envelope transfer is online payment.
  • the online payment is matched with the online payment in the payment type set. If the match is successful and the target payment type is online shopping, read List of payment channels for this payment type for online shopping.
  • the following operations are also performed: determine whether the corresponding payment status of the target payment type is available; if so, perform the reading of the user's payment status for the target The payment channel configuration set by the payment type; if not, the payment processing of the payment order is performed based on the global payment channel configuration.
  • the payment classification label is matched with the payment type in the payment type set, and after the matching is successful, it is determined whether the payment status of the target payment type carried in the matching result is an available status, and if so, the reading of the user is performed.
  • the payment channel configuration step set for the target payment type; if not, perform payment processing of the payment order based on the global payment channel configuration.
  • Step S108 Perform payment processing of the payment order based on the payment channel configuration.
  • the payment order is processed based on the payment channel configuration.
  • the payment order is processed based on the payment channel configuration.
  • Payment processing includes: reading the user's payment channel configuration, and performing payment processing on the payment order based on the payment priority of the user's payment channel configuration.
  • the payment process based on the payment priority is provided.
  • the payment priority of the payment channel configured by the user is used to process the payment order, including:
  • the payment priority of a payment channel set by the user for the target payment type is obtained. level, select the payment channel with the highest payment priority of the target payment type, and make the payment through this payment channel; after the payment fails, select the payment channel with the next highest payment priority of the target payment channel. Payment, or determining a payment channel on the at least one payment channel based on the user's payment history data and performing payment processing.
  • the user's priority payment channel for online shopping is credit card payment.
  • the credit card payment fails, it is detected that the user has paid for online shopping through the credit payment channel.
  • the payment processing method first determines the payment classification label of the user's payment order, and then matches the payment classification label with the payment type in the payment type set. If the matching is successful, then the payment classification label is matched according to the matching For the target payment type carried in the result, read the payment channel configuration set by the user for the target payment type, and finally process the payment order according to the payment channel configuration, so as to meet the different requirements of different users for online payment methods; further , when the execution result after the step of matching the payment classification label and the payment type in the payment type set is a successful match, read the payment channel configuration operation set by the user for the target payment type, and determine the Check whether the corresponding payment status of the target payment type is available, and perform the payment channel configuration operation set by the user for the target payment type, so as to avoid the user's payment failure due to unavailable payment status and improve the user's payment effectiveness.
  • Step S602 Read the payment classification tag recorded in the user's payment order.
  • Step S604 Match the payment classification label with the payment type in the payment type set; if the matching is successful, perform steps S606 to S608; if the matching fails, perform step S612.
  • Step S606 According to the target payment type carried in the matching result, read the payment channel configuration set by the user for the target payment type.
  • the user enters the tag page by triggering the setting entry configured on the setting page of the application program, and the user enters the setting sub-page of the corresponding payment type by triggering the type tag entry configured on the tag page.
  • the payment type setting sub-page is set with a type control corresponding to the payment type. If the control status of the type control is an open state, the payment status of the payment type to which the type control belongs is an available state. .
  • Step S608 Determine whether the corresponding payment status of the target payment type is an available status; if yes, execute step S610; if not, execute step S612.
  • Step S610 Perform payment processing on the payment order based on the payment priority configured in the payment channel set by the target payment type.
  • the payment processing of the payment order is performed based on the payment priority of the payment channel configuration set by the target payment type, including: if the first target payment channel pays successfully, the process ends; if the first target payment channel fails to pay , then select the payment channel with the payment priority next to the target payment channel to make the payment until the payment is successful and the process ends; if the payment result of each payment channel in the target payment channel for the order is payment failure , then a payment failure reminder is sent to the user.
  • Step S612 Perform payment processing of the payment order based on the global payment channel configuration.
  • step S602 the following steps may also be performed: obtain a recommended list of the at least one payment channel and send it to the user; and determine the payment priority of the payment channel in the recommended list based on the user's preference data. ; Further, the payment priority may be determined based on the user's adjustment instructions for adjusting the payment channels in the recommendation list.
  • the following takes the application of a payment processing device provided by this embodiment in the second payment scenario as an example.
  • the payment processing method provided by this embodiment is further described in conjunction with Figure 7. See Figure 7 for application in the second payment scenario.
  • the payment processing method specifically includes the following steps.
  • Step S702 Determine the payment classification label based on the order data carried in the user's payment order.
  • Step S704 Match the payment classification label with the payment type in the payment type set; if the matching is successful, execute step S706; if the matching fails, execute step S712.
  • Step S706 Determine whether the control status of the trigger control set on the tab page is in the on state; if so, execute steps S708 to step S710; if not, execute step S714.
  • the user enters the tag page by triggering the setting entry configured on the setting page of the application program, and the user enters the setting sub-page of the corresponding payment type by triggering the type tag entry configured on the tag page.
  • the payment type setting sub-page is set with a type control corresponding to the payment type. If the control status of the type control is an open state, the payment status of the payment type to which the type control belongs is an available state. .
  • Step S708 According to the target payment type carried in the matching result, read the payment channel configuration set by the user for the target payment type.
  • Step S710 Perform payment processing on the payment order based on the payment priority configured in the payment channel set by the target payment type.
  • the payment processing of the payment order is performed based on the payment priority of the payment channel configuration set by the target payment type, including: if the first target payment channel pays successfully, the process ends; if the first target payment channel fails to pay , then select the payment channel with the payment priority next to the target payment channel to make the payment until the payment is successful and the process ends; if the payment result of each payment channel in the target payment channel for the order is payment failure , then a payment failure reminder is sent to the user.
  • Step S712 Recommend payment types in the payment type set whose similarity to the payment type tag is higher than a threshold to the user.
  • Step S714 Perform payment processing of the payment order based on the global payment channel configuration.
  • step S702 the following steps may also be performed: obtain a recommended list of the at least one payment channel and send it to the user; determine the payment priority of the payment channel in the recommended list based on the user's preference data; further , the payment priority may be determined based on the user's adjustment instruction for adjusting the payment channels in the recommendation list.
  • FIG. 8 a schematic diagram of a payment processing device provided in this embodiment is shown.
  • the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above.
  • the device embodiments described below are merely illustrative.
  • This embodiment provides a payment processing device, including: a determination module 802, configured to determine the obtained payment classification label of the user's payment order; a matching module 804, configured to match the payment classification label with a payment type set The payment type is matched; if the match is successful, the configuration reading module 806 is run.
  • the configuration reading module 806 is configured to read the settings set by the user for the target payment type according to the target payment type carried in the matching result.
  • Payment channel configuration; the payment module 808 is configured to perform payment processing of the payment order based on the payment channel configuration.
  • FIG. 9 is a schematic structural diagram of a payment processing device provided by one or more embodiments of this specification.
  • the payment processing device may vary greatly due to different configurations or performance, and may include one or more processors 901 and memories 902.
  • the memory One or more storage applications or data may be stored in 902.
  • the memory 902 may be short-term storage or persistent storage.
  • Applications stored in memory 902 may include one or more modules (not shown), each of which may include a sequence of computer-executable instructions in the payment processing device.
  • the processor 901 may be configured to communicate with the memory 902 to execute a series of computer-executable instructions in the memory 902 on the payment processing device.
  • the payment processing device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input/output interfaces 905, one or more keyboards 906, etc.
  • the payment processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each Each module may include a series of computer-executable instructions in a payment processing device, and the one or more programs configured to be executed by one or more processors may include computer-executable instructions for: determining the acquired user's The payment classification label of the payment order; match the payment classification label with the payment type in the payment type set; if the match is successful, read the user's target payment type according to the target payment type carried in the matching result Set payment channel configuration; perform payment processing of the payment order based on the payment channel configuration.
  • An example of a storage medium provided in this specification is as follows: Corresponding to a payment processing method described above and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
  • the storage medium provided by this embodiment is used to store computer executable instructions.
  • the computer executable instructions When executed by the processor, the computer executable instructions implement the following process: determine the obtained payment classification label of the user's payment order; convert the payment classification label Match with the payment types in the payment type set; if the match is successful, read the payment channel configuration set by the user for the target payment type according to the target payment type carried in the matching result; perform based on the payment channel configuration Payment processing of said payment order.
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers and embedded microcontrollers.
  • controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, For Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.
  • the controller in addition to implementing the controller in the form of pure computer-readable program code, the controller can be completely programmed with logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded logic by logically programming the method steps. Microcontroller, etc. to achieve the same function. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as structures within hardware components as well as software modules implementing the methods.
  • a typical implementation device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
  • one or more embodiments of this specification may be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may be implemented entirely in hardware or entirely in software. embodiments, or embodiments that combine software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in computer-readable media, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information.
  • Information may be computer-readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, tape disk storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device.
  • computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • One or more embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.
  • One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network.
  • program modules may be located in both local and remote computer storage media including storage devices.

Landscapes

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

Abstract

本说明书实施例提供了一种支付处理方法及装置，其中，一种支付处理方法包括：确定获取的用户的支付订单的支付分类标签；将所述支付分类标签与支付类型集合中的支付类型进行匹配；若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；基于所述支付渠道配置进行所述支付订单的支付处理。

Description

支付处理方法及装置 技术领域
本文件涉及支付技术领域，尤其涉及一种支付处理方法及装置。
背景技术
随着电子商务的发展和普及，用户使用线上支付方式的频率越来越高，网络支付系统得到越来越广泛地应用，同时也为用户日常生活带来了很大便利。并且随着用户生活水平的提高，线上支付渠道也在不断拓展，不同用户对线上支付方式的要求也越来越多样化，这也对线上支付的提供方提出了更高的考验。
发明内容
本说明书一个或多个实施例提供了一种支付处理方法，包括：确定获取的用户的支付订单的支付分类标签。将所述支付分类标签与支付类型集合中的支付类型进行匹配。若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置。基于所述支付渠道配置进行所述支付订单的支付处理。
本说明书一个或多个实施例提供了一种支付处理装置，包括：确定模块，被配置为确定获取的用户的支付订单的支付分类标签。匹配模块，被配置为将所述支付分类标签与支付类型集合中的支付类型进行匹配。若匹配成功，运行配置读取模块，所述配置读取模块，被配置为根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置。支付模块，被配置为基于所述支付渠道配置进行所述支付订单的支付处理。
本说明书一个或多个实施例提供了一种支付处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：确定获取的用户的支付订单的支付分类标签。将所述支付分类标签与支付类型集合中的支付类型进行匹配。若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置。基于所述支付渠道配置进行所述支付订单的支付处理。
本说明书一个或多个实施例提供了一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：确定获取的用户的支付订单的支付分类标签。将所述支付分类标签与支付类型集合中的支付类型进行匹配。若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置。基于所述支付渠道配置进行所述支付订单的支付处理。
附图说明
为了更清楚地说明本说明书一个或多个实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图；
图1为本说明书一个或多个实施例提供的一种支付处理方法执行流程图；
图2为本说明书一个或多个实施例提供的一种支付设置页面示意图；
图3为本说明书一个或多个实施例提供的一种标签页面示意图；
图4为本说明书一个或多个实施例提供的一种设置子页面示意图；
图5为本说明书一个或多个实施例提供的一种支付渠道添加页面示意图；
图6为本说明书一个或多个实施例提供的一种应用于第一支付场景的支付处理方法执行流程图；
图7为本说明书一个或多个实施例提供的一种应用于第二支付场景的支付处理方法执行流程图；
图8为本说明书一个或多个实施例提供的一种支付处理装置示意图；
图9为本说明书一个或多个实施例提供的一种支付处理设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
本说明书提供的一种支付处理方法实施例：本申请提供的支付处理方法，在不同支付类型的支付渠道设置相应的支付渠道配置的基础上，对用户的支付订单进行支付的过程中，确定获取的用户的支付订单的支付分类标签，将支付分类标签与支付类型组成的支付类型集合中的支付类型进行匹配，获得与支付分类标签匹配的目标支付类型，进一步读取针对目标支付类型设置的支付渠道配置，并基于支付渠道配置进行支付订单的支付处理，以此针对不同类型的支付订单进行个性化支付处理，从而来满足不同用户对于不同的支付类型的支付需求，增加了支付处理的灵活性，提升了用户支付的便捷性。
参照图1，本实施例提供支付处理方法，所述方法具体包括步骤S102至步骤S108。
步骤S102，确定获取的用户的支付订单的支付分类标签。
本实施例所述支付分类标签，是指用于标识支付订单的订单类型的标签，比如用户针对线上购物产生的支付订单的支付分类标签为“线上购物”，用户针对线下购物产生支付订单的支付分类标签为“线下购物”，用户针对银行转账产生的支付订单的支付分类标签为“转账”。
具体实施时，首先，获取用户的支付订单之后，在获取用户的支付订单基础上，确定支付订单的支付分类标签，将确定的支付分类标签作为后续与支付类型集合中的支付类型进行匹配的数据依据，以此来确定用户支付时的支付场景，从而满足不同用户对不同支付场景的支付诉求，使用户体验到更加灵活、个性化的支付。
本实施例提供两种确定支付分类标签的可选实施方式，下述针对两种支付分类标签的确定方式进行详细说明。
本实施例提供的一种可选实施方式中，所述支付分类标签，采用如下方式确定：读取所述支付订单中记录的订单分类标签，作为所述支付分类标签。
本实施例提供的另一种可选实施方式中，所述支付分类标签，采用如下方式确定：根据所述支付订单携带的订单数据确定所述支付分类标签。
具体执行过程中，可在所述支付订单中记录有订单分类标签的情况下，读取所述支付订单中记录的订单分类标签；例如，用户针对线上购物产生的支付订单记录的订单类型的标签为“线上购物”，则读取“线上购物”这一标签并确定为该支付订单的支付分类标签；此外，可在所述支付订单未记录有订单分类标签的情况下，根据所述支付订单携带的订单数据确定所述支付分类标签；所述订单数据包括商家名称、商家类型和/或账户类型；例如，用户针对线下购物产生的支付订单携带有扫码支付标记，根据该扫码支 付标记可以确定该支付订单的支付分类标签为“线下购物”。
除此之外，在确定支付分类标签的过程中，还可以采集用户针对支付订单输入的标签作为支付分类标签的方式，来确定所述支付订单的支付分类标签。例如，用户观看直播时打赏主播产生的支付订单，可自行输入一个标签“直播打赏”，在这种情况下，将采集到的用户输入的“直播打赏”标签，作为该打赏主播产生的支付订单的支付分类标签。
步骤S104，将所述支付分类标签与支付类型集合中的支付类型进行匹配。
本实施例所述支付类型，是指对支付订单进行支付处理的支付场景或者支付环境，比如针对线上购物产生的订单进行支付的支付场景、线下小店支付产生的订单进行支付的支付场景、红包转账产生的订单进行支付的支付场景。本实施例所述支付类型集合，是指至少一个支付类型组成的集合，比如由线上支付、线下支付、红包支付组成的支付类型集合。
具体实施时，将所述支付分类标签与支付类型集合中的支付类型进行匹配，匹配之后获得匹配成功或者匹配失败的匹配结果；在匹配成功的情况下，执行下述步骤S106；在匹配失败的情况下，向用户发送匹配失败提醒，或者，读取所述全局支付渠道的支付优先级，根据读取所述全局支付渠道的支付优先级的支付顺序进行所述支付订单的支付处理。
此外，为了提升用户在基于支付分类标签与支付类型集合中的支付类型进行匹配的基础上，在相应支付类型对支付订单进行支付处理的成功率，本实施例提供的可选实施方式中，在匹配失败的情况下，则向所述用户推荐所述支付类型集合中与所述支付分类标签的相似度高于阈值的支付类型，以此，进一步提升支付灵活性。
具体的，在将所述支付分类标签与支付类型集合中的支付类型进行匹配的过程中，可通过将所述支付分类标签与支付类型集合中的各个支付类型分别进行对比，并分别计算所述支付分类标签与支付类型集合中的每个支付类型的相似度，选取相似度较高的一个支付类型作为目标支付类型，以此精准分类支付订单，有利于用户合理安排消费。例如，支付订单的支付分类标签为“线上购物”，则与支付类型集合中的支付类型依次对比，与线上购物这个支付类型相符合，则确定本次支付的支付类型为线上购物。
可选的，所述支付类型集合中的支付类型分别设置有各自的支付渠道配置；其中，所述支付类型的支付渠道配置，包括：在所述支付类型下进行订单支付设置的至少一个支付渠道，以及所述至少一个支付渠道的支付优先级。其中，所述支付优先级是指在支付时选择支付渠道的优先次序，也即是指支付渠道的支付顺序。例如，针对线下购物这一支付类型，针对该支付类型设置的支付渠道配置包括账户余额支付、储蓄卡支付、授信支付这三个支付渠道，以及这三个支付渠道的支付顺序，如图4所示。
实际应用中，为了提升用户针对所述支付目标支付类型设置的支付渠道配置的灵活性，满足用户个性化需求，本实施例提供的一种可选实施方式中，通过向用户提供推荐列表的方式，使用户能够自定义设置支付渠道的优先级，例如，用户在线下小店支付产生的支付订单对应的至少一个支付渠道为账户余额支付，支付优先级从高到低的排序依次为账户余额支付->授信支付->信用卡支付->储蓄卡支付。
本实施例提供的一种可选实施方式中，所述支付优先级，采用如下方式确定：基于所述用户的偏好数据，确定推荐列表中的支付渠道的支付优先级；所述推荐列表由所述至少一个支付渠道构成。
具体的，在确定至少一个支付渠道的支付优先级的过程中，获取至少一个支付渠道 的推荐列表，该推荐列表中的支付渠道的支付优先级基于用户的偏好数据确定，在获取到推荐列表后向用户发送，根据用户的调整指令对推荐列表中的支付渠道的顺序进行调整，获得调整后的推荐列表，调整后的推荐列表中支付渠道的支付优先级基于用户调整后的支付渠道的顺序确定。
例如，支付类型集合中的支付类型分别设置有各自的支付渠道配置基础上，针对线下购物这一支付类型，基于用户的偏好数据确定的推荐列表顺序为支付顺序为授信支付、储蓄卡支付、账户余额支付，用户调整后的支付顺序为账户余额支付、储蓄卡支付、授信支付，将调整后的支付顺序作为支付优先级。
可选的，所述至少一个支付类型中任意一个支付类型的推荐列表，通过所述任意一个支付类型的设置子页面进行展示，所述用户通过触发应用程序的设置页面配置的设置入口进入标签页面，所述用户通过触发所述标签页面配置的类型标签入口进入所属的支付类型的设置子页面。
例如，用户通过触发图2所示的应用程序的设置页面配置的“支付个性配置”的设置入口，进入图3所示的标签页面，其中，可通过状态控件302设置支付个性配置的可用状态；通过触发标签页面配置的“线下购物”的类型标签入口304进入图4所示的设置子页面；以对“线下购物”的支付渠道进行顺序调整；其中，用户可通过状态控件402设置线下购物的可用状态；通过触发“授信支付”的调整控件404将支付渠道的支付顺序进行调整。
本实施例提供的一种可选实施方式中，所述支付类型的设置子页面设置有所述支付类型对应的类型控件，若所述类型控件的控件状态为开启状态，则所述类型控件所属的支付类型的支付状态为可用状态。
除上述在所述标签页面设置有触发控件之外，还可在所述支付类型的设置子页面设置有所述支付类型对应的类型控件，若所述类型控件的控件状态为开启状态，则所述类型控件所属的支付类型的支付状态为可用状态。
此外，还可以在所述标签页面设置有触发控件的基础上，在所述支付类型的设置子页面设置有所述支付类型对应的类型控件，若所述触发控件的控件状态为开启状态，则所述支付类型集合中所有支付类型的支付状态为可用状态，若所述类型控件的控件状态为开启状态，则所述类型控件所属的支付类型的支付状态为可用状态。
例如，线上支付的设置子页面设置有线上支付类型控件，且处于开启状态，则线上支付为可用状态。
具体实施时，将所述支付分类标签与支付类型集合中的支付类型进行匹配，若匹配成功，则执行下述步骤S106，根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；若匹配失败，返回支付失败提醒；此外，还可进一步在返回支付失败提醒的基础上，通过支付渠道添加页面配置的触发控件502进行支付渠道的添加，如图5所示。
此外，为了保证用户能正常完成支付，本实施例提供的支付分类标签与支付类型集合中的支付类型在匹配失败的情况下，通过基于全局支付渠道配置进行所述支付订单的支付处理的方式，实现读取所述全局支付渠道的支付优先级的支付顺序及逆行所述支付订单的支付处理；具体的，本实施例提供的一种可选实施方式中，所述基于全局支付渠道配置进行所述支付订单的支付处理，包括：读取所述全局支付渠道的支付优先级，根据读取所述全局支付渠道的支付优先级的支付顺序进行所述支付订单的支付处理。
其中，在所述支付分类标签与支付类型集合中的支付类型匹配的过程中，将匹配的 相似度作为判断匹配结果的依据，读取所述全局支付渠道的支付优先级，然后选取支付优先级处于首位的目标支付渠道，并利用目标支付渠道进行支付，以保证用户支付顺利完成；若支付失败，则选取支付优先级下一位次的支付渠道进行支付，直至支付完成。
如图4所示的设置子页面中，展示有用户的全局支付渠道的支付优先级的支付顺序，用户进行支付时，首选账户余额支付这一支付渠道，如果支付失败，选择支付优先级下一位的储蓄卡支付这一支付渠道进行支付，依次类推，直至支付成功。
除上述提供的通过全局支付渠道配置进行所述支付订单的支付处理之外，为了提升用户支付的便捷性，可选的，向所述用户推荐所述支付类型集合中与所述支付分类标签的相似度高于阈值的支付类型，以此满足不同用户的支付需求；比如用户观看直播时打赏主播，在支付类型集合中未匹配到支付类型，就可以推荐线上购物这个相似度较高的支付类型作为目标支付类型，读取线上购物这一支付类型的支付渠道列表。
步骤S106，根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置。
本步骤在所述支付分类标签与支付类型集合中的支付类型匹配成功的基础上，根据匹配结果中记录的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置。
具体的，所述支付分类标签与支付类型集合中的支付类型匹配成功后，匹配结果中记录有所述支付订单的支付类型，读取所述用户针对该支付类型设置的支付渠道列表。
例如，用户基于红包转账的支付订单对应的分类标签为线上支付，所述线上支付与支付类型集合中的线上支付进行匹配，如果匹配成功，目标支付类型为线上购物，则读取线上购物这一支付类型的支付渠道列表。
本实施例提供的一种可选实施方式中，在将所述支付分类标签与支付类型集合中的支付类型进行匹配步骤执行之后的执行结果为匹配成功的情况下，且在读取所述用户针对所述目标支付类型设置的支付渠道配置操作执行之前，还执行如下操作：判断所述目标支付类型的对应的支付状态是否为可用状态；若是，执行所述读取所述用户针对所述目标支付类型设置的支付渠道配置；若否，基于全局支付渠道配置进行所述支付订单的支付处理。
具体的，将支付分类标签与支付类型集合中的支付类型进行匹配，且匹配成功后，判断匹配结果中携带的目标支付类型的支付状态是否为可用状态，若是，执行所述读取所述用户针对所述目标支付类型设置的支付渠道配置步骤；若否，基于全局支付渠道配置进行所述支付订单的支付处理。
例如，将支付分类标签与支付类型集合中的支付类型进行匹配，匹配结果中记录的支付类型为线上购物，则判断线上购物这一支付类型的支付状态是否可用，若是，则读取线上购物这一支付类型的支付渠道列表；若否，则读取全局支付渠道的支付优先级，根据读取的全局支付渠道的支付优先级的支付顺序进行所述支付订单的支付处理。
此外，在判断所述目标支付类型的对应的支付状态是否为可用状态之后，并且在目标支付类型对应的支付状态为不可用状态的情况下，除上述提供的基于全局支付渠道配置进行所述支付订单的支付处理的实现方式之外，还可以向用户推荐相似度高的支付类型，或者，返回支付失败提醒。
步骤S108，基于所述支付渠道配置进行所述支付订单的支付处理。
具体实施时，在读取到支付渠道配置后，基于支付渠道配置进行支付订单处理，本实施例提供的一种可选实施方式中，所述基于所述支付渠道配置进行所述支付订单的支 付处理，包括：读取所述用户的支付渠道配置，基于所述用户的支付渠道配置的支付优先级进行所述支付订单的支付处理。
进一步，基于所述用户的支付渠道配置的支付优先级进行所述支付订单的支付处理的过程中，为了保证用户正常完成支付，本实施例提供的一种可选实施方式中，所述基于所述用户的支付渠道配置的支付优先级进行所述支付订单的支付处理，包括：
选择所述目标支付类型下支付优先级处于首位的目标支付渠道，并利用目标支付渠道进行支付；在支付失败后，选择支付优先级处于所述目标支付渠道的下一位次的支付渠道进行支付，或者，根据所述用户的支付历史数据在所述至少一个支付渠道确定支付渠道并进行支付处理。
具体的，在根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置步骤执行后，获得用户针对所述目标支付类型设置的一个支付渠道的支付优先级，选择所述目标支付类型的支付优先级处于首位的支付渠道，并通过该支付渠道进行支付；在支付失败后，选择支付优先级处于所述目标支付渠道的下一位次的支付渠道进行支付，或者，根据所述用户的支付历史数据在所述至少一个支付渠道确定支付渠道并进行支付处理。
例如，用户针对线上购物这一支付类型的支付优先级处于首位的支付渠道是信用卡支付，当使用信用卡支付失败时，检测到用户根据授信支付这一支付渠道支付过支付类型为线上购物的支付订单，则可选取授信支付这一支付渠道进行本次支付。
综上所述，本实施例提供的支付处理方法，首先确定获取的用户的支付订单的支付分类标签，然后将支付分类标签与支付类型集合中的支付类型进行匹配，若匹配成功，则根据匹配结果中携带的目标支付类型，读取用户针对所述目标支付类型设置的支付渠道配置，最后根据支付渠道配置进行支付订单的支付处理，以此满足不同用户对线上支付方式的不同要求；进一步，在支付分类标签与支付类型集合中的支付类型进行匹配步骤执行之后的执行结果为匹配成功的情况下，读取所述用户针对所述目标支付类型设置的支付渠道配置操作执行之前，判断所述目标支付类型的对应的支付状态是否为可用状态，执行用户针对目标支付类型设置的支付渠道配置操作，以此避免用户因为支付状态不可用而导致支付失败，提升用户的支付有效性。
下述以本实施例提供的一种支付处理方法在第一支付场景的应用为例，结合图6，对本实施例提供的支付处理方法进行进一步说明，参见图6，应用于第一支付场景的支付处理方法，具体包括下述步骤。
步骤S602，读取用户的支付订单中记录的支付分类标签。
步骤S604，将所述支付分类标签与支付类型集合中的支付类型进行匹配；若匹配成功，执行步骤S606至步骤S608；若匹配失败，执行步骤S612。
步骤S606，根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置。
可选的，所述用户通过触发应用程序的设置页面配置的设置入口进入标签页面，所述用户通过触发所述标签页面配置的类型标签入口进入所属的支付类型的设置子页面。
可选的，所述支付类型的设置子页面设置有所述支付类型对应的类型控件，若所述类型控件的控件状态为开启状态，则所述类型控件所属的支付类型的支付状态为可用状态。
步骤S608，判断所述目标支付类型的对应的支付状态是否为可用状态；若是，执行步骤S610；若否，执行步骤S612。
步骤S610，基于所述目标支付类型设置的支付渠道配置的支付优先级进行所述支付订单的支付处理。
具体的，基于所述目标支付类型设置的支付渠道配置的支付优先级进行所述支付订单的支付处理，包括：若首位的目标支付渠道支付成功，则流程结束；若首位的目标支付渠道支付失败，则选择支付优先级处于所述目标支付渠道的下一位次的支付渠道进行支付，直至支付成功，流程结束；若所述目标支付渠道中各支付渠道对所述订单的支付结果为支付失败，则向用户发送支付失败提醒。
步骤S612，基于全局支付渠道配置进行所述支付订单的支付处理。
此外，在步骤S602之前，还可执行下述步骤：获取所述至少一个支付渠道的推荐列表并向用户发送；基于所述用户的偏好数据，确定所述推荐列表中的支付渠道的支付优先级；进一步，可基于所述用户对所述推荐列表中支付渠道进行调整的调整指令，确定所述支付优先级。
下述以本实施例提供的一种支付处理装置，在第二支付场景的应用为例，结合图7，对本实施例提供的支付处理方法进行进一步说明，参见图7，应用于第二支付场景的支付处理方法，具体包括下述步骤。
步骤S702，根据用户的支付订单携带的订单数据确定支付分类标签。
步骤S704，将所述支付分类标签与支付类型集合中的支付类型进行匹配；若匹配成功，执行步骤S706；若匹配失败，执行步骤S712。
步骤S706，判断标签页面设置的触发控件的控件状态是否为开启状态；若是，执行步骤S708至步骤S710；若否，执行步骤S714。
可选的，所述用户通过触发应用程序的设置页面配置的设置入口进入标签页面，所述用户通过触发所述标签页面配置的类型标签入口进入所属的支付类型的设置子页面。
可选的，所述支付类型的设置子页面设置有所述支付类型对应的类型控件，若所述类型控件的控件状态为开启状态，则所述类型控件所属的支付类型的支付状态为可用状态。
步骤S708，根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置。
步骤S710，基于所述目标支付类型设置的支付渠道配置的支付优先级进行所述支付订单的支付处理。
具体的，基于所述目标支付类型设置的支付渠道配置的支付优先级进行所述支付订单的支付处理，包括：若首位的目标支付渠道支付成功，则流程结束；若首位的目标支付渠道支付失败，则选择支付优先级处于所述目标支付渠道的下一位次的支付渠道进行支付，直至支付成功，流程结束；若所述目标支付渠道中各支付渠道对所述订单的支付结果为支付失败，则向用户发送支付失败提醒。
步骤S712，向所述用户推荐所述支付类型集合中与所述支付类型标签的相似度高于阈值的支付类型。
步骤S714，基于全局支付渠道配置进行所述支付订单的支付处理。
在步骤S702之前，还可执行下述步骤：获取所述至少一个支付渠道的推荐列表并向用户发送；基于所述用户的偏好数据，确定所述推荐列表中的支付渠道的支付优先级；进一步，可基于所述用户对所述推荐列表中支付渠道进行调整的调整指令，确定所述支付优先级。
本说明书提供的一种支付处理装置实施例如下：在上述的实施例中，提供了一种支付处理方法，与之相对应的，还提供了一种支付处理装置，下面结合附图进行说明。
参照图8，其示出了本实施例提供的一种支付处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种支付处理装置，包括：确定模块802，被配置为确定获取的用户的支付订单的支付分类标签；匹配模块804，被配置为将所述支付分类标签与支付类型集合中的支付类型进行匹配；若匹配成功，运行配置读取模块806，所述配置读取模块806，被配置为根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；支付模块808，被配置为基于所述支付渠道配置进行所述支付订单的支付处理。
本说明书提供的一种支付处理设备实施例如下：对应上述描述的一种支付处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种支付处理设备，该支付处理设备用于执行上述提供的支付处理方法，图9为本说明书一个或多个实施例提供的一种支付处理设备的结构示意图。
本实施例提供的一种支付处理设备，包括：如图9所示，支付处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器901和存储器902，存储器902中可以存储有一个或一个以上存储应用程序或数据。其中，存储器902可以是短暂存储或持久存储。存储在存储器902的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括支付处理设备中的一系列计算机可执行指令。更进一步地，处理器901可以设置为与存储器902通信，在支付处理设备上执行存储器902中的一系列计算机可执行指令。支付处理设备还可以包括一个或一个以上电源903，一个或一个以上有线或无线网络接口904，一个或一个以上输入/输出接口905，一个或一个以上键盘906等。
在一个具体的实施例中，支付处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对支付处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：确定获取的用户的支付订单的支付分类标签；将所述支付分类标签与支付类型集合中的支付类型进行匹配；若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；基于所述支付渠道配置进行所述支付订单的支付处理。
本说明书提供的一种存储介质实施例如下：对应上述描述的一种支付处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：确定获取的用户的支付订单的支付分类标签；将所述支付分类标签与支付类型集合中的支付类型进行匹配；若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；基于所述支付渠道配置进行所述支付订单的支付处理。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于支付处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪30年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本说明书一个或多个实施例可提供为方法、系统或计算机程序产品。因此，本说明书一个或多个实施例可采用完全硬件实施例、完全软件实 施例、或结合软件和硬件方面的实施例的形式。而且，本说明书可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书是参照根据本说明书实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书的一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本文件的实施例而已，并不用于限制本文件。对于本领域技术人员来说，本文件可以有各种更改和变化。凡在本文件的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本文件的权利要求范围之内。

Claims (16)

  1. 一种支付处理方法，包括：
    确定获取的用户的支付订单的支付分类标签；
    将所述支付分类标签与支付类型集合中的支付类型进行匹配；
    若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；
    基于所述支付渠道配置进行所述支付订单的支付处理。
  2. 根据权利要求1所述的支付处理方法，所述支付类型集合中的支付类型分别设置有各自的支付渠道配置；
    其中，所述支付类型的支付渠道配置，包括：在所述支付类型下进行订单支付的至少一个支付渠道，以及所述至少一个支付渠道的支付优先级。
  3. 根据权利要求2所述的支付处理方法，所述支付优先级，采用如下方式确定：
    获取所述至少一个支付渠道构成的推荐列表并向用户发送；
    基于所述用户对所述推荐列表中支付渠道进行调整的调整指令，确定所述支付优先级。
  4. 根据权利要求2所述的支付处理方法，所述支付优先级，采用如下方式确定：
    基于所述用户的偏好数据，确定推荐列表中的支付渠道的支付优先级；所述推荐列表由所述至少一个支付渠道构成。
  5. 根据权利要求2所述的支付处理方法，所述支付类型集合中任意一个支付类型的推荐列表，通过所述任意一个支付类型的设置子页面进行展示；
    所述用户通过触发应用程序的设置页面配置的设置入口进入标签页面，所述用户通过触发所述标签页面配置的类型标签入口进入所属的支付类型的设置子页面。
  6. 根据权利要求5所述的支付处理方法，所述任意一个支付类型的设置子页面设置有所述任意一个支付类型对应的类型控件，若所述类型控件的控件状态为开启状态，则所述类型控件所属的支付类型的支付状态为可用状态；
    或者，
    所述标签页面设置有触发控件，若所述触发控件的控件状态为开启状态，则所述支付类型集合中所有支付类型的支付状态为可用状态。
  7. 根据权利要求1所述的支付处理方法，所述将所述支付分类标签与支付类型集合中的支付类型进行匹配步骤执行之后的执行结果为匹配成功的情况下，且所述根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置操作执行之前，还包括：
    判断所述目标支付类型对应的支付状态是否为可用状态；
    若是，执行所述根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置操作。
  8. 根据权利要求7所述的支付处理方法，若所述判断所述目标支付类型对应的支付状态是否为可用状态步骤执行之后的执行结果为否，执行如下操作：
    基于全局支付渠道配置进行所述支付订单的支付处理。
  9. 根据权利要求8所述的支付处理方法，所述基于全局支付渠道配置进行所述支付订单的支付处理，包括：
    读取全局支付渠道的支付优先级，按照读取到的所述全局支付渠道的支付优先级对应的支付顺序进行所述支付订单的支付处理。
  10. 根据权利要求1所述的支付处理方法，所述基于所述支付渠道配置进行所述支付订单的支付处理，包括：
    基于所述目标支付类型设置的支付渠道配置的支付优先级进行所述支付订单的支付处理。
  11. 根据权利要求10所述的支付处理方法，所述基于所述目标支付类型设置的支付渠道配置的支付优先级进行所述支付订单的支付处理，包括：
    确定所述目标支付类型下支付优先级处于首位的目标支付渠道，并利用所述目标支付渠道进行支付处理；
    在支付失败后，选择支付优先级处于所述目标支付渠道的下一位次的支付渠道进行支付处理，或者，根据所述用户的支付历史数据在至少一个支付渠道中确定支付渠道并进行支付处理。
  12. 根据权利要求1所述的支付处理方法，所述将所述支付分类标签与支付类型集合中的支付类型进行匹配步骤执行之后，还包括：
    若匹配失败，则向所述用户推荐所述支付类型集合中与所述支付分类标签的相似度高于阈值的支付类型。
  13. 根据权利要求1所述的支付处理方法，所述支付分类标签，采用如下方式确定：
    读取所述支付订单中记录的订单分类标签，作为所述支付分类标签；
    或者，
    根据所述支付订单携带的订单数据确定所述支付分类标签。
  14. 一种支付处理装置，包括：
    确定模块，被配置为确定获取的用户的支付订单的支付分类标签；
    匹配模块，被配置为将所述支付分类标签与支付类型集合中的支付类型进行匹配；
    若匹配成功，运行配置读取模块，所述配置读取模块，被配置为根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；
    支付模块，被配置为基于所述支付渠道配置进行所述支付订单的支付处理。
  15. 一种支付处理设备，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    确定获取的用户的支付订单的支付分类标签；
    将所述支付分类标签与支付类型集合中的支付类型进行匹配；
    若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；
    基于所述支付渠道配置进行所述支付订单的支付处理。
  16. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：
    确定获取的用户的支付订单的支付分类标签；
    将所述支付分类标签与支付类型集合中的支付类型进行匹配；
    若匹配成功，则根据匹配结果中携带的目标支付类型，读取所述用户针对所述目标支付类型设置的支付渠道配置；
    基于所述支付渠道配置进行所述支付订单的支付处理。
PCT/CN2023/110186 2022-08-26 2023-07-31 支付处理方法及装置 WO2024041316A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211033575.4 2022-08-26
CN202211033575.4A CN115310956A (zh) 2022-08-26 2022-08-26 支付处理方法及装置

Publications (1)

Publication Number Publication Date
WO2024041316A1 true WO2024041316A1 (zh) 2024-02-29

Family

ID=83864158

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/110186 WO2024041316A1 (zh) 2022-08-26 2023-07-31 支付处理方法及装置

Country Status (2)

Country Link
CN (1) CN115310956A (zh)
WO (1) WO2024041316A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115310956A (zh) * 2022-08-26 2022-11-08 支付宝(杭州)信息技术有限公司 支付处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102117455A (zh) * 2011-03-21 2011-07-06 广州市动景计算机科技有限公司 基于移动终端浏览器的安全支付方法和系统
US20140279421A1 (en) * 2013-03-15 2014-09-18 Elwha Llc Methods and systems for agnostic payment systems
CN111091358A (zh) * 2019-12-16 2020-05-01 中国建设银行股份有限公司 多支付渠道的统一处理方法及系统
CN113112263A (zh) * 2021-05-07 2021-07-13 深圳乐信软件技术有限公司 一种支付方式的展示方法、装置、服务器及存储介质
CN115310956A (zh) * 2022-08-26 2022-11-08 支付宝(杭州)信息技术有限公司 支付处理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102117455A (zh) * 2011-03-21 2011-07-06 广州市动景计算机科技有限公司 基于移动终端浏览器的安全支付方法和系统
US20140279421A1 (en) * 2013-03-15 2014-09-18 Elwha Llc Methods and systems for agnostic payment systems
CN111091358A (zh) * 2019-12-16 2020-05-01 中国建设银行股份有限公司 多支付渠道的统一处理方法及系统
CN113112263A (zh) * 2021-05-07 2021-07-13 深圳乐信软件技术有限公司 一种支付方式的展示方法、装置、服务器及存储介质
CN115310956A (zh) * 2022-08-26 2022-11-08 支付宝(杭州)信息技术有限公司 支付处理方法及装置

Also Published As

Publication number Publication date
CN115310956A (zh) 2022-11-08

Similar Documents

Publication Publication Date Title
US20200334676A1 (en) Information recommendation method and apparatus, and medium
WO2021223675A1 (zh) 风险检测
TWI709933B (zh) 虛擬卡的開卡方法、系統和支付系統、發卡系統
WO2024041316A1 (zh) 支付处理方法及装置
CN113516480B (zh) 一种支付风险识别方法、装置及设备
WO2022247969A1 (zh) 用于支付的方法及装置
CN110390182B (zh) 一种确定小程序类目的方法、系统及设备
US11397597B2 (en) Application processing method and apparatus
WO2021249526A1 (zh) 风险防控信息处理方法、装置及设备
CN112347512A (zh) 图像处理方法、装置、设备及存储介质
WO2020207086A1 (zh) 一种信息的处理系统、方法、装置及设备
CN110852503A (zh) 一种支付渠道的选择方法和设备、支付渠道路由
US20200211010A1 (en) Resource transfer verification method and apparatus, and electronic payment verification method and apparatus
CN108550033A (zh) 一种显示数字对象唯一标识符的方法及装置
TWI728357B (zh) 序列號的生成方法及裝置
CN110134860B (zh) 用户画像生成方法、装置和设备
US11158319B2 (en) Information processing system, method, device and equipment
CN114819012A (zh) 一种图形码校验方法及装置
CN110187874B (zh) 一种在计算机设备中执行的规则配置方法及装置
CN107918863A (zh) 基于金融产品的前置处理及配置方法、装置及设备
CN115147227B (zh) 一种交易风险的检测方法、装置及设备
CN114201086B (zh) 信息的展示方法及装置
CN112184074A (zh) 一种提示信息输出方法及装置
CN110008358B (zh) 一种资源信息展示方法和系统、客户端及服务端
CN109584088B (zh) 产品信息的推送方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23856406

Country of ref document: EP

Kind code of ref document: A1