Implementing epayments at QUB Library

Trevor Lyttle

Assistant Director, Information Services, QUB

The background

• Fines Policy

• Circulation Services Strategy

• Range of payment methods needed

• Adverse audit reports

Payment methods in 2007

• Cash or cheque only at Issue Desks

• Smartcard terminal in Main Library

Epayments requirement

• Online payments

• Electronic terminals

Electronic terminals

• Credit and debit cards

• Available at Issue Desks – now rolled out to all branches

• Cardholder present

• Cardholder not present

• Easy to get – phone the bank and use existing merchant IDs

Online payments

• Worldpay

• Queen’s Online

• My Library

Queen’s Online - the electronic university

• Accessed by nearly all students and most staff

• All users in University directory

• Available to all Library users – even non-staff/student members

Implementing epayments

• Talis proposal July 2007

• Project group established

• Requirements confirmed

Service Integration

Queens Online

Talis Keystone

WorldPay Queens Online

Integrating Services

• Queens Online – the university portal– PHP application

• WorldPay – Internet payment provider– Payment processing system software used to accept payments

on the Internet using credit and debit cards

• Talis Keystone – library management software– Web services

Library Services

Requirements

• Keep it simple to use and implement

• £5 minimum payment

• Payment type recorded as “Credit Card”

• No part payments allowed

Queens Online Portal

Requirements

• Link for all library borrowers

• Secure payment provision

• Talis ‘payment’ web service

Queens Online Portal

Library Charges

– Use Talis web service to obtain current charge amount

– Use Talis web service (paymentProperties) - retrieve min and max payment amounts

– Call to WorldPay to carry out internet payment transaction

– Call to Talis web service (payment)- update borrower’s record to reflect payment

Program Overview

callback.php(WorldPay)

Program to carry out secure payment transaction

index.php

Main Program calling Talis web services and WorldPay.Also responsible for creating dynamic HTML

handler-library_charge

s.php

Step 1

Step 2

Step 3

Logon Form

QOL index Page

SuccessfulLog on

QOL Page containing information relating to Student/Staff library account.

Program to write WP transaction to DB and call Talis Payment web service

Talis Payment Web Service

• Request submitted via HTTP POST-To post a payment to the borrowers account

• Parameters sent- BorrowerId, BorrowerIdType, Amount, PaymentType

• http://quprism/TalisSOA/services/payment/2096358?borrower_identifier_type=BARCODE&amount=5.50&payment_type=CreditCard

Talis Payment Web Service

• Returns an XML response detailing the charge paid off[<?xml version="1.0" encoding="UTF-8" standalone="yes"?><payments xmlns:tsoa="http://schemas.talis.com/2007/soa/e-payment">

<payment_accepted>true</payment_accepted> <tsoa:payment> <tsoa:accepted>true</tsoa:accepted> <tsoa:borrower_id>1896</tsoa:borrower_id> <tsoa:credit_id>2096358</tsoa:credit_id> <tsoa:charge_id>1214988</tsoa:charge_id> <tsoa:amount>5.50</tsoa:amount> <tsoa:timestamp>2007-1017T12:37:01.222+01:00</tsoa:timestamp> <tsoa:outstanding_amount>0.00</tsoa:outstanding_amount> </tsoa:payment>

</payments>

• Update database with payment • Update log file

What have we achieved?

• A 24/7 online payment service giving greater customer service.

• Services combined seamlessly under one application.

• Easily identifiable and accessible from an interface within the

University’s portal.

• Within official University processes

• Audit

• Tighter procedures at Desks

Lessons learned

• Refunds

• Staff confusion between web payments and terminal payments

• Student confusion between fines and charges for lost items

• Screens clarified and additional training

Questions?

Jane O’Neill j.oneill@qub.ac.uk

Anne Duffy a.t.duffy@qub.ac.uk