Quick Start
Platform Examples
Checkout Customization
Mobile Recipes
start(...) call, and each one includes abandoned-session recovery. Build the flow by hand only if none of the SDKs fits your stack.Prerequisites
Before you start, you need:- A Dodo Payments account.
- An API key from Developer → API Keys and a webhook signing secret from Developer → Webhooks.
- An Android, iOS, React Native, or Flutter app.
- A backend server that creates checkout sessions. The API key stays on this server.
Integration Workflow
Your backend makes every Dodo Payments API call. Your app only asks your backend for a checkout URL, opens it, and shows the result.status in the deep link tells your app what to show the customer. It is not proof of payment. Grant access from the payment.succeeded or subscription.active webhook on your backend, not from the mobile result.Backend: Create Checkout Session
checkout_url to the app. Set the session’s return_url to the deep link your app registers, for example myapp://checkout/return.Checkout Session API Docs
Mobile: Get Checkout URL
userSessionToken is that token and CheckoutResponse is your own response type.- iOS (Swift)
- Android (Kotlin)
- React Native (JavaScript)
- Flutter (Dart)
Mobile: Open Checkout in Browser
Pick your mobile SDK
Backend: Handle Payment Completion
payment.succeeded or subscription.active webhook. Use the result from the return URL only to update the app’s screen.Choose Your SDK
Every mobile SDK has the same contract. Onestart(...) call opens Dodo Payments hosted checkout in the platform’s system browser surface and returns a typed CheckoutResult whose status is succeeded, failed, cancelled, pending, or expired. No SDK holds an API key or calls the Dodo Payments API, and all four support abandoned-session recovery.
Android
com.dodopayments.api:checkout-android opens a Custom Tab. Requires minSdk 23.iOS
dodopayments-mobile-sdk-ios opens SFSafariViewController. Requires iOS 16+.React Native
@dodopayments/react-native-checkout, a Turbo Module over both native cores. Requires React Native 0.77+ with the New Architecture.Flutter
dodopayments_checkout, a Pigeon channel over both native cores. Requires Flutter 3.44+.Registering a Callback URL Scheme
All four SDKs return control to your app through a custom URL scheme that you choose, for examplemyapp://checkout/return. Register it once per platform:
- Android
- iOS
- Expo
returnUrl.checkout_url in the platform’s system browser surface (a Custom Tab on Android, SFSafariViewController on iOS), intercept the navigation to your return_url, and read the status and payment_id query parameters. The SDKs do this for you.Appearance Customization
Every SDK accepts an optionalcustomization parameter on start(...) or CheckoutParams. It controls the system browser surface: the toolbar, the buttons, and how the browser is presented. The checkout page’s own theme is separate. You set it on your server with customization.theme_config when you create the checkout session.
The options are grouped by platform, because a Custom Tab on Android and SFSafariViewController on iOS expose different native controls. Every field is optional. An unset field leaves the platform’s own default in place.
Android - Custom Tab
Android - Custom Tab
default shows the system “X” icon; back draws a back arrow instead.iOS - SFSafariViewController
iOS - SFSafariViewController
pageSheet presents checkout as a card that the customer can swipe to dismiss. fullScreen covers the whole screen.presentationStyle is fullScreen. With pageSheet, the bars stay pinned.android and ios option groups. The native SDKs take only their own platform’s options.
- React Native
- Flutter
- Android (Kotlin)
- iOS (Swift)
Checkout Page Customization
The checkout page itself (which fields appear, the theme, and which payment methods show) is set on your server when you create the checkout session. Appearance Customization covers only the browser surface around it. The parameters below have the most effect on mobile conversion. Estos parámetros se encuentran en tres lugares de la solicitud de sesión de checkout: en el nivel superior, encustomization o en feature_flags. La columna Dónde va indica el objeto correspondiente a cada uno. Coloca cada parámetro en el objeto mostrado, porque un parámetro en el objeto incorrecto no tiene ningún efecto.

show_order_details: false moves the contact and payment fields above the fold, instead of behind the order summary.
minimal_address: true to collect only a postcode instead of the full street, city, and state fields:

minimal_address: true reduces the billing address to a single postcode field.
theme: "system" so the checkout follows the device’s light or dark mode preference:

With theme: system, the checkout follows the device's light or dark appearance automatically.
Full checkout session parameter reference
Mobile-Optimized Recipes
Each recipe is a complete checkout session request that your backend sends. Pick the one that matches your scenario and replace the product ID with your own. The Node.js and Python clients are set up in the first recipe, and the other recipes reuse them.Minimal Mobile Checkout - fastest path to payment
Minimal Mobile Checkout - fastest path to payment
- Node.js SDK
- Python SDK
One-Click Returning Customer - saved card, instant confirmation
One-Click Returning Customer - saved card, instant confirmation
customer_id, their saved payment_method_id, and confirm: true to skip the checkout form. With a payment_method_id, the session charges the saved method directly and returns no checkout_url, so your app has nothing to open. Learn the outcome from webhooks.- Node.js SDK
- Python SDK
payment.succeeded webhook. Any status your app shows is a UI hint only.Subscription with Free Trial - trial before first charge
Subscription with Free Trial - trial before first charge
trial_period_days sets the trial length for this session.- Node.js SDK
- Python SDK
subscription.active webhook, not when the mobile SDK returns. For the full webhook flow, see the Subscription Integration Guide.On-Demand Mandate - save a card for future variable charges
On-Demand Mandate - save a card for future variable charges
- Node.js SDK
- Python SDK
Subscription Flows from Mobile
A mobile app starts a subscription with the same checkout session flow as a one-time payment. The SDK opens hosted checkout, the customer subscribes, and your app handles the deep-link return. Your backend manages the rest of the subscription lifecycle.Regular Recurring Subscriptions
For billing at a fixed interval, such as monthly or yearly, create a checkout session with a subscription product and a deep-linkreturn_url. Your backend receives subscription.active when the subscription starts.
On-Demand Subscriptions
An on-demand subscription authorizes a customer’s payment method once, so you can charge variable amounts later. Use it for wallet top-ups, pay-as-you-go, and any charge whose amount you don’t know in advance. For the full request body, see the On-Demand Mandate recipe. On mobile, keep these points in mind:- Set
show_on_demand_tag: falseso the checkout page doesn’t show subscription or on-demand wording. Customers who save a card for top-ups don’t expect subscription terms. - After the customer authorizes the mandate, your backend receives
subscription.active. Store thesubscription_id, because every later charge uses it.
Subscription with Free Trial
To offer a trial before the first charge, passsubscription_data.trial_period_days in the checkout session. The customer authorizes a payment method at signup, and Dodo Payments charges it when the trial ends. For the full request body, see the Subscription with Free Trial recipe.
Upgrades and Downgrades
Your backend changes plans through the API, not through a new checkout session. Dodo Payments calculates proration with the proration mode you choose. To let customers change plans themselves, link to the Customer Portal.Subscription Integration Guide
On-Demand Subscriptions
Upgrade / Downgrade
Customer Portal
Reducing Checkout Drop-Offs
En una pantalla pequeña, completar cada campo del formulario requiere más esfuerzo. Las siguientes opciones de configuración de la sesión de checkout acortan el formulario y reducen los abandonos.Optimize the Form
These settings shorten the checkout form on mobile:Pre-Fill Customer Data
Each field you pre-fill is one the customer doesn’t have to type:- New customers: set
customer.emailandcustomer.namefrom your auth session. - Returning customers: set
customer.customer_idto use the customer’s stored details. - Currency: pass
billing_currencyandbilling_address.countrytogether.
Recovery Tools
Recovery tools bring back customers whose checkout or renewal didn’t complete:Abandoned Cart Recovery
Payment Retries
Subscription Dunning
Recovery Overview
Prácticas recomendadas
- Seguridad: Nunca incluyas una clave de API en tu aplicación. Crea sesiones de checkout en tu backend y pasa a la aplicación únicamente el
checkout_url. - Autoridad: Trata
CheckoutResult.statuscomo una indicación de la interfaz de usuario. Concede acceso únicamente después de que tu backend confirme el pago. - Experiencia de usuario: Muestra un estado de carga mientras tu backend crea la sesión. No trates
cancelledcomo un fallo, porque es posible que el pago se haya realizado correctamente. - Pruebas: Usa el modo de prueba y tarjetas de prueba, y comprueba el recorrido de ida y vuelta de la URL de retorno en un dispositivo real y en un simulador.
- Conversión: Configura
show_order_details: falseyminimal_address: true. Juntos, colocan los métodos de pago en la parte visible sin desplazamiento y eliminan la mayoría de los campos de dirección. - Moneda: Pasa tanto
billing_currencycomobilling_address.country. Si omites cualquiera de los dos, Adaptive Currency puede elegir la moneda de facturación a partir de la dirección IP del cliente. - Facturación bajo demanda: Configura
show_on_demand_tag: falsecuando uses suscripciones bajo demanda únicamente para guardar una tarjeta. Los clientes que recargan una billetera no esperan un texto relacionado con suscripciones. - Recuperación: Activa Abandoned Cart Recovery en el dashboard para enviar un correo electrónico a los clientes que no completen el checkout.
Solución de problemas
Problemas frecuentes
- La devolución de llamada nunca llega: El esquema de
returnUrldebe coincidir con el esquema que registraste. En Android, ese es el marcador de posición de manifiestododoCallbackScheme. En iOS, es el tipo de URLInfo.plist. Las aplicaciones de React Native y Flutter necesitan ambos, y en Expo el complemento de configuración establece los dos. - El checkout vuelve al navegador en lugar de a tu aplicación (iOS): Tu aplicación no reenvía la URL entrante. Llama a
DodoCheckout.handleOpenURL(url)desde.onOpenURL,scene(_:openURLContexts:)o un listener de React NativeLinking. PLATFORM_ERRORen Android: La causa más común es una discrepancia de esquemas. También aparece cuando tuMainActivityconfiguraandroid:taskAffinity=""(el valor predeterminadoflutter create), lo que permite que algunas compilaciones de OEM de Android pierdan el checkout en curso.ALREADY_IN_PROGRESS: Todavía hay un checkout abierto. Espera a que termine el anterior o ciérralo antes de iniciar otro.- La compilación falla debido a un marcador de posición sin resolver: Añadiste el SDK de Android, pero no configuraste
manifestPlaceholders["dodoCallbackScheme"]. - El pago se realizó correctamente, pero no se concedió acceso: Tu aplicación concede acceso a partir del resultado móvil. En su lugar, concede acceso desde el webhook
payment.succeededosubscription.active. - Apple Pay o Google Pay no aparece en dispositivos móviles: Comprueba si el checkout se está cargando dentro de un WebView integrado (
WKWebViewo AndroidWebView). Ábrelo con el SDK o en la superficie del navegador del sistema: una Custom Tab en Android, oSFSafariViewControlleroASWebAuthenticationSessionen iOS.
Recursos adicionales
- Guía de integración de pagos
- Documentación de Webhook
- Proceso de pruebas
- Preguntas frecuentes técnicas
- Personalización de la sesión de checkout
- Suscripciones bajo demanda
- Actualización o reducción de la suscripción
- Abandoned Cart Recovery
- Customer Portal
