> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ripio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Partner settings

> What Ripio configures on your account for the widget, and how the interface language is chosen.

The widget adapts to a handful of settings held against your Ripio account. This page is the single place to see what is negotiable, so you know what to ask for.

<Note>
  All of it is configured by Ripio, not by you at runtime. There is no API for changing these and no query parameter that overrides them — ask your Ripio contact.
</Note>

### What Ripio configures on your account

| Setting                                | What it changes                                                                                                                                                         |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your brand name                        | Shown in the interface — the "Back to …" button, for instance — and interpolated into the [emails Ripio sends your users](/ramps-api/widget/flows/emails).              |
| The fee shown to users                 | The percentage the user sees in the quote breakdown.                                                                                                                    |
| Your redirect URL                      | Where the widget sends the user when they are done. You provide it during onboarding. See [Returning to your app](/ramps-api/widget/get-started/returning-to-your-app). |
| The off-ramp QR deposit screen         | Whether the off-ramp ends on a deposit screen with a QR code, or redirects straight back to you. See [Selling crypto](/ramps-api/widget/flows/off-ramp).                |
| Whether the wallet address is required | Whether the address is mandatory in the `username` when you mint a session token. See [Authentication](/ramps-api/widget/get-started/authentication).                   |
| Your theme                             | The CSS file that styles the widget. See [Theming](/ramps-api/widget/configuration/theming).                                                                            |
| Enabled payment providers              | Which payment and payout methods are offered, per country. See [Countries & payment methods](/ramps-api/overview/countries/overview).                                   |
| The active Terms & Conditions          | What the user is asked to accept at sign-in. See [Sign-in and terms](/ramps-api/widget/flows/identity-and-terms).                                                       |

### Capabilities that can be turned on or off

Two parts of the widget only exist for accounts that have them enabled. Both are worth confirming before you design around them.

| Capability                      | What your users get, and what they lose without it                                                                                                                                                                                                                                                                     |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Identity verification           | With it, the widget runs the whole KYC flow before an operation. Without it, users transact without verifying. See [Identity verification](/ramps-api/widget/flows/kyc).                                                                                                                                               |
| Transaction history and refunds | With it, users see their past operations and can claim money back when something went wrong. Without it, both disappear — a refund is claimed from the history, so the two are enabled together. Refunds also need the per-ramp refund opt-in. See [History and refunds](/ramps-api/widget/flows/history-and-refunds). |

<Note>
  Emailed recovery links for a rejected off-ramp payout are enabled per account too, and fail closed: without them, no link is sent and the user resolves it through support. See [Recovering a rejected payout](/ramps-api/widget/flows/order-recovery).
</Note>

### Language

The widget is available in four locales: Spanish, Rioplatense Spanish, English and Portuguese.

It picks one in this order:

<Steps>
  <Step title="The _la parameter, if you sent one">
    Overrides everything else. See [Launch the widget](/ramps-api/widget/get-started/launch#query-parameters).
  </Step>

  <Step title="Otherwise, your account country">
    Argentina and Uruguay get Rioplatense Spanish, Brazil gets Portuguese, English-speaking countries get English.
  </Step>

  <Step title="Otherwise, Spanish">
    The fallback.
  </Step>
</Steps>

The same choice drives the language of the [emails Ripio sends](/ramps-api/widget/flows/emails).