Design of online payment interface based on ASP.net

1 Status of online payments

Online payment refers to a business in which a bank provides an online fund settlement service when the seller and the buyer trade through an E-commerce website on the Internet.

Online payment, also known as real-time electronic payment. This is a necessary part of E-commerce, the lack of online payment is not fully realized e-commerce. Online payment is made by the merchant to choose the online payment platform service provider (such as the preset includes PayPal, fast Money, Alipay, the first letter, Ipay, NPS, net Bank and so on more than 10 kinds of main online payment interface, with the payment platform to sign a service agreement, open the payment interface, by the merchant to pay the transaction generated by the fees, Customers can choose to use online payment method to pay for the goods they purchase.

At present, most online payment platform online payment interface has been applied to many aspects of life, but some of the payment interface is still deficient:

(1) The database cannot be shared in real time. It is not possible to implement different people, from different locations, to access and manipulate common databases at the same time in different access modes.

(2) The client's hardware and software configuration requirements are complex. Often use this payment platform, download the payment platform control, in the use of online payment interface transactions also need to carry out software and hardware configuration, to bring a lot of inconvenience to customers.

In view of the above deficiencies, this interface is selected by ASP technology for writing, testing can be done in the IIS application directory.

2 Technical advantages of applying asp.net

ASP.net is an Internet programming technology launched by Microsoft in 2000 and is a platform for the next-generation enterprise-class Web application development. It is executed when the Web server receives a pair of ASP. NET page, if this is the first application that is modified after the page is created, the content of the page is first compiled into an MSIL language, and then the MSIL is then compiled into machine code for execution.

In view of the shortcomings of the current online payment interface, ASP technology has its own solution.

(1) To achieve different people, from different locations, to access and operate a common database in different ways. The application of the traditional server/client structure requires that the user and server must be on the same network segment, but in fact the user has the cross region and the network segment. In this way, the application of traditional server/client is difficult to realize this kind of trans-region and cross-net segment. The application of asp.net security information management system, whether the user in the field, or abroad, as long as there is a machine can be on the Internet, can be authenticated through the user access to the Network Payment Platform system query information, users whether it is the morning, Or at night at any time can be verified by the user to use the system for online payment transactions, to the user to bring great convenience.

(2) The client's software and hardware configuration has no special requirements, as long as the client installation browser can query information through the network. When the system needs to upgrade, the application of traditional server/client structure, must be upgraded to all customers, and the application of ASP.net security information management system, developers only need to upgrade the server program, the user unknowingly completed the replacement of software, so that the user is convenient, and convenient maintenance.

3 Functional Requirements for interfaces

The interface design of the payment service is as shown in Figure 1, which consists mainly of the payment interface, the order enquiry interface and the 3 parts of the order refund interface.

(1) Payment interface. Through the payment request file to initiate the payment request, the merchant may write own order information in this file, and then submits the request to the platform payment system, waits for the platform payment system processing, the transaction successful callback (browser redirects), or the transaction succeeds, the backstage active notification (server point-to-point communication) One of the above browser redirects and one active notification will go through the HTTP protocol to the Merchant return URL address, as shown in Figure 2.