Skip to main content
Try our Yuno SDK now
Configure a checkout and see it update live, no account or code required.
Try it now →
Payment methods
PIX
Card
Pay R$150.00
initializestart()onStatus · SUCCEEDED ✓
New Yuno SDK & Deprecation Notice: This documentation covers the new Yuno SDK (Web v2.x, iOS v3.x, Android v3.x). Legacy SDKs (Full, Lite, Seamless, Render, Headless, and Secure Fields) remain supported side-by-side during the transition and are scheduled for deprecation in 2027. Please contact your Account Manager for migration planning, timeline details, or support.
One integration, every platform. Yuno’s SDKs for iOS, Android, and Web share the same unified API, so what you build once works everywhere: the same Transaction, the same start(), the same setup. Initialize the SDK with your API key and start a Transaction for each payment or enrollment. From there the SDK takes your shopper from picking a method to a finished payment: forms, tokenization, 3DS, and the final status, all handled for you. How a transaction flows shows the sequence step by step.
iOS· Swift↗Android· Kotlin↗Web· JavaScript↗

​
Start with the default checkout

The SDK ships a complete checkout: method list, forms, 3DS, and results. Yuno renders and runs everything; you only listen for the result with onStatus. The form it renders is tuned so shoppers finish in seconds, with nothing to configure. See A faster checkout for more examples of what speeds it up.

Use our default checkout

Recommended. Nothing to build and nothing to override. See it live in the playground →

​
Want more control?

Override just the piece you need. Everything else keeps working by default:
Loading UIThe spinner shoppers see while the SDK works.
showLoading →
Where forms renderEmbed the SDK’s forms in your own screens. Mobile only.
showView →
The form itselfCollect the payment details in your own UI.
transactionData →
Payment creationYour backend creates the payment instead of the SDK.
createPayment →
Not sure which pieces you need? Where do I start? walks you through each decision, case by case.

​
Choose a session type

The same Transaction class handles two flows:
  • Pass a checkoutSession to process a payment.
  • Pass a customerSession to enroll a payment method without charging.
See Sessions for details.

​
Backend requirements

The SDKs are client-side only. Your backend must:
  1. Create checkout or customer sessions.
See Get Started for the full backend integration walkthrough.

​
Migrating from a previous version

If you’re currently using one of the legacy SDKs (Full, Lite, Seamless, Render, Headless, Secure Fields), the new unified API replaces all of them with a single Transaction class. Your existing integration will continue to work, but new features and improvements ship in the unified SDK. See the Migration guide for a mapping from legacy modes to the new API and step-by-step instructions for each platform.

​
Next steps

Get started

Install, initialize, and process your first payment.

Where do I start?

Decide which parameters and controllers fit your integration.

Build with AI

Install and integrate the SDK with your AI coding agent.

Controllers

Control rendering, submission, and result handling.

Guides

Payment methods list, enrollment, deeplinks, styling.

Reference

Config, payment method selection, transaction data, status.

Migration

Move from Lite, Full, Render, Headless, or Seamless to the unified SDK.