Skip to main content
Connections are how you bring your existing payment-provider accounts (Stripe, Adyen, dLocal, PayU, …) into Yuno’s orchestration. Once a connection exists, you can reference it from a routing rule to send payments through that provider. A routing tells Yuno, for one payment_method on one account, which connection to use — and lets you branch by buyer attributes (country, currency, amount, card brand, custom metadata, …).

​
Common contract

​
Base URL

​
Authentication & headers

Use an account key or an organization key. Dashboard Developers → Customized API keys are rejected on every /v1/routing* and /v1/connections* endpoint today.

​
Conventions

  • Field names are snake_case everywhere — request, response, errors. The one exception is inside params[] on the provider catalog response, where individual param_id values are passed through with their native casing (merchantAccount, HMAC_KEY, apple-merchant-id, etc.) — you must echo these verbatim when creating a connection.
  • Error envelope is the same across all endpoints:
Stable code values are listed per endpoint.