Add online show entry system with payment gateway interface to existing website

An annual Australian regional wine show needs an online entry system that stores entry details into a database and also interfaces with a payment system. The entry system should be added to the existing web site. This website is hosted on [login to view URL] and is maintained using WordPress. The hosting service supports both MySQL (v5.5) and MSSQL (version not specified) databases. The supported scripting options are PHP 5 & 7, ASP, ASP.NET, Perl/CGI and Python. The PayWay Net payment gateway from Westpac bank has been chosen to handle payments. The developers guide for this system has the following list of required technologies: A dynamic back-end which can send a HTTPS POST directly to PayWay server, The ability to make an outbound HTTPS connection to PayWay through your proxy and firewall (for secure token request), A valid SSL certificate issued by a trusted certificate authority (for server to server payment notification), A dynamic back-end which can receive and parse HTTPS requests with parameters or can parse XML (for customising receipt page), The ability to decrypt and verify data encrypted using AES with Cipher Block Chaining (for customising receipt page). See the attached [login to view URL] document for full details. Obtaining a SSL certificate and subscribing to PayWay is our responsibility, as is providing developer access to both PayWay and the website hosting account. The solution should be available for testing by 17 October 2016, to be ready to go live at the end of the month. Your proposal should provide for support in the first month of going live. The following general description of the entry requirements is provided for information only. The attached Scope document should be referred to as the definitive list of the work required to include in your proposal for this project. This Scope document lists the requirements in two groups - Administrator functionality and website functionality. The show is based on classes, where a Class is based on variety and vintage. An Entrant will typically be entering for only one Exhibitor, but some Entrants have multiple Exhibitors. An Exhibitor will typically have more than one Entry, and each Entry is a single wine in a single Class. The entry fee depends on the Class. The number of Entries will be less than 500 each year. The number of bottles to be delivered for judging also depends on the Class. See the attached preliminary database schema. From the perspective of an Entrant, an 'entry' is a transaction with one or more Entries and a calculated total entry fee. The 'entry' is only valid after payment is received. The Entrant should get acknowledgement of payment. Once an Entrant has created login details (email based), they should be able to come back and add entries. The Entrant details should be persisted and lost password functionality provided for use in future years. A csv file of entries produce after the closing date is needed. Administrator(s) access is required including an administrator report of entries.