Registration example with rhai flow #2

Open
opened 2025-07-08 18:49:34 +00:00 by timur · 0 comments
Owner

Currently registration for the digital free zone is implemented using a regular backend server to API flow. The kyc and payment calls are made from the backend, sessions are tracked for each, and when certain conditions are met view is updated to reflect and allow proceeding in the registration form.

We want to switch to using our architecture around circles, which requires the implementation of functionality around creating and proceeding in flows. This flow management should be push based and non-blocking / spawning, able to accommodate a single worker multiplexing multiple flows. This will also allow us to better observe and administer registration flows.

For this we first need a full simulation of how the registration would work with rhai scripts and using the stripe and idenfy API's. So #2 and #3 are necessary.

Currently registration for the digital free zone is implemented using a regular backend server to API flow. The kyc and payment calls are made from the backend, sessions are tracked for each, and when certain conditions are met view is updated to reflect and allow proceeding in the registration form. We want to switch to using our architecture around circles, which requires the implementation of functionality around creating and proceeding in flows. This flow management should be push based and non-blocking / spawning, able to accommodate a single worker multiplexing multiple flows. This will also allow us to better observe and administer registration flows. For this we first need a full simulation of how the registration would work with rhai scripts and using the stripe and idenfy API's. So #2 and #3 are necessary.
timur changed title from Registration with rhai flow to Registration example with rhai flow 2025-07-08 19:10:04 +00:00
timur self-assigned this 2025-07-08 19:33:37 +00:00
timur added this to the Zanzibar Digital Freezone project 2025-07-08 19:33:42 +00:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: herocode/rhailib#2
No description provided.