Project
Specifications
Project Title
Claimit 3.3 – Card Processing
Update Date
13-Jul-17
Version
1.1
Specification Author Andrew Thornberry
Copyright © 2009 Yuranga Pty. Ltd. All rights reserved.
Yuranga
58 Auburn St
Wollongong 2500
extending your horizons…
1
(p) 1300 78 58 07
(f) 1300 78 58 09
(e) [email protected]
(w) www.yuranga.com
Claimit 3.3 – Cards
Project Specifications
Contents
Contents ......................................................................................................... 2
Revision .......................................................................................................... 2
Project Overview ............................................................................................ 3
Process Overview ................................................................................................ 3
Data Description................................................................................................... 3
Members............................................................................................................. 3
Members_Claims ................................................................................................ 4
Promotion ........................................................................................................... 4
Requirement Specifications .......................................................................... 4
Promo Changes ................................................................................................... 4
Front End Process Changes ............................................................................... 4
Fulfilment Process Changes ............................................................................... 4
Card Inventory .................................................................................................... 5
Card Payment ..................................................................................................... 5
Card Fulfilment ................................................................................................... 5
Revision
Date
Version
Description
Author
20/04/2011
1.0
Initial
Andrew
20/04/2011
1.1
Updated CSV load
Andrew
Yuranga
58 Auburn St
Wollongong 2500
extending your horizons…
2
(p) 1300 78 58 07
(f) 1300 78 58 09
(e) [email protected]
(w) www.yuranga.com
Project Specifications
Claimit 3.3 – Cards
Project Overview
This is an update to the claimit system to handle Card Processing.
Until now the way a consumer can get something from the system is either Cashback
(EFT or Cheque) or Reward (physical gift).
We are adding a new Cashback option called a Cashback Card which is another
form of cash transfer (like EFT) BUT which in some cases means that a physical card
will need to be fulfilled and sent to a consumer.
Process Overview
Front End
Data Description
Members
We need to add a new data element called ‘Member’. A Member will have the
following fields initially:
 MemberId
 FirstName
 LastName
Yuranga
58 Auburn St
Wollongong 2500
extending your horizons…
3
(p) 1300 78 58 07
(f) 1300 78 58 09
(e) [email protected]
(w) www.yuranga.com
Project Specifications











Claimit 3.3 – Cards
UnitNumber
AddressNumber
Address
LocationId
PhoneArea
Phone
Mobile
Email
CardNumber
Password
CardSent
Members_Claims
There will be a second table that maps Members to Claims called members_claims
with
 MemberId
 ClaimId
Promotion
We will also need a new flag in the Promotion table

use_card_flag
Requirement Specifications
Promo Changes
In the promotion setup, we need to ask an extra question when a cashback is given.
When the promotion type is set to Cash, we should add a new Payments option for
Cashback Card.
Front End Process Changes
The front end process needs to change. At the point where we would normally enter
the consumers details, we need to decide if the promotion is using cashback cards
as a payment option. IF so, we offer that option and IF that option is chosen then we
need to ask the question as to whether the consumer ALREADY has a Cashback
Card.
If they do, then we allow them to logon and then proceed to the data entry screen of
the personal details and prefill all the details, if not, they put in all their details as
usual.
Fulfilment Process Changes
Yuranga
58 Auburn St
Wollongong 2500
extending your horizons…
4
(p) 1300 78 58 07
(f) 1300 78 58 09
(e) [email protected]
(w) www.yuranga.com
Project Specifications
Claimit 3.3 – Cards
Card Inventory
I have found a table called found_distributed (not sure what that means) which looks
like an inventory table. We need a system to store cards in the inventory as with
other products, BUT we need to store each individual card number.
When adding cards to inventory, the system should prompt for the first card number
and the last card number and create all the cards in between. The reason is that
each batch of cards will be sequential, but one batch wont run into another batch.
Eg.
Batch 1: 4032-4232
Batch 2: 4566-4966
Card Payment
All card payment claims will have the cashback amount credited to their card.
We will create a new Queue called the Card Queue. This queue will work the same
as the other batch queue in that when an invoice is marked as paid, this will generate
one item in the queue for the total amount to be paid.
A special process here is to assign cards to Members. IF there are 10 claims in the
invoice that has been paid, and 5 of those people ALREADY have cards, then they
will exist in the Members table (as defined by email address)
The other 5 do NOT have cards. In this case, we first assign the next 5 cards from
the card inventory to those members and create 5 new records in the Members table
for them with the flag CardSent=’No’.
Use the EFT queue as a template.
When clicking on a batch number we will see the same information, plus the card
number and the CardSent flag.
On approve of the batch, a dialogue box will popup asking for a location to save the
csv file (called cashback_batch[batchnumber].csv
The format of the CSV file is:
Card Number, Amount To Be Credited, Client, Promotion
The batch is then marked as PAID and it is up to the user to transfer the CSV file and
continue the process.
Card Fulfilment
On payment of the invoice, we also trigger the fulfilment process.
In this case the cards to be sent out are those that are in the Members table that
have CardSent=No (And are for this promo and have had the invoice paid).
Yuranga
58 Auburn St
Wollongong 2500
extending your horizons…
5
(p) 1300 78 58 07
(f) 1300 78 58 09
(e) [email protected]
(w) www.yuranga.com
Project Specifications
Claimit 3.3 – Cards
In this case, we generate the fulfilment letter in order of card number and the staff in
the warehouse will get the next card from the pile and put it in an envelope with the
next letter.
Yuranga
58 Auburn St
Wollongong 2500
extending your horizons…
6
(p) 1300 78 58 07
(f) 1300 78 58 09
(e) [email protected]
(w) www.yuranga.com