| Contact us : |  |
| Contact us : | |
Cards come in many varieties. It is important to identify the type of application our customer is interested to launch. Depending on the application selected, different system requirements will need to be addressed.
Cards can store anywhere from a single value that cannot be changed up to 32K of dynamic data. It is important to match the storage requirements with the correct card. It also often makes sense to allocate space for future scalability.
Card-accepting devices can vary from readers attached to PCs, to specially designed terminals, or even to small value checking readers. Readers attached to PCs tend to be less expensive, while stand-alone kiosk terminals are at the other end of the price range.
Fulfillment is the process of printing, encoding and issuing cards. Card personalization can be done at the factory or at customer site. There are many options for print quality, signature panel, holograms, card thickness, etc.
The number of cards will influence card pricing, printing options and other system components. A pilot is a great way to test an application before rolling it. Wipaq can build a prototype that can help customer evaluate an idea and explore various options.
Systems integration is a complex component of a card solution. To avoid complications, it is important to select an integrator who understands these issues.
Scalability should be built into the system design. Thorough and concise requirements gathering help guard against early obsolescence. We call this "future-proofing" the application.
If there are practical card issues that require special consideration, it would be helpful to address them here.
Informative reports are valuable for measuring effectiveness, auditing transactions and marketing to new customers. In most cases, the transaction data is as valuable as the card system itself.
Settlement is the process of updating backend data with terminal data and then adjusting account balances accordingly.
There are many related support services crucial to the success of the overall application. Wipaq provides the total solution support or just specific areas as required.
There are important differences between starting a card project from scratch and picking up on one that is well along. Knowing where the customer stands will enable us to respond to customer needs more efficiently.
A guide to designing your card solution
The Wipaq Application Guide is an exclusive service to current and prospective clients. By following along the questions outlined below, we can easily step through the issues that surround the development of card-based applications. We find this guide an excellent tool for helping end-users understand the process of designing card applications. At the same time, it gives us a better idea of what the customer is trying to accomplish.
Get answers for as many questions as possible. If customer is not sure about an answer, just skip it. If you are unsure of a question, please do contact Smart Card Solutions Division. There's only one thing that counts, and that's whether our solution meets customer needs.
We call it…Making an Application Smart
1. Customer’s Anticipated Application
Please identify the type of card application the customer have in mind: (check all that apply)
|
Accreditation |
|
Benefits |
|
Cash Replacement |
|
ECoupon |
|
Gift Card |
|
Healthcare |
|
Inventory |
|
License |
|
Loyalty Points |
|
Membership ID |
|
Network Security |
|
Physical Access |
|
Season Pass |
|
Time & Attendance |
|
Tradeshow |
|
Transportatio |
|
Vending |
|
Other |
2. Quantity of Data
How much data do the customer want to store on the card?
3. Kinds of Cards
What type of cards do the customer plan to use?
4. Card-Accepting Devices
How will the cards be read?
5. Fulfillment
Which of the following fulfillment services will this application require?
|
In house |
|
Outside |
|
|
Badging |
|
Printing |
|
|
Personalization |
|
Mailing |
|
|
Not sure yet |
|
|
|
6. Quantity Required.
How many cards does the customer application require in a year?
7. Integration
What is the integration scenario for this card?
8. Scalability
How scalable do the application to be?
|
New systems may be deployed |
|
More cards may be required |
|
|
Fielded cards must accept new applications |
|
A transition plan has been developed |
|
|
Not sure yet |
|
|
|
9. Other Issues
What other concerns does the customer anticipate?
|
Procedures governing lost cards |
|
Maintaining overall system security |
|
|
Establishing expiration dates |
|
Allocating various tiers of cards |
|
|
Maximum value for cards |
|
Administrator/Manager functions |
|
|
Printed receipts |
|
|
|
|
Other |
|
||
10. Data Management
What type of data reporting is required?
11. Settlement and Adjustment
What is the anticipated frequency of data settlement/reconciliation?
12. System Support
What application support do the customer require?
|
Deployment |
|
Installation |
|
|
Card Manufacturing |
|
Fulfillment |
|
|
Registration |
|
Help desk |
|
|
Training |
|
Maintenance contract |
|
|
Application Documentation |
|
Other |
|
13. Project Status
Please tell us where are does the customer stand in his decision process:
14. Potential products or vendors
Please enter specific vendors of program components the customer is considering or require:
|
Cards |
|
Readers |
|
POS |
|
Vending |
|
Software |
|
Integration services |
|
Card printing service or equipment |
|
Transaction clearing |
|
Other support |
15. Other
Please tell us anything else about the customer requirements that will enable us to respond to the inquiry more fully. For example, if customer has more description of their application, please include it here.
16. Please tell us how to reach you.
Contact Us for Abu Dhabi, Dubai, Ajman, Sharjah, UAE, Middle East and Africa
{literal}
{/literal}