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

# Uruguay

> Payout methods, timing, transaction limits, and required fields for payouts to Uruguay.

## Supported payout methods

| Payout method               | Currencies | Typical timing    |
| --------------------------- | ---------- | ----------------- |
| SPI                         | UYU        | 0-1 business days |
| International Wire Transfer | See below  | 0-3 business days |

Please refer to the sections below for the key required fields and other considerations for each supported method.

## SPI

Uruguayan local bank transfer

### Supported currencies

`UYU`

### Timing

| Attribute               | Value             |
| ----------------------- | ----------------- |
| Processing window       | Same day          |
| Typical delivery        | 0-1 business days |
| Business day dependency | Yes               |
| Supports instant        | No                |

### Transaction limits

| Limit type | Value |
| ---------- | ----- |
| Minimum    | None  |
| Maximum    | None  |

### Fields

#### Payout Method Type

<ResponseField name={"payout_method_type"} type="string" required>
  **Value:** `UruguaySpi`
</ResponseField>

#### Routing Type

<ResponseField name={"routing_type1"} type="string" required>
  **Value:** `bank_code`
</ResponseField>

#### Bank Code

<ResponseField name={"routing_value1"} type="string" required>
  Bank code (1-10 alphanumeric characters)

  **Validation:**

  * Between 1 and 10 characters (inclusive).
  * Must match this regular expression: `^[0-9A-Za-z]{1,10}$`

  **Example:** `001`
</ResponseField>

#### Routing Type 2

<ResponseField name={"routing_type2"} type="string" required>
  **Value:** `branch_code`
</ResponseField>

#### Branch Code

<ResponseField name={"routing_value2"} type="string" required={false}>
  Branch code (optional, 1-10 alphanumeric characters, required for certain banks like Banco Santander)

  **Validation:**

  * Between 1 and 10 characters (inclusive).
  * Must match this regular expression: `^[0-9A-Za-z]{1,10}$`

  **Example:** `01`
</ResponseField>

#### Account Number

<ResponseField name={"account_number"} type="string" required>
  Recipient's bank account number (up to 20 alphanumeric characters)

  **Validation:**

  * Between 1 and 20 characters (inclusive).
  * Must match this regular expression: `^[0-9A-Za-z]{1,20}$`

  **Example:** `1234567890`
</ResponseField>

#### Account Type

<ResponseField name={"account_type"} type="string" required>
  **Value:** One of `checking`, `savings`

  Type of bank account
</ResponseField>

#### Tax ID Type

<ResponseField name={"tax_id_type"} type="string" required={false}>
  **Conditional:** Required for Company payees only.

  **Value:** `BUSINESS_REGISTRATION_NUMBER`
</ResponseField>

#### RUT (Business Tax ID)

<ResponseField name={"tax_id"} type="string" required={false}>
  **Conditional:** Required for Company payees only.

  RUT (Registro Único Tributario) - 8-12 digits

  **Validation:**

  * Between 8 and 12 characters (inclusive).
  * Must match this regular expression: `^[0-9]{8,12}$`

  **Example:** `12345678`
</ResponseField>

#### Tax ID Type

<ResponseField name={"tax_id_type"} type="string" required={false}>
  **Conditional:** Required for Individual payees only.

  **Value:** `NATIONAL_ID`
</ResponseField>

#### CI Number

<ResponseField name={"tax_id"} type="string" required={false}>
  **Conditional:** Required for Individual payees only.

  CI (Cédula de Identidad) number (6-8 digits)

  **Validation:**

  * Between 6 and 8 characters (inclusive).
  * Must match this regular expression: `^[0-9]{6,8}$`

  **Example:** `12345678`
</ResponseField>

## International Wire Transfer

International wire transfer via SWIFT network

### Supported currencies

`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`

### Timing

| Attribute               | Value             |
| ----------------------- | ----------------- |
| Processing window       | Business days     |
| Typical delivery        | 0-3 business days |
| Business day dependency | Yes               |
| Supports instant        | No                |

### Transaction limits

| Limit type | Value |
| ---------- | ----- |
| Minimum    | None  |
| Maximum    | None  |

### Fields

#### Payout Method Type

<ResponseField name={"payout_method_type"} type="string" required>
  **Value:** `SwiftInternational`
</ResponseField>

#### Currency

<ResponseField name={"currency"} type="string" required>
  **Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
</ResponseField>

#### Recipient Bank SWIFT/BIC Code

<ResponseField name={"swift_code"} type="string" required>
  8 or 11 character SWIFT code of recipient bank

  **Validation:**

  * Between 8 and 11 characters (inclusive).
  * Must match this regular expression: `^[A-Z]{6}[A-Z0-9]{2}([A-Z0-9]{3})?$`
  * `bic`

  **Example:** `CBCUUYMMXXX`
</ResponseField>

#### Routing Type

<ResponseField name={"routing_type1"} type="string" required>
  **Value:** `bic`
</ResponseField>

#### Intermediary Bank SWIFT/BIC

<ResponseField name={"routing_value1"} type="string" required={false}>
  Optional, only needed if routing through correspondent bank

  **Validation:**

  * Between 8 and 11 characters (inclusive).
  * Must match this regular expression: `^[A-Z]{6}[A-Z0-9]{2}([A-Z0-9]{3})?$`
  * `bic`

  **Example:** `CHASUS33`
</ResponseField>

#### Account Number

<ResponseField name={"account_number"} type="string" required>
  **Validation:**

  * Between 1 and 50 characters (inclusive).
  * Must match this regular expression: `^[0-9A-Za-z]{1,50}$`

  **Example:** `1234567890`
</ResponseField>

### Notes

* All payments sent via SWIFT will be instructed such that the full value of the payment should credit the beneficiary. However, Acclaim is not in control of intermediary bank adherence to SWIFT messages and cannot guarantee that the beneficiary bank will not charge their account holder for receipt of payment.