YunoEnrollmentRenderFlowProtocol, asked it for a formView, and called submitForm() from your own button. It also exposed needSubmit: Bool to tell you whether the form required a submit button at all.
In the unified API the same pattern is expressed by overriding showView: the SDK delivers the form view together with a TransactionProcess you call onSubmit() on.
Before you start
- Replace
import YunoSDKwithimport SdkPayments. Your public API key and the customer sessions your backend creates do not change (Before you begin). - There is no payment to create:
createPaymentis not invoked during enrollment, so overriding it has no effect.
Side-by-side
What changes
Grouped in the order you edit the code. Renamed: same role, new name. Moved: same value, new owner. Removed: nothing to call. New: no legacy counterpart. The last column is the only thing you have to do beyond the rename.Initialization and config
Controller
Views
Entry points
Related
- Enrollment feature. Unified-API enrollment walkthrough.
- Lite enrollment. SDK-driven, no view embedding.
- Headless enrollment. Collect data in your own UI.
showView. The controller you override here.