3DS (3D Secure)
3D Secure (3DS) is a security protocol that adds a verification step to card-not-present transactions to authenticate the customer and reduce fraud. Yuno records a 3DS verification as a secondary transaction on the payment and supports 3DS2 and 3DS Standalone. See 3DS.Account
An account is a unit inside your organization that can represent a country, franchise, or business unit, with its own users, connections, and keys. Each account has unique Account IDs for Live Mode and Test Mode. See Account Management.Authorize
Authorize is a primary transaction type that reserves a payment amount on a card so you can capture it later. To authorize without charging the customer, sendcapture as false when you create the payment. See Transactions.
Cancel
Cancel is a secondary transaction that voids an initial authorization and releases the held funds. Only payments withPENDING status can be canceled. See Cancel Payments.
Capture
Capture is a secondary transaction that collects the funds from an initial authorization, in full or in part. Only payments withPENDING status can be captured. See Capture Payments.
Chargeback
A chargeback is a claim a customer raises through their issuing bank to contest a transaction. In Yuno, a chargeback and a dispute are the same object: the chargeback becomes an active dispute when you submit evidence. See Chargeback Management.Checkout Builder
The Checkout Builder is a no-code dashboard tool that enables payment methods with a published route, sets their display conditions and required fields, and styles the checkout. Changes apply after you click Publish settings. See Checkout Builder.Checkout session
A checkout session starts the payment flow for one customer and gives access to all payment methods available to that customer. You create a new checkout session for each payment when you use Yuno’s SDKs. See Sessions.Connection
A connection links your Yuno account to a provider, such as a payment method, a processor, or an anti-fraud solution, using the provider’s credentials. You add connections in the dashboard and then assign them to routes. See Connections.Customer
A customer is an individual in a merchant’s payment network who can make payments and store payment methods in Yuno. Every payment links to a customer, identified by thecustomer_id that Yuno generates. See Customers.
Customer session
A customer session lets you enroll and store a customer’s payment methods for future use. You create a new customer session each time you register a payment method for a specific customer. See Sessions.Customer-initiated transaction (CIT)
A customer-initiated transaction (CIT) is a payment the customer actively starts, such as an online or in-store purchase. It typically requires cardholder authentication. See Stored Credentials.Enrollment
Enrollment stores a customer’s payment method in Yuno’s vault for future use and returns avaulted_token. Enrolled payment methods enable recurring payments, subscriptions, and retries across providers. See Enroll Payment Methods.
Fraud screening
Fraud screening is the pre-authorization or post-authorization check that an external fraud detection provider runs on a payment. When a route includes fraud verification, Yuno adds aFRAUD_SCREENING transaction to the payment. See Fraud prevention.
Idempotency key
An idempotency key is a unique UUID sent in theX-Idempotency-Key header so you can safely retry a request with an unclear outcome. Reusing the key returns the original payment instead of creating a duplicate. See Authentication.
Installments
Installments let a customer spread the cost of a card purchase over several payments. Yuno supports merchant installments, defined by your own agreements, and provider installments, defined by the payment processor. See Installments.Lite SDK
The Lite SDK is a lightweight integration that gives you full control over how and where each payment method is displayed. You implement payment method selection yourself. See Choose Integration.Merchant-initiated transaction (MIT)
A merchant-initiated transaction (MIT) is a payment the merchant sends without the customer’s active involvement, such as a recurring charge or a subscription renewal. It relies on an initial customer authentication at setup. See Stored Credentials.Monitors
Monitors detect drops in approval rate on a route, alert you through your configured channels, and automatically redirect traffic to fallback providers. Traffic returns to the original route when the approval rate recovers. See Monitors.Network token
A network token is a digitized representation of a card’s Primary Account Number (PAN), issued by card networks such as Visa, Mastercard, or American Express. When enabled, Yuno provisions network tokens for all enrolled cards, and the card network updates them automatically. See Network Tokens.One-time token
A one-time token holds the payment information the Yuno SDK collects for a single checkout session. You use it once when you create the payment, and it cannot be reused. See Tokens.Organization
An organization is the top-level entity that groups your Yuno accounts and users. Organization keys grant access to all accounts in the organization, and organization-level roles apply across every account. See Developers (Credentials).Payment
A payment represents a user’s transaction, regardless of the processors or payment methods used, and collects order details such as customer, amount, and currency. A payment consists of one or more transactions that determine its final outcome. See Payments.Payment link
A payment link is a URL you create in the dashboard to collect a payment without writing code. You set the country, currency, amount, payment methods, and optional start and expiration dates. See Payment Links.Payment method
A payment method is a way to collect the customer’s payment information and send it to a processor, such as cards, digital wallets, bank transfers, or buy now, pay later services. Payment methods differ by enrollment support and by synchronous or asynchronous processing. See Payment methods.Payment status
The paymentstatus and sub_status describe the current state of a payment and follow a standardized lifecycle across all payment methods. Yuno recommends using them as the main reference for the payment’s state, regardless of how many transactions it has. See Payment Status and Response Codes.
Payout
A payout sends funds from you to a beneficiary through a bank, card, or wallet withdrawal method. A payout starts asCREATED, moves to PENDING, and ends as SUCCEEDED, REJECTED, or DECLINED. See Payouts.
Plan
A plan is a reusable pricing definition with a name, a price (optionally per country), a billing frequency, and an optional trial phase. You subscribe customers to a plan withplan_id instead of sending amount and frequency on each subscription. See Plans.
Private secret key
Theprivate-secret-key is the credential your server sends, together with the public-api-key, to authenticate every Yuno API request. Do not share it in public places such as GitHub or Bitbucket. See Authentication.
Provider
A provider is a third party you connect to Yuno, including payment methods, payment processors, and anti-fraud solutions. Routing decides which provider processes each payment. See Connections.Public API key
Thepublic-api-key is the credential you send in every Yuno API request and use for client-side SDK initialization. You find it in the Developers section of the dashboard. See Authentication.
Reconciliation
Reconciliation compares the transactions processed through Yuno with the settlement files from each payment provider to find discrepancies and confirm settlement. The dashboard shows the reconciliation rate by provider, account, and currency. See Reconciliations.Refund
A refund returns funds to the customer for a captured payment, in full or in part, and appends aREFUND transaction to the payment. Yuno supports referenced refunds through the API, batch refunds through a dashboard CSV upload, and unreferenced refunds that do not reference a Yuno payment. See Refunds.
Risk conditions
Risk conditions are Yuno’s own fraud prevention rules, blocklists, and allowlists that you add to a route to control which transactions get screened. They reduce unnecessary requests to fraud prevention providers. See Risk Conditions.Routing
Routing directs each payment to a provider based on rules you configure in the dashboard, such as card type, transaction amount, currency, and payment origin. A route belongs to a payment method and must be published before it processes transactions. See Routing.Seamless SDK
The Seamless SDK is Yuno’s recommended integration: it provides pre-built UI components, gives you control over the payment experience, and lets you add payment methods from the dashboard without code. See Seamless SDK.Secure Fields
Secure Fields are prebuilt input fields you embed in your own Web payment form so raw card data never touches your servers. They keep a custom checkout UI PCI compliant. See Secure Fields Overview.Smart Routing
Smart Routing optimizes payment performance by choosing among two or more connections in a route according to the variable you select: conversion rate and latency, or conversion rate and costs. You turn it on with a toggle when you set route conditions. See Routing.Split payments
Split payments divide a marketplace payment among multiple recipients, the submerchants you onboard in Yuno, with amounts, fees, and commissions. The selected payment provider must support split payments, because Yuno orchestrates the split but does not process it. See Split Payments Marketplace.Subscription
A subscription is a recurring payment that Yuno’s recurrence engine creates and sends on your behalf at the frequency you define. Its status moves fromCREATED to ACTIVE or TRIALING, and can become PAUSED, PAST_DUE, COMPLETED, or CANCELED. See Subscriptions.
Test Mode and Live Mode
Test Mode (Sandbox) lets you explore the dashboard and run tests without real transactions. Live Mode (Production) processes real customer transactions and requires an activation request, and one dashboard toggle switches between the two. See Environments.Transaction
A transaction is an operation inside a payment, processed through a connection. Primary transactions (purchase, authorize, verify) start a payment, and secondary transactions (refund, cancel, capture, chargeback, 3DS, fraud screening) change its outcome. See Transactions.Vaulted token
A vaulted token is created when a payment method is enrolled and stored in Yuno’s centralized vault with the customer’s information. It works across all processors connected to your account and persists until the customer unenrolls the payment method. See Tokens.Webhook
A webhook is an HTTP POST notification that Yuno sends to your public REST API whenever an event occurs in the payment flow. Webhooks keep your system updated on payment status changes without repeated requests to Yuno. See Webhooks.Workflow
Theworkflow attribute of a payment tells Yuno which integration you use: SDK_CHECKOUT when the Yuno SDK collects the payment details, DIRECT when you send them server to server and receive the provider’s raw response, and REDIRECT when Yuno also provides a redirect URL and handles the payment experience for that payment. See Direct Flow Integration.