Skip to main content
This page documents a legacy SDK. Starting a new integration? Use the Yuno SDK. Already on a legacy SDK? Follow the migration guide.The new Yuno SDK (Web v2.x, iOS v3.x, Android v3.x, React Native v2.x) replaces the Full, Lite, Seamless, Render, Headless, and Secure Fields SDKs with one API across every platform. Legacy SDKs remain supported side by side during the transition and are scheduled for deprecation in 2027. Contact your Account Manager for migration planning.
Orientation: Choosing Your Integration Flow, before you begin, please review the Official Integration Flow.
  • Standard Flow (Full Checkout): Recommended for most merchants. Yuno handles the UI, security, and automatic updates for payment methods.
  • Custom Flow (This SDK): Use this only if you require full control over the UX. Note: You will be responsible for manually handling payment statuses, 3DS transitions, and fraud routing data collection.

Deep linking / external browser return

Some payment flows redirect users to an external browser, including 3DS authentication challenges, bank transfer redirects, PIX payments, and other alternative payment methods. Handle their return to your app with the following steps.

1. Set callback_url in checkout session

Include callback_url when creating the checkout session on your backend:
iOS - Info.plist:
Android - AndroidManifest.xml:

4. Continue payment after return

After handling the deep link, continue the payment flow:

Performance

Lazy loading

Initialize the SDK only when the user enters the payment flow to save resources.

Error handling

Listen to the onPaymentStatus event to handle failures gracefully.

Platform-specific configuration

Handle differences between iOS and Android in your React Native app.

Conditional configuration

Platform differences