CN113191762B - Method for realizing public component based on configured financial transaction type short message verification code - Google Patents
Method for realizing public component based on configured financial transaction type short message verification code Download PDFInfo
- Publication number
- CN113191762B CN113191762B CN202110751650.XA CN202110751650A CN113191762B CN 113191762 B CN113191762 B CN 113191762B CN 202110751650 A CN202110751650 A CN 202110751650A CN 113191762 B CN113191762 B CN 113191762B
- Authority
- CN
- China
- Prior art keywords
- short message
- verification code
- end component
- code
- message verification
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000012795 verification Methods 0.000 title claims abstract description 122
- 238000000034 method Methods 0.000 title claims abstract description 14
- 230000000694 effects Effects 0.000 claims abstract description 32
- 230000004913 activation Effects 0.000 abstract description 2
- 238000002955 isolation Methods 0.000 abstract description 2
- 230000000737 periodic effect Effects 0.000 description 5
- 230000008676 import Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
- G06Q20/3255—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks using mobile network messaging services for payment, e.g. SMS
-
- 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/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Computer Networks & Wireless Communication (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a method for realizing a public component based on a configured financial transaction type short message verification code. Determining and storing a binding relationship between a specific service and a short message verification code template configuration; the back end exposes HTTP interface services such as short message verification code sending, verification and the like to form a back end component, and the back end component exposes short message verification code sending and verification services for the front end component to call; publishing the front-end component to the repository through npm forms the front-end component, and other items are installed directly through npm, which can be used in the page upon introduction and activation. The invention solves the problem of functional redundancy of the system, improves the expandability and isolation of the system, and is easy to maintain and upgrade; the short message identifying code component can be used at the front end through simple configuration, and the difference of the short message identifying codes of the unavailable service activities is also distinguished according to the difference of the transmitted parameters; the absolute safety of the business activity is ensured.
Description
Technical Field
The invention relates to the technical field of user identity authentication, in particular to a realization method of a public component based on a configured financial transaction type short message verification code.
Background
In recent years, with the continuous development and growth of business scale of our industry, more and more business support systems come into existence, and as a banking and financial industry system, short message verification codes which are the most common means for identifying user identities can see the body shadow of the users in each application system.
The method for accessing the short message verification code in each existing application system is a mode of repeatedly manufacturing wheels, for example, the short message verification code is accessed to an Aliyun short message verification code platform, and the method comprises the following steps: 1. an SDK (a client JAR packet sent by a short message) introduced into an Aliskiun short message platform; 2. writing a short message sending logic code related to the service according to the access document; 3. and writing a short message verification logic code related to the service according to the access document. The function of each application system for accessing the short message verification code is repeated by 1, 2 and 3 steps, so that the system generates a considerable degree of functional redundancy.
Secondly, each system has own short message verification code function logic, so that unified maintenance of codes is inconvenient, for example, when an SDK (software development kit) of an Aliyun short message platform is upgraded, each system needs to be upgraded one by one, and tests are needed after upgrading, which wastes time and labor.
The scenes of short message verification codes used in customer-oriented application systems in banking and financial industries are relatively fixed, and the scenes can be basically divided into: transaction type, subscription type, authentication login type and the like, and the integration and modularization of the service short message verification code are possible due to the characteristic that the transaction type, the subscription type, the authentication login type and the like can be tracked.
Disclosure of Invention
The invention aims to provide a method for realizing a public component based on a configured financial transaction type short message verification code aiming at the defects in the prior art.
In order to achieve the aim, the invention provides a method for realizing a public component based on a configured financial transaction type short message verification code, which comprises the following steps:
step 1, determining and storing a binding relationship between a specific service and a short message verification code template configuration;
step 2, the back end exposes HTTP interface services such as short message verification code sending, verification and the like to form a back end component, and the back end component exposes short message verification code sending and verification services for the front end component to call;
step 3, publishing the front-end component to the resource library through npm to form the front-end component, and installing other items directly through npm, wherein the front-end component can be used in the page after being introduced and activated.
Further, the step 1 specifically includes:
step 1.1, adopting a unique application code to identify the service system;
step 1.2, defining a service code for each specific service to identify the specific service;
step 1.3, defining an activity type to identify the activity type of a specific service;
step 1.4, determining specific services through the application codes, the service codes and the activity types;
step 1.5, dividing the short message verification code template into a short message template number part and a short message template parameter list part, wherein the short message template number is unique, and the short message template parameter list is used for filling the short message template to generate the final content of the sent short message;
and step 1.6, binding and storing the specific service in the step 1.4 and the short message verification code template in the step 1.5.
Further, the step 2 specifically includes:
step 2.1, the front end component calls a short message verification code sending interface of the back end component and triggers the short message verification code to send an HTTP request, the short message verification code sends the HTTP request by taking a mobile phone number, an application code, a service code, an activity type, a short message template parameter list, a product name and/or a transaction amount as sending request parameters, the back end component uniquely determines a short message template number bound with the back end component according to the application code, the service code and the activity type after receiving the request, then queries the short message template parameter list configured in a database according to the value of the short message template number to check whether parameter subentries in the short message template parameter list transmitted by the front end component are complete, if complete, the back end component calls a short message platform SDK to send the short message verification code, and generates a short message serial number after the short message verification code is successfully sent, correspondingly storing the serial number of the short message and all request parameters into a database;
and 2.2, the front end component calls a short message verification code verification interface of the back end component and triggers a short message verification code verification HTTP request, the short message verification code verification HTTP request takes a short message serial number as a verification request parameter, the back end component inquires all corresponding parameters from a database cache according to the short message serial number after receiving the request, then collects a mobile phone number, a verification code, a short message template parameter list and a product name and/or a transaction amount, calls a verification code input by a short message platform SDK verification client, returns a Token to the front end component after the short message verification code is successfully verified, and continues to call a specific service activity interface with the Token parameter after the short message verification code is successfully verified.
Further, the short message platform comprises an Aliyun short message platform.
Further, the database comprises a Redis database, and the Redis database is stored by taking the serial number of the short message as key and a Hash table formed by all request parameters as value.
Has the advantages that: 1. the traditional short message verification code access logic code is stripped from each irrelevant application system to form an independent public component service, so that the problem of function redundancy of the system is solved, the short message verification code function and the specific application system are isolated by the component, and the expandability and the isolation of the system are improved. The independent public component also enables the short message verification code function code to be easy to maintain and upgrade, for example, in the function logic of the traditional short message verification code, if the SDK of the short message platform is upgraded, each application system is also upgraded, and the advantages of componentization are obviously separated at the moment: so the component is upgraded at one place.
2. In the specific field such as banks, the short message verification code links are related to a plurality of service scenes which can be counted as the number of fingers, and the short message verification code is bound with the short message verification code template configuration through specific services so that the short message verification code functional assembly is possible, so that the short message verification code assembly can be used at the front end through simple configuration, and meanwhile, the difference of the short message verification codes which do not have service activities is distinguished according to the difference of the transmitted parameters.
3. Through a mechanism based on the disposable Token, the Token Token parameter returned by the short message verification code component is carried after the short message verification code link of the business activity is finished to request the real business activity, so that the absolute safety of the business activity is ensured.
Drawings
Fig. 1 is a schematic workflow diagram of a configured financial transaction type short message verification code-based public component according to an embodiment of the present invention.
Detailed Description
The present invention will be further illustrated with reference to the accompanying drawings and specific examples, which are carried out on the premise of the technical solution of the present invention, and it should be understood that these examples are only for illustrating the present invention and are not intended to limit the scope of the present invention.
The embodiment of the invention provides a method for realizing a public component based on a configured financial transaction type short message verification code, which comprises the following steps:
step 1, determining and storing the binding relationship between the specific service and the short message verification code template configuration. Since specific business activities (such as deposit business for the client to handle periodic deposits) must occur on a certain business system, the following steps can be implemented:
step 1.1, unique application code (appCode) is used to identify the business system.
Step 1.2, a service code (bizCode) is defined for each specific service to identify the specific service.
Step 1.3, define an activity type (actType) to identify the activity type of a specific service.
Step 1.4, the specific service is determined by the application code (appCode) + service code (bizCode) + activity type (actType).
For example:
{
appCode CFSP,// CFSP stands for Intelligent deposit System
BizCode DQCK,// DQCK stands for periodic deposit service
actType 1// 1-represents deposit, 2-represents draw
}
Represents a complete business activity: a client is handling deposit transaction of periodic deposits, and the online handling of the transaction is actually completed through the intelligent deposit system.
And step 1.5, dividing the short message verification code template into a short message template number (smsTemplateCode) and a short message template parameter list (smsTemplatePaarams), wherein the short message template number is unique, and the short message template parameter list is used for filling the short message template to generate the final content of the sent short message.
For example, if there is a "periodic deposit client submitting deposit" short message verification code template:
"you are handling the periodic deposit service, the verification code: { smsCode }, Do not reveal verification code, detail consultation customer service telephone xxxx "
Then the short message authentication code template has a unique smstempatecode to represent it, and the parameter smsCode in the template is the component of smsTemplateParams.
And step 1.6, binding and storing the specific service in the step 1.4 and the short message verification code template in the step 1.5. The storage location may be a database such as MySQL.
Namely, a service short message is uniquely determined by an application code (appCode) + a service code (bizCode) + an activity type (actType) + a short message template parameter list (smsTemplateCode).
And 2, the back end exposes HTTP interface services such as short message verification code sending, verification and the like to form a back end component, and the back end component exposes short message verification code sending and verification services for the front end component to call. The specific business service does not need to concern the logic of sending, verifying and the like of the short message verification code. The method specifically comprises the following steps:
step 2.1, the front-end component calls a short message verification code sending interface of the back-end component and triggers the short message verification code to send an HTTP request, the short message verification code sends the HTTP request by taking a mobile phone number, an application code (appCode), a service code (bizCode), an activity type (action type), a short message template parameter list (smstemplateCode), a product name (productName) and/or a transaction amount (amt) as sending request parameters, the back-end component uniquely determines a short message template number (smstemplateCode) bound with the request according to the application code, the service code and the activity type after receiving the request, then inquires a short message template parameter list (smtemplatePaams) configured in a database according to the value of the short message template number (smstemplateCode) to check whether the parameter sub-items in the short message template parameter list (smstemplatePaams) sent by the front-end component are complete, if so, the back-end component calls the short message verification code to send the short message verification code, and after the short message verification code is successfully sent, generating a short message serial number (smsSerialNo), and correspondingly storing the short message serial number (smsSerialNo) and all the request parameters into a database.
Specifically, the short message platform may be an aricloud short message platform, and the database includes a Redis database, which stores a Hash table composed of all request parameters as a value in a cache of the Redis database, with a short message serial number (smsSerialNo) as a key. Therefore, only two parameters of the smsSerialNo and the smsCode need to be transmitted in the next short message verification code verification link.
Step 2.2, the front-end component calls a short message verification code verification interface of the back-end component and triggers a short message verification code verification HTTP request, the short message verification code verification HTTP request takes a short message serial number (smsSerialNo) as a verification request parameter, after the back-end component receives the request, all parameters corresponding to the short message serial number (smsSerialNo) are inquired from a database cache according to the short message serial number (smsSerialNo), then necessary parameters (mobile, smsCode, smsTemplateCode, product name and/or transaction amount and the like) are collected, a short message platform SDK is called to verify a verification code input by a client, after the short message verification code is verified successfully, a Token is returned to the front-end component, and the front-end component continues to call a specific service activity interface with the Token parameter of the Token after the short message verification code is verified successfully. For example, a deposit interface for a fixed deposit is called. It should be noted that, among the above-mentioned necessary parameters, the object, the smsCode, and the smstemplate code are necessary parameters required by the short message verification code template, the product name and/or the transaction amount are necessary service parameters, the necessary service parameters required by each short message template are not fixed, and some of them may only be the product name or the amt, and some of them may both be the product name or the amt.
The Token is a one-time Token, and is used for really executing business activities under the condition that the customer really executes business activities through pre-verification after passing identity authentication based on a short message verification code, and otherwise, an error is returned. The purpose of this is to improve the security, because through certain technical means, the hacker can completely bypass the short message verification link and directly enter the business activity at the browser end
And 3, issuing a front-end component to the resource library through npm (a JavaScript world package management tool) to form the front-end component, directly installing other items through npm, and enabling the front-end component to be used in the page after being introduced and activated. The method comprises the following specific steps:
//1, introducing front-end components in the page
import { vcsmss } from 'vcsmss-ui'/import component
Cs 'import' vcsmss-ui/lib/index;/import component style
Use (vcsms);/activation component
//2, use of front-end Components in pages
<vcsms app-code="CFSP" biz-code="DQCK" act-type="1" :sms-template-params="smsTemplateParams"/>
The short message verification code public component comprises a front end component and a back end component, when the short message verification code public component works, a front end page of an application system is accessed to the front end component of the short message verification code, the front end component triggers the short message verification code to send an HTTP request to the back end component, the back end component inquires the binding relation between a business activity and a short message template according to business parameters, the back end component also temporarily stores all the data obtained in the front into a Redis to be used when the data is verified, the front end component triggers the short message verification code to verify the HTTP request to the back end component, the back end component returns a Token to the front end component after the short message verification code is successfully verified, and the application service takes the Token to execute real business activity.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that other parts not specifically described are within the prior art or common general knowledge to those of ordinary skill in the art. Without departing from the principle of the invention, several improvements and modifications can be made, and these improvements and modifications should also be construed as the scope of the invention.
Claims (3)
1. The implementation method based on the public component of the configured financial transaction short message verification code is characterized by comprising the following steps:
step 1, determining and storing a binding relationship between a specific service and a short message verification code template configuration;
step 2, the back end exposes HTTP interface services such as short message verification code sending, verification and the like to form a back end component, and the back end component exposes short message verification code sending and verification services for the front end component to call;
step 3, publishing a front-end component to a resource library through npm to form the front-end component, and installing other items directly through npm, wherein the front-end component is introduced and activated to be used in a page;
the step 1 specifically comprises:
step 1.1, adopting a unique application code to identify each business system;
step 1.2, defining a service code for each specific service to identify the specific service;
step 1.3, defining an activity type to identify the activity type of a specific service;
step 1.4, determining specific services through the application codes, the service codes and the activity types;
step 1.5, dividing the short message verification code template into a short message template number part and a short message template parameter list part, wherein the short message template number is unique, and the short message template parameter list is used for filling the short message template to generate the final content of the sent short message;
step 1.6, binding and storing the specific service in step 1.4 and the short message verification code template in step 1.5;
the step 2 specifically comprises:
step 2.1, the front end component calls a short message verification code sending interface of the back end component and triggers the short message verification code to send an HTTP request, the short message verification code sends the HTTP request by taking a mobile phone number, an application code, a service code, an activity type, a short message template parameter list, a product name and/or a transaction amount as sending request parameters, the back end component uniquely determines a short message template number bound with the back end component according to the application code, the service code and the activity type after receiving the request, then queries the short message template parameter list configured in a database according to the value of the short message template number to check whether parameter subentries in the short message template parameter list transmitted by the front end component are complete, if complete, the back end component calls a short message platform SDK to send the short message verification code, and generates a short message serial number after the short message verification code is successfully sent, correspondingly storing the serial number of the short message and all request parameters into a database;
and 2.2, the front end component calls a short message verification code verification interface of the back end component and triggers a short message verification code verification HTTP request, the short message verification code verification HTTP request takes a short message serial number as a verification request parameter, the back end component inquires all corresponding parameters from a database cache according to the short message serial number after receiving the request, then collects a mobile phone number, a verification code, a short message template parameter list and a product name and/or a transaction amount, calls a verification code input by a short message platform SDK verification client, returns a Token to the front end component after the short message verification code is successfully verified, and continues to call a specific service activity interface with the Token parameter after the short message verification code is successfully verified.
2. The method as claimed in claim 1, wherein the sms platform comprises an ariloc sms platform.
3. The method as claimed in claim 1, wherein the database comprises a Redis database, and the Redis database stores the serial number of the short message as key and the value of a Hash table composed of all request parameters.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110751650.XA CN113191762B (en) | 2021-07-03 | 2021-07-03 | Method for realizing public component based on configured financial transaction type short message verification code |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110751650.XA CN113191762B (en) | 2021-07-03 | 2021-07-03 | Method for realizing public component based on configured financial transaction type short message verification code |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113191762A CN113191762A (en) | 2021-07-30 |
| CN113191762B true CN113191762B (en) | 2021-11-12 |
Family
ID=76976973
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110751650.XA Active CN113191762B (en) | 2021-07-03 | 2021-07-03 | Method for realizing public component based on configured financial transaction type short message verification code |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113191762B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114025316B (en) * | 2021-10-27 | 2023-04-07 | 土巴兔集团股份有限公司 | Method and device for sending verification code and computer-readable storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109936826A (en) * | 2017-12-18 | 2019-06-25 | 福州锐掌网络科技有限公司 | A method of it is sent based on Ali's cloud short message service |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106851602A (en) * | 2017-03-31 | 2017-06-13 | 武汉票据交易中心有限公司 | A kind of transaction system short-message verification method and system |
| CN110650447B (en) * | 2019-10-09 | 2022-02-18 | 中国联合网络通信集团有限公司 | Short message access management method and system, terminal and operator server |
-
2021
- 2021-07-03 CN CN202110751650.XA patent/CN113191762B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109936826A (en) * | 2017-12-18 | 2019-06-25 | 福州锐掌网络科技有限公司 | A method of it is sent based on Ali's cloud short message service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113191762A (en) | 2021-07-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108427581A (en) | System micro services method and terminal device | |
| CN109194495B (en) | Server, message processing method, and computer-readable storage medium | |
| CN112163946A (en) | Accounting processing method and device based on distributed transaction system | |
| CN110245116A (en) | Reconciliation data processing method, device, equipment and computer readable storage medium | |
| CN101882293A (en) | Method and system for processing data between domestic custodian bank and overseas custodian agent bank | |
| CN103150647A (en) | Report file processing method, server and system | |
| CN102255867A (en) | Service request processing method, device and system | |
| CN108830715A (en) | Batch file part disk returning processing method and system | |
| CN107528912A (en) | A kind of automatic method, system and relevant apparatus for realizing distributing real time system | |
| CN112017007A (en) | User behavior data processing method and device, computer equipment and storage medium | |
| CN113191762B (en) | Method for realizing public component based on configured financial transaction type short message verification code | |
| CN113791586A (en) | Novel industrial APP and identification registration analysis integration method | |
| CN102385617A (en) | Dynamic domain query and query translation | |
| CN107644263A (en) | Method and server are handled in banking reservation | |
| CN112015826B (en) | Intelligent contract security detection method based on block chain and related equipment | |
| CN110336872B (en) | Method, device and system for acquiring third-party data | |
| CN111901299A (en) | Application authentication method and device, electronic equipment and storage medium | |
| CN109753767B (en) | Software distribution and updating method and device based on block chain, server and client | |
| CN112800127B (en) | Data mining analysis method and device based on transaction bill | |
| CN113055401B (en) | Enterprise business authorization processing method and device | |
| CN113850683A (en) | Car insurance inquiry request processing method and device, computer equipment and storage medium | |
| CN113450112A (en) | Data checking method, device, electronic equipment and storage medium | |
| CN112270626A (en) | Enterprise credit line management method, device, storage medium and server | |
| CN111178995B (en) | Method and system for processing bill based on cloud bill system | |
| CN109933573B (en) | Database service updating method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: No.4 building, Hexi Financial City, Jianye District, Nanjing City, Jiangsu Province, 210000 Patentee after: Jiangsu Sushang Bank Co.,Ltd. Country or region after: China Address before: No.4 building, Hexi Financial City, Jianye District, Nanjing City, Jiangsu Province, 210000 Patentee before: JIANGSU SUNING BANK Co.,Ltd. Country or region before: China |