PayMobile VoMS solution - EServGlobal · 2019-07-25 · Service: Mobile to Mobile or Voucher on...

PayMobile VoMS solution

| 2

Agenda

| 3

n  Capability to recharge his prepaid account

n  Always find a suitable way to perform a recharge thanks to:

–  A comprehensive set of types of vouchers

–  A comprehensive set of access channels

n  Access multiple recharge options with one voucher

Services for the prepaid subscriber

| 4

n  Capability to generate and store vouchers n  Capability to adress finely tuned subscribers segments with dedicated recharge options

n  Capability to manage prepaid subscribers life cycle and notification in place of the IN

n  Capability to control fraud

Services for the operator

| 5

A proven experience

As a provider of recharge sercices in more than 35 coutries, eServGlobal has a comprehensive understanding of the voucher management market

A flexible segmentation toolbox

PayMobile provides a flexiole service creation environment to mediate various criteria from different sources through recharge scenarios. As they are way to

segment the subscribers base, it enables in real-time to let the subscriber choose an appropriate recharge

Fast, secure voucher generation in real time

PayMobile uses a flexible and uncreakable world-call 8-22 digits voucher PIN encryption to preserve revenue and decrease exposure to frraud and loss

Key success factors

| 6

Easy, straight forward administration

Web-based front-end application to reduce overhead, iprove recordkeeping and speed-up deployments

Multiple recharge channels

It provides customer convenience and satisdfaction

Multiple balance recharge

It sticks to customer’s prepaid credit usage (MS, airtime, bonus airtime etc…)

Scalable

Allows romm for future growth. The eServGlobal VoMS can be deplyoed in several configurations to adress small, mediemu and large telecommunication operator’s

prepaid subscribers bases

Key success factors

| 7

Comprehensive customer care eServglobal provides full web-based customer care service or a customer care API. The PayMobile SOAP API offers all the customer care services.

Key success factors

| 8

Agenda

| 9

Types of vouchers

Vouchers properties

Vouchers life cycle

Vouchers generation and management

| 10

Type of vouchers

| 11

Physical voucher

Denomination, SNE, HRN and expiry date are printed on a plastic voucher

Electronic voucher – logistic cost reduction

Dematerialized voucher with a predefined denomination; can be sent per SMS or printed on a receipt

VoMS generates the vouchers which will be uploaded into the PayMobile electronic recharge for its distribution

VOD (Voucher On Demand) – capture small amounts

PayMobile generates « on the fly » a voucher with the requested denomination

Subscriber uses its HRN as a standard voucher to recharge it

Type of vouchers

| 12

Multi-HRN

Voucher contains several HRNs

Capability to define several behaviours

n  Prepaid subscriber use one of the HRN, this disables the others (lottery use case)

n  Prepaid subscriber uses one of the HRN, the others can be used by this prepaid subscriber only

n  Prepaid subscriber uses one of the HRN, he can either use the others, either give the others to other prepaid subscribers

Not applicable for VODs

Type of vouchers

| 13

Vouchers parameters

| 14

HRN (Hidden Recharge number)

Secret code used by the subscriber to recharge the voucher

SNE (Serial Number External)

Unique public voucher identifier

Expiry date

Upon expiry, the voucher can’t be used

Recharge category

A unique identifier refering to a set of parameters which defines the voucher inside PayMobile

n  The voucher properties

n  One or several linked recharge scenarios

Voucher parameters | Global parameters

| 15

Voucher denomination value and currency

Serial number min/max in which the SNEs will be taken during the voucher creation to avoid dupplicates

Multi HRN yes/no

Multi HRN behaviour

number of HRNs in the voucher

State

Scenario(s) (see dedicated chapter)

Sets the recharge content

Default scenario

Vouchers parameters | Recharge category parameters for physical or electronic vouchers

| 16

Vouchers parameters | Recharge category parameters for physical or electronic vouchers

| 17

Voucher denomination currency

Serial number min/max in which the SNEs will be taken during the voucher creation to avoid dupplicates

Recharged product

Service: Mobile to Mobile or Voucher on Demand

Type of billing: Postpaid, prepaid or all

State

Scenario(s) (see dedicated chapter)

Takes into account the quantity or amount entered by the subscriber to defined the recharge content

Vouchers parameters | Recharge category for VOD creation or M2M

| 18

Vouchers parameters | Recharge category for VOD creation or M2M

| 19

Vouchers life cycle

| 20

n  Active: recharge is possible n  Pending: Voucher is currently used for a recharge. Used to avoid fraudulent double recharge

n  Used: Recharge is successful

n  Expired

n  Locked: For security reason, the operator can lock vouchers (in case of loss for example)

Vouchers life cycle

| 21

Vouchers provisioning

| 22

Voucher provisioning | Overview

Inside PayMobile Outside PayMobile

1- Operator orders several packages of vouchers 2- PayMobile generates encrypted files containing the vouchers details

3- Printer shop decrypts the files and prints the vouchers

4- Operator links the generated vouchers to the distributors

5- Operator delivers the vouchers to the distributors

6- Operator activates the vouchers

7- vouchers can be sold

| 23

operator enters

The number of packages

The number of vouchers per packages

The recharge category which defines the vouchers properties

PayMobile reserves the SNEs and PayMobile generates a unique reference ID for each ordered package

Voucher provisioning | Order vouchers

| 24

Voucher provisioning | Order vouchers

| 25

Log file

Voucher provisioning | Order vouchers

| 26

operator selects

Enters the package(s) to be printed

Defines the vouchers expiry date

Selects the printer shop

PayMobile associates a HRN and an expiry date to the already provisioned SNEs and generates an encrypted printing flat file inside the

PayMobile system

Voucher provisioning | Generate printing files

| 27

Voucher provisioning | Generate printing files

| 28

Log file

Voucher provisioning | Generate printing files

| 29

n  Using PayMobile, the printer shop retrieves the encrypted vouchers printing file –  The printer shop prints the file

Voucher provisioning | Print the vouchers

| 30

Voucher provisioning | Print the vouchers

| 31

Encrypted vouchers printing file

Voucher provisioning | Print the vouchers

| 32

The operator logistics department delivers the vouchers to the distributors

Using PayMobile, the operator can link a set of SNEs or a set of packages to the relevant distributor

Voucher provisioning | Distribute the vouchers

| 33

Voucher provisioning | Distribute the vouchers

| 34

n  The operator activates a set of SNEs or a set of packages n  The vouchers can be sold

Voucher provisioning | Activate the vouchers

| 35

Voucher provisioning | Activate the vouchers

| 36

Electronic vouchers

Same process

The operator downloads the vouchers printing file and loads it in the PayMobile electronic recharge

VOD

Pre-provisioning: One or several ranges of SNEs are booked for VOD.

Provisioning on the fly (SMS, USSD, SOAP API, no web)

Voucher provisioning | Electronic vouchers & VOD use cases

| 37

Agenda

| 38

n  Workflow n  Recharge scenario

n  Recharge content

n  Subscriber life cycle management

n  Submit recharge to the IN

n  Notify the prepaid subscriber

Recharge

| 39

Workflow

| 40

n  A prepaid subscriber initiates a recharge with his HRN n  PayMobile filters the applicable(s) scenarios for the recharge

n  The subscriber selects one option

n  PayMobile computes the recharge content and the prepaid subscriber’s life cycle dates

n  PayMobile submits the recharge to the IN

n  PayMobile notifies the prepaid subscriber

Workflow

| 41

Recharge scenario

| 42

n  One or several scenarios are associated to one recharge category n  PayMobile filters parameters sets inside each scenario to select the applicable recharge options

n  Scenario defines

–  Recharge content

–  Life cycle calculation

–  Additional parameters to be communicated to the IN

Recharge scenario | Overview

Provide different recharge behaviors for one voucher, for example different combinations of products (1 hour airtime, 100 SMS) for the a fixed denomination (10 €)

| 43

PayMobile filters a set of parameters which are provided by the IN Subscriber’s provider ID

Access channel used by subscriber

Subscriber type

Subscriber state Feature available only if the IN and the IN connector manage these parameters

Recharge scenario | Filter parameters for the physical and electronic vouchers

| 44

n  Used access channel to submit the recharge request

n  First recharge executed by the subscriber*

n  Service: RECHARGE, M2M, VOD CREATION

n  The associated recharge category

n  HRN rank in case of muliple HRN

–  Example: the second HRN in a list of four.

Recharge scenario | Scenario parameters

| 45

n  Billing type*

n  Subscriber provider ID*

n  Subscriber state*

n  Default scenario

–  For recharge category with multiple scenarios, it is the applicable scenario in case the access channel used by the prepaid susbcriber can’t expose several

scenarios such as SMS or Standard USSD

Recharge scenario | Scenario parameters

| 46

Recharge content

| 47

Scenario defines the recharge content

Products have to exist in the IN

Capability to set one or several products

Example: with one voucher, the subscriber can recharge 1 hour airtime and 100 SMS

Quantity

Voucher defines the quantity

In case of VOD creation, the quantity is the number entered by the requeste

Recharge content

| 48

Life cycle management

| 49

n  Scenario defines the validity and Grace calculation and parameters

n  PayMobile calculates the activity and the Grace end dates

n  Requires to record every subscribers’ life cycles

n  Master and slave balances

–  Master balance has a life cycle

–  Slave balances follow the master balance life cycle

n  Life cycle is communicated to the IN

n  Idelit, cus vellibusa sectam et ventiat iistrumquas molor molupta tatiorem faccus.

Life cycle management | Overview

| 50

Non-initialized Subscriber didn’t permi any successful recharge. His balance hasn’t been initialized.

Active Balance(s) is/are available for consumption

Inactive Restricted use of the balance(s). Recharge is still possible

Deactivated Subscriber didn’t rechagre during the Grace period. He can’t access his balance(s). The account will be deleted.

Life cycle management | Life cycle presentation

| 51

Cumulative

n  The voucher duration is added to the current duration

Cumulative with threshold

n  Same method with a maximum duration threshold

Standard

n  The highest of the current or the voucher duration applies

Fixed

n  Sets a predefined expiry date

Unchange

n  The current date doesn’t change

Life cycle management | Dates calculation modes

| 52

Submit recharge to the IN

| 53

PayMobile communicates the recharge content, the life cycle dates and additional parameters required by the IN to process the recharge

IN processing

OK. PayMobile sets the voucher status to « Used »

NOK. PayMobile rollbacks the life-cyce, voucher status is reverted to « Active »

No answer. Voucher status stays at « Pending ». This requires a manual reconciliation by the customercare

Submit recharge to the IN | Overview

| 54

n  Set of predefined parameters which are required by the IN to process the submited recharge request

n  The parameters are

–  Card Type

–  Validity Rule

–  Payment Mode

–  Provider Identifier Voucher

–  Voucher Type

–  Tariff plan

Submit the recharge to the IN | Communicated parameters

| 55

Submit the recharge to the IN | Communicated parameters

| 56

Notification

| 57

n  PayMobile can notify the successful recharge via SMS

n  Multiple language. PayMobile strores the subscriber’s language selection which is used for the notification

n  Notification can include

–  Quantity and name of each products

–  Activity and Grace date

–  Activity and Grace duration

–  Subscriber’s updated balance(s) if the IN communicates it

–  Operation ID

Notification

| 58

Agenda

| 59

n  Using his handset, a prepaid subscriber subscribes to the M2M service n  A prepaid subscriber debits its prepaid account and credits another prepaid subscriber’s account.

M2M | Overview

| 60

M2M protected with specific pincode

Upon subscription, a specific pincode is sent to the subscriber

Using his handset, subscriber can cange his password

Pincode needs to be entered each time the susbcriber uses the M2M service

Activated or not in the general settings

Minimum quantity/validity left

Setting in the general settings per product

PayMobile blocks the transfer is the configured minimum value Ensure a minimum credit or validity is left after the transfer completion for the sender

M2M | Parameters

| 61

M2M transfer min/max amount

Settings in the general settings per product

PayMobile blocks the transfer if the min or the max threshold is overpassed

M2M | Parameters

| 62

Capability to set one or several fees per transfered product

Per product the parameters are

Fee is added or included in the amount

n  In case fee is added, sender is prepaid or postpaid

Fee calculation order (in case of several fees apply)

Fee calculation mode

n  Fee apply on the entered amount (exclude fees if previous fees are added to the amount)

n  Fee apply on the last calculated debited amount (the fee calculation is based on the entered amount and the previous fees)

M2M | Fees computation

| 63

Rounding policy

Round: if precision is 0 digit, [0,0 - 0,4] => 0, [0,5 - 0,9] =>1

Ceiling: if precision is 0 digit, 0,0 =>0, [0,1 - 0,9] =>1

Floor: if precision is 0 digit, [0,0 - 0,9] =>0

M2M | Fees computation

| 64

Agenda

| 65

n  Suspends subscriber’s capability to recharge

n  Suspends subscriber’s capability to perform a M2M

n  Vouchers printing file encryption

n  Block a voucher

n  Rights and credentials for all the users

n  Oversight

Fraud management | Agenda

| 66

PayMobile suspends automatically the subscriber’s capability to recharge based an the number of incorrect recharge requests (for example

wrong HRN):

Max number of consecutive errors in the same call

Max number of errors during the day

Max number of errors during the month

PayMobile GUI

The customer care can suspend the subscriber’s capability to recharge (+ record a reason)

The customer care can unsuspend a subscriber from an automated or manual susension

Fraud management | Suspend subscriber’s capability to recharge

| 67

Automatically suspend the subscriber’s capability to use the M2M service based an the number of incorrect pincode:

Max number of errors during the day

Max number of errors during the month

Max number of errors during the customized recurrent period defined by a starting date and duration in days

Customer care can reactivate the capability to transfer

Capability for the customer care to lock/unlock the subscriber’s capability to use the M2M service.

Customer care can’t block capability to receive M2M transfer

Fraud management | M2M

| 68

Proprietary encryption algorithm: CB10

Operator defines an encryption key for each printer shop

Key is manually set

Automatically generated

Imported from a file

Fraud management | Voucher printing file encryption

| 69

Fraud management | Voucher printing file encryption

| 70

In case of loss for example

Customer care has the capability to block one voucher

Administrator has the capability to block

One or a set of vouchers

One or a set of packages of vouchers

Both can record a reason

Fraud management | Block a voucher

| 71

Fraud management | Block a voucher

| 72

n  Credential for every actor using the PayMobile system

n  Store KYC information for each actor

n  Select predefined operation rights for each actor

n  Strong password policy

–  Capability to force change password after first login

–  at least one of the following special character(s): -_@%$,!#&:;/

–  at least one alphanumeric character

–  at least one upper case letter

Fraud management | Rights and credentials for all the users

| 73

Fraud management | Rights and credentials for all the users

| 74

Fraud management | Rights and credentials for all the users

| 75

n  All the operations are recorded in an audit trail

n  Every transactions is recorded with a unique transaction ID

n  Capability to search for operations based on

–  Type of activity

–  Voucher management

–  User management

–  Administration

–  All

–  Used access channel

Fraud management | Oversight

| 76

n  Service

–  Customer care

–  Administration

–  Voman

–  Recharge

n  Operation

n  Date & time period

n  Actor’s username

n  Actor’s ID

Fraud management | Oversight

| 77

Fraud management | Oversight

| 78

Agenda

| 79

n  PayMobile records the subscriber’s information each time he initiates a recharge for the following purposes

n  Life cycle management

–  Stores the validity and grace dates to calcualte their new values after the recharge

n  Fraud management

–  Stores the fraud counters to enable the automated service suspension

n  Notification language

–  PayMobile uses the subscriber’s prefered language

n  Recharge scenario(s) selection

–  Potentially used as a parameter to select a scenario

Susbcriber management

| 80

Agenda

| 81

n  Customer care n  In-line reports

n  Off-line reports

n  Reconciliation

Back office features

| 82

Customer care

| 83

n  Retrieve the HRN from the SNE

Customer care | HRN from SNE

| 84

n  View vouchers details

n  Search criteria

–  MSISDN

–  Denomination value

–  State

–  SNE or package range

–  Distributor

n  Capability to change the voucher state + record reason

Customer care | Vouchers details

| 85

Customer care | Vouchers details

| 86

Customer care | Vouchers details

| 87

n  View subscribers details

n  Search criteria: MSISDN

n  Block/unblock subscribers

n  Block/unblock M2M service

n  Generate a M2M pincode

n  Reset the M2M fraud counter

Customer care | Subscribers details

| 88

Subscribers management | Subscribers details

| 89

Subscribers management | Subscribers details

| 90

Recharge a subscriber

Using the HRN

Using the SNE (1st step, retrieve the HRN form the SNE)

Customer care | Recharge a subscriber

| 91

Customer care | Recharge a subscriber

| 92

n  Transactions view

n  Filter to seach transaction

–  Requester ID

–  Transaction state

–  Recharge ou M2M ou 3rd party recharge

–  Transaction ID

–  Requester username

–  Recharged MSISDN

Customer care | Transactions

| 93

Customer care | Transactions

| 94

Customer care | Transactions

| 95

In-line reports

| 96

n  Number of recorded subscribers n  Filter criteria

–  Period

–  Subscriber’s profile

–  Source

–  Scope

–  BE source

In-line reports | Subscribers

| 97

In-line reports | Subscribers

| 98

n  In-line report of the number of provisioned vouchers n  Filter criteria

In-line reports | Vouchers

| 99

In-line reports | Vouchers

| 100

n  In-line report of the number of HRN recharges attempts for

–  Successful recharges

–  Recharges by new subscribers

–  Cause of failed recharges

n  Filter criteria

–  Period

–  Source

In-line reports | Recharges

| 101

In-line reports | Recharges

| 102

In-line report of the number of transaction attempts n  Successful

n  Recharges by new subscribers

n  Cause of failure

Filter criteria n  Period

n  Source

n  Transaction type

n  Used access channel

In-line reports | All transactions

| 103

In-line reports | All transactions

| 104

Divider subtitle Off-line reports

| 105

Flat files produced daily by PayMobile

Subscribers reports

Reports on the modified lifecycle of subscribers

Vouchers reports

Modified state of vouchers

CC reports

Customer care recharging activity details and vouchers production, activation, and deletion

Customer fraud reports

Subscribers that have tried to recharge with incorrect voucher PINs and have been suspended,

Off-line reports

| 106

Clearing file

n  Transactions that have been created through the online connector to the IN

n  One file per connector, thus per IN

Off-line reports

| 107

Recnciliation

| 108

n  Administrator can change some vouchers properties after their generations

n  Properties are

–  Voucher expiration date

–  Associated echarge category

n  Filter the vouchers based on

–  A set of vouchers (SNEs) or a set of packages

–  Recharge category

–  Range of expiration date (begin/end dates)

–  Vouchers’ state

n  Capability to record a reason

Reconciliation | Vouchers properties modification

| 109

Reconciliation | Vouchers properties modification

| 110

THANK YOU