ValueBean val1 = new ValueBean();
val1.setName(”sum“);
val1.setNumericValue(3800);

ValueBean val2 = new ValueBean();
val2.setName(”product“);
val2.setNumericValue(”printer“);

ActionBean action = new ActionBean();
action.setMemberId(”customer card for John Doe“);
action.setName(”purchase“);
action.setValues(new ValueBean[] { val1, val2 });

return action;

From this example you can see that
- “John Doe” has made a “purchase” of a “product” named “printer” and spend “sum” of $130.

In your information system there is a record of this purchase, so there should be no problem in passing this data to PointLoyalty Manager.
(Encryption, data protection, local installations of the product are out of this blog entry scope)
Full description of the integration mechanism.

Here are the advantages of integration with our product:
- Additional functionality
When you look for your competitors – you can often find that there is much similarity in offered products. Integration with a customer rewards system “PointLoyalty Manger” will help you to stand out against a background and enhance functionality of your product. Integration is simple and does not require much effort from your side.

- Additional profit
You can make this integration module optional and charge additionally for enabling it. You can charge on subscription base, on amount of established reward programs, on amount of processed transactions, etc

- Cutting costs
In essence we propose you to outsource important but non-core part of your system. This way you don’t need to support this part, spend resources on its further development, bugfixing, etc.

On all integration issues http://www.pointloyalty.com/web20.html – please contact technical support of PoinLoyalty company.

We tried to simplify our API to make it easier to learn the system, but we recommend to study the system documentation especially before using it in production.

Example:
Login object has following fields:
- Name – Client name in PointLoyalty Manager.
- Password – Password.
- Locale – Client language string. ‘EN’ by default.
- TimeZoneId – Timezone. String representation as in Java programming language.

Fields «Locale» and «TimeZoneId» are optional and all tests will work without passing them into the system.
But please consider the following:
- If you not an English speaking user and you do not pass «Locale» parameter you will get all
messages from our services in English; date and time fields will be processed according to US
date/time formats, etc.
- If you are not in US/California (where our servers are) – all empty date/time fields by default will
have current US/California time and not time of your time zone as you could expect.

Errors of this kind are easy to avoid by spending a couple of minutes on reading API documentation.

How to organize this system on your site?
1. Your customer enters your site. You request the amount of bonus points he earned from our system (API – http://www.pointloyalty.com/web20_details.html).
2. Assume he has 45 bonus points.
3. On the page designed to choose gifts you display only items from list A. Items from list B remain invisible.
4. If the customer selects some gift – call our API and reduce amount of his points by 10 points. After choosing 4 gifts, items in list A also become invisible.

Why we don’t want to automate this process?
We don’t know following:
- what design you choose for the page with gifts
- what should happen in your system after customer gets a gift
- do you want to display unavailable gifts to your clients?
- etc

This functionality despite looking simple will be individual for every client.
Of course we will help you with integrating our system with your software; we will take into account all your requirements and answer all your questions. We can also implement this task for you on individual base.