Registration example with rhai flow #2
Labels
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: herocode/rhailib#2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Registration with rhai flowto Registration example with rhai flow