Skip to main content
The unified SDK replaces all previous SDK modes (Full, Lite, Seamless, Render, Headless, and Secure Fields) with a single Transaction class. If you’re currently using any of those modes, pick your platform and legacy mode from the table below. On React Native the guides start from the 1.x API of @yuno-payments/yuno-sdk-react-native and end on 2.0.0.

​
Find your guide

​
What changed

Every legacy mode maps to the same Transaction class. The mode name is gone. What you pass to the config and which controllers you override determines the behavior:
  • Session type (checkoutSession vs customerSession) determines payment vs enrollment.
  • createPayment controller determines whether the SDK creates the payment or your backend does. If you don’t override it, the SDK manages payment creation end-to-end (the Seamless equivalent).
  • showView controller (iOS, Android, React Native) determines whether the SDK presents the form full-screen or hands you the view to embed (the Render equivalent).
  • transactionData on PaymentMethodSelected (iOS, Android, React Native) or data on the paymentMethod you pass to start() (Web) determines whether the SDK shows a form or tokenizes data you’ve already collected (the Headless equivalent).
  • getPaymentMethodsViews replaces all legacy list-mounting and external wallet button APIs (the Full equivalent).
Each guide has the same shape: what to settle before you start, a side-by-side code comparison, and one table of what changes, with what to do about each change.