Payment and verification DSL implementations #3

New Issue

timur · 2025-07-08T19:09:42Z

timur commented

2025-07-08 19:09:42 +00:00

We need rhai wrappers around certain stripe and idenfy API functionality to be able to dispatch scripts that create payment intents and verification requests, per #1.

For instance, the circle worker needs to be able to assign a flow id metadata when creating the payment intent or verification api request. Also, the circle worker, after kyc verification step, will be asked to move to next flow step, which is creation of payment intent. Basically to use these APIs in the circle architecture they must be executable over rhai scripts.

We need rhai wrappers around certain stripe and idenfy API functionality to be able to dispatch scripts that create payment intents and verification requests, per #1. For instance, the circle worker needs to be able to assign a flow id metadata when creating the payment intent or verification api request. Also, the circle worker, after kyc verification step, will be asked to move to next flow step, which is creation of payment intent. Basically to use these APIs in the circle architecture they must be executable over rhai scripts.

timur referenced this issue

2025-07-08 19:13:23 +00:00

Registration example with rhai flow #2

timur self-assigned this 2025-07-08 19:34:49 +00:00

timur added this to the Zanzibar Digital Freezone project 2025-07-08 19:34:55 +00:00

Sign in to join this conversation.

No Label

No Milestone

No project

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#3