CN116167834A - Customer contact information verification method and management system for banking system - Google Patents

Abstract

The invention discloses a method and a management system for verifying customer contact information in a banking system. By establishing a customer label corresponding to the mobile phone number scene of the customer, scene driving and data calling can be performed through the mobile phone number combination label under the customer item during business processing , and then identify customers and businesses. When customers verify their contact information, they no longer need to verify repeatedly. They only need to input once, and the system will automatically match according to the specific scenario, solving the problem that the system needs repeated calculations when encountering different businesses, so as to achieve one verification everywhere. Use, so that users can more conveniently handle business related to contact information, simplify the handling procedures, improve user experience and meet regulatory needs.

Description

A method and management system for verifying customer contact information in a banking system

technical field

The invention relates to the technical field of computer systems, in particular to a verification method and management system for customer contact information used in banking systems.

Background technique

Due to the large number of mobile phone numbers and the complex application scenarios of the banking system, such as opening customer information, opening account information and other business processes, customers often need to enter contact information multiple times for verification when verifying contact information in different scenarios. There is a security risk.

The existing mobile phone number verification method, such as a mobile phone number verification method, system and terminal disclosed in CN102802150A, the method includes: the called terminal receives the communication interaction request initiated by the calling terminal through the calling number; 2. Verify whether the information is the same to verify whether the calling number is legal. If the verification is legal, then communicate and interact with the calling terminal. The first verification information is the authentication corresponding to the calling number stored locally by the network authentication center. The key and the authentication algorithm calculate a random sequence code, and the second verification information is generated by the calling terminal based on the locally stored authentication key and authentication algorithm to calculate the random sequence code, realizing the called terminal The reliability of the calling number used by the calling terminal to initiate communication interaction is verified, and the communication security of the called user is guaranteed.

However, this technology still has the following defects: there is no unified verification method, it cannot support the unified processing of complex scenarios in the banking system, it needs repeated calculations, the efficiency is low, and the user experience is not good. Therefore, it is necessary to design a new and efficient contact verification method for the banking system.

Contents of the invention

Aiming at the problems that the existing banking system needs to input contact information multiple times for verification when encountering different business scenarios, repeated calculations are inefficient, and the user experience is not good, the present invention proposes a customer contact method verification method and management for the banking system system.

In order to achieve the above object, the technical scheme of the present invention is as follows:

In one aspect, the present invention provides a method for verifying customer contact information in a banking system, comprising the following steps:

101. Input the information to be checked, the information to be checked includes: customer information, customer contact information and account information;

102. Match the verification rules according to the scenario; the scenario includes: the channel for sending the information to be checked, the type of contact method, whether the customer information has been opened, and whether the account information has been opened;

103. Verify the information to be checked: According to the verification method and verification rules, verify the information sent by the customer to be checked; the first order: the system checks whether the mobile phone number has the same name; the second order: the system checks the mobile phone reserved under other customer items No. and mobile banking/online banking contract mobile phone number have the same number;

The verification methods include: weak verification, standard verification, strong verification and policy verification; wherein, weak verification refers to a verification method in which only the mobile phone number is registered, and the system only checks the logic of the mobile phone number; standard verification refers to verification only through SMS verification method; strong verification means that on the basis of the standard verification method, the verification method of the same name as the mobile phone number or the verification method of the uplink SMS is adopted for the mobile phone number; policy verification refers to the standard verification or strong verification. verification method;

The validation rules include:

Implement business code rule coding for the mobile phone number verification method, a total of 10 digits;

No. 1: Represents the first-level verification method

Among them: 0=weak verification, 1=standard verification, 2=strong verification, 3=policy verification, 4=standard verification+policy verification, 5=strong verification+policy verification;

No. 2: Represents whether a SMS verification code is required

Among them: 0 = required, 1 = not required;

The third digit: represents the second-level verification method under the first-level verification method

Among them: 0=SMS verification code verification only, 1=same name verification, 2=uplink SMS verification, 3=same name verification+uplink SMS verification;

Bits 4-6: represent the verification strategy

Among them: 100=same verification of reserved mobile phone numbers, 101=same verification of mobile banking/online banking mobile phone numbers, 102=same verification of SMS SMS mobile phone numbers, 103=same verification of wealth management contract mobile phone numbers; 202=two-factor verification, 203=Three-factor verification, 204=Four-factor verification, 205=Five-factor verification, 206=Six-factor verification; 301=WeChat link authorization verification; 401=Same-name transfer verification for small amount; 501=Bank contract information verification;

No. 7-8: Represents verification support channels

Among them: 00 = counter only, 02 = ITM only, 03 = mobile banking only, 04 = online banking only; 10 = counter + ITM, 11 = mobile banking + online banking, 12 = counter + ITM + mobile banking, 13 = counter Face + ITM + mobile banking + online banking; 21 = only external channel A, 22 = only external channel B, 23 = only external channel C, 24 = only external channel D;

Bit 9-10: reserved for function expansion;

104. Storage: storing the inspection information, the inspection information includes: inspection result information, customer information and customer contact information;

105. Return inspection result information: display the inspection result to the client.

Further, the verification method of the mobile phone number with the same name is as follows:

Mobile phone number with the same name: verification passed;

If the mobile phone number is not the same name: According to the regulatory policy, further verification measures need to be taken as follows:

1) Initiate the four-factor verification of the debit card of another bank under the customer's own name;

2) If the four-factor verification of the debit card of another bank under my name is consistent, the mobile phone number can be used as the reserved mobile phone number;

3) If a customer cannot perform four-factor verification, the mobile phone number standard verification method will be adopted, and the mobile phone number will be verified with a SMS verification code.

Further, verification methods for peripheral data verification include but are not limited to verification of the same mobile phone number, four-factor or five-factor verification or six-factor verification of the bank's/other bank's debit card/credit card, verification of the bank's contracted business information, One or more verification methods of third-party channel platform link authorization verification, small-amount transfer verification with the same name, and verification of the bank's contract information.

On the other hand, the present invention also provides a customer contact information management system for the banking system, including the following modules for implementing the method described in any one of the above:

An information collection module, configured to collect information to be checked;

A verification rule matching module, configured to match the information to be checked with the verification rules;

A verification module, configured to verify the verification information according to verification rules;

An information storage module, configured to store inspection information and inspection result information;

The display module is used to display the inspection results.

Compared with prior art, the beneficial effect of the present invention is:

The present invention proposes a customer contact method verification method and management system for the banking system. By establishing the customer label corresponding to the mobile phone number scene of the customer, scene driving and data calling can be performed through the mobile phone number combination label under the customer item during business processing , and then identify customers and businesses. When customers verify their contact information, they no longer need to verify repeatedly. They only need to input once, and the system will automatically match according to the specific scenario, solving the problem that the system needs repeated calculations when encountering different businesses, so as to achieve one verification everywhere. Use, so that users can more conveniently handle business related to contact information, simplify the handling procedures, improve user experience and meet regulatory needs.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the drawings required in the embodiments. Apparently, the drawings in the following description are only some embodiments described in the present invention, and those skilled in the art can also obtain other drawings according to these drawings.

Fig. 1 is a flow chart of a method for verifying customer contact information used in a banking system provided by an embodiment of the present invention;

Fig. 2 is a functional block diagram of a customer contact information management system used in a banking system provided by an embodiment of the present invention.

Detailed ways

In order to better understand the technical solution, the method of the present invention will be described in detail below in conjunction with the accompanying drawings.

Referring to Fig. 1, the present invention provides a method for verifying customer contact information in a banking system, which uploads the inspection information collected by peripheral channels to the core system, and the core system matches the customer information and contact information according to the specific scene. Check the rules and verify the contact information. After the inspection is completed, the customer contact information and the inspection results are stored in the core system, and the inspection results are returned to the customer.

Specific steps are as follows:

101. Receive the information to be checked and upload the information to be checked to the system. The information to be checked includes: customer information (such as name, ID number), customer contact information (such as phone number) and account information (such as bank card number) ; The system is an IT system that mainly deals with the most basic deposits and loans of banks. It mainly includes several main modules such as deposits, customers, operations, and products, which are common in this field.

102. Peripheral channels match verification rules according to specific scenarios; the scenarios include: channels for sending information to be checked, contact type, whether customer information has been opened, and whether account information has been opened;

According to the characteristics of the business, the business can be divided into three main categories: account opening, contract signing and others.

Account opening: Account opening transactions can be divided into two types: offline face-to-face account opening and online non-face-to-face transactions.

Signing category: newly opened mobile banking/online banking mobile phone number, account movement SMS reminder, financial management signing.

Other categories: refers to the need to retain the mobile phone number in the business information when handling business other than the specified type of business, and the mobile phone number only serves as registration information (that is, the registered mobile phone number does not play the role of mobile account verification and account verification. , customer verification, etc.) mobile phone number. It mainly includes contract deduction, contract payment, agency business, registration of large deposits and withdrawals, and other services that require registration of mobile phone numbers.

Risk levels can be divided from two dimensions:

Customer dimension: It is generally believed that the more complete the customer information (customer certificate information, account information, contact information, etc.), the higher the consistency (referring to the consistency of contact information retained in different systems or different operations of the unified system), and the information status verification passed The higher the rate, the lower the risk level, and vice versa, the higher the risk level.

Business dimension: For other types of business, the mobile phone number does not play a practical role, so for this part of the business, the risk is the lowest, followed by the account opening business. During the account opening process, customer information will be collected synchronously in accordance with current regulatory requirements. The integrity and consistency of information can be guaranteed, and the last is the contract business. Since this type of business involves multiple systems, and the integrity and consistency of historical data cannot be guaranteed (for example, customer contact information has changed or has not been retained. Information) leads to the highest risk level of contract business.

According to business characteristics and risk levels, mobile phone number verification standards are divided into four verification methods from low to high: weak verification, standard verification, strong verification and policy verification; among them:

Weak verification: refers to the verification method that only registers the mobile phone number, and the system only verifies the logic of the mobile phone number;

Standard verification: refers to the verification method that only passes the SMS verification code;

Strong verification: refers to the verification method that, on the basis of the standard verification method, also adopts the verification method of the mobile phone number with the same name as the mobile phone number and uplink SMS;

Policy verification: refers to the verification method of adding peripheral data verification on the basis of standard verification or strong verification; verification methods of peripheral data verification include but not limited to verification of the same mobile phone number, using the bank's/other bank's debit card/ Credit card four-factor or five-factor verification or six-factor verification, the Bank's contracted business information verification, WeChat and other third-party channel platform link authorization verification, small transfer verification with the same name, and the Bank's contract information verification and other verification methods;

The validation rules include:

The mobile phone number verification method is coded according to business code rules, a total of 10 digits, in the form of X-X-X-X-X-X-X-X-X-X; where:

No. 1: Represents the first-level verification method

For example: 0=weak verification, 1=standard verification, 2=strong verification, 3=policy verification, 4=standard verification+policy verification, 5=strong verification+policy verification;

No. 2: Represents whether a SMS verification code is required

For example: 0 = required, 1 = not required;

The third digit: represents the second-level verification method under the first-level verification method

For example: 0=only SMS verification code verification, 1=same name verification, 2=uplink SMS verification, 3=same name verification+uplink SMS verification;

Bits 4-6: represent the verification strategy

For example: 100=same verification of reserved mobile phone numbers, 101=same verification of mobile banking/online banking mobile phone numbers, 102=same verification of SMS SMS mobile phone numbers, 103=same verification of wealth management contract mobile phone numbers; 202=two-factor verification, 203=Three-factor verification, 204=Four-factor verification, 205=Five-factor verification, 206=Six-factor verification; 301=WeChat link authorization verification; 401=Same-name transfer verification for small amount; 501=Bank contract information verification;

No. 7-8: Represents verification support channels

For example: 00 = counter only, 02 = ITM only, 03 = mobile banking only, 04 = online banking only; 10 = counter + ITM, 11 = mobile banking + online banking, 12 = counter + ITM + mobile banking, 13 = counter Face + ITM + mobile banking + online banking; 21 = only external channel A, 22 = only external channel B, 23 = only external channel C, 24 = only external channel D, etc.;

Bit 9-10: reserved for function expansion;

Generally speaking, peripheral channels match specific business rules, assemble business code rule codes, and the core performs specific business operations according to business codes. Here we take account opening at the counter as an example.

The counter system will check whether the customer has opened a customer according to the customer's certificate information:

When opening a new account without a customer number, the mobile phone number retained by the customer shall be verified as follows.

(1) The system checks whether the mobile phone has the same name.

(2) The system checks whether the "reserved mobile phone number" and "mobile banking/online banking contract mobile phone number" under other customers have the same number.

The code of the business code rule assembled according to the above rules is 4011010000.

If you open a new account with a customer number and a reserved mobile phone number, the system will use the existing reserved mobile phone number under the customer number by default. The system will judge the corresponding status of the existing reserved mobile phone number under the customer number The reserved mobile phone number shall prevail, and a SMS verification code will be sent, and the corresponding business code rule code shall be 1000000000.

In addition, if the customer insists on not keeping the mobile phone number, the "fixed line" can be kept, and the retained "fixed line" will not be verified with the same name, SMS verification code, and same number; the corresponding status of the fixed line will not be marked, and the business code rules will be encoded is 0100000000.

After the core system obtains the corresponding verification rules, it parses them in sequence according to the encoding rules.

103. Verify the information to be checked: According to the verification method and verification rules, verify the information to be checked sent by the customer to determine whether it is legal; the first order of judgment: the system checks whether the mobile phone number has the same name. like:

Phone numbers with the same name: verification passed.

If the mobile phone number is not the same name: According to the regulatory policy, further verification measures need to be taken as follows:

Initiate the four-factor verification of the debit card of another bank under the customer's own name.

If the four-factor verification of the debit card of another bank under my name is consistent, this mobile phone number can be used as the reserved mobile phone number.

In the event that a customer cannot provide the debit card number of another bank, or is unwilling to provide the card number, or does not have other debit cards, etc., the four-factor verification cannot be performed; Code" to verify the phone number.

Judging the second order: the system checks whether the mobile phone numbers reserved under other customers and the mobile banking/online banking contract mobile phone numbers have the same number.

For the same mobile phone number as "Reserved Mobile Number" or "Mobile Banking/Internet Banking Contract Mobile Number" under other customers, the following procedures shall be taken.

1) The same "reserved mobile phone number" or "mobile banking/online banking contracted mobile phone number" under other customers: do not delete.

2) For the same "reserved mobile phone number" under other customers, mark the duplicate status of the mobile phone number as: "Other customers have verified use".

3) Make the mobile phone number of the same mobile banking/online banking contract under other customers the same mobile phone number, and mark the duplicate status of the mobile phone number as: "Verified and used by other customers". At the same time, Linkage will mark the holding status of mobile banking/online banking contracted mobile phone numbers under other customers as "invalid".

4) Exceptional scenario: If the mobile phone number is the same as the "reserved mobile phone number" or "mobile banking/online banking contract mobile phone number" under other customers, but the system retrieves the "family mobile phone number queue" and this customer belongs to the " Family mobile phone number registration relationship", the duplicate status of the same mobile phone number under other customers will not be updated.

According to different businesses (such as contract signing and account opening), it is stipulated whether the same-name verification of the mobile phone number is required (for example, contract signing is required, if the customer has not reserved a mobile phone number for account opening business, or the reserved mobile phone number needs to be modified for account opening business) needs to be verified). The verification channel for the same name of the mobile phone number is subject to the channel determined by the operation professional. The verification method of the mobile phone number with the same name is as follows:

Mobile phone number with the same name: verification passed;

If the mobile phone number is not the same name: According to the regulatory policy, further verification measures need to be taken as follows:

1) Initiate the four-factor verification of the debit card of another bank under the customer's own name;

2) If the four-factor verification of the debit card of another bank under my name is consistent, the mobile phone number can be used as the reserved mobile phone number;

3) If a customer cannot perform four-factor verification, the mobile phone number standard verification method will be adopted, and the mobile phone number will be verified with a SMS verification code.

104. Storage: storing the inspection information, the inspection information includes: inspection result information, customer information and customer contact information;

105. Return inspection result information: display the inspection result to the client.

On the other hand, the present invention also provides a customer contact information management system for the banking system, as shown in Figure 2, including the following modules for implementing any of the methods described above:

An information collection module, configured to collect information to be checked;

A verification rule matching module, configured to match the information to be checked with the verification rules;

A verification module, configured to verify the verification information according to verification rules;

An information storage module, configured to store inspection information and inspection result information;

The display module is used to display the inspection results.

To sum up, the present invention proposes a customer contact verification method and management system for the banking system. By establishing the customer label corresponding to the mobile phone number scene of the customer, the scene can be driven by the mobile phone number combination label under the customer item during business processing. And data calls, and then identify customers and businesses. When customers verify their contact information, they no longer need to verify repeatedly. They only need to input once, and the system will automatically match according to specific scenarios, solving the problem that the system needs repeated calculations when encountering different businesses. One-time verification can be used everywhere, so that users can more conveniently handle business related to contact information, simplify the handling procedures, improve user experience and meet regulatory requirements.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present invention are included in the protection scope of the present invention.

Claims (4)

1. A method for verifying a customer contact address for a banking system, comprising the steps of:

101. inputting information to be checked, wherein the information to be checked comprises: customer information, customer contact information, and account information;

102. according to scene matching verification rules; the scene includes: information uploading channels to be checked, contact information types, whether customer information is already opened and whether account information is already opened;

103. verifying information to be checked: according to the verification mode and the verification rule, the information to be checked is sent to the client for verification; a first sequence: the system checks whether the mobile phone numbers are the same name or not, and the second sequence is as follows: the system checks whether the reserved mobile phone number and the mobile phone number signed by the mobile phone bank/the online banking have the same number or not under other client items;

the verification mode comprises the following steps: weak authentication, standard authentication, strong authentication, and policy authentication; wherein, weak verification refers to a verification mode that only mobile phone numbers are registered and only mobile phone number logic is checked by a system; standard verification refers to a verification mode of only passing through a short message verification code; the strong verification means that on the basis of a standard verification mode, a mobile phone number same-name verification mode or an uplink short message verification mode is adopted for the mobile phone number; the policy verification refers to a verification mode of adding peripheral data verification on the basis of standard verification or strong verification;

the validation rule includes:

carrying out service code rule coding on a mobile phone number verification mode, wherein the total number of the mobile phone number verification mode is 10;

bit 1: representing a primary authentication mode

Wherein: 0=weak authentication, 1=standard authentication, 2=strong authentication, 3=policy authentication, 4=standard authentication+policy authentication, 5=strong authentication+policy authentication;

bit 2: representing whether short message verification code is needed or not

Wherein: 0=required, 1=not required;

3 rd bit: representing the second level verification scheme under the first level verification scheme item

Wherein: 0=short message verification code only, 1=homonym verification, 2=uplink short message verification, 3=homonym verification+uplink short message verification;

4 th to 6 th bits: representing authentication policies

Wherein: 100 The same check of the reserved mobile phone number, the same check of the mobile phone number of 101=mobile phone bank/internet banking mobile phone number, the same check of the mobile phone number of 102=short message communication, and the same check of the 103=financial signing mobile phone number; 202 Two-element authentication, 203=three-element authentication, 204=four-element authentication, 205=five-element authentication, 206=six-element authentication; 301 WeChat Link authorization verification; 401 =small homonym transfer verification; 501 =present line subscription information verification;

7 th to 8 th bits: representative verification support channel

Wherein: 00 Counter only, 02=itm only, 03=cell phone bank only, 04=internet bank only; 10 Counter + ITM,11 = mobile banking + internet banking, 12 = counter + ITM + mobile banking, 13 = counter + ITM + mobile banking + internet banking; 21 External channel a only, 22=external channel B only, 23=external channel C only, 24=external channel D only;

bits 9-10: reserved bits for function expansion;

104. and (3) storing: storing inspection information, the inspection information comprising: checking result information, customer information and customer contact information;

105. returning inspection result information: and displaying the checking result to the client.

2. The method for verifying a customer contact address of a banking system as claimed in claim 1, wherein the method for verifying a same name of a mobile phone number is as follows:

the mobile phone numbers are the same as the names: checking is passed;

the mobile phone numbers are not of the same name: further verification measures are taken as follows, according to regulatory policy requirements:

1) Initiating verification of four elements of the debit card of the other row under the name of the customer;

2) The four elements of the debit card of the other line under the name of the person are verified to be consistent, and the mobile phone number can be used as a reserved mobile phone number;

3) If the client cannot perform four-element verification, a mobile phone number standard verification mode is adopted, and the mobile phone number is verified by a short message verification code.

3. A customer contact verification method for use in a banking system according to claim 1, wherein the peripheral data verification includes, but is not limited to, one or more of the same cell phone number verification, four-element or five-element verification or six-element verification using a present line/his line debit/credit card, present line subscription service information verification, third party channel platform link authorization verification, micropayment verification, present line subscription information verification.

4. A customer contact management system for a banking system, comprising the following modules for implementing the method of any of claims 1-3:

the information acquisition module is used for collecting information to be inspected;

the checking rule matching module is used for matching the information to be checked with the checking rule;

the verification module is used for verifying the verification information according to the verification rule;

the information storage module is used for storing the checking information and the checking result information;

and the display module is used for displaying the inspection result.

Images