Skip to main content
How Yuno worksIntroduction

What is Yuno?

Yuno is the AI operating system for payments.

This request is real and runs in sandbox, so copy it, set your keys, and run it. Run it in the API playground. Sandbox setup is in the Quickstart. In production, sending card data from your server requires PCI DSS.

Auth

Headers public-api-key and private-secret-key

Keys start with sandbox_ or prod_

Writes

Send X-Idempotency-Key when you create a payment

Amounts in major units: 25 is USD 25.00

01 / How it works

Your app talks to Yuno. Yuno talks to everyone else.

You add providers and change routing in the Dashboard. Your code does not change.

02 / Core objects

Four objects, in the order you use them.

Every payment follows this sequence, with any method and any provider.

  1. 1Customer OptionalPOST /v1/customersThe payer. Stores their details and saved payment methods for reuse.
  2. 2Checkout sessionPOST /v1/checkout/sessionsThe amount and country. The SDK uses it to show the payment methods your account has enabled.
  3. 3PaymentPOST /v1/paymentsThe charge. It holds the transactions: authorization, capture, and refund.
  4. 4WebhookYuno → your serverYuno sends each status change to a URL you register in the Dashboard or by API.

The SDK turns card data into a one-time token (OTT) that you send with the payment. The Direct API skips the session and sends card data from your server, which requires PCI DSS. Full sequence: Payment flow.

03 / Choose your integration

Pick how much of the flow you own.

All four use the same objects and the same API keys.

Also: Flutter, React Native, WooCommerce, VTEX. To build with a coding agent, see Build with AI.

04 / Product index

Everything else Yuno does.

One line each. Each link opens the guide or the API reference.

Next

Your first sandbox payment.

  1. 1Quickstart TutorialConnect the test gateway and send one sandbox payment.
  2. 2Developers ReferenceBase URLs, keys, specs, SDK versions, and tools.
  3. 3Payment flow ConceptEach step of a payment, field by field.
  4. 4API reference ReferenceEvery endpoint, with request and response schemas.

Stuck on a term? See the Glossary.