1. Prerequisites
You need:- A Yuno sandbox account. Sign up if you don’t have one.
- Your sandbox
public-api-keyandprivate-secret-key— find them in Dashboard → Developers → API keys. See Authentication for the full key reference. - Your
account_id(sometimes called the account code). Available alongside the API keys. curl, or one of: Node 18+, Python 3.9+, Go 1.21+.
Sandbox processes no real funds and exposes no PCI surface. Use it freely for testing.
2. Set your credentials
Export your sandbox credentials so the snippets below can read them:3. Create a checkout session
A checkout session is the entry point for every payment in Yuno. It captures the transaction context (amount, country, order id) and returns ansdk_token your client uses to render the payment UI.
- cURL
- Node.js
- Python
- Go
200 OK with the session. Hold onto checkout_session (the id) and sdk_token (the value your frontend will mount).
Sample success response
Sample success response
sdk_token to the Yuno SDK on the client; pass checkout_session along with it so the SDK can resolve the session.Sample error response (4xx)
Sample error response (4xx)
Every Yuno error returns the same envelope:Share
request_id with Yuno support when opening a ticket. See Error handling for the full code catalog.4. Render the checkout
Thesdk_token is consumed by the Yuno SDK to render the payment UI in your application. Pick your platform and follow the SDK quickstart from there:
Web SDK
Mount the full checkout, seamless, lite, secure-fields, or headless variant in any web app.
Mobile SDKs
iOS, Android, and Flutter quickstarts with native checkout components.
sdk_token, renders the available payment methods, collects sensitive details client side, and submits to Yuno without your servers ever touching card data.
5. Confirm the payment landed
Once the customer completes the SDK flow, retrieve the resulting payment to confirm its status:transaction_status of SUCCEEDED means funds are captured. For methods like Pix, Boleto, or PSE you’ll see PENDING synchronously — the final status arrives by webhook. See Async results and timeouts for the full list.
Next steps
Save the card
Vault the customer’s card for one-click checkout and MIT.
Set up webhooks
Receive real-time payment lifecycle events, signed for verification.
Move to production
Swap base URLs and keys; everything else stays the same.