Android payment plug-in management method and system

Abstract

The invention discloses an Android payment plug-in management method. The method comprises the steps that a payment platform generates configuration files for a transaction interface and a transaction flow and submits the configuration files to a middle service layer; a front-end application registers a transaction type supported by the front-end application and calls back the transaction type to the middle service layer; the middle service layer obtains a user transaction channel, a corresponding payment platform transaction interface is called according to the configuration files, and transaction is completed. In this way, by means of the Android payment plug-in management method, high coupling of the service function and the transaction function can be achieved, the workload of a front-end platform is eliminated, and the input cost of expansion and maintenance in the later period is reduced.

Description

technical field [0001] The invention relates to the technical field of Android payment, in particular to a management method and system of an Android payment plug-in. Background technique [0002] In the past, when developing an APP with payment functions, developers usually directly integrated these payment functions in the APP, and the business functions and payment functions were combined and interacted. In the era when UnionPay card payment is the main transaction platform, this approach can barely meet the development needs. However, as payment methods such as WeChat and Alipay have gradually become popular payment channels for ordinary consumers and merchants, more and more payment platforms need to be connected to APP. geometric growth. [0003] Android smartphones usually install many APPs, and these APPs are all focused on realizing their main functions, and they usually do not pay attention to secondary functions in order to provide users with a good experience. ...

AI Technical Summary

Problems solved by technology

[0005] Disadvantage 1: In addition to supporting traditional UnionPay card payment channels, APPs with payment functions must also support emerging payment platforms. In addition to business functions, developers must also pay attention to multi-platform access, including calling interfaces between platforms. Differences in processes, data packets, etc.

[0006] Disadvantage 2: Later expansion and maintenance require a lot of manpower and time, but the effect is often not good

[0007] Disadvantage 3: Business functions and payment functions are strongly coupled, and cannot be easily transplanted to new APPs

Images