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.
Headers public-api-key and private-secret-key
Keys start with sandbox_ or prod_
Send X-Idempotency-Key when you create a payment
Amounts in major units: 25 is USD 25.00
Your app talks to Yuno. Yuno talks to everyone else.
You add providers and change routing in the Dashboard. Your code does not change.
Four objects, in the order you use them.
Every payment follows this sequence, with any method and any provider.
- 1Customer Optional
POST /v1/customersThe payer. Stores their details and saved payment methods for reuse. - 2Checkout session
POST /v1/checkout/sessionsThe amount and country. The SDK uses it to show the payment methods your account has enabled. - 3Payment
POST /v1/paymentsThe charge. It holds the transactions: authorization, capture, and refund. - 4Webhook
Yuno → 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.
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.
Everything else Yuno does.
One line each. Each link opens the guide or the API reference.
- Payment methodsCards, wallets, and local methods
- SubscriptionsPlans and recurring billing
- Split paymentsMarketplace payments across recipients
- In-person (POS)Card-present payments on store terminals
- CryptoAsk your Yuno account team
Your first sandbox payment.
Stuck on a term? See the Glossary.