Registration as a Service

Registration as a Service (RaaS) provides customer identity and account management features native to Synerise without any need for third party systems. To use RaaS, implement a set of methods listed below in your application.

Additionally, in the Synerise platform (app.synerise.com) you can define the following settings:

• Registration mode
• Assignment of loyalty card
• JWT longevity
• Custom ID overwriting
• External ID overwriting
• Enabling email address change through a link in the email
• Templates of email notifications such as account confirmation, email change request, PIN confirmation, and so on.
• Password policy

Registration methods

Register new customers

This method lets you pass all customer information along with any agreements and attributes at once.

The primary unique identifier used by Synerise is the email address. However, you may also define a customId as a unique identifier. You can read more here.

Depending on backend configuration at Synerise, the registration may or may not require email confirmations/ The following registration behaviors are supported:

Request customer account by email

This method requests sending an email with a URL that confirms the registration and activates the account.

Confirm customer account

This method confirms a customer account with the confirmation token.

Request customer account by pin

This method requests sending an email to a customer with the PIN code needed during account registration process.

Confirm customer account activation by pin

This method requires a customer to enter a PIN code during account registration process sent through an email.

Authentication methods

Once a customer is registered, you can let users log in by implementing this method. After a successful log-in, the application receives a JWT token which is valid for 1 hour (default setting). The SDK refreshes that token while a customer is using the application and events are being sent (auto-refresh occurs only when the token is still valid).

Other methods

Check if a customer is signed in

This method checks if a customer is signed in through oAuth, Facebook, Sign in with Apple, or RaaS.

Customer sign out

This method signs out the customer. The method terminates the JWT token and ends the customer session.

What’s next

When the customer’s account is registered and/or they are signed in, you can implement profile management methods and session management methods.