<YunoPaymentMethods> component, and YunoSdk.startPayment() paid with the method the shopper picked. In the unified API the list is a view you request from the transaction with getPaymentMethodsViews and render with <YunoView>. The shopper’s pick arrives in onPaymentSelected, and you pass it to transaction.start().
Before you start
- Upgrade
@yuno-payments/yuno-sdk-react-nativeto 2.0.0 and runpod install. Your public API key and the checkout sessions your backend creates do not change (Before you begin). - On Android,
minSdkVersionis now 23. If yourandroid/build.gradleapplies the Compose compiler plugin to the Yuno module (a 1.x workaround), remove that block: with 2.0.0 the build fails with “The Compose Compiler requires the Compose Runtime to be on the class path”. - Decide who creates the payment. The checkout session’s
workflowmust match that decision:
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
Payment methods list
Controller
Entry points
Related
- Payment Methods List. Types, list controller and express buttons.
- Get Started. Full unified-API walkthrough.
Status. Values and substatus.