Hey everyone,
We’re finalizing the architecture for a self-custodial Visa payment platform on Nervos and would appreciate some architectural clarity.
The intended payment flow is:
-
User taps their Visa card.
-
Their Nervos wallet prompts them to approve the payment.
-
Once they approve, we need to settle the corresponding CKB immediately so the Visa authorization can complete with minimal delay.
Our goal is to keep users in full control of their CKB until the moment they approve the payment, without requiring a pre-funded custodial balance.
I’m trying to determine the recommended CKB implementation pattern for this.
Specifically:
-
What is the recommended way to achieve strong settlement assurance for this type of payment flow?
-
Is broadcasting a signed transaction and acting once it has been accepted by the network considered a reasonable approach, or is waiting for block confirmation the only safe option?
-
Given CKB’s transaction replacement (RBF) behavior, is there a recommended pattern that avoids settlement risk without requiring users to keep funds permanently locked in a separate payment pool?
-
Would you recommend using Omnilock 2-of-2 cells, CoBuild, another lock-script pattern, or something else entirely for this use case?
I’d appreciate any guidance or examples of existing patterns that would fit this type of real-time payment application.