Seven Steps to Implementing an E-Commerce Solution Using QuikPAY
- The customer completes the online e-commerce service request form.
- The Treasurer’s Office reviews the request and contacts the customer to discuss the following items:
- The University’s payment processing solution, QuikPAY, from Nelnet Business Solutions (NBS)
- Security guidelines and audit requirements
- Information regarding the implementation time line
If you want to use a vendor-purchased front-end application, the Treasurer’s Office arranges contact between the vendor and Nelnet Business Solutions. NBS requires you to sign a nondisclosure agreement before you can receive NBS documentation.
If you want to use a payment processing solution other than QuikPAY, provide the Treasurer’s Office with vendor contact information, proof of vendor PCI compliance, and application documentation. The Treasurer’s Office and the Information Security & Access Management (ISAM) team will evaluate the vendor product for compliance with the University’s e-commerce security guidelines. The Treasurer’s Office contacts you within two weeks as to whether the vendor product meets University of Missouri e-commerce requirements.
Final approval for all e-commerce activity requests will come from the Treasurer’s Office.
- Upon approval, the following information is sent to the customer:
- Pricing information
- E-commerce security guide
- Nelnet Business Solutions technical documentation to interface with QuikPAY:
- Pass-through authentication from customer’s application to QuikPAY
- Receipt redirect from QuikPAY to customer’s application
- Code examples of the pass-through authentication and receipt redirect
- QuikPAY generic test site URL
- Nondisclosure agreement (sent to customers using a vendor front-end application)
- The Treasurer’s Office will schedule the application in a future QuikPAY implementation phase and will notify the customer of the tentative project period. The formal implementation typically lasts from six to eight weeks, including testing.
- The Treasurer’s Office works with Nelnet Business Solutions to schedule the project kick-off meeting and notifies you. Prior to the project kick-off meeting you will be sent the following documents:
- Business Requirements Checklist
- Merchant ID Request Form
- Project Plan
The customer will be asked to provide a PeopleSoft item type for feeds to PeopleSoft student financials (when applicable)
- During the formal implementation, the Treasurer’s Office will:
- Work with the Nelnet Business Solutions project manager to complete the project tasks and meet objectives defined in the project time line
- Set up a merchant ID and YourPay acccount
- Request ISAM schedule an audit during the project acceptance testing phase
- Provide accounting information for Nelnet Business Solutions invoice recharge processing
- Download a PEM file from YourPay and register it with QuikPAY
- Provide QuikPAY API technical support to customers and campus e-commerce contacts
- Provide QuikPAY API support to their campus customers
- Modifies the front-end application to transfer data to and receive data from QuikPAY according to the QuikPAY API specifications
- Meets all project deadlines as outlined in the Nelnet Business Solutions project plan
- Completes the security documents when requested by ISAM
- Works with ISAM to meet audit requirements as outlined in the e-commerce security guidelines
- Participates in the project status calls
- Develops reconciliation procedures
- Schedules and conducts audits
- Notifies the Treasurer’s Office of successful audits
- Advises the customer of system changes needed to successfully meet the audit requirements
- Go live. The application is available for production use.
How an E-Commerce Credit Card Payment Works
This is an example of how a credit card payment is processed from an e-commerce web application using QuikPAY. The web application could be designed for a variety of business needs, including a shopping cart, conference registration, or to accept donations.
- The customer uses a web application to select goods or services for purchase. The customer clicks a “pay now” button to initiate payment.
- The customer is transferred to QuikPAY. The customer enters the credit card account number and expiration date. The customer presses the “confirm” button to submit the payment.
- QuikPAY passes the transaction to the merchant bank’s processor, YourPay.
- YourPay submits the transaction to the credit card interchange.
- The credit card interchange submits the transaction to the issuer for authorization.
- The credit card issuer approves or declines the transaction and passes the results back through the credit card interchange.
- The credit card interchange passes the authorization results to YourPay.
- YourPay passes the transaction results to QuikPAY.
- QuikPAY stores the transaction results and sends them to the web application.
- The web application presents a transaction successful or declined message to the customer.
- The credit card interchange passes the funds to the University’s Commerce bank account.
- Successful transaction information is sent to the University through QuikPAY real-time notification and end-of-day files. The data is stored in the University’s Oracle databases.
- A University process creates feeder files to the general ledger for all QuikPAY transactions and, optionally, to CSAR or PeopleSoft student financials.
- QuikPAY transactions are posted to PeopleSoft general ledger.
- When applicable, QuikPAY transactions are posted to PeopleSoft student financials.