Skip to main content
Render mode let you embed the SDK’s payment form inside your own layout: you got a YunoPaymentRenderFlowProtocol from Yuno.startPaymentRenderFlow(...), asked it for a formView to place wherever you wanted, and called submitForm() from your own button when the user was ready to pay. In the unified API the same pattern is expressed by overriding showView. The SDK still provides the form view; you receive it together with a TransactionProcess control object that exposes onSubmit().

Before you start

  • Replace import YunoSDK with import SdkPayments. Your public API key and the checkout sessions your backend creates do not change (Before you begin).
  • Decide who creates the payment. The checkout session’s workflow must match that decision:
A default-workflow session with no createPayment override ends in INTERNAL_ERROR: the backend rejects the SDK’s payment creation. See createPayment.

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