Skin

Skin allows for you to customize look and feel of your mobile application depending on the specific events. Skin is json format data including logo image, background color, text color and many more, which to set look and feel of your mobile application. As a default, you can configure your default skin in the CloudPayments portal. If you want to change default look and feel of your mobile application due to Christmas, Summer theme, or certain promotion etc., you can do it without modifying and release of new mobile application. In addition to default skin, you can add multiple customized skin data based on your marketing purpose; for example, unique brand specific look and feel. You can set skin data along with even trigger information. When event triggered, you can update look and feel of your mobile application.
Skin is configured in CloudPayments portal and you can obtain this data by using CloudPayments Service API. For the default skin, when the End User launch your application, you can retrieve all available skin data and update default look and feel of your mobile application.

Type of Skins

Default
Default look and feel. For any case to fail to retrieve this data, your mobile application should have certain default setting inside.
Geofencing
Geofencing is commonly used for notifications and alerts for when a user enters or leaves a designated area, such as tracking location via GPS for a specific area. A geofence is just a user-defined virtual perimeter for a geographic area. It is a location-based service, providing the customized look and feel of mobile application on a pre-defined location. Once the user exists the geofence location, the look and feel should be aborted and returned to the default setting.
You can obtain geofencing information to be monitored from the CloudPayments Service API and monitor user location to apply or remove the geofencing skin.
Beacon
Beacons transmits very small amounts of data according to a specific standard using very little power. This data includes information that helps identify each Beacon. When an End User enters a proximity of a Beacon transmits, your mobile application can identify a specific Beacon and change its skin accordingly.
Skin data can be configured in the CloudPayments portal along with Beacon Identifier. You can obtain Beacon information to be monitored from the Fintive Service API and monitor user location to apply or remove the beacon skin.

Get skin events

The consumer application retrieves the default skin and event triggered skin data set by the administrator. You can call this API during splash screen presented so you can apply default skin immediately before user enters into the homescreen of your mobile application. Event triggered skin has its type of events and events detail for you to monitor. It is recommend to call this API at every launch and resume. Skin change is not notified as a push so you should have the logic to determine if the skin data is changed. Each skin has last update timestamp so that you can compare the value with stored value in your cache. If timestamp is changed or if new skin is detected, you can retrieve only the updated skin json data.

API

The main APIs used in the use case are the following:

getMySkinService()

Retrieve and apply skin

The consumer application may retrieve json format skin data right after retrieval of skin event or when event is occurred, whichever works with your use case. However, the former is recommended. If you retrieved and cached skin data in advance, you can immediately change look and feel of your application when the event is occurred.

API

The main APIs used in the use case are the following:

getSkin()