[{"_id":"project-settings","settings":{"translateMetaTags":true,"translateAriaLabels":true,"translateTitle":true,"showWidget":true,"isFeedbackEnabled":false,"fv":1,"customWidget":{"theme":"custom","font":"rgb(255,255,255)","header":"rgb(62, 79, 224)","background":"rgba(62, 79, 224,0.8)","position":"right","positionVertical":"bottom","border":"rgb(204,204,204)","borderRequired":false,"widgetCompact":true,"isWidgetPositionRelative":false},"widgetLanguages":[{"code":"es-LA","name":"Español (América Latina)"},{"code":"fr","name":"Français"},{"code":"pt-BR","name":"Português (Brasil)"},{"code":"zh","name":"中文(简体)"}],"activeLanguages":{"pt-BR":"Português (Brasil)","es-LA":"Español (América Latina)","fr":"Français","zh":"中文(简体)","en":"English"},"enabledLanguages":["en","es-LA","fr","pt-BR","zh"],"debugInfo":false,"displayBranding":true,"displayBrandingName":true,"localizeImages":false,"localizeUrls":false,"localizeImagesLimit":false,"localizeUrlsLimit":true,"localizeAudio":false,"localizeAudioLimit":false,"localizeDates":false,"disabledPages":[],"regexPhrases":[],"allowComplexCssSelectors":false,"blockedClasses":false,"blockedIds":false,"phraseDetection":true,"customDomainSettings":[],"seoSetting":[],"translateSource":true,"overage":false,"detectPhraseFromAllLanguage":false,"googleAnalytics":false,"mixpanel":false,"heap":false,"disableDateLocalization":false,"ignoreCurrencyInTranslation":false,"blockedComplexSelectors":[]},"version":57340},{"_id":"en","source":"en","pluralFn":"return n != 1 ? 1 : 0;","pluralForm":2,"dictionary":{},"version":57340},{"_id":"outdated","outdated":{"#Indicates if the ticket is refundable or not.":1,"#The passenger's document type (MAX 6, MIN 2; Document Type List).":1,"#Skip link to Available permissions":1,"#Skip link to Environment-specific configuration":1,"#Skip link to Creating custom roles":1,"#Skip link to Team for each account":1,"#<strong ljsid-0=\"\">Security</strong> - Manage 2FA and SSO configurations":1,"#<strong ljsid-0=\"\">Audit logs</strong> - View dashboard, API, and monitor logs":1,"#<strong ljsid-0=\"\">Risk conditions</strong> - View and manage rules and lists":1,"#<strong ljsid-0=\"\">Team and roles</strong> - View and manage team members and roles":1,"#<strong ljsid-0=\"\">Accounts</strong> - Manage account settings":1,"#<strong ljsid-0=\"\">Webhooks</strong> - View and manage webhooks":1,"#<strong ljsid-0=\"\">Developers</strong> - View and manage account keys":1,"#<strong ljsid-0=\"\">Checkout builder</strong> - View and build checkout configurations":1,"#<strong ljsid-0=\"\">Routing</strong> - View and manage processing routes":1,"#<strong ljsid-0=\"\">Connections</strong> - View and manage payment connections":1,"#<strong ljsid-0=\"\">Reconciliation</strong> - View settlement reports":1,"#<strong ljsid-0=\"\">Payouts</strong> - View payouts and transaction details":1,"#<strong ljsid-0=\"\">Payments</strong> - View and operate payments, manage payment links":1,"#<strong ljsid-0=\"\">Insights</strong> - Access to actionable payment insights":1,"#The custom role creation interface includes these permissions:":1,"#Available permissions":1,"#This granular control allows you to create roles where users might have full access in sandbox for testing purposes, but restricted access in production for security reasons.":1,"#<strong ljsid-0=\"\">Production environment</strong>: For live operations and sensitive data":1,"#<strong ljsid-0=\"\">Sandbox environment</strong>: Perfect for testing and development activities":1,"#For each permission, you can independently configure access for:":1,"#Environment-specific configuration":1,"#Yuno's <strong ljsid-1=\"\">Create role</strong> feature provides enhanced flexibility for role management by allowing you to create custom roles with environment-specific permissions. This feature enables you to define precise access controls for different environments, promoting better security and operational control.":1,"#To create a custom role, navigate to the <strong ljsid-1=\"\">Roles management</strong> tab and select <strong ljsid-3=\"\">Create role</strong>. You can then define the role name, description, and assign specific permissions for each environment according to your team's needs.":1,"#Creating custom roles":1,"#Defining clear roles and permissions strengthens the security of your operations. Each team member works within a specific scope, reducing the risk of accidental errors or unauthorized access. Roles give individuals the access they need to do their jobs efficiently, while keeping workflows organized and secure.":1,"#A running index (starts with 1), describing the order of routes by time. E.g: If an order contains 2 Routes: New-York->London->Paris (connection in London) New-York->London should have route_order=1, order=1; London->Paris should have route_order=1, order=2; Paris->London->New-York: Paris->London should have route_order=2, order=1; London->New-York should have route_order=2, order=2.":1,"#Skip link to Enroll Payment Method":1,"#Skip link to Create Customer Session":1,"#Skip link to Create Customer":1,"#Skip link to Create Installments Plan":1,"#Skip link to Create a Report":1,"#Skip link to Update Subscription":1,"#Skip link to Create Subscription":1,"#Skip link to Create Payment Link":1,"#Skip link to Create Payment":1,"#Skip link to Create Checkout Session":1,"#Shipping details":1,"#Connection ID":1,"#Parent payment method type":1,"#Subscription retries":1,"#Example: <a ljsid-1=\"\">3132450765</a>.":1,"#Example: <a ljsid-1=\"\">1093333333</a>.":1,"#Example: <a ljsid-1=\"\">021000021</a>":1,"#transportations":1,"#Customer object":1,"#Neighborhood":1,"#Other providers compatible with SAML 2.0 (Okta enabled by default. Contact support for other providers).":1,"#For other providers, please contact support.":1,"#Yuno works with identity providers supporting the <strong ljsid-1=\"\">SAML 2.0</strong> standard:":1,"#Yuno supports SSO using the <strong ljsid-1=\"\">SAML 2.0</strong> (Security Assertion Markup Language) standard. This ensures compatibility with any identity provider that follows the protocol, such as Google and Okta.":1,"#Skip link to Demo app":1,"#Skip link to Important Note":1,"#This request enables you to retrieve details of a payment link based on its <code ljsid-1=\"\"></code>, which needs to be provided in the request path.":1,"#Next Page: iOS SDKs":1,"#Skip link to Under development":1,"#The <code ljsid-1=\"\"></code> is linked to the contract, not to the customer. Treat it as a reusable payment method.":1,"#<code ljsid-0=\"\"></code>, <code ljsid-2=\"\"></code>":1,"#Skip link to Secure Channel Required":1,"#Skip link to Security Requirements":1,"#building-ai-integrations-with-yunos-llms-and-mcp":1,"#formación":1,"#Tú":1,"#Skip link to Set up costs for new connections":1,"#🚧Under development\nOverview\nPix Automático is the Central Bank of Brazil’s new merchant-initiated recurring-payment feature built on the ubiquitous Pix instant-payment network. Since its launch in late 2020, Pix has become Brazilians’ favorite way to pay—handling over 26 trillion BRL in transaction…":1,"#Nesta página, você encontra as informações necessárias sobre países para usar os endpoints da API da Yuno. A tabela abaixo fornece códigos padrão para identificação do país, moedas, tipos de documentos usados em cada país e códigos telefônicos. Use esta página para entender e ter acesso aos valores padrão de cada informação. Use os botões abaixo para ir diretamente para a região da lista de países desejada.":1,"#Na Coleção Yuno, vários parâmetros são considerados variáveis. Esses valores podem ser definidos no ambiente ou ao receber uma resposta do servidor. As variáveis do Postman ajudam a testar diferentes endpoints em sequência, à medida que os valores recebidos preenchem os parâmetros do corpo da solicitação subsequente.":1,"#Os ambientes fornecem uma lista de variáveis usadas pelos endpoints. Em vez de definir valores para cada parâmetro toda vez que executar uma solicitação, você pode usar as variáveis de ambiente.":1,"#boleto":1,"#ID for use in Step 4 of the integration":1,"#Store the returned <code ljsid-1=\"\"></code> ID for use in Step 4 of the integration":1,"#Nenhum resultado de pesquisa para 'bandeira'.":1,"#Make a request to see them here or <a ljsid-1=\"\">Try It</a>!":1,"#Last 24 Hours":1,"#My Top Endpoints":1,"#The state / province considered for the billing address (MAX 255; MIN 3).":1,"#The customer's country (ISO 3166-1 MAX 2; MIN 2).":1,"#Beneficiary's cell phone number. (MAX 32; MIN 1).":1,"#Beneficiary's cell phone area code. (MAX 3; MIN 2).":1,"#reembolsos":1,"#Calling this endpoint will change the subscription <code ljsid-1=\"\"></code> to PAUSED. This status can be changed to ACTIVE or CANCELED.":1,"#Previous Page: Unblock Onboarding":1,"#Conflict - Recipient cannot be cancelled":1,"#Recipient cancelled successfully":1,"#Cancels a recipient's onboarding.":1,"#The onboarding workflow follows a structured process to ensure submerchants are properly integrated into the marketplace ecosystem. The diagram below illustrates the complete flow from initial setup to payment processing.":1,"#Previous Page: example-transaction-report.csv":1,"#<code ljsid-0=\"\"></code> – Requires <code ljsid-2=\"\"></code> and <code ljsid-4=\"\"></code> (for web, Android, and iOS payments)":1,"#<code ljsid-0=\"\"></code> – Redirect-based payment flow":1,"#<code ljsid-0=\"\"></code> – Direct payment processing":1,"#The <code ljsid-1=\"\"></code> tool supports three workflow types:":1,"#The unique identifier of the account (MAX 64 ; MIN 36)":1,"#Previous Page: Update connection":1,"#For example, a chatbot with access to these files could help a developer debug a payment integration, explain how vaulted tokens work, or walk through MCP setup — all based on real, structured content.":1,"#length between 2 and 2":1,"#Beneficiary's bank account routing number":1,"#Beneficiary's bank account type":1,"#Beneficiary's bank account digit":1,"#Beneficiary's bank account number":1,"#length between 3 and 250":1,"#Bank's branch digit":1,"#Bank's branch":1,"#The bank account's currency":1,"#The bank account's country":1,"#Bank's code":1,"#length between 3 and 3":1,"#Bank account information":1,"#Beneficiary's bank account type (MAX 3; MIN 1).":1,"#Beneficiary's bank account type (MAX 3; MIN 1). Could be: CHECKINGS, SAVINGS, VISTA, PIX_EMAIL, PIX_PHONE, PIX_DOCUMENT_ID, PIX_BANK_ACCOUNT.":1,"#Beneficiary's bank account digit (MAX 250; MIN 3).":1,"#Beneficiary's bank account number (MAX 250; MIN 3).":1,"#Bank's branch digit (MAX 3; MIN 3).":1,"#Bank's branch (MAX 3; MIN 3).":1,"#The bank account's currency (ISO 4217 MAX 3; MIN 3).":1,"#The bank account's country (ISO 3166-1 MAX 2; MIN 2).":1,"#Beneficiary's bank account routing number.":1,"#Bank's code (MAX 3; MIN 3).":1,"#Bank's account information":1,"#The unique identifier of the provider's recipient":1,"#Beneficiary's document type (MAX 6; MIN 2).":1,"#Beneficiary's national document id (MAX 40; MIN 3).":1,"#estados":1,"#Conflict - Recipient cannot be deleted":1,"#Recipient deleted successfully":1,"#Next Page: Create onboarding":1,"#Previous Page: Update Recipient":1,"#Deletes a recipient. This action cannot be undone.":1,"#denied":1,"#🚧Deprecated SDKYuno’s Flutter SDK is no longer maintained. Refer to our integration documentation to choose the best SDK for your project.\nThis page provides a step-by-step guide to integrating the Lite Flutter SDK for enrollment functionalities into your application.\n🚧PrerequisitesEnsure all requ…":1,"#🚧Deprecated SDKYuno’s Flutter SDK is no longer maintained. Refer to our integration documentation to choose the best SDK for your project.\nYuno's Flutter SDKs are crafted to simplify the integration of payment processing capabilities into your Flutter applications. By leveraging these SDKs, develop…":1,"#To control the appearance, you must use the <code ljsid-1=\"\"></code> function to define a variable with all your customizations. Then you have to inform it when initializing the SDK, as exemplified in the following code block:":1,"#Refere-se à":1,"#👍Recommended SDKWe recommend using the iOS Seamless SDK for a smooth integration experience. This option provides a flexible payment solution with pre-built UI components and customization options.\nYuno's Headless iOS SDK lets you enroll in payment methods and tokenize cards, saving them for future…":1,"#After enrolling the new card, you will receive the <code ljsid-1=\"\"></code>, which you can use to make payments in the future without asking for your customer's card information. The following code block presents an example of a response from the <code ljsid-3=\"\"></code> function. The response is a dictionary of type <code ljsid-5=\"\"></code>.":1,"#To verify cards with zero value authorization before enrollment, include the <code ljsid-1=\"\"></code> object when creating the payment method object for the customer session.":1,"#Exemplo: '438413b7-4921-41e4-b8f3-28a5a0141638'":1,"#de inscrição atual recebida como resposta ao ponto de extremidade":1,"#👍Recommended SDKFor a smooth integration experience, we recommend using the Android Seamless SDK. This option provides a flexible payment solution with pre-built UI components and customization options.\nThe Headless Android SDK provides a flexible, low-level integration option that gives you comple…":1,"#To disable this behavior, the merchant should set the property <code ljsid-1=\"\"></code> to <code ljsid-3=\"\"></code> in the method <code ljsid-5=\"\"></code>. Check the documentation for <a ljsid-7=\"\">Full SDK</a> or <a ljsid-9=\"\">Lite SDK </a>.":1,"#The loader is displayed from when the One Time Token is created until the merchant calls <code ljsid-1=\"\"></code> or <code ljsid-3=\"\"></code>. This way, the user experience is improved because they will see the loader while the merchant creates the payment.":1,"#Provide a checkbox on your checkout for users to choose if they want to save their card for future use. If the user selects this option, set <code ljsid-1=\"\"></code> when calling the <code ljsid-3=\"\"></code> function. You'll receive the <code ljsid-5=\"\"></code> in the function response.":1,"#With Headless SDK, you can save credit/debit cards for future purchases within the same payment request without the enrollment <a ljsid-1=\"\">integration</a>. You can obtain the <a ljsid-3=\"\">vaulted token</a> while executing the <code ljsid-5=\"\"></code> function in <a ljsid-7=\"\">Step 4</a>.":1,"#pyout":1,"#Lite Web SDK (Enrollment Web)":1,"#Lite SDK v1.2 (Payment)":1,"#Lite SDK v1.1 (Payment)":1,"#ee21718d-e911-42a9-ba13-46f492923fe9":1,"#6f673258-dd66-4901":1,"#Wed, 25 Jun 2025 23:45:21 GMT":1,"#sandbox_gAAAAABmWfidHN_tVpqWr2Zz9l5SiBkMcJt14mM2OpcJHl2c-PkVZNPqr6iAnvIbXr7W1NANcOFL76CfaEcMuXK8dBgDe7Fll_7CB-KJjY_2k0t27L6QAMnI-OvImKgjoYQ7t0IGI0HIUw2uHEd2nvgjf4WlEPRF0xwJ2Z0T__gedoSVZtGBpNMM-R2XPWIX-Y1pEfWv2GGOn5KllEwcDfDOIth4LLTLAc0ynYGrf9sPKVQsa39fykSRqnAEzWRNRb3dMoH-s6pe":1,"#bbfe2a40-2109-46ff-8c2d-d3f14059cb3c":1,"#3f10ec3c-a3ee-438b":1,"#Wed, 25 Jun 2025 22:16:47 GMT":1,"#{\"amount\":{\"currency\":\"CLP\"},\"name\":\"plan_007\",\"account_id\":[\"346787b3-c41e-4b4b-b211-56ddfad3bd6c\"],\"merchant_reference\":\"Test\",\"installments_plan\":[{\"installment\":1,\"rate\":1},{\"installment\":3,\"rate\":1},{\"installment\":6,\"rate\":1}],\"country_code\":\"CL\"}":1,"#gAAAAABmWfidC3r91F8PYcPPSU3eHiykDK7xTcFee7e4Gei5A5cj4shv9V6dpei8SrlX8TMFvJcMQRJuAUIcC3mSvQ3f4lX37fVu8o-irQ_a6fYzhbe0Y3rDI1hA-mNyJ6GsLdRAHud8zPJmq6ehF5wa1JcFtBdCyG-ncDPeHUlEXDIsWiEOvpu3PBdhy7gcEfuGKGJYCvPqTGte3ahNg0dF0mLAWTh6IbVIaUhwALbJKZS6VnPHDyDj6wVVz58daRvZ59Ny3INh":1,"#Skip link to Enrollment Guide":1,"#Skip link to Access the Demo Application":1,"#Skip link to Using Webhooks for Enrollment Status":1,"#newemail@example.com":1,"#Provider id.":1,"#Previous Page: Full SDK v1.2":1,"#c312c47c-4faa-4c64-b3da-893d93e32362":1,"#84ca35a3-5197-49bf":1,"#Tue, 24 Jun 2025 20:17:55 GMT":1,"#gAAAAABlrrZen1nsah5byjV6vB1kYA0M4sJNCH_h2pcu1WuwVBoiEAGBmZM6ZU06JvL6wVoriBTHwEmdQzisky5Fcr_g_pohTo1xqJu9KuLU0lrqU_Ys21wjecH7v9mhJN9z6cnw_XF9tkjHDrcEXSHReMa3Lqh7tM9LsPxWTjsV4X70a_wVIU8=":1,"#sandbox_gAAAAABlrrZelfNP-Ul1ZSX_vVOuT9VtsUrZ37aiYKbbfavwP_IQOKn7TAAqW5tAPfytClys0Nhp9AM0KAImadx5rwYwIvdtAAgaXUZZ6kHH6KIfHJ_fqTFT5Ngztogm-_7vQIqVmQVinb7I2w40UpbwdLhf2-5Ugam981Y1tyF3mQIo3bOtppc=":1,"#f67ea23d-7da0-4a9d-9b9b-062d418519ee":1,"#b3d9366e-2d3a-438f":1,"#Tue, 24 Jun 2025 20:13:26 GMT":1,"#<Your private-sgAAAAABlrrZe_r8wBl1yQwh5XWiYmZ9nre6BmaHnply3IRQIkcrduNJVWUxf3Rf28ZxX9B-hU0cO7IeUCiC--jyvyBuIi2P7vEHfuhU-RRSY8vxv4OevprfKi3z1MuaCUmT0hzsZdIUjMnK6JGgqdH-ohX_SUk0sg2zYg8vJ3UCvs69IezuXT1M=ecret-key>":1,"#prod_gAAAAABlrrZePIaM6BoKQkHV6nN4xxyyq5CpQVjqlR07NU-S3TW22G-Saj9NPRSDUT_UPp_cLbbgpgG8kmoi_Ugv8lJ1viSed1_QBKHJTlmjWxCtj0SP_2hrAhYSbInf7TzRsYXEY6UFnjVvbIBu6dYI8-Rlp6v6hKBYi-bLXYrOwmhTC0vuoGQ=":1,"#e41e26e9-a5ba-4543-a4b3-8376945c7379":1,"#ec4bc5a4-111e-436d":1,"#Tue, 24 Jun 2025 20:12:38 GMT":1,"#{\"type\":\"PAYMENTS\",\"start_date\":\"2025-06-23T00:00:00.000Z\",\"end_date\":\"2025-06-24T00:00:00.000Z\"}":1,"#856b891e-b33a-4120-bb20-a21bca1fa8ee":1,"#dae5aae1-c360-422b":1,"#Tue, 24 Jun 2025 20:12:00 GMT":1,"#{\"type\":\"PAYMENTS\",\"start_date\":\"2023-07-28\",\"end_date\":\"2023-07-29\"}":1,"#97b9dbda-3654-4e92-85db-cc440eee2264":1,"#59439bb5-97e6-4fa2":1,"#Tue, 24 Jun 2025 20:08:46 GMT":1,"#5f695d28-7fd9-45c1-9521-a77e2e23b7c8":1,"#0a05364b-b06e-4ef5":1,"#Tue, 24 Jun 2025 20:08:12 GMT":1,"#reembol":1,"#*KTP** (Kartu Tanda Penduduk)":1,"#To unenroll the payment method, you need to provide the":1,"#received when using the":1,"#, which is the":1,"#Tier of passenger loyalty program. Check the Airline information reference.":1,"#The passenger nationality (MAX 2; MIN 2; ISO 3166-1).":1,"#The passenger type (MAX 1; MIN 1). Check the Airline information reference.":1,"#Recommended SDK We recommend using the Web Seamless SDK for a smooth integration experience. This option provides a flexible payment solution with pre-built UI components and customization options.\nWelcome to the Yuno Lite SDK (Web) guide. This guide will help you get started with Yuno's payment sol…":1,"#Particularly for Brazil and some regions, merchants can accept <strong ljsid-1=\"\">meal vouchers</strong> as payment methods. “Voucher” is the name given to benefit cards that companies provide to their employees. They must be used to purchase specific products, such as groceries (meal allowance) and meals (restaurant allowance), in other words, the well-known meal and food vouchers.":1,"#As mentioned before, this feature allows <strong ljsid-1=\"\">merchants to split payments among multiple recipients</strong>, which is particularly useful for marketplace models where transactions need to be divided among different sellers or stakeholders. Merchants can specify how the payment is split, including the amounts, recipients, and any applicable fees.":1,"#As mentioned before, this feature allows merchants to split payments among multiple recipients, which is particularly useful for marketplace models where transactions need to be divided among different sellers or stakeholders. Merchants can specify how the payment is split, including the amounts, re…":1,"#Once the recipient creation is made, then the <strong ljsid-1=\"\">payment</strong> needs to be created specifying the recipient_id in the payment request as previously mentioned in the <a ljsid-3=\"\">Split Payments Marketplace</a> guides section.":1,"#Request recipient creation":1,"#<strong ljsid-0=\"\">B- Dynamic onboarding</strong>: If no credentials are provided, Yuno will initiate the onboarding process for the chosen provider (onboardings.type=ONBOARD_ONTO_PROVIDER):":1,"#<strong ljsid-0=\"\">A- Pre-onboarded accounts</strong>: If a submerchant has already completed the onboarding process with a specific provider (e.g., through an external dashboard or platform), the marketplace can supply the corresponding recipient_id during creation. In this scenario, no further onboarding is required, and the status will be immediately set to SUCCEEDED (onboardings.type=PREVIOUSLY_ONBOARDED).":1,"#These onboardings can be done by the marketplace owner outside Yuno, or Yuno can perform those onboardings.":1,"#For payment creation":1,"#For Onboarding":1,"#Fields required":1,"#In case you work as a marketplace and want your submerchants (recipients) to accept meal vouchers as well, you'll need to setup you provider connections in the Yuno dashboard and an onboarding needs to be made for each recipient and provider supported:":1,"#Skip link to Adyen Connection":1,"#To initialize the payment flow, create a new <code ljsid-1=\"\"></code> using the <a ljsid-3=\"\">Create checkout session</a> endpoint:":1,"#Retrieve a customer by ID":1,"#The customer's document type (MAX 6, MIN 2). Access <a ljsid-1=\"\">Document Type List</a> for more details.":1,"#Hide subpages for Android SDKs":1,"#Skip link to Using a vaulted token":1,"#First, create a customer or retrieve an existing customer ID using the <a ljsid-1=\"\">Create Customer</a> endpoint":1,"#Skip link to Customer and Merchant-Initiated Transactions":1,"#Skip link to Should I use Lite or Full Seamless SDK?":1,"#The merchant can use the currency conversion service of an external provider and send the corresponding information directly in the payment in Yuno. In order to use this, please contact your technical account manager to make sure that the information is set properly.":1,"#Conflict - Recipient cannot be blocked":1,"#Recipient blocked successfully":1,"#Next Page: Unblock Onboarding":1,"#Blocks a recipient. This prevents the recipient from receiving payments until unblocked.":1,"#Previous Page: Cancel Onboarding":1,"#This request enables you to retrieve details of a payout based on their <code ljsid-1=\"\"></code>, which needs to be provided in the request path.":1,"#This request enables you to retrieve details of a payout based on their `id`, which needs to be provided in the request path.":1,"#This service allows you to cancel or refund an existing payment. Our system will identify if a cancellation or a refund is necessary based on the payment, no <code ljsid-1=\"\"></code> is needed in this case. This service performs the following functions based on the status of the transaction:":1,"#Calling this endpoint will change the subscription status to PAUSED. This status can be changed to ACTIVE or CANCELED.":1,"#This feature allows merchants to split payments among multiple recipients, which is particularly useful for marketplace models where transactions need to be divided among different sellers or stakeholders. Merchants can specify how the payment is split, including the amounts, recipients, and any app…":1,"#Next Page: Block Onboarding":1,"#The Beneficiary's type of organization. GOVERNMENTAL, PUBLIC, NON_PROFIT, PRIVATE":1,"#The merchant category code (MCC) (MAX 235; MIN 1).":1,"#The seller's industry.":1,"#The seller's website URL.":1,"#The seller's industry (MAX 235; MIN 1). For more information access the Industry category reference page.":1,"#length between 1 and 235":1,"#The Beneficiary's date of birth in the YYYY-MM-DD format (MAX 10; MIN 10).":1,"#length between 10 and 10":1,"#Beneficiary's date of birth.":1,"#Beneficiary's type of organization.":1,"#15000":1,"#Hide subpages for":1,"#For example, a chatbot with access to these files could help a developer debug a payment integration, explain how vaulted tokens work, or walk through MCP setup, all based on real, structured content.":1,"#For the <code ljsid-1=\"\"></code> workflow, all the information is going to be stored in the <a ljsid-3=\"\"><code ljsid-3-0=\"\"></code></a> returned by Yuno's SDK, so you don't have to change your integration depending on the payment method. The basic structure of the payment will be the same for every payment method, as in the example below.":1,"#The <code ljsid-1=\"\"></code> workflow allows you to manage the entire payment experience by integrating directly with our APIs. Depending on your needs, you can choose from the following workflows:":1,"#<code ljsid-0=\"\"></code> Workflow":1,"#Poor translation":1,"#Good translation":1},"version":57340}]