...
RBI will provide an endpoint and keys to create a user in the RBI Platform.
This endpoint will also ensure the associated user gets created in the RBI Loyalty Platform, with its appropriate linkage to the RBI User.
Homeria must store and associate the returned RBI User ID and RBI Loyalty ID with their Homeria User.
Homeria will make sure that any user created in the current system will be also created in the RBI Platform via the provided endpoint.
| Lucidchart |
|---|
| pageCount | 45 |
|---|
| autoUpdate | falsetrue |
|---|
| align | left |
|---|
| type | rich |
|---|
| autoSize | 1 |
|---|
| macroId | 1af6873699365006-83d38b9a-4fd54740-8892bcf2-e924d3382cd0f45d35c397d0 |
|---|
| instanceId | 920ae5b1-83d6-3e36-b794-1710780f64f3 |
|---|
| pages | 1 |
|---|
| width | 700 |
|---|
| documentToken | v2_36780044c64e30f0813c4367457fe8ee73b3898af2b733e912c3e19c4e3bcbe09f1ba0f9615adb98998dda1deeaac75e1f00c01c698b5afc1de0d2680af2cee6-a=133831322&c=920ae5b1-83d6-3e36-b794-1710780f64f3&d=d7a4e6b03f78436c-3bf8b5c3-486144ff-bd9d840e-47059000a698c468e134dd0a&p=44294475434460904486 |
|---|
| documentId | d7a4e6b03f78436c-3bf8b5c3-486144ff-bd9d840e-47059000a698c468e134dd0a |
|---|
| updated | 17049042050771706259482233 |
|---|
| height | 500 |
|---|
|
| Lucidchart |
|---|
| pageCount | 5 |
|---|
| autoUpdate | true |
|---|
| type | rich |
|---|
| align | left |
|---|
| autoSize | 1 |
|---|
| macroId | 99365006-8b9a-4740-bcf2-f45d35c397d0 |
|---|
| pages | 1 |
|---|
| instanceId | 920ae5b1-83d6-3e36-b794-1710780f64f3 |
|---|
| width | 700 |
|---|
| documentId | 3f78436c-b5c3-44ff-840e-c468e134dd0a |
|---|
| documentToken | v2_9f1ba0f9615adb98998dda1deeaac75e1f00c01c698b5afc1de0d2680af2cee6-a=133831322&c=920ae5b1-83d6-3e36-b794-1710780f64f3&d=3f78436c-b5c3-44ff-840e-c468e134dd0a&p=4460904486 |
|---|
| updated | 1706259482233 |
|---|
| height | 500 |
|---|
|
Homeria will provide a CSV with all the user data from Homeria will provide a CSV with all the user data from their system and all the user loyalty data from SessionM (eg. SessionM ID, Homeria User ID, points, balance, tier, and transactions).
RBI will host these files in a private S3 bucket and create the necessary database records via a script run in a provisioned EC2 instance with the appropriate role.
RBI will not create duplicated users for those already created by the synchronization process.
RBI will update the Loyalty Points balance, tiers, and other Loyalty data for the users already created.
(Optional) I suggest Homeria disables Loyalty Earning, Burning, and Tier and Points expiration while this process takes place.
RBI will provide a CSV back with the correlation between the Homeria User, RBI User ID, and the RBI Loyalty ID to be imported by Homeria.
...
...
...
...
...
...
...
| b3bb-970a10228010 | | pages | 2 |
|---|
| instanceId | 920ae5b1-83d6-3e36-b794-1710780f64f3 |
|---|
|
...
...
...
| documentId | 3f78436c-b5c3-44ff-840e-c468e134dd0a |
|---|
| documentToken | v2_ |
|---|
|
...
| 9f1ba0f9615adb98998dda1deeaac75e1f00c01c698b5afc1de0d2680af2cee6-a=133831322&c=920ae5b1-83d6-3e36-b794-1710780f64f3&d= |
|
...
...
...
...
...
...
...
At this point, both RBI and Homeria should have their user databases in sync, with the correct associations between RBI IDs and Homeria User IDs with no downtime, and (if following the correct order) ensuring we don’t have any lost users while the user import process took place.
...
Flow 1 - The FE client knows who the user is (Web / App):
| Lucidchart |
|---|
| pageCount | 45 |
|---|
| autoUpdate | true |
|---|
| type | rich |
|---|
| align | left | type |
|---|
| rich | autoSize | 1 |
|---|
| macroId | dd3046a96fa09e8c-66cdf622-46ce4578-9c60-a7f4e5c10c2a93b3-83adc15b552d |
|---|
| pages | 3 |
|---|
| instanceId | 920ae5b1-83d6-3e36-b794-1710780f64f3 |
|---|
| pageswidth | 3700 | width | 700
|---|
| documentId | 3f78436c-b5c3-44ff-840e-c468e134dd0a |
|---|
| documentToken | v2_c3e557dbca22342918f987f0c86fb03a514a18dce2d91e29ece0de0fd320f7289f1ba0f9615adb98998dda1deeaac75e1f00c01c698b5afc1de0d2680af2cee6-a=133831322&c=920ae5b1-83d6-3e36-b794-1710780f64f3&d=d7a4e6b03f78436c-3bf8b5c3-486144ff-bd9d840e-47059000a698c468e134dd0a&p=4452646913 |
|---|
| documentId | d7a4e6b0-3bf8-4861-bd9d-47059000a698 |
|---|
| 4460904486 | | updated | 17059148492861706259717415 |
|---|
| height | 500 |
|---|
|
Flow 2 - The FE client doesn’t know who the user is (Kiosks and POSs):
| Lucidchart |
|---|
| pageCount | 45 |
|---|
| autoUpdate | true |
|---|
| type | rich |
|---|
| align | left | type | rich |
|---|
| autoSize | 1 |
|---|
| macroId | e360c7199179a2c5-cf04724c-4bbb4d97-b87e-e151639478e3b4f1-3dab27cf2957 |
|---|
| pages | 4 |
|---|
| instanceId | 920ae5b1-83d6-3e36-b794-1710780f64f3 |
|---|
| pageswidth | 4700 | width | 700
|---|
| documentId | 3f78436c-b5c3-44ff-840e-c468e134dd0a |
|---|
| documentToken | v2_c3e557dbca22342918f987f0c86fb03a514a18dce2d91e29ece0de0fd320f7289f1ba0f9615adb98998dda1deeaac75e1f00c01c698b5afc1de0d2680af2cee6-a=133831322&c=920ae5b1-83d6-3e36-b794-1710780f64f3&d=d7a4e6b03f78436c-3bf8b5c3-486144ff-bd9d840e-47059000a698c468e134dd0a&p=4452646913 |
|---|
| documentId | d7a4e6b0-3bf8-4861-bd9d-47059000a698 |
|---|
| 4460904486 | | updated | 17059148728721706259778615 |
|---|
| height | 500 |
|---|
|
Rollback Plan
Given all transactions are still being reported to SessionM. Homeria and all other existing platforms must have mechanisms in place to switch the source of truth back to SessionM once again.
...