CN115730932A

CN115730932A - Cross-platform binding card processing method, system, equipment and computer readable storage medium

Info

Publication number: CN115730932A
Application number: CN202211430842.1A
Authority: CN
Inventors: 郑萍军
Original assignee: Ping An Bank Co Ltd
Current assignee: Ping An Bank Co Ltd
Priority date: 2022-11-15
Filing date: 2022-11-15
Publication date: 2023-03-03

Abstract

The application discloses a cross-platform binding processing method, a cross-platform binding processing system, cross-platform binding processing equipment and a computer readable storage medium, when a merchant system is in butt joint with a binding payment platform and different jump pages are configured, jump callback addresses of different merchant systems are taken, return marks unified with the merchant system are used in the jump link addresses, the merchant system can be directly called back according to the return marks after a business process is completed, the business process is completed, corresponding calling can be carried out on the different merchant systems based on the return marks, the butt joint of the platform and the merchant system is quickly realized, and the technical problems that a large amount of manpower and server resources are consumed to match and customize for each merchant, a large number of redundant systems exist and the efficiency is low in the conventional binding payment system are solved.

Description

Cross-platform binding card processing method, system, equipment and computer readable storage medium

Technical Field

The application relates to the technical field of financial technology, in particular to a cross-platform card binding processing method, a cross-platform card binding processing system, cross-platform card binding processing equipment and a computer readable storage medium.

Background

With the rapid development of mobile payment, in order to promote the transaction usage amount of the bank card and achieve the purposes of obtaining customers in batches by the bank 2C and improving the retail deposit amount, the bank can prompt the user to carry out card binding payment through card binding payment preference in some offline order receiving scenes.

The existing card binding payment implementation is developed aiming at a certain platform, and an independent complete payment system is made for joint cards of a single payment platform. The card binding payment system for a certain expanded merchant needs to spend a large amount of manpower and server resources for matching and customizing for each merchant, which results in a large amount of redundant systems and low efficiency. When a new expansion merchant needs to access a bank or a bank joint name card is used, a new card binding payment system needs to be developed firstly, so that the access of the new merchant needs to wait for the completion of development, and the new merchant can be put into use only through the long-time debugging of the new system, and the efficiency is low.

Disclosure of Invention

The application provides a cross-platform card binding processing method, a cross-platform card binding processing system, cross-platform card binding equipment and a computer readable storage medium, and solves the technical problems that a large amount of redundant systems and low efficiency are caused by the fact that a large amount of manpower and server resources are spent for matching and customizing of each merchant in the conventional card binding payment system.

In view of this, a first aspect of the present application provides a cross-platform card binding processing method, where the method includes:

s1, receiving a card binding request sent by a first user through a merchant system, wherein the card binding request carries a jump callback address of the merchant system;

s2, sending a first link address of the skipped binding card H5 page to the merchant system according to the binding card request, wherein the first link address carries a first return mark of the merchant system, so that the merchant system skips to the binding card H5 page corresponding to the first link address to finish binding, and recalling and displaying a binding result according to the first return mark.

Optionally, before the step S1, the method further includes:

s3, receiving a member registration request sent by a first user through a merchant system;

and S4, creating member information of the first user according to the member registration request and returning the member information to the merchant system.

Optionally, after the step S2, the method further includes:

s5, receiving an order payment request initiated by a first user through the merchant system, wherein the order payment request carries a jump callback address of the merchant system;

s6, according to the order payment request, checking whether the first user completes payment password setting, and if so, sending a password input page to the merchant system;

s7, receiving a payment password input by the first user based on the password input page;

s8, sending a second link address of the skipped payment result H5 page to the merchant system according to the verification result of the payment password, wherein the second link address carries a second return mark of the merchant system, so that the merchant system skips to the payment result H5 page corresponding to the second link address, and calls back to display the payment result according to the first return mark.

Optionally, after the step S6, the method further includes:

s9, if the password setting is not finished, a password setting page is sent to the merchant system;

and S10, receiving payment password setting information finished by the first user based on the password setting page.

A second aspect of the present application provides a cross-platform binding card processing system, where the apparatus includes:

the system comprises a first receiving unit, a second receiving unit and a processing unit, wherein the first receiving unit is used for receiving a card binding request sent by a first user through a merchant system, and the card binding request carries a jump callback address of the merchant system;

and the first processing unit is used for sending a first link address of the skipped binding H5 page to the merchant system according to the binding request, wherein the first link address carries a first return mark of the merchant system, so that the merchant system skips to the binding H5 page corresponding to the first link address to complete binding, and displays a binding result by calling back according to the first return mark.

Optionally, the method further comprises:

the second receiving unit is used for receiving a member registration request sent by the first user through the merchant system;

and the second processing unit is used for creating the member information of the first user according to the member registration request and returning the member information to the merchant system.

Optionally, the method further comprises:

a third receiving unit, configured to receive an order payment request initiated by a first user through the merchant system, where the order payment request carries a jump callback address of the merchant system;

the third processing unit is used for verifying whether the first user completes payment password setting or not according to the order payment request, and if the payment password setting is completed, a password input page is sent to the merchant system;

a fourth receiving unit, configured to receive a payment password input by the first user based on the password input page;

and the fourth processing unit is configured to send a second link address of the skipped payment result H5 page to the merchant system according to the verification result of the payment password, where the second link address carries a second return flag of the merchant system, so that after the merchant system skips to the payment result H5 page corresponding to the second link address, the merchant system calls back to display the payment result according to the first return flag.

Optionally, the method further comprises:

the fifth processing unit is used for sending a password setting page to the merchant system if the password setting page is not finished;

a fifth receiving unit, configured to receive payment password setting information that is completed by the first user based on the password setting page.

A third aspect of the present application provides a cross-platform card binding processing device, which includes a processor and a memory:

the memory is used for storing program codes and transmitting the program codes to the processor;

the processor is configured to execute the steps of the method of cross-platform card binding processing according to the first aspect, according to instructions in the program code.

A fourth aspect of the present application provides a computer-readable storage medium for storing program code for performing the method of the first aspect described above.

According to the technical scheme, the embodiment of the application has the following advantages:

the application provides a cross-platform card binding processing method, a cross-platform card binding processing system, a cross-platform card binding processing device and a computer readable storage medium, when a merchant system is in butt joint with a card binding payment platform and different jump pages are configured, jump callback addresses of different merchant systems are taken, so that return marks unified with the merchant system are utilized in the jump link addresses, the merchant system can be directly called back according to the return marks after a business process is completed, the business process is completed, corresponding calling can be performed on the different merchant systems based on the return marks, the butt joint of the platform and the merchant system is quickly realized, and the technical problems that a large amount of manpower and server resources are consumed to match and customize for each merchant, a large amount of redundant systems exist, and the efficiency is low in the conventional card binding payment system are solved.

Drawings

Fig. 1 is a flowchart of a first method of a cross-platform card binding processing method in an embodiment of the present application;

FIG. 2 is a flow chart of a second method of a cross-platform card binding processing method in an embodiment of the present application;

FIG. 3 is a flowchart of a third method of a cross-platform card binding processing method in an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a cross-platform card binding processing system in an embodiment of the present application;

fig. 5 is a schematic structural diagram of a cross-platform card binding processing device in an embodiment of the present application.

Detailed Description

In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The application designs a cross-platform card binding processing method, a cross-platform card binding processing system, cross-platform card binding equipment and a computer readable storage medium, and solves the technical problems that a large amount of redundant systems and low efficiency are caused by the fact that the existing card binding payment system spends a large amount of manpower and server resources for matching and customizing each merchant.

For convenience of understanding, please refer to fig. 1, where fig. 1 is a flowchart of a first method of a cross-platform card binding processing method in the embodiment of the present application, and as shown in fig. 1, the method specifically includes:

it should be noted that the merchant system may be all merchants of the collaborative expansion, and may be accessed to the card binding processing system.

S2, sending a first link address of the skipped binding H5 page to the merchant system according to the binding request, wherein the first link address carries a first return mark of the merchant system, so that the merchant system skips to the binding H5 page corresponding to the first link address to complete binding, and recalling and displaying a binding result according to the first return mark.

It should be noted that, when the card binding H5 page is skipped, a jump callback address of the app of the merchant system needs to be taken, that is, a uniform return flag returnUrl is used by the app of the merchant system in the skipped link address, so that after the card binding payment is completed, the uniform return flag returnUrl is taken out from the link address to call back the merchant system, thereby completing the card binding or payment process.

And after the merchant system jumps to the binding H5 page, the bank card binding process is completed, the merchant system acquires a uniform mark return Url on the link address through the link address of the binding H5 page, jumps after the uniform mark return Url is acquired through the link address location, and recalls and displays the binding result.

Further, referring to fig. 2, fig. 2 is a flowchart illustrating a second method of the cross-platform card binding processing method according to the embodiment of the present application, and as shown in fig. 2, step S1 further includes:

It should be noted that, the merchant system jumps to the card binding processing system to request for creating the member registration information, and the card binding processing system enters the card binding process after creating the member information.

Further, referring to fig. 3, fig. 3 is a flowchart of a third method of the cross-platform card binding processing method in the embodiment of the present application, and as shown in fig. 3, after step S2, the method further includes:

s5, receiving an order payment request initiated by a first user through a merchant system, wherein the order payment request carries a jump callback address of the merchant system;

s7, receiving a payment password input by a first user based on the password input page;

and S8, sending a second link address of the skipped payment result H5 page to the merchant system according to the verification result of the payment password, wherein the second link address carries a second return mark of the merchant system, so that the merchant system skips to the payment result H5 page corresponding to the second link address and then calls back to display the payment result according to the first return mark.

It should be noted that, the merchant system initiates an order payment request, the card binding processing system checks whether the payment password setting is completed, and if not, the payment password needs to be set on the corresponding H5 page; if the password is forgotten, the password is reset, and the user jumps back to the payment page after the password is reset successfully.

And inputting a payment password in the card binding processing system, verifying whether the merchant number, the payment password, the amount of money exceed the limit or not by the acquiring system, and the like, skipping to a payment success page after the verification is passed, wherein the acquiring and paying system displays corresponding payment success and failure pages. After the payment is completed, the unified mark return Url can be obtained from the link address, so that the merchant system app can freely display the payment result and the order details after the call is called back.

It can be understood that the docking of the cooperative expansion merchant system can be configured with a corresponding jump address, and the backend database is configured with corresponding joint card authority data to invoke the binding card and payment functions. The front-end page is compatible with the card binding payment of each platform channel, can simultaneously meet the card binding payment functions of a debit card and a credit card, and can automatically jump back to an expanded merchant system after all operations are completed.

Further, step S6 is followed by:

s9, if the password setting is not finished, sending a password setting page to the merchant system;

Referring to fig. 4, fig. 4 is a schematic structural diagram of a cross-platform card binding processing system in an embodiment of the present application, as shown in fig. 4, specifically, the structure is as follows:

a first receiving unit 401, configured to receive a card binding request sent by a first user through a merchant system, where the card binding request carries a skip callback address of the merchant system;

the first processing unit 402 is configured to send a first link address of the skipped binding card H5 page to the merchant system according to the binding card request, where the first link address carries a first return flag of the merchant system, so that the merchant system skips to the binding card H5 page corresponding to the first link address to complete binding, and call back a binding result according to the first return flag.

Further, still include:

and the second processing unit is used for creating member information of the first user according to the member registration request and returning the member information to the merchant system.

Further, the method also comprises the following steps:

a third receiving unit, configured to receive an order payment request initiated by a first user through a merchant system, where the order payment request carries a jump callback address of the merchant system;

the third processing unit is used for verifying whether the first user completes payment password setting or not according to the order payment request, and if the payment password setting is completed, sending a password input page to the merchant system;

and the fourth processing unit is used for sending a second link address of the skipped payment result H5 page to the merchant system according to the verification result of the payment password, wherein the second link address carries a second return mark of the merchant system, so that the merchant system skips to the payment result H5 page corresponding to the second link address and then calls back to display the payment result according to the first return mark.

Further, still include:

and the fifth receiving unit is used for receiving payment password setting information finished by the first user based on the password setting page.

The embodiment of the present application further provides another cross-platform card binding processing device, as shown in fig. 5, for convenience of description, only a part related to the embodiment of the present application is shown, and details of the specific technology are not disclosed, please refer to a method part of the embodiment of the present application. The terminal may be any terminal device including a mobile phone, a tablet computer, a Personal Digital Assistant (PDA, abbreviated as "Personal Digital Assistant"), a Sales terminal (POS, abbreviated as "Point of Sales"), a vehicle-mounted computer, etc., and the terminal is taken as a mobile phone as an example:

fig. 5 is a block diagram illustrating a partial structure of a mobile phone related to a terminal provided in an embodiment of the present application. Referring to fig. 5, the handset includes: radio Frequency (RF) circuit 1010, memory 1020, input unit 1030, display unit 1040, sensor 1050, audio circuit 1060, wireless fidelity (WiFi) module 1070, processor 1080, and power source 1090. Those skilled in the art will appreciate that the handset configuration shown in fig. 5 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile phone in detail with reference to fig. 5:

RF circuit 1010 may be used for receiving and transmitting signals during a message transmission or a call, and in particular, for receiving downlink information from a base station and processing the received downlink information to processor 1080; in addition, the data for designing uplink is transmitted to the base station. In general, RF circuit 1010 includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (Low Noise Amplifier, LNA), a duplexer, and the like. In addition, the RF circuitry 1010 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communications (GSM), general Packet Radio Service (GPRS), code Division Multiple Access (CDMA), wideband Code Division Multiple Access (WCDMA), long Term Evolution (LTE), e-mail, short message Service (Short SMS), and so on.

The memory 1020 can be used for storing software programs and modules, and the processor 1080 executes various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 1020. The memory 1020 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 1020 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 1030 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 1030 may include a touch panel 1031 and other input devices 1032. The touch panel 1031, also referred to as a touch screen, may collect touch operations by a user (e.g., operations by a user on or near the touch panel 1031 using any suitable object or accessory such as a finger, a stylus, etc.) and drive corresponding connection devices according to a preset program. Alternatively, the touch panel 1031 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 1080, and can receive and execute commands sent by the processor 1080. In addition, the touch panel 1031 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 1030 may include other input devices 1032 in addition to the touch panel 1031. In particular, other input devices 1032 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a track ball, a mouse, a joystick, or the like.

The display unit 1040 may be used to display information input by a user or information provided to the user and various menus of the cellular phone. The Display unit 1040 may include a Display panel 1041, and optionally, the Display panel 1041 may be configured by using a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch panel 1031 can cover the display panel 1041, and when the touch panel 1031 detects a touch operation on or near the touch panel 1031, the touch operation is transmitted to the processor 1080 to determine the type of the touch event, and then the processor 1080 provides a corresponding visual output on the display panel 1041 according to the type of the touch event. Although in fig. 5, the touch panel 1031 and the display panel 1041 are two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 1031 and the display panel 1041 may be integrated to implement the input and output functions of the mobile phone.

The handset may also include at least one sensor 1050, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1041 according to the brightness of ambient light, and the proximity sensor may turn off the display panel 1041 and/or the backlight when the mobile phone moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the gesture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

Audio circuitry 1060, speaker 1061, microphone 1062 may provide an audio interface between the user and the handset. The audio circuit 1060 can transmit the electrical signal converted from the received audio data to the speaker 1061, and convert the electrical signal into a sound signal for output by the speaker 1061; on the other hand, the microphone 1062 converts the collected sound signal into an electrical signal, which is received by the audio circuit 1060 and converted into audio data, which is then processed by the audio data output processor 1080 and then sent to, for example, another cellular phone via the RF circuit 1010, or output to the memory 1020 for further processing.

WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help the user to send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 1070, which provides wireless broadband internet access for the user. Although fig. 5 shows the WiFi module 1070, it is understood that it does not belong to the essential constitution of the handset, and can be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 1080 is a control center of the mobile phone, connects various parts of the whole mobile phone by using various interfaces and lines, and performs various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 1020 and calling data stored in the memory 1020, thereby integrally monitoring the mobile phone. Optionally, processor 1080 may include one or more processing units; preferably, the processor 1080 may integrate an application processor, which handles primarily the operating system, user interfaces, applications, etc., and a modem processor, which handles primarily the wireless communications. It is to be appreciated that the modem processor described above may not be integrated into processor 1080.

The handset also includes a power source 1090 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 1080 via a power management system to manage charging, discharging, and power consumption via the power management system.

Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.

In the embodiment of the present application, the processor 1080 included in the terminal further has the following functions:

The embodiment of the present application further provides a computer-readable storage medium, configured to store a program code, where the program code is configured to execute any one implementation manner of the cross-platform card binding processing method described in the foregoing embodiments.

In the embodiment of the application, a cross-platform card binding processing method, a cross-platform card binding processing system, cross-platform card binding processing equipment and a computer readable storage medium are provided, when a merchant system is in butt joint with a card binding payment platform and different jump pages are configured, jump callback addresses of different merchant systems are taken, so that return marks unified with the merchant system are utilized in the jump link addresses, the merchant system can be directly called back according to the return marks after a business process is completed, the business process is completed, corresponding calling can be performed on the different merchant systems based on the return marks, the butt joint of the platform and the merchant system is quickly realized, and the technical problems that a large amount of manpower and server resources are consumed to match and customize for each merchant, a large amount of redundant systems exist, and efficiency is low in the conventional card binding payment system are solved.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The terms "first," "second," "third," "fourth," and the like in the description of the application and the above-described figures, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, which are essential or part of the technical solutions contributing to the prior art, or all or part of the technical solutions, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A cross-platform card binding processing method is characterized by comprising the following steps:

2. The cross-platform card binding processing method according to claim 1, wherein the step S1 is preceded by:

3. The cross-platform card binding processing method according to claim 1, wherein the step S2 is followed by further comprising:

s6, checking whether the first user completes payment password setting or not according to the order payment request, and if so, sending a password input page to the merchant system;

4. The cross-platform card binding processing method according to claim 3, wherein the step S6 is followed by further comprising:

5. A cross-platform card binding processing system, comprising:

and the first processing unit is used for sending a first link address of the skipped binding H5 page to the merchant system according to the binding request, wherein the first link address carries a first return mark of the merchant system, so that the merchant system skips to the binding H5 page corresponding to the first link address to finish binding, and displays a binding result according to the first return mark.

6. The cross-platform bound card processing system according to claim 5, further comprising:

7. The cross-platform bound card processing system according to claim 5, further comprising:

the third processing unit is used for verifying whether the first user completes payment password setting or not according to the order payment request, and if the first user completes payment password setting, a password input page is sent to the merchant system;

8. The cross-platform bound card processing system according to claim 7, further comprising:

a fifth processing unit, configured to send a password setting page to the merchant system if the password setting page is not completed;

9. A cross-platform card binding processing device, the device comprising a processor and a memory:

the processor is used for executing the cross-platform card binding processing method of any one of claims 1 to 4 according to instructions in the program code.

10. A computer-readable storage medium for storing a program code for executing the cross-platform bind card processing method according to any one of claims 1 to 4.