PUSH NOTIFICATIONS

Push notification is a way of propagating messages to the users' device(s) registered with the bank.

Through push notifications, a user can be notified of any event/transaction that has occurred in the user's account.

The user will need to enable the push notification setting on the device for Futura Bank application for the bank to send push notifications. If the user does not wish to receive notifications through push messages then he can disable notifications through device settings.

The user also has an option to subscribe for alerts with an additional option of ‘push notification’ as the delivery mode for specific transactions in the application. If the user does not wish to receive notifications through push message for specific event(s), then he can disable push notification against that event.

If the user has opted for push notifications, then the system will push a message on the user’s device and it will appear on the device as a banner/ pop-up message.

Pre-Requisites

• The user has installed Futura Bank mobile application on the device and opted for push notifications.
• For the set of subscribed alerts for which the user does not wish to receive the notification through push message, he will need to disable push notifications against those events so that the bank does not push notifications to the user’s device on the occurrence of those events.
• Alert template has been maintained for delivery mode ‘Push Notification’.

Push notifications on the device

A notification is sent on the mobile device, as a banner or a pop-up message, by the application on the occurrence of the event in the system.

1. Launch the Futura Bank mobile application.
2. On launching the application for the first time, the system asks for permission to enable push notifications for Futura Bank.
3. Click Allow if you want the bank to push notifications on your mobile device.
   OR
   Click Don't Allow if you do not want the bank to push notifications on your mobile device.
   

FAQ

Can the same mobile device be enrolled for multiple users for push notifications?

No, the same device cannot be enrolled for multiple users for push notifications. A push token is generated for a user + device combination and if there is already a push token registered for the device and another user re-installs the application then the earlier token is invalidated and overridden.

Is it possible to have privacy/priority settings for push notifications, that is, an option to not display the message content on the lock screen?

Currently, this feature is not supported. The message content will be shown to the user even if the device is locked.

Will an application upgrade/update require re-registration for push notifications?

No, the application upgrade/update will not need re-registration for push notifications. The earlier registration holds good.

Is the delivery of push notification to the end user from the respective OS servers audited in OBDX?

There are logs available in the system about the delivery of the notification to the iOS or Android server. The delivery of the notification to the end customer on the device from the respective servers (iOS and Android) is not available in OBDX.

Does OBDX have in-app messaging enabled to send messages to customers like mandatory app update to latest version?

No, in-app messaging capability for mandatory app updates is not supported.

How many maximum number of devices can be registered to get push notifications for a particular user?

There is no restriction on the maximum number of devices that can be registered for push notifications.

If a customer/admin de-registers a device for push notifications from the front end, how can it be re-enabled to get push notifications back again?

The user can reinstall the app. On reinstalling, the user will be asked to enable push notifications for that device and once the user logs in, a push token can be associated with the user.