Skip to main content
Full mode rendered the SDK’s payment method list inside your layout, fired callbacks when the user picked a method, then handed off to the SDK to render the form and process the payment. In the unified API the same flow uses a single Transaction plus getPaymentMethodsViews(...) for the embedded list, with the controllers split in two: SdkPayments.TransactionController for the transaction lifecycle and SdkPayments.PaymentListController for list-specific events.

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. The last column is the only thing you have to do beyond the rename.

Initialization and config

The SDK result screen is off by default now. Set showStatusScreen: true to keep it.

Controller

Entry points