Skip to main content
The Yuno Web SDK offers several configuration options to modify its visual presentation and functional flow. You can control everything from display modes (Modal vs. Element) to fine-grained CSS injection for card forms.
For a complete list of all initialization parameters and their possible values, visit the Web SDK Reference.

Display Modes

The renderMode parameter determines how the payment forms are presented to your customers. You can choose between a popup modal or embedding the SDK directly into an HTML element on your page.

Example: Embedding as an Element

If you choose element, you must provide a selector for the container where the APM form and the Action form (e.g., PIX QR code) will be mounted.

Card Form Customization

The card configuration object allows you to modify the look and feel of the sensitive card data fields (Card Number, Expiry, CVV), which are rendered inside a secure iframe for PCI compliance.

CSS Injection

Use the styles property to inject custom CSS directly into the card form iframe. This is the most powerful way to match the SDK to your site’s aesthetic.

Custom Labels and Texts

You can override the default placeholder and button labels to better fit your application’s tone or language requirements.

General UI Controls

Modify general SDK behaviors such as loaders, issuer forms, and button visibility.

SDK Loader Control

By default, Yuno shows a loading spinner during transitions. You can hide it if you prefer to use your own application’s loading state.

Pay Button Visibility

In scenarios where you want to trigger the payment precisely from your own UI logic, you can hide the SDK’s built-in “Pay” button.
If you hide the Pay button, you must call yuno.submitOneTimeTokenForm() programmatically to proceed with the payment.

Advanced Flow Management

Performance and Retries

If a transaction fails, you can update the session without unmounting the form, ensuring a smoother user experience for retries.

WebView Considerations (Mercado Pago)

If you are integrating in a WebView environment and using Mercado Pago Checkout Pro, you must handle the redirect results returned by continuePayment().