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.

We don’t want our users to get confused – use our rich Flash client to define your bonus offers and you will not get lost in a multitude of options our system provides.

2) It is added the possibility of full customization of «User console» for customer’s needs
-  Support of Company’s logotype.
- Support of application’s form  (CSS).
- Support service’ address has been changed.
(See Pointloyalty Manager “Registration page”)
3) the utility for adjustment of application’s form has been developed

4) The detailed description of integration process with “User console” has been added. The given description contains the detailed examples and recommendations on the application’ using.
http://www.pointloyalty.com/member_console.html

To resume — the possibility of full integration of widget “User console” with your sites has been added.

The future plans — to provide with plugins for integration with support systems of e-commerce.

What are personalIds – personal identifiers?
When submitting the data on your members to the system you can pass personal identifier (personalId) field for every member. This field is required for your customers to work with the Member Console (view transactions record, active loyalty programs and offers, etc).
You can choose from 3 options to join customers to your programs:
- By matching personalId.
- By matching personalId and email. PersonalId and email of the user who created account in the Member Console should match with information you have associated with this user.
- By matching personalId and password. (PersonalId and password should match).

In any case the customer must know his/her personalId to be able to work with the Member Console.
In most simple case personalId can coincide with memberId and can be credit card number (for offline retail) or system identifier (for online shops).

Why do we establish such a complex system with two identifiers? We want to support as many options as possible. For example, customer transactions data can be submitted with internal identifiers (memberId) but for creating account in the Member Console a customer will get other, human-readable key.

Our system supports complex identification schemes but you can always use (at least for testing) a simplified option – have same identifier for all usage scenarios.

Typical tasks you have in your shop:
- Calculate bonus points or discount during the purchase.
- Show the amount of bonus points earned by the client once he enters his account.
- Modify the amount of bonus points if you redeem bonuses in your online shop.

The integration process step by step:
1. Register in PointLoyalty Manager, create loyalty programs, offers, etc
2. Call remote method to calculate bonus points during the purchase
http://www.pointloyalty.com/web20_details.html#actions (POST method)
Pay attention:
- If you want to use calculated amount as a discount – change shopping cart total price accordingly.
- If you want to demonstrate earned bonus points before actual payment take place (f.e. when a client puts an item to the shopping cart) – you will need to delete bonus points if client abandon the purchase. Use DELETE method in this case.
3. After client authentication – show the amount of accumulated bonus points. (If you only use discount – you will need this step)
http://www.pointloyalty.com/web20_details.html#members (GET method)
4. When registering a new client you will need to add her/him to bonus processing system
http://www.pointloyalty.com/web20_details.html#members (POST method)
Pay attention:
- You need to do this step if you want to create loyalty offers based on client attributes
- If you already have a big customer base – you will need to invoke this REST API method for all customers you have.
5. Bonus points redemption
Depending on how you plan to redeem bonus points (gifts, discounts, additional services, …) you will need to decrease amount of points after redemption take place.
- http://www.pointloyalty.com/web20_details.html#bonuses (DELETE method) – to completely clear client bonus points. In this case you will not be able to keep the record of transactions.
- http://www.pointloyalty.com/web20_details.html#adjustments (POST method) – adjust the amount of points on the client account. In this way you could use loyalty offers accounting for client purchase record.
6. If you plan to have loyalty offers based on your product categories (you might give points when purchasing certain product categories, not specific items) – you’ll need to submit this information using PointLoyalty Manager online application.
See also http://www.pointloyalty.com/contacts.html — «Technical links», DTD files.

On all integration issues and question contact our technical support: support@pointloyalty.com.

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.