# Authentication
Source: https://docs.withacclaim.com/api/auth
Learn how to authenticate with the Acclaim API. This guide explains secret and publishable keys, sandbox vs. production environments, and best practices for secure API access.
All requests to the Acclaim API require authentication using an API key. API keys are used to identify and authorize requests made by your organization.
You can create and manage your API keys in the **Acclaim Console** under **Settings → Developers → API Keys**.
## API Keys
Acclaim provides two types of keys:
| Type | Usage | Example |
| :------------------ | :---------------------------------------------------------------------- | :------------------ |
| **Secret key** | Used for server-side API requests. Must be kept private. | `sk_live_ABC123...` |
| **Publishable key** | Used in client-side integrations (for example, embeddable payee forms). | `pk_live_DEF456...` |
Secret keys allow full access to your account and must **never** be exposed in client code, logs, or version control.
## Authorization Header
Include your secret API key as a Bearer token in the `Authorization` header when making requests:
```text Text theme={null}
Authorization: Bearer sk_live_ABC123
```
## Environment
The same API endpoint is used for both sandbox and production requests:
```text Text theme={null}
https://api.withacclaim.com/v1
```
Sandbox and production environments are isolated by key — sandbox keys begin with `sk_test_`, while live keys begin with `sk_live_`.
## Example
```bash cURL theme={null}
curl https://api.withacclaim.com/v1/wallets \
-H "Authorization: Bearer sk_test_12345" \
-H "Content-Type: application/json"
```
## Best Practices
* Rotate API keys periodically.
* Limit key permissions to only what’s required.
* Revoke unused keys immediately.
* Never embed secret keys in client-side or mobile applications.
# Errors
Source: https://docs.withacclaim.com/api/errors
Learn how to handle errors returned by the Acclaim API. This document covers HTTP status codes, common error types, and best practices for debugging and retries.
The Acclaim API uses standard HTTP status codes and structured JSON error responses to indicate problems with a request. This guide explains how to interpret and handle those errors gracefully in your integration.
## Error Format
Every error response includes a top-level `error` object with details about what went wrong.
Example:
```json theme={null}
{
"error": {
"code": "invalid_request",
"message": "Missing required field: amount",
"details": {
"violations": [
{
"field": "amount"
}
]
},
"request_id": "req_7lYt4o2x"
}
}
```
### Status Codes
| Code | Meaning |
| ------- | ----------------------------------------- |
| **400** | Bad request or validation failure. |
| **401** | Missing or invalid API key. |
| **403** | The key is valid but lacks permission. |
| **404** | Resource not found. |
| **429** | Too many requests; retry after a delay. |
| **5xx** | Server error; safe to retry with backoff. |
### Error Codes
The `error.code` field is a stable, machine-readable string that helps automate error handling. Common values include:
* `invalid_request`
* `authentication_failed`
* `resource_not_found`
* `rate_limited`
* `internal_error`
* `permission_denied`
### Retry Guidance
| Scenario | Retry? | Recommendation |
| --------------------------------- | ------ | ----------------------------------------- |
| Network timeouts or 5xx responses | ✅ | Retry with exponential backoff. |
| 429 Too Many Requests | ✅ | Wait and retry after the indicated delay. |
| 400, 401, 403, 404 | 🚫 | Fix input or credentials before retrying. |
Log the `request_id` in error responses — it helps Acclaim Support trace issues quickly.
#### Rate Limits
Acclaim applies rate limits to ensure reliability for all clients. If you exceed the limit, the API will return a `429 Too Many Requests` response with a short retry window. Use exponential backoff and respect the `Retry-After` header if provided.
# Introduction
Source: https://docs.withacclaim.com/api/introduction
The Acclaim REST API enables you to automate claims and commission payments, manage wallets and balances, and more — all through a consistent RESTful interface.
Welcome to the Acclaim API reference. This reference provides technical details for integrating with Acclaim’s platform, including endpoints, parameters, and response formats.
## Base URL
All API requests are made to the following base URL:
```bash theme={null}
https://api.withacclaim.com/v1
```
Requests must be made over **HTTPS**. Unencrypted HTTP is not supported.
## Data Format
The API is **JSON-only**. Requests should include the following header:
```bash theme={null}
Content-Type: application/json
```
Responses are always returned in JSON.
You can read our [API Conventions](/developers/api-conventions) guide to learn more about how specific data types are formatted, such as, dates, monetary values, and object IDs.
## Versioning
As Acclaim evolves, new fields may be added to responses without notice. Removing or renaming fields will only occur in a versioned API release. You can safely ignore fields your integration does not recognize.
# Pagination
Source: https://docs.withacclaim.com/api/pagination
Learn how to paginate Acclaim API results using cursors for reliable, efficient access to large datasets.
Most list endpoints in the Acclaim API use cursor-based pagination. This approach allows you to efficiently navigate through large result sets without the inconsistencies of offset-based pagination.
## How It Works
When you request a list of resources (such as wallets, payees, or payouts), the response includes a few helpful fields for pagination:
```json theme={null}
{
"data": [
{ "id": "po_123", "object": "payout" },
{ "id": "po_124", "object": "payout" }
],
"has_more": true,
"next_cursor": "eyJ2IjoiMTI0In0="
}
```
| Field | Type | Description |
| ---------------- | ------- | ---------------------------------------------------------------------------------- |
| **data** | array | A list of returned objects. |
| **has\_more** | boolean | Indicates whether there are additional results beyond this page. |
| **next\_cursor** | string | A token to retrieve the next page of results. Pass this value to the next request. |
***
## Request Parameters
You can control pagination with the following query parameters:
| Parameter | Type | Description |
| ---------- | ------- | ---------------------------------------------------------------- |
| **limit** | integer | The maximum number of objects to return (default: 25, max: 100). |
| **cursor** | string | A cursor token from a previous response to fetch the next page. |
Example request:
```
GET /v1/payouts?limit=25&cursor=eyJ2IjoiMTI0In0=
```
***
## Example Flow
1. Request the first page:
```
GET /v1/payees?limit=25
```
2. Check the `has_more` field in the response.
If `true`, use the `next_cursor` value to request the next page:
```
GET /v1/payees?cursor=eyJ2IjoiMTI0In0=
```
3. Repeat until `has_more` is `false`.
***
## Tips
* Always use the `next_cursor` value from the previous response; cursors may expire after some time.
* Avoid guessing cursor values or reusing them across unrelated queries.
* If you need sorted results, apply consistent filters (e.g., by creation date).
* Treat each page of data as immutable — do not assume previously retrieved pages will remain identical over time.
# Create or update a payee by identifier
Source: https://docs.withacclaim.com/api/payees/create-or-update-a-payee-by-identifier
https://api.withacclaim.com/openapi.yaml put /payees/{identifier}
Idempotent endpoint to create or update a payee using a custom identifier.
If a payee with the given identifier exists, it will be updated.
If not, a new payee will be created with that identifier.
Returns 201 for creation, 200 for update.
# Retrieve a payee
Source: https://docs.withacclaim.com/api/payees/retrieve-a-payee
https://api.withacclaim.com/openapi.yaml get /payees/{payee_id}
# Update a payee
Source: https://docs.withacclaim.com/api/payees/update-a-payee
https://api.withacclaim.com/openapi.yaml patch /payees/{payee_id}
# Create a payer
Source: https://docs.withacclaim.com/api/payers/create-a-payer
https://api.withacclaim.com/openapi.yaml post /payers
Create a payer for payment collection. A unique identifier will be generated if not provided.
# Delete a payer
Source: https://docs.withacclaim.com/api/payers/delete-a-payer
https://api.withacclaim.com/openapi.yaml delete /payers/{payer_id}
# List payers
Source: https://docs.withacclaim.com/api/payers/list-payers
https://api.withacclaim.com/openapi.yaml get /payers
# Retrieve a payer
Source: https://docs.withacclaim.com/api/payers/retrieve-a-payer
https://api.withacclaim.com/openapi.yaml get /payers/{payer_id}
# Update a payer
Source: https://docs.withacclaim.com/api/payers/update-a-payer
https://api.withacclaim.com/openapi.yaml patch /payers/{payer_id}
# Delete a payment method
Source: https://docs.withacclaim.com/api/payment-methods/delete-a-payment-method
https://api.withacclaim.com/openapi.yaml delete /payers/{payer_id}/payment_methods/{payment_method_id}
Payment methods that have been used in a transaction cannot be deleted; returns 403 in that case. Deactivate instead.
# List payment methods for a payer
Source: https://docs.withacclaim.com/api/payment-methods/list-payment-methods-for-a-payer
https://api.withacclaim.com/openapi.yaml get /payers/{payer_id}/payment_methods
# Retrieve a payment method
Source: https://docs.withacclaim.com/api/payment-methods/retrieve-a-payment-method
https://api.withacclaim.com/openapi.yaml get /payers/{payer_id}/payment_methods/{payment_method_id}
# Update a payment method
Source: https://docs.withacclaim.com/api/payment-methods/update-a-payment-method
https://api.withacclaim.com/openapi.yaml patch /payers/{payer_id}/payment_methods/{payment_method_id}
# Cancel a payment request
Source: https://docs.withacclaim.com/api/payment-requests/cancel-a-payment-request
https://api.withacclaim.com/openapi.yaml post /payment_requests/{payment_request_id}/cancel
Cancel a payment request that is in RequiresPaymentMethod or RequiresAction status. Once canceled, the payment request can no longer be confirmed and funds collected.
# Confirm a payment request
Source: https://docs.withacclaim.com/api/payment-requests/confirm-a-payment-request
https://api.withacclaim.com/openapi.yaml post /payment_requests/{payment_request_id}/confirm
Confirm a payment request to complete the payment lifecycle. The payment request must be in RequiresPaymentMethod or RequiresAction status. This can be used when collecting a payment method to create and process a payment. The payment request status updates based on the result.
# Create a payment request
Source: https://docs.withacclaim.com/api/payment-requests/create-a-payment-request
https://api.withacclaim.com/openapi.yaml post /payment_requests
Create a payment request for collecting a payment. The request will be in RequiresPaymentMethod status until a payment method is provided.
# List payment requests
Source: https://docs.withacclaim.com/api/payment-requests/list-payment-requests
https://api.withacclaim.com/openapi.yaml get /payment_requests
# Retrieve a payment request
Source: https://docs.withacclaim.com/api/payment-requests/retrieve-a-payment-request
https://api.withacclaim.com/openapi.yaml get /payment_requests/{payment_request_id}
# Update a payment request
Source: https://docs.withacclaim.com/api/payment-requests/update-a-payment-request
https://api.withacclaim.com/openapi.yaml patch /payment_requests/{payment_request_id}
Update a payment request. Only provided fields will be updated. Can update description, reference, amount, currency, tokenization flags, expiration date, payer, payment method, IP address, and user agent.
# Add payouts to a batch
Source: https://docs.withacclaim.com/api/payout-batches/add-payouts-to-a-batch
https://api.withacclaim.com/openapi.yaml post /payout_batches/{batch_id}/add_items
# Cancel a payout batch
Source: https://docs.withacclaim.com/api/payout-batches/cancel-a-payout-batch
https://api.withacclaim.com/openapi.yaml post /payout_batches/{batch_id}/cancel
# Create a payout batch
Source: https://docs.withacclaim.com/api/payout-batches/create-a-payout-batch
https://api.withacclaim.com/openapi.yaml post /payout_batches
# List payout batches
Source: https://docs.withacclaim.com/api/payout-batches/list-payout-batches
https://api.withacclaim.com/openapi.yaml get /payout_batches
# List payouts in a batch
Source: https://docs.withacclaim.com/api/payout-batches/list-payouts-in-a-batch
https://api.withacclaim.com/openapi.yaml get /payout_batches/{batch_id}/items
# Process a payout batch
Source: https://docs.withacclaim.com/api/payout-batches/process-a-payout-batch
https://api.withacclaim.com/openapi.yaml post /payout_batches/{batch_id}/process
# Remove payouts from a batch
Source: https://docs.withacclaim.com/api/payout-batches/remove-payouts-from-a-batch
https://api.withacclaim.com/openapi.yaml post /payout_batches/{batch_id}/remove_items
# Retrieve a payout batch
Source: https://docs.withacclaim.com/api/payout-batches/retrieve-a-payout-batch
https://api.withacclaim.com/openapi.yaml get /payout_batches/{batch_id}
# Create a payout method for a payee
Source: https://docs.withacclaim.com/api/payout-methods/create-a-payout-method-for-a-payee
https://api.withacclaim.com/openapi.yaml post /payees/{payee_id}/payout_methods
# Delete a payout method
Source: https://docs.withacclaim.com/api/payout-methods/delete-a-payout-method
https://api.withacclaim.com/openapi.yaml delete /payees/{payee_id}/payout_methods/{payout_method_id}
Payout methods that have been used in a transaction cannot be deleted; return 403 in that case. Deactivate instead.
# Generate payout method schemas
Source: https://docs.withacclaim.com/api/payout-methods/generate-payout-method-schemas
https://api.withacclaim.com/openapi.yaml get /payout_method_schemas
Returns available payout method types and their field schemas (required fields, types, validation)
for the given country. Use this to build dynamic create forms for payout methods.
# List payout methods for a payee
Source: https://docs.withacclaim.com/api/payout-methods/list-payout-methods-for-a-payee
https://api.withacclaim.com/openapi.yaml get /payees/{payee_id}/payout_methods
# Retrieve a payout method
Source: https://docs.withacclaim.com/api/payout-methods/retrieve-a-payout-method
https://api.withacclaim.com/openapi.yaml get /payees/{payee_id}/payout_methods/{payout_method_id}
# Update a payout method
Source: https://docs.withacclaim.com/api/payout-methods/update-a-payout-method
https://api.withacclaim.com/openapi.yaml patch /payees/{payee_id}/payout_methods/{payout_method_id}
# Cancel a payout
Source: https://docs.withacclaim.com/api/payouts/cancel-a-payout
https://api.withacclaim.com/openapi.yaml post /payouts/{payout_id}/cancel
# Create a payout
Source: https://docs.withacclaim.com/api/payouts/create-a-payout
https://api.withacclaim.com/openapi.yaml post /payouts
Create a payout from a treasury account to a payee. Also creates a payout link for recipient choice.
# List payouts
Source: https://docs.withacclaim.com/api/payouts/list-payouts
https://api.withacclaim.com/openapi.yaml get /payouts
# Retrieve a payout
Source: https://docs.withacclaim.com/api/payouts/retrieve-a-payout
https://api.withacclaim.com/openapi.yaml get /payouts/{payout_id}
# Update a payout
Source: https://docs.withacclaim.com/api/payouts/update-a-payout
https://api.withacclaim.com/openapi.yaml patch /payouts/{payout_id}
# Create a refund for a payment
Source: https://docs.withacclaim.com/api/refunds/create-a-refund-for-a-payment
https://api.withacclaim.com/openapi.yaml post /payments/{payment_id}/refunds
Create and process a refund for a specific payment. The refund amount must not exceed the remaining refundable amount.
# List refunds
Source: https://docs.withacclaim.com/api/refunds/list-refunds
https://api.withacclaim.com/openapi.yaml get /refunds
# Retrieve a refund
Source: https://docs.withacclaim.com/api/refunds/retrieve-a-refund
https://api.withacclaim.com/openapi.yaml get /refunds/{refund_id}
# Cancel a setup request
Source: https://docs.withacclaim.com/api/setup-requests/cancel-a-setup-request
https://api.withacclaim.com/openapi.yaml post /setup_requests/{setup_request_id}/cancel
Cancel a setup request that is in RequiresPaymentMethod or RequiresAction status. Once canceled, the setup request cannot be used.
# Confirm a setup request
Source: https://docs.withacclaim.com/api/setup-requests/confirm-a-setup-request
https://api.withacclaim.com/openapi.yaml post /setup_requests/{setup_request_id}/confirm
Confirm a setup request to complete the setup lifecycle. The setup request must be in RequiresPaymentMethod or RequiresAction status. This will validate the payment method and tokenize it. The setup request status updates based on the result.
# Create a setup request
Source: https://docs.withacclaim.com/api/setup-requests/create-a-setup-request
https://api.withacclaim.com/openapi.yaml post /setup_requests
Create a setup request for securely storing a payment method. The request will be in RequiresPaymentMethod status until a payment method is provided.
# List setup requests
Source: https://docs.withacclaim.com/api/setup-requests/list-setup-requests
https://api.withacclaim.com/openapi.yaml get /setup_requests
# Retrieve a setup request
Source: https://docs.withacclaim.com/api/setup-requests/retrieve-a-setup-request
https://api.withacclaim.com/openapi.yaml get /setup_requests/{setup_request_id}
# Update a setup request
Source: https://docs.withacclaim.com/api/setup-requests/update-a-setup-request
https://api.withacclaim.com/openapi.yaml patch /setup_requests/{setup_request_id}
Update a setup request. Only provided fields will be updated. Can update description, payer, payment method, and expiration date.
# Deposit from a settlement account
Source: https://docs.withacclaim.com/api/treasury-funding/deposit-from-a-settlement-account
https://api.withacclaim.com/openapi.yaml post /treasury_accounts/{treasury_account_id}/fundings
# List settlement accounts
Source: https://docs.withacclaim.com/api/treasury-funding/list-settlement-accounts
https://api.withacclaim.com/openapi.yaml get /settlement_accounts
Settlement accounts are linked and verified in the Console. Creation via API is not available.
# List virtual accounts
Source: https://docs.withacclaim.com/api/treasury-funding/list-virtual-accounts
https://api.withacclaim.com/openapi.yaml get /virtual_accounts
Virtual Accounts are virtual bank account numbers for funding treasury accounts in a specific country and currency.
# Retrieve a settlement account
Source: https://docs.withacclaim.com/api/treasury-funding/retrieve-a-settlement-account
https://api.withacclaim.com/openapi.yaml get /settlement_accounts/{settlement_account_id}
# Retrieve a virtual account
Source: https://docs.withacclaim.com/api/treasury-funding/retrieve-a-virtual-account
https://api.withacclaim.com/openapi.yaml get /virtual_accounts/{virtual_account_id}
# Withdraw to a settlement account
Source: https://docs.withacclaim.com/api/treasury-funding/withdraw-to-a-settlement-account
https://api.withacclaim.com/openapi.yaml post /treasury_accounts/{treasury_account_id}/withdrawals
# Create a payee
Source: https://docs.withacclaim.com/api/treasury-payees/create-a-payee
https://api.withacclaim.com/openapi.yaml post /payees
# List payees
Source: https://docs.withacclaim.com/api/treasury-payees/list-payees
https://api.withacclaim.com/openapi.yaml get /payees
# Create a treasury account
Source: https://docs.withacclaim.com/api/treasury-treasury-accounts/create-a-treasury-account
https://api.withacclaim.com/openapi.yaml post /treasury_accounts
# List treasury accounts
Source: https://docs.withacclaim.com/api/treasury-treasury-accounts/list-treasury-accounts
https://api.withacclaim.com/openapi.yaml get /treasury_accounts
# List treasury transactions
Source: https://docs.withacclaim.com/api/treasury-treasury-accounts/list-treasury-transactions
https://api.withacclaim.com/openapi.yaml get /treasury_accounts/{treasury_account_id}/transactions
# Retrieve a treasury account
Source: https://docs.withacclaim.com/api/treasury-treasury-accounts/retrieve-a-treasury-account
https://api.withacclaim.com/openapi.yaml get /treasury_accounts/{treasury_account_id}
# Retrieve a treasury transaction
Source: https://docs.withacclaim.com/api/treasury-treasury-accounts/retrieve-a-treasury-transaction
https://api.withacclaim.com/openapi.yaml get /treasury_accounts/{treasury_account_id}/transactions/{transaction_id}
# Transfer between treasury accounts
Source: https://docs.withacclaim.com/api/treasury-treasury-accounts/transfer-between-treasury-accounts
https://api.withacclaim.com/openapi.yaml post /treasury_accounts/{treasury_account_id}/transfers
Create an internal transfer that moves funds from the source treasury account (path param) to a destination treasury account in the same account.
# Quickstart Guide
Source: https://docs.withacclaim.com/developers/accept
Acclaim Accept gives you a unified way to accept inbound payments across multiple payment service providers (PSPs). Whether you’re collecting premiums, deductibles, fees, or partner remittances, Accept provides a secure, PCI-friendly workflow for requesting payment details, creating payment requests, and reconciling incoming funds.
This guide walks through the core flow:
1. Create a **Payer** and **Setup Request**
2. Securely capture and store the payment method using **Payment Element**
3. Charge the payment method using **Payment Requests**
***
# Collecting Payment Details
## Creating a Payer
A **Payer** represents the individual or organization you want to collect money from. Typical examples include policyholders, brokers, employers, or business partners.
Creating a payer helps you tie payment activity and reconciliation back to a specific entity. The full list of request parameters can be found [here](/api/payers/create-a-payer).
### Example
```http theme={null}
POST https://api.withacclaim.com/v1/payers
Content-Type: application/json
Authorization: Bearer myApiKey
{
"given_name": "Jane",
"family_name": "Doe",
"email": "jane@example.com",
}
```
***
## Creating a Setup Request
A **Setup Request** lets your payer securely provide payment details through an Acclaim-hosted interface. Payment details never pass through your backend. The [Create Setup Request](/api/setup-requests/create-a-setup-request) documentation has more details about this endpoint.
```http theme={null}
POST https://api.withacclaim.com/v1/setup_requests
Content-Type: application/json
Authorization: Bearer myApiKey
{
"payer_id": "pyr_93LdZvQ19a"
}
```
Response: (abbreviated)
```json theme={null}
{
"id": "trq_7QvP1mNw3d",
"session_identifier": "trq_s3UBMW8il18ICbev1EUdKT1Fclwbnd3EUjxkqkpj6N6FfE6gJRWVEtO2ZpM95eRSThzxWdV77fLlMNNKovx0Rq5JEmdxNOv2gjMMlrGe90AEwy6f3Nxx05INZrAo4AyL"
}
```
***
## Collecting Details Securely with the Payment Element
```html theme={null}
```
***
# Processing Payments
Processing payments in Acclaim Accept happens in two major steps:
1. **Create a Payment Request**: an instruction to collect money from a payer
2. **Confirm the Payment Request**: by either (a) confirming a payment method supplied via UI, or (b) charging a previously saved token
Payment Requests provide a consistent flow for collecting premiums, deductibles, fees, or partner remittances across multiple PSPs.
## Creating a Payment Request
The full list of request parameters can be found [here](/api/payment-requests/create-a-payment-request).
```http theme={null}
POST https://api.withacclaim.com/v1/payment_requests
Content-Type: application/json
Authorization: Bearer myApiKey
{
"payer_id": "pyr_93LdZvQ19a",
"amount": 12000,
"currency": "usd",
"description": "April premium",
"payment_method_id": "pm_4NtzLp83Da"
}
```
## Confirming a Payment Request
Once the payment request has a payer and payment method assigned, or collected, it is ready to be confirmed, which will attempt to collect payment. The [Confirm Payment Request](/api/payment-requests/confirm-a-payment-request) documentation has more details.
```http theme={null}
POST https://api.withacclaim.com/v1/payment_requests/{payment_request_id}/confirm
Content-Type: application/json
Authorization: Bearer myApiKey
```
Response: (abbreviated)
```json theme={null}
{
"status": "succeeded"
}
```
## Tracking Payment State
You can track the status of a payment request in two ways:
1. **Polling from your backend**
```http theme={null}
GET /v1/payment_requests/{payment_request_id}
```
Useful for synchronous flows or to verify final state after a redirect.
2. **Listening for webhooks**
Acclaim sends webhook events for all major lifecycle changes:
* `payment_request.succeeded`
* `payment_request.failed`
* `setup_request.succeeded`
## Handling Failed Payments
When a payment request moves to a failed state:
You may:
* Present the payer with a link to re-enter payment details
* Trigger a new setup request
* Retry with a fallback PSP (if configured)
* Mark the invoice as overdue in your internal billing system
Acclaim returns granular error codes to help categorize failed payments (insufficient funds, authentication failed, payment method unsupported, network issues, etc.). See [Payment failures](/guides/accept/payment-failures#failure-codes) for the complete list of codes and messages.
***
# Summary
* A Payment Request is the core object for charging payers.
* Payments can be confirmed immediately using a saved token, or interactively using the Payment Element.
* Acclaim manages the full lifecycle, including PSP routing, authentication, and error handling.
* Use webhooks to reliably update your systems when payments succeed or fail.
# API Conventions
Source: https://docs.withacclaim.com/developers/api-conventions
This guide describes how Acclaim structures data across the API and how to interpret responses, work with identifiers, currencies, and timestamps.
## Object IDs
Every resource in Acclaim has a unique **object ID**. These IDs are string values that include a short prefix identifying the object type.
Examples:
* `po_dlZwQyd0Sn` — payout
* `pyee_KfIuLz83Ya` — payee
* `tac_b0TrsSg91h` — treasury account
* `bapo_r8PxTnQ5Dv` — batch payout
Treat these IDs as opaque strings — their internal structure may change over time, but prefixes remain consistent for readability.
When storing Acclaim object IDs in your own database, use a `VARCHAR(255)` column for full compatibility.
## Dates and Datetimes
All timestamps in Acclaim follow the **ISO 8601** format in UTC.
Examples:
* `2025-10-08T18:20:31Z` — full datetime with UTC timezone.
* `2025-10-08` — date-only value where applicable.
## Currency & Amounts
All monetary amounts are represented in the **smallest currency unit** for that currency:
| Currency | Smallest Unit | Example Value | Meaning |
| :------- | :------------ | :------------ | :------ |
| USD | Cents | 100 | \$1.00 |
| GBP | Pence | 100 | £1.00 |
| JPY | Yen | 100 | ¥100 |
Acclaim supports any ISO 4217 currency.
When performing calculations, use integers rather than floating point numbers to avoid rounding errors.
## Idempotency
You should design your integration to prevent duplicate submissions by reusing identifiers for business objects, such payees and payouts. In the event that you retry the same payout, for example, then the duplicate submission would be rejected.
# Batch Payouts
Source: https://docs.withacclaim.com/developers/batch-payouts
Batch payouts let you send many payouts at once — perfect for commission runs, claims reimbursements, or any recurring disbursement that involves multiple recipients. This guide covers when to use batches, how they work, and what to expect as they process.
## Why Use Batch Payouts
Batch payouts simplify repetitive or large-scale payments by allowing you to group them into a single operation.
Benefits include:
* Reduced API calls and easier reconciliation.
* Consistent tracking and reporting for related payouts.
* A single webhook event to track batch completion.
Example use cases:
* Monthly commission payouts to agents.
* Weekly vendor payments.
* Claims reimbursements to multiple members.
## How Batch Payouts Work
When you create a batch, you provide:
* A **funding account** (the account that funds all payouts).
* A list of **payouts** (each with amount, currency, and payee).
Each payout in the batch runs independently, but Acclaim manages them as one coordinated process.
Once created, Acclaim:
1. Validates all payout details.
2. Processes each payout in parallel.
3. Sends webhook events for both individual payouts and the batch as a whole.
## Batch Lifecycle
A typical batch flows through these stages:
| Stage | Description |
| :------------------ | :------------------------------------------------ |
| **created** | The batch was accepted and queued for processing. |
| **processing** | Payouts within the batch are being executed. |
| **succeeded** | All payouts finished successfully. |
| **partial\_failed** | Some payouts failed, but others succeeded. |
| **failed** | All payouts failed (e.g., insufficient funds). |
You’ll see these states reflected in both the Acclaim Console and webhook events.
## Webhooks for Batches
Acclaim sends events for both the batch and its individual payouts.
Common events include:
* `payout_batch.created`
* `payout_batch.updated`
* `payout_batch.succeeded`
* `payout_batch.failed`
* `payout_batch.canceled`
Each individual payout will also trigger its own events such as `payout.succeeded` or `payout.failed`.
You can listen for batch-level webhooks to summarize or reconcile results, and payout-level events for detailed reporting.
## Tips for Working with Batches
* **Use consistent reference IDs** to help match batches with internal reports.
* **Handle partial failures** gracefully by checking which payouts succeeded before retrying.
* **Use sandbox testing** to validate batch flows before moving to production.
## Next Steps
* Learn how to [handle webhook events](#) to track batch and payout statuses in real time.
* Explore [reconciliation and reporting](#) to close the loop on large payout runs.
## What’s Next
Learn how to **handle webhook events** track batch and payout statuses in real time. Explore **reconciliation and reporting** to close the loop on large payout runs.
# Concepts
Source: https://docs.withacclaim.com/developers/concepts
Before you start integrating with the Acclaim API, it helps to understand the core ideas that shape how payments and money movement work in the platform. These concepts describe the objects you’ll work with and the ways they connect.
Acclaim is organized around three core functional areas: **Accept**, **Disburse**, and **Treasury**. These map directly to the major money movement flows inside insurance operations.
## Accept
The **Accept** domain handles inbound payments such as premiums, deductibles, and fees from policyholders or partner organizations. It includes tools to request, receive, and securely store payment information.
### Payers
A **payer** represents the entity responsible for originating or funding an inbound payment. A payer typically is a policyholder or client. Payers are used to ensure accurate attribution, reporting, and reconciliation of incoming funds.
### Payment Requests
A **Payment Request** is an instruction to collect money from a payer.
Common use cases include:
* Premium collection
* Deductible collection
* Policy or administrative fees
A payment request includes:
* The payer
* The amount and currency
* A status lifecycle such as: `RequiresPaymentMethod`, `Processing`, `Succeeded`, `Failed`
* An associated payment once the funds have been captured
When paid, funds settle through the processor that processed the payment.
### Setup Requests
A **Setup Request** allows a payer to securely provide payment information, such as a card or bank account, without your system handling sensitive data.
Token characteristics:
* Collected through a secure Acclaim-hosted interface
* Returned as a reusable payment method token
* Can be used for future payment requests or recurring billing
* Significantly reduces PCI/PII exposure
## Disburse
The **Disburse** domain covers outbound payments: agent commissions, member reimbursements, provider payments, and vendor bill payments.
### Payees
A **payee** is anyone you need to pay — agents, brokers, providers, or members.
* Payees store payment details securely, so you don’t have to handle sensitive banking information yourself.
* Each payee can have multiple payout methods (e.g., bank account, card, digital wallet).
### Payouts
A **payout** transfers funds from one of your accounts to a payee.
* Each payout has an amount, currency, and a destination (linked to a payee).
* Payouts can generate **payout links**, letting you send a secure payment link to the recipient for them to choose how they want to be paid.
### Payout Batches
A **payout batch** is a group of payouts processed together.
* Useful for commissions or recurring disbursements.
* Batches let you track success and failure across many payments at once.
## Treasury
The **Treasury** domain manages where funds live and how they move — including treasury accounts, ledgering, settlement accounts, virtual accounts, and internal transfers.
### Accounts
A **treasury account** is an account that can hold funds and send or receive money. Treasury accounts are the foundation of how Acclaim tracks and moves value.
* You can create one or many accounts for operational needs. For example, separate accounts for collecting premium, paying commissions, and paying claims.
* Accounts always have a balance denominated in a single currency.
* You can transfer funds between accounts.
### Settlement Accounts
A **settlement account** is an external bank or treasury account that connects your organization to the outside financial system.
* It can **fund your accounts** — pulling money into your treasury account so you can make payouts.
* It can **withdraw from accounts** — letting you return unused funds or move balances back to your external bank account.
* Each organization typically links one or more settlement accounts, depending on currency or operational needs.
### Virtual Accounts
A **virtual account** is a unique, system-generated bank account number created in a specific country and currency for the purpose of automatically reconciling incoming funds into your Acclaim treasury accounts.
Virtual accounts make it easier to fund accounts from an external bank account, partners, or insurers in their local markets. Each virtual account is tied to a single Acclaim treasury account and reflects inbound transfers in real time once funds are received. Funds added via virtual accounts are available on a faster timeframe than funds added via a settlement account.
## How It All Fits Together
Think of it like this:
1. **Accept**: Payment requests or setup requests collect funds from payers.
2. **Treasury**: Inbound funds settle into treasury accounts via virtual accounts; treasury tools manage balances and movement amongst first-party and third-party account holders.
3. **Disburse**: Funds in accounts are used for payouts to payees.
## What’s Next
With the fundamentals covered, you are ready to start integrating. For a **Console-oriented walkthrough** of your first payout, see **[Sending your first payout](/guides/disburse/sending-your-first-payout)**. For **webhooks** and API-driven status updates, continue with **[Webhooks](/developers/webhooks)** and the **API Reference**.
# Embedded Elements
Source: https://docs.withacclaim.com/developers/embeddable-components
Acclaim.js is a comprehensive payment processing SDK that handles credit cards, digital wallets, and alternative payment methods with built-in PCI compliance and 3D Secure support.
## Quick Start
### Installation
```html theme={null}
```
### Basic Setup
```javascript theme={null}
const acclaim = new Acclaim({
publishableKey: 'pk_live_your_api_key_here',
});
```
## Core Concepts
### Requests vs Elements
Acclaim uses two main concepts:
* **Requests**: Server-side objects that define what you want to do (payment or setup)
* **Elements**: Client-side UI components that collect payment information
### Payment Request
1. Create a **Payment Request** for immediate processing
2. Create an **Element** to collect payment info
3. Mount the element to your page
4. Submit the element when the user clicks the pay button
### Setup Request
1. Create a **Setup Request** to save payment methods
2. Create an **Element** to collect payment info
3. Mount the element to your page
4. Submit the element when the user clicks the submit button
## Payment Processing
### Creating Payment Requests
See the [Payment Requests](/api/payment-requests/create-a-payment-request) documentation for more information on how to create a payment request.
### Creating and Mounting Elements
```javascript theme={null}
// Create payment element
const element = await acclaim.createElement(paymentRequest.session_identifier, {
theme: 'clean', // 'clean', 'material', 'minimal'
locale: 'en', // Language code
appearance: {
primaryColor: '#007bff',
borderRadius: '8px',
fontFamily: 'Inter, sans-serif'
}
});
// Mount to DOM
await element.mount('#payment-container');
```
### Element Options
| Parameter | Type | Description |
| ------------ | ------ | -------------------------------------------------- |
| `theme` | string | Visual theme: `'clean'`, `'material'`, `'minimal'` |
| `locale` | string | Language code (e.g., `'en'`, `'fr'`, `'es'`) |
| `appearance` | object | Custom styling options |
### Appearance Customization
```javascript theme={null}
const element = await acclaim.createElement(sessionId, {
appearance: {
primaryColor: '#6366f1', // Brand color
backgroundColor: '#ffffff', // Background color
textColor: '#1f2937', // Text color
borderColor: '#d1d5db', // Border color
borderRadius: '8px', // Border radius
fontFamily: 'Inter, sans-serif', // Font family
fontSize: '16px', // Base font size
padding: '12px', // Input padding
focusColor: '#3b82f6' // Focus highlight color
}
});
```
### Handling Payment Completion
```javascript theme={null}
try {
// Submit the payment
const result = await element.submit();
if (result.status === 'succeeded') {
// Payment successful
window.location.href = '/success';
} else if (result.status === 'requires_action') {
// 3D Secure or additional authentication required
console.log('Additional authentication in progress...');
}
} catch (error) {
console.error(error.message);
}
```
### Complete Payment Example
```javascript theme={null}
async function setupPayment() {
// Initialize Acclaim
const acclaim = new Acclaim({
publishableKey: 'pk_test_your_api_key',
});
// Create and mount element
const element = await acclaim.createElement(paymentRequest.session_identifier);
await element.mount('#payment-container');
// Handle the submission of the form the Payment Element is embedded within
const theForm = document.getElementById('payment-form');
theForm.addEventListener('submit', async (e) => {
e.preventDefault();
// Hide any previous error messages
hideError();
const submitButton = document.querySelector('#submit-button');
submitButton.disabled = true;
submitButton.textContent = 'Processing...';
try {
const result = await element.submit();
if (result.status === 'succeeded') {
window.location.href = '/success';
} else {
throw new Error(result.error?.message || 'Payment failed');
}
} catch (error) {
showError(error.message);
submitButton.disabled = false;
submitButton.textContent = 'Pay Now';
}
return false;
});
}
function showError(message) {
const errorElement = document.querySelector('#error-message');
errorElement.textContent = message;
errorElement.style.display = 'block';
}
function hideError() {
const errorElement = document.querySelector('#error-message');
errorElement.style.display = 'none';
}
```
## Setup (Saving Payment Methods)
### Creating a Setup Request
See the [Setup Requests](/api/setup-requests/create-a-setup-request) documentation for more information on how to create a setup request.
### Creating and Mounting Elements
```javascript theme={null}
// Create payment element
const element = await acclaim.createElement(setupRequest.session_identifier, {
theme: 'clean', // 'clean', 'material', 'minimal'
locale: 'en', // Language code
appearance: {
primaryColor: '#007bff',
borderRadius: '8px',
fontFamily: 'Inter, sans-serif'
}
});
// Mount to DOM
await element.mount('#save-card-container');
```
### Handling Setup
```javascript theme={null}
try {
// Save the payment method
const result = await setupRequest.submit();
if (result.status === 'succeeded') {
// Payment successful
window.location.href = '/success';
} else if (result.status === 'requires_action') {
// 3D Secure or additional authentication required
console.log('Additional authentication in progress...');
}
} catch (error) {
console.error(error.message);
}
```
## 3D Secure Authentication
Acclaim automatically handles 3D Secure authentication when required. The process is transparent to your integration.
### Manual 3DS Handling
```javascript theme={null}
// If you need manual control over 3DS
try {
const result = await paymentRequest.submit();
if (result.status === 'requires_action') {
// Handle 3DS authentication
const authResult = await acclaim.handle3DSecure();
if (authResult.status === 'succeeded') {
// Authentication successful
console.log('Payment completed after 3DS');
}
}
} catch (error) {
console.error('3DS authentication failed:', error);
}
```
## Digital Wallets
### Apple Pay
Apple Pay is automatically detected on supported devices and browsers. No additional setup required.
**Requirements:**
* Safari browser
* macOS with Touch ID or iPhone/iPad with Face ID/Touch ID
* Valid Apple Pay merchant certificate (handled by Acclaim)
### Google Pay
Google Pay is automatically detected when the Google Pay API is available.
**Requirements:**
* Supported browser (Chrome, Edge, etc.)
* Valid Google Pay merchant configuration
### PayPal
In order to use the PayPal payment method, you must supply a `return_url` and `cancel_url` in your payment request.
## Event Handling
### Element Events
```javascript theme={null}
element.on('ready', () => {
console.log('Element is ready');
});
element.on('change', (state) => {
console.log('Element state changed:', state);
// Update submit button based on validation
document.querySelector('#submit-btn').disabled = !state.complete;
});
element.on('success', (result) => {
console.log('Payment element completed:', result);
});
element.on('error', (error) => {
console.error('Element error:', error);
});
```
### Available Events
| Event | Description | Payload |
| --------- | -------------------------------------- | ------------------------------ |
| `ready` | Element is mounted and ready | - |
| `change` | Form validation state changed | `{ complete, empty, invalid }` |
| `success` | Payment element completed successfully | `{ id, ... }` |
| `error` | An error occurred | `{ code, message, ... }` |
## Error Handling
### Common Error Types
```javascript theme={null}
element.on('error', (error) => {
switch (error.code) {
case 'validation_error':
// Invalid card number, expired card, etc.
showFieldError(error.field, error.message);
break;
case 'card_declined':
// Card was declined by issuer
showError('Your card was declined. Please try a different payment method.');
break;
case 'network_error':
// Network connectivity issues
showError('Network error. Please check your connection and try again.');
break;
case 'api_error':
// Server-side error
showError('Something went wrong. Please try again.');
break;
default:
showError(error.message);
}
});
```
### Error Object Structure
```javascript theme={null}
{
code: 'validation_error',
message: 'Your card number is invalid.',
details: [
{
message: 'Your card number is invalid.',
field: 'cardNumber',
code: 'invalid_number'
}
]
}
```
## Styling and Themes
### Built-in Themes
```javascript theme={null}
// Default theme
const element = await acclaim.createElement(sessionId, {
theme: 'clean'
});
// Material theme
const element = await acclaim.createElement(sessionId, {
theme: 'material'
});
// Minimal theme
const element = await acclaim.createElement(sessionId, {
theme: 'minimal'
});
```
### Custom Styling
```javascript theme={null}
const element = await acclaim.createElement(sessionId, {
appearance: {
// Colors
primaryColor: '#6366f1',
backgroundColor: '#ffffff',
textColor: '#1f2937',
placeholderColor: '#9ca3af',
borderColor: '#d1d5db',
focusColor: '#3b82f6',
errorColor: '#ef4444',
// Typography
fontFamily: 'Inter, -apple-system, sans-serif',
fontSize: '16px',
fontWeight: '400',
// Layout
borderRadius: '8px',
borderWidth: '1px',
padding: '12px 16px',
// States
':hover': {
borderColor: '#9ca3af'
},
':focus': {
borderColor: '#3b82f6',
boxShadow: '0 0 0 3px rgba(59, 130, 246, 0.1)'
},
'.invalid': {
borderColor: '#ef4444'
}
}
});
```
## Testing
### Test Cards
Use these test card numbers in sandbox mode:
| Card Type | Number | CVC | Expiry |
| ---------------- | ------------------ | ------------ | --------------- |
| Visa | `4242424242424242` | Any 3 digits | Any future date |
| Visa (debit) | `4000056655665556` | Any 3 digits | Any future date |
| Mastercard | `5555555555554444` | Any 3 digits | Any future date |
| American Express | `378282246310005` | Any 4 digits | Any future date |
| Declined | `4000000000000002` | Any 3 digits | Any future date |
| 3D Secure | `4000000000003220` | Any 3 digits | Any future date |
### Test Environment
```javascript theme={null}
const acclaim = new Acclaim({
publishableKey: 'pk_test_your_test_key',
});
```
### Webhook Testing
Use tools like ngrok to test webhooks locally:
```bash theme={null}
# Install ngrok
npm install -g ngrok
# Expose local server
ngrok http 3000
# Use the HTTPS URL for webhook endpoint
```
## API Reference
### Acclaim Constructor
```javascript theme={null}
new Acclaim(options)
```
**Options:**
* `publishableKey` (string, required): Your Acclaim publishable API key
### Methods
#### `createPaymentElement(sessionId, container)`
Creates a payment element for the given request.
**Returns:** `Promise`
### PaymentElement Methods
#### `mount(container)`
Mount the element to a DOM container.
**Parameters:**
* `container` (string|Element): CSS selector or DOM element
**Returns:** `Promise`
#### `unmount()`
Remove the element from the DOM.
#### `on(event, callback)`
Listen for element events.
**Parameters:**
* `event` (string): Event name
* `callback` (function): Event handler
#### `update(options)`
Update element appearance or configuration.
**Parameters:**
* `options` (object): New options to apply
#### `submit()`
Confirm and process the payment or setup.
**Returns:** `Promise`
#### `handle3DSecure(options)`
Manually handle 3D Secure authentication.
**Returns:** `Promise`
# Failed Payouts
Source: https://docs.withacclaim.com/developers/failed-payouts
Even the best payment systems encounter occasional payout failures. This guide explains how Acclaim reports failed payouts, how to diagnose the cause, and how to resolve them quickly.
A payout can fail for a variety of reasons — such as invalid recipient details, closed bank accounts, or compliance issues. When a payout fails, Acclaim updates its status, notifies you via webhook, and automatically returns the funds to the funding account.
Your system should be designed to listen for these events, update records, and, if appropriate, reissue the payout once the issue is corrected.
***
## Common Causes
Payout failures can happen for several reasons:
* **Incorrect payee details** — wrong account number, routing number, or payment method.
* **Closed or restricted accounts** — the recipient’s bank rejected the payment.
* **Insufficient account balance** — not enough funds were available at the time of execution.
* **Currency or jurisdiction mismatch** — the payment route was not supported for the destination country or currency.
* **Compliance or sanctions hold** — payment blocked due to screening requirements.
Each failed payout also includes a specific `failure_code` and `failure_message` to help you identify what went wrong. See [Failures and reversals](/guides/disburse/failures-and-reversals#failure-codes) for the complete list of codes and messages.
***
## Detecting Failures
You can detect failed payouts through several channels:
* **Webhooks:** Subscribe to the `payout.failed` event to receive instant notification when a payout cannot be completed.
* **API:** Retrieve a payout by ID and inspect the `status` field — it will show `failed`.
* **Console:** View detailed failure reasons, timestamps, and related account adjustments in the Acclaim Console.
Example webhook event:
```json JSON theme={null}
{
"id": "evt_MjdYqzLbsS",
"type": "payout.failed",
"data": {
"object": {
"id": "po_vkj7BPRPr9",
"payment_amount": 10000,
"payment_currency": "usd",
"failure_code": "payout.beneficiary_account_closed",
"failure_message": "The beneficiary account is closed and cannot receive funds."
// truncated for brevity
}
}
}
```
***
## Resolving Failed Payouts
When a payout fails:
1. **Review the failure reason** — check the `failure_code` and `failure_message` fields.
2. **Correct the issue** — update payee information, verify account balance, or contact your banking team if necessary.
3. **Reissue the payout** — create a new payout once the issue is resolved.
Failed payouts are automatically reversed — the full amount returns to the funding account and becomes available for future payouts.
***
## Webhook Events
Important events to handle when managing failed payouts:
| Event | Description |
| ------------------------------ | ------------------------------------------ |
| `payout.failed` | A payout could not be completed. |
| `treasury.transaction.created` | A payout reversal transaction was created. |
These events can trigger automated workflows — such as retrying payouts, notifying your team, or updating accounting records.
***
## Best Practices
* Ensure accounts remain adequately funded before initiating large batches.
* Implement webhook listeners to handle failures automatically.
* Avoid retrying the same payout ID; always create a new one after correction.
# Funding
Source: https://docs.withacclaim.com/developers/funding
Before you can send payouts, your treasury accounts need to be funded. This guide explains how to link a settlement account, move funds into an account, and confirm available balances.
Each organization in Acclaim has one or more **treasury accounts** that hold funds. Accounts are funded from **settlement accounts**, which are external bank or treasury accounts you connect to Acclaim, or **virtual accounts**, which are unique bank details that allow you to send funds into your account.
Funding is what enables your organization to make payouts and cover related fees. You can add funds manually from the Acclaim Console or automatically through the API.
## Linking a Settlement Account
Settlement accounts connect your Acclaim environment to your external banking network.
You can add and manage settlement accounts in the **Acclaim Console** under **Treasury → Funding → Settlement Accounts**.
* Each settlement account is tied to a specific currency.
* You can link multiple settlement accounts if you manage funds across currencies or business units.
* All settlement accounts must be verified before they can fund accounts or receive withdrawals.
## Funding Through the Console
You can fund an account directly from the Acclaim Console:
Navigate to **Treasury** in the sidebar.
Choose the account you want to fund.
Click **Add Funds**.
Select a linked **settlement account**.
Enter an amount and confirm.
The Console will display the transaction once the funds are in flight and update the account balance once they are cleared.
## Funding via API
Funding can also be initiated programmatically through the API.
At a high level, you’ll specify:
* The **settlement account ID** (source of funds).
* The **account ID** (destination).
* The **amount** and **currency**.
You can then monitor the transfer status via webhooks or polling the transaction resource.
This enables automated funding workflows — for example, topping up an account when its balance falls below a defined threshold.
## Checking Account Balances
To verify that an account has sufficient funds:
* Open the **Accounts** page in the Console to view balances for each account.
* Use the API to retrieve account details and check the `balance` field.
* Subscribe to the `treasury.transaction.created` webhook to get real-time updates.
Account balances in the API are always shown in the smallest currency unit (for example, 100 = \$1.00).
## Best Practices
* **Separate operational accounts by purpose** — such as commissions, claims, or reimbursements.
* **Monitor balances regularly** to avoid failed payouts due to insufficient funds.
* **Automate funding** with rules or schedules that trigger top-ups when needed.
* **Reconcile** funding transactions alongside payout activity to maintain accuracy across systems.
## What’s Next
Once your accounts are funded, you are ready to send your first payout. For a user guide walkthrough, see **[Sending your first payout](/guides/disburse/sending-your-first-payout)**.
# Welcome
Source: https://docs.withacclaim.com/developers/getting-started
Welcome to Acclaim — the payments infrastructure built for the insurance industry.
We help carriers, MGAs, TPAs, and brokers move money smarter and faster. Whether you’re sending commissions, paying claims, or creating new digital insurance products, Acclaim gives you modern rails to build on.
This guide introduces the basics of how to begin using Acclaim and sets you up to explore the core concepts behind the API.
## Create an Account
In order to access the Acclaim API you need to first create an account. Once you have an account, sign in to the Acclaim Console. From the dashboard, you can manage settings, create treasury accounts, and issue API keys for both live and sandbox environments.
If you want to experiment safely, use a **sandbox account**. Sandbox accounts share the same API base URL as production but use separate API keys and won’t move real money.
## API Keys
Acclaim uses API keys to authenticate requests. You’ll find them under **Settings → Developers → API Keys** in the console.
* **Secret key** — used on your server to authenticate API calls. Keep it private.
* **Publishable key** — safe to use client-side with Acclaim’s embeddable components.
## What’s Next
You’re ready to dive deeper into how Acclaim models money movement and payment flows.
Start with the **Concepts** guide to understand these building blocks and how they fit together before you begin integrating.
# Payment Request Lifecycle
Source: https://docs.withacclaim.com/developers/payment-request-lifecycle
A Payment Request represents an attempt to collect money from a payer. It moves through several states from creation to completion. These states describe what Acclaim needs, what the payer must do, and what your backend should expect as the request progresses.
The lifecycle is designed to support:
* Card payments (including 3-D Secure authentication)
* Wallet payments
* Bank-based methods
* Apple Pay and Google Pay
* PSP fallbacks and retries
* Multi-step flows where payers provide payment details interactively
This guide explains each lifecycle state and the transitions between them.
***
# Overview of States
A payment request can move through the following states:
* `RequiresPaymentMethod`
* `RequiresAction`
* `Processing`
* `Authorized`
* `Succeeded`
* `Failed`
* `Canceled`
Each state has clearly defined meaning and transition rules.
***
# State Definitions
A payment request is created when your backend calls `POST /payment_requests`. From here, the request will branch into the next appropriate state based on what Acclaim needs.
***
### `RequiresPaymentMethod`
Acclaim needs a payment method before it can proceed.
A payment request enters this state when:
* No payment method was provided at creation, and
* You intend for the payer to complete the payment through the UI
You will typically render a **Payment Element** here. Once the payer enters a payment method, your UI should call:
```
paymentElement.submit();
```
This moves the request forward into `Processing`.
***
### `RequiresAction`
Acclaim requires payer interaction, such as authentication (e.g. **3-D Secure**).
This state occurs when:
* The card issuer requires authentication
* A payment method triggers a regulatory confirmation
* The PSP indicates a user approval step is needed
Your UI should guide the payer through the action. Acclaim.js automatically handles supported flows.
Once completed, the request transitions to `Processing`.
***
### `Processing`
The payment is being transmitted to the PSP, but the outcome is not yet final.
A request enters `Processing` when:
* A valid payment method has been provided, and
* No further user action is required
Acclaim handles:
* Authorization attempts
* Network routing
* PSP-specific flows
* Fallback logic
From `Processing`, the payment may transition to:
* `Authorized`
* `Succeeded`
* `Failed`
***
### `Authorized`
The PSP has authorized the payment, but settlement has not yet occurred.
This state only appears for payment methods that support two-step Authorization and Capture flows. You have to select an auth capture flow when creating the payment request. Acclaim automatically captures the payment in most insurance workflows instead of doing it as a separate step.
Once capture succeeds, the payment transitions to `Succeeded`.
***
### `Succeeded`
The payment is fully settled.
This is the terminal success state. You receive a `payment_request.succeeded` webhook. You can trigger downstream events such as:
* Policy activation
* Coverage reinstatement
* Claim evaluation
* Ledger reconciliation
***
### `Failed`
The payment could not be completed.
A payment request enters `Failed` when:
* The payment method is declined
* Authentication fails
* The payer exits required-action flow
* The PSP returns an unrecoverable error
* Network or routing issues prevent completion
See [Payment failures](/guides/accept/payment-failures#failure-codes) for the complete list of failure codes and messages.
You receive a `payment_request.failed` webhook. Your system may:
* Prompt the payer to update their payment method
* Initiate a fallback PSP route
* Retry with additional validation
* Mark the invoice or policy period as unpaid
***
### `Canceled`
A payment request can be canceled intentionally. This state appears when you call the [Cancel Payment Request](/api/setup-requests/cancel-a-setup-request) API before the payment request is succeeded. Canceled payments do not attempt collection and are not considered failures.
***
# Lifecycle Diagram
A diagram of the full lifecycle is shown below:
***
# Summary
* A **Payment Request** is the core object for charging payers.
* It moves through well-defined states describing what Acclaim needs next.
* UI-driven payments flow through:\
`RequiresPaymentMethod → RequiresAction → Processing`
* Server-driven payments typically flow through:\
`Created → Processing → Succeeded`
* Webhooks should be used to reliably update internal systems.
The lifecycle design supports modern multi-PSP flows, authentication steps, retries, and clear back-office reconciliation.
# Reconciliation & Reporting
Source: https://docs.withacclaim.com/developers/reconciliation-reporting
Reconciliation is an essential part of financial operations. With Acclaim, you can track how money moves across treasury accounts, payouts, and settlement accounts — giving you confidence that everything adds up. This guide covers how to reconcile payments and generate meaningful reports for your finance or accounting teams.
Every payout, account transfer, and funding action creates a financial record. Reconciliation helps you:
* Verify that the money leaving your accounts matches your internal accounting system.
* Detect failed or delayed payouts quickly.
* Produce audit-ready reports for compliance and finance teams.
***
## Key Data Sources
Acclaim provides several sources of truth for reconciliation:
| Source | What It Contains | How to Access |
| ----------------------- | ------------------------------------------------------------------------ | ---------------------- |
| **Account Balances** | Current and historical balances for all accounts. | API or Console. |
| **Payouts** | Individual payout records with status, amount, and payee. | API or Console. |
| **Batches** | Aggregated payout runs with success/failure summaries. | API or Console. |
| **Settlement Accounts** | Records of inbound and outbound transfers between Acclaim and your bank. | Console. |
| **Webhooks** | Real-time events for updates on payout or balance changes. | Your webhook endpoint. |
***
## Reconciliation Flow
A simple reconciliation workflow looks like this:
1. **Export payout data** from the Acclaim Console or API.
2. **Match payouts to internal transactions** in your accounting, claim, or policy administration system.
3. **Verify account balances** align with expected debits and credits.
4. **Check settlement transfers** against your external bank statements.
5. **Log discrepancies** for manual review or correction.
You can automate this process using the Acclaim API or by subscribing to relevant webhooks.
***
## Common Scenarios
### Matching Payouts to Policies or Claims
Attach your own `reference` when creating payouts or batches. This field helps you link Acclaim transactions to internal records during reconciliation.
### Handling Partial Failures
If a batch has both successful and failed payouts, reconcile the successful ones immediately and mark the failed ones for reprocessing.
### Multi-Currency Operations
Reconcile each currency independently. Treasury accounts and settlement accounts are always denominated in a single ISO currency.
***
## Reporting in the Console
The Acclaim Console provides visibility into financial activity:
* **Accounts view** — track balances and transaction histories.
* **Payouts view** — search, filter, and export payout data.
* **Batches view** — review aggregated results across payout runs.
* **Reports tab** — generate exports for accounting or audit teams.
***
## Automating Reporting
Use the Acclaim API to build automated reports that run on a schedule.
Common patterns include:
* Daily payout summary by account or business unit.
* Weekly reconciliation report matching payouts to funding activity.
* Alerts for failed or delayed payouts.
Webhook events can also trigger these reports automatically as data changes.
# Testing
Source: https://docs.withacclaim.com/developers/testing
Before you go live with Acclaim, you should test your integration in a safe environment. The Acclaim sandbox lets you create payers, save payment methods, and run payment requests without moving real money.
This guide explains:
* How the Acclaim test environment behaves
* How to use test cards and test bank accounts
* How to test the full flow from saving payment method to payment requests and webhooks
***
## Test environment overview
The Acclaim test environment is designed to behave as close to production as possible, with a few key differences.
* **No real charges are made**. Test cards and bank accounts never pull or deposit real funds.
* **Same API base URL**:\
`https://api.withacclaim.com/v1`\
You switch between test and live using different API keys.
* **Separate API keys**. Use test keys from the Acclaim Console when running automated tests.
* **Lifecycle and webhooks**. Payment requests in test mode still move through lifecycle states and emit webhooks so you can verify your handling logic.
***
## Test card details
In the test environment you can use special card numbers to simulate different outcomes. Expiry dates and CVC values are usually flexible, as long as the date is in the future.
| Scenario | Brand | Card Number | Expiry | CVC | Result |
| ----------------------------- | ----------- | ------------------- | ---------- | ---- | ---------------------------------------- |
| Successful payment | Visa | 4242 4242 4242 4242 | Any future | 123 | Succeeds |
| Successful payment | Mastercard | 5555 5555 5555 4444 | Any future | 123 | Succeeds |
| Successful payment | Amex | 3782 822463 10005 | Any future | 1234 | Succeeds |
| Successful payment | Discover | 6011 1111 1111 1117 | Any future | 123 | Succeeds |
| Successful payment | JCB | 3566 0020 2036 0505 | Any future | 123 | Succeeds |
| Successful payment | Diners Club | 3056 9309 0259 04 | Any future | 123 | Succeeds |
| Insufficient funds | Visa | 4000 0000 0000 9995 | Any future | 123 | Fails insufficient funds |
| Insufficient funds | Mastercard | 5200 8282 8282 8210 | Any future | 123 | Fails insufficient funds |
| Generic decline | Visa | 4000 0000 0000 0002 | Any future | 123 | Generic decline |
| Generic decline | Mastercard | 5105 1051 0510 5100 | Any future | 123 | Generic decline |
| Generic decline | Discover | 6011 0009 9013 9424 | Any future | 123 | Generic decline |
| Incorrect CVC | Visa | 4000 0000 0000 0127 | Any future | 000 | CVC failure |
| Incorrect CVC | Mastercard | 5555 5555 5555 5557 | Any future | 000 | CVC failure |
| Requires authentication (3DS) | Visa | 4000 0000 0000 3220 | Any future | 123 | Moves to `requires_action` |
| Requires authentication (3DS) | Mastercard | 5200 0000 0000 0106 | Any future | 123 | Moves to `requires_action` |
| Card not supported | Visa | 4000 0000 0000 0069 | Any future | 123 | Not supported / unsupported method error |
| Card not supported | Amex | 3787 3449 3671 000 | Any future | 1234 | Not supported / unsupported method error |
| Fraudulent card test | Visa | 4000 0000 0000 9979 | Any future | 123 | Fails fraud checks |
| Fraudulent card test | Mastercard | 5155 5555 5555 5557 | Any future | 123 | Fails fraud checks |
### How to use test cards
1. Create a **setup request** for your test payer.
2. Load the **Payment Element** in your UI using the setup request.
3. Enter one of the test card numbers with a future expiry and CVC.
4. Complete the flow and observe how the payment method and subsequent payment requests behave.
Use different cards to validate:
* Successful flows
* Declines and error messages
* 3DS or additional authentication flows
See [Payment failures](/guides/accept/payment-failures) for how failed payments are categorized and reported.
***
## Test bank account details
For bank based payment methods (for example ACH or SEPA) you can use special test account details. These accounts never move real money but are accepted by the sandbox as valid instruments.
### Example US ACH test accounts
| Scenario | Routing number | Account number | Account type | Result |
| ------------------ | -------------- | -------------- | ------------ | -------------------------------- |
| Successful debit | 110000000 | 000123456789 | checking | Payment succeeds |
| Insufficient funds | 110000000 | 000000000001 | checking | Payment fails insufficient funds |
| Account closed | 110000000 | 000000000002 | checking | Payment fails account closed |
### Example EU SEPA test IBANs
| Scenario | IBAN example | Result |
| ---------------- | ---------------------- | ---------------------------- |
| Successful debit | DE89370400440532013000 | Payment succeeds |
| Rejected mandate | DE89370400440532013001 | Mandate or debit is rejected |
Use these IBANs or your configured equivalents when testing SEPA collection flows for Accept.
# Testing & Going Live
Source: https://docs.withacclaim.com/developers/testing-going-live
Before you launch real payments with Acclaim, you should test your integration carefully in a safe environment and then switch to production with confidence. This guide shows how to prepare, test, and go live.
## Start in Sandbox
When you sign up, your organization begins in **sandbox mode**. Sandbox behaves like production but never moves real money.
* Sandbox and production share the same API base URL:
```bash theme={null}
https://api.withacclaim.com/v1
```
* They use different API keys. Example prefixes: `sk_test_...` for sandbox and `sk_live_...` for production.
* Create test funding accounts, payees, payouts, and batches without risk.
## Test Your Integration
Work through the key payment flows in sandbox:
* **Funding an account** - confirm balances update as expected.
* **Creating payees** - add a test payee or onboard one with the embedded components.
* **Sending payouts** - verify amounts, currency handling, and optional payout links.
* **Batch payouts** - test mass disbursement runs if you plan to use them.
* **Webhook handling** - ensure your endpoint receives and processes events such as `payout.succeeded` and `payout.failed`.
**TIP**
Use **Settings > Webhooks** in the Acclaim Console to add your endpoint and send test events so you can validate delivery.
## Review Webhook Delivery
Reliable webhooks keep your system in sync.
* Make your webhook endpoint idempotent so it can handle duplicates safely.
* Log event IDs to prevent double-processing.
* Monitor the Console for undelivered events during testing.
* Remember that Acclaim retries failed deliveries for up to 48 hours with exponential backoff.
## Go Live Checklist
When you are ready to move to production:
1. **Switch to production keys** Replace any `sk_test_` keys with live keys from **Settings → Developers → API Keys**.
2. **Confirm funding sources** Link and verify your production **settlement account** so treasury accounts can be funded.
3. **Deploy your webhook endpoint** Register your live webhook URL under **Settings → Developers → Webhooks** and confirm it is reachable from Acclaim.
4. **Clear test data if needed** Sandbox objects stay in sandbox. Production starts clean.
5. **Run a small live payout** Send a small transaction to validate end-to-end money movement, status updates, and webhook delivery.
## Support and Monitoring
After launch you can:
* Monitor payouts and account balances in the Acclaim Console.
* Review webhook delivery logs for each event.
* Contact [support@withacclaim.com](mailto:support@withacclaim.com) if you have any issues or questions.
Once you are live and stable, explore advanced topics such as batch payouts, embedded payee onboarding, and reconciliation workflows to fully automate your payment operations.
# Webhooks
Source: https://docs.withacclaim.com/developers/webhooks
Webhooks keep your system in sync with what’s happening inside Acclaim. Instead of polling the API, you can receive real-time notifications whenever key events occur — like a payout completing or failing.
Payments are event-driven. Once you create a payout, it may take seconds or days to complete depending on the payment method and banking networks involved. Webhooks let you:
* Update internal records when payouts succeed or fail.
* Trigger notifications to your team or payees.
* Automate reconciliation and reporting.
## Setting Up a Webhook Endpoint
A webhook endpoint is just an HTTPS URL on your server that can accept `POST` requests.
When something happens — like a payout completing — Acclaim sends a JSON payload to your endpoint.
Key considerations when building your endpoint:
* Must accept `POST` requests with a JSON body.
* Must return a `2xx` HTTP status code to acknowledge receipt.
* Should be idempotent (able to safely handle duplicate deliveries).
Example flow:
1. Acclaim sends an event payload to your webhook URL.
2. Your server processes the event.
3. Your server responds with `200 OK` to confirm receipt.
### Installing Webhooks in the Console
You can install and manage webhook endpoints directly from the **Acclaim Console** under **Settings → Developers → Webhooks**.
* Add one or more HTTPS URLs where Acclaim should send events.
* Choose which event types to subscribe to, or receive all events by default.
* Test delivery right from the console to verify your endpoint is working.
## Event Payload Structure
All webhook events share a consistent format:
```json JSON theme={null}
{
"id": "evt_MjdYqzLbsS",
"type": "payout.succeeded",
"account_id": "acct_ovGlkewETl",
"created_at": "2025-10-08T18:20:31Z",
"data": {
"id": "po_vkj7BPRPr9",
"payee_id": "pyee_PXlpcv13X9",
"payment_amount": 50000,
"payment_currency": "usd"
// truncated for brevity
}
}
```
Unique event identifier.
Event type, such as `payout.completed`.
The account ID that generated the event.
Timestamp of the event.
The resource that changed (e.g., payout details). This will match the same format as retrieving the resource through the API.
## Event Types
### Payer Events
* `payer.created`
* `payer.updated`
* `payer.deleted`
### Payment Request Events
* `payment_request.created`
* `payment_request.updated`
* `payment_request.succeeded`
* `payment_request.failed` — see [Payment failures](/guides/accept/payment-failures#failure-codes) for failure code reference
* `payment_request.canceled`
### Setup Request Events
* `setup_request.created`
* `setup_request.updated`
* `setup_request.succeeded`
* `setup_request.failed`
* `setup_request.canceled`
### Refund Events
* `refund.created`
* `refund.failed`
* `refund.succeeded`
### Dispute Events
* `dispute.created`
### Payee Events
* `payee.created`
* `payee.updated`
* `payee.deleted`
### Payout Events
* `payout.created`
* `payout.updated`
* `payout.processing`
* `payout.succeeded`
* `payout.failed`
### Payout Batch Events
* `payout_batch.created`
* `payout_batch.updated`
* `payout_batch.succeeded`
* `payout_batch.failed`
* `payout_batch.canceled`
### Treasury Account Events
* `treasury.account.created`
* `treasury.account.updated`
### Treasury Transaction Events
* `treasury.transaction.created`
## Reliability & Retries
Acclaim automatically retries failed webhook deliveries for up to **48 hours** using exponential backoff.
Your endpoint should:
* Be idempotent: safely handle duplicate events.
* Respond quickly: return `2xx` as soon as the event is accepted, then process asynchronously if needed.
* Log event `id`s to avoid reprocessing the same event.
If all retry attempts fail, the event will be marked as undelivered in the Acclaim Console.
## Securing Webhooks
Webhooks should be secure so only Acclaim can call them:
* Use HTTPS for encryption.
* Verify the webhook signature before you process the event.
### Signature verification
Each webhook request includes these headers:
* `Acclaim-Timestamp` - The Unix timestamp used when the request was signed.
* `Acclaim-Signature` - The HMAC signature for the request body, in the format `v1=`.
Acclaim signs the exact request body bytes using HMAC SHA-256 and your webhook endpoint secret.
To verify a webhook:
1. Read the raw request body exactly as it was received.
2. Read the `Acclaim-Timestamp` header.
3. Build the signed payload as `timestamp.raw_body`, with a literal `.` between the timestamp and raw body.
4. Compute an HMAC SHA-256 digest using your webhook endpoint secret.
5. Prefix the digest with `v1=` and compare it to the `Acclaim-Signature` header using a constant-time comparison.
6. Reject the request if the signature does not match.
Use the raw request body for verification. If your framework parses and re-serializes the JSON before verification, the signature check can fail.
Example verification flow in JavaScript:
```javascript theme={null}
import crypto from 'node:crypto';
const timestamp = req.header('Acclaim-Timestamp') ?? '';
const signatureHeader = req.header('Acclaim-Signature') ?? '';
const rawBody = req.rawBody;
const signedPayload = `${timestamp}.${rawBody}`;
const expectedSignature = crypto
.createHmac('sha256', webhookSecret)
.update(signedPayload, 'utf8')
.digest('hex');
const expectedHeader = `v1=${expectedSignature}`;
if (!crypto.timingSafeEqual(Buffer.from(expectedHeader), Buffer.from(signatureHeader))) {
res.status(400).send('Invalid signature');
return;
}
```
For additional protection, you can also reject requests with old timestamps to reduce replay risk.
## What’s Next
Once your webhook endpoint is live, test it using your sandbox environment. Create a payout and watch events arrive, confirming your system can react to status changes and keep your records up to date.
# Collect your first payment
Source: https://docs.withacclaim.com/guides/accept/collecting-your-first-payment
Create and complete your first payment request using a hosted payment page. Learn how to request, collect, and track a payment end to end.
This guide walks through creating and completing your first payment request using a hosted page.
You will:
* Create a payment request
* Share the payment link
* Complete the payment
* Verify the result in the Console
***
## Step 1: Create a payment request
In the Console, go to **Accept → Payment requests** and create a new request.
Provide:
* Amount and currency
* Description (optional)
* Payer (optional)
You can also configure:
* Allowed payment methods
* Metadata for internal tracking
Once created, the payment request will be ready to present to the payer.
***
## Step 2: Share the payment link
Each payment request includes a **hosted payment page**.
Copy the payment link and share it with the payer via:
* Email
* SMS
* Your application
The payer will use this link to complete the payment.
***
## Step 3: Complete the payment
Open the payment link and complete the payment as the payer would:
1. Enter payment details
2. Select a payment method
3. Submit the payment
The experience will vary slightly depending on the payment method selected.
***
## Step 4: Verify the payment
Return to the Console and view the payment request.
You should see the status update to:
* **Processing** → while the payment is being handled
* **Succeeded** → once the payment is complete
You can also:
* View payment details
* Confirm amount and method
* Track associated payer information
***
## What happens next
After the payment is completed:
* Funds are processed based on the selected payment method
* Status updates are available in the Console
* Webhooks can notify your systems in real time
***
## Common variations
You can adapt this flow depending on your needs:
* Use **embedded elements** instead of a hosted page
* Predefine a **payer** to reduce data entry
* Limit **payment methods** based on region or use case
***
## Summary
* Payment requests are the starting point for collecting funds
* Hosted payment pages provide a quick way to collect payments
* Payments can be tracked from creation through completion
* The Console provides full visibility into payment status and details
# Disputes
Source: https://docs.withacclaim.com/guides/accept/disputes
Understand how disputes occur, how to respond, and how outcomes impact your payments and balances.
Disputes occur when a payer challenges a completed payment through their bank or card network.
They are typically initiated after a payment has been completed and may result in funds being **reversed**, **held**, or **recovered** depending on the outcome.
***
## How disputes work
Disputes follow a multi-step process: **initiated**, **reviewed**, and **resolved**.
1. **Dispute initiated**
The payer contacts their bank or card issuer to challenge a transaction.
2. **Dispute received**
The dispute is communicated through the payment network and recorded in Acclaim.
3. **Respond with evidence** (if applicable)
You may provide supporting information to contest the dispute.
4. **Outcome determined**
The dispute is resolved as either won or lost.
***
## When disputes occur
Disputes are most common with **card payments**, but may occur with other payment methods depending on network rules.
Common reasons include:
* Unauthorized transaction
* Duplicate charge
* Service not provided
* Fraud or misuse
***
## Responding to disputes
When a dispute is received, you may have the option to respond.
Typical response actions include:
* Reviewing the dispute reason
* Submitting supporting evidence
* Accepting the dispute (no response)
Evidence may include:
* Proof of payment authorization
* Transaction details
* Communication with the payer
Deadlines for responses are defined by the payment network.
***
## Outcomes
Disputes can result in different outcomes:
### Won
The dispute is resolved in your favor.
* Funds are returned to your balance
* The payment remains valid
***
### Lost
The dispute is resolved in favor of the payer.
* Funds are returned to the payer
* The payment is effectively reversed
***
## Financial impact
Disputes affect your balances and reporting.
* Funds may be **debited** when a dispute is initiated or lost
* Funds may be **returned** if the dispute is won
* Fees or penalties may apply depending on the network
Disputes should be included in your reconciliation process.
***
## Timing
Disputes can occur **days or weeks after a payment**.
* Response windows are limited
* Final resolution may take several weeks
Timing depends on the payment method and network.
***
## Relationship to refunds
* **Refunds** are initiated by you
* **Disputes** are initiated by the payer through their bank
Issuing a refund early may help prevent disputes in some cases.
***
## Best practices
* Respond to disputes promptly within required timeframes
* Keep clear records of payment authorization and communication
* Use clear descriptors to reduce confusion for payers
* Issue refunds proactively when appropriate
* Monitor dispute rates and trends
***
## Summary
* Disputes occur when a payer challenges a completed payment
* They are initiated through banks or card networks
* Outcomes determine whether funds are returned or retained
* Disputes impact balances and should be tracked in reconciliation
# Accept Overview
Source: https://docs.withacclaim.com/guides/accept/overview
Accept payments through hosted or embedded experiences, virtual accounts, or the Console. Collect payer details and reconcile incoming funds in one place.
Bring funds into your business with clarity and control.
Acclaim’s Accept capabilities power incoming payments from **customers, policyholders, and partners** across payment methods and currencies.
From requesting payment to reconciling funds, every pay-in is **tracked, validated, and connected** to your workflows.
***
## How Accept works
Accept is built around a simple lifecycle: **request**, **collect details**, **receive funds**, and **reconcile**.
1. **Create a payment request or provision a collection method**
Define the amount, currency, and payer, or assign a virtual account to receive funds. Payment requests can be created via API or the Console.
2. **Collect payer details or funds**
Use a hosted or embedded experience, or receive funds directly via bank transfer into a virtual account.
3. **Receive funds**
The payer completes the payment using the selected method or sends funds to the assigned account.
4. **Track and reconcile**
Monitor status, receive webhooks, and match incoming funds to your internal records.
***
## Core concepts
### Payment requests
A **payment request** represents a request for funds from a payer.
It defines:
* Amount and currency
* Payer
* Payment method options
Payment requests can be fulfilled through hosted or embedded flows.
***
### Payment methods
Payment methods define **how funds are collected**.
Examples include:
* Bank debit methods
* Cards
* Local payment methods
Available methods vary by country and currency.
***
### Virtual accounts
A **virtual account** is a bank account assigned to you to receive incoming transfers from payers.
Use virtual accounts to:
* Collect funds via **bank transfer**
* Assign unique account details to a payer or workflow
* Simplify reconciliation of incoming payments
Funds received into virtual accounts are automatically tracked and can be matched to your internal records.
***
### Payers
A **payer** represents the individual or business sending funds.
Payers can be:
* Known and stored for reuse
* Collected dynamically during the payment flow
* Associated with virtual account activity
***
### Reconciliation
All incoming payments are tracked and structured for reconciliation.
You can:
* Match payments to internal records
* Track payment status and outcomes
* Export data for reporting
***
## Ways to collect payments
Choose the integration that fits your experience:
* **Embedded elements** — integrate payment collection directly into your application
* **Hosted pages** — send a payment link for a fully managed experience
* **Virtual accounts** — receive bank transfers directly from payers
* **Console** — create and manage payments on behalf of payers
***
## Key behaviors
* Payment requests can exist **before payer details are known**
* Payment collection can be **payer-driven (hosted/embedded)** or **transfer-based (virtual accounts)**
* Payment methods and requirements vary by **country and currency**
* Status updates are delivered via **webhooks**
* All payments are **tracked from request to settlement**
***
## Summary
* Accept enables you to **request, receive, and reconcile funds**
* Payment requests and virtual accounts are the core ways to collect funds
* Hosted and embedded experiences handle payer interaction
* Every payment is **tracked and connected to your workflow**
# Payers
Source: https://docs.withacclaim.com/guides/accept/payers
Manage the individuals and businesses sending funds. Store payer details, reuse across payment flows, and improve reconciliation.
Payers are the individuals or businesses that send funds to you.
A payer represents the source of incoming payments, including their **identity details**, **contact information**, and associated **payment methods or activity**.
By creating and managing payers, you can **reuse information**, reduce friction, and improve reconciliation across payment flows.
***
## Why use payers
Using payers allows you to:
* **Store payer details once** and reuse them across payment requests
* **Prefill payment experiences** to reduce friction
* **Associate payment methods** for future use
* **Track payment activity** at the payer level
* **Improve reconciliation** of incoming funds
***
## How payers work
Payers can be created and used in multiple ways depending on your workflow.
### Create directly
Create a payer via API or the Console by providing **identity and contact details**.
This is useful when:
* You already know the payer
* You want to reuse payer information across payments
***
### Collect during payment
If a payer is not predefined, their details can be collected during a:
* **Payment request**
* **Setup request**
The payer is created or updated automatically once details are submitted.
***
### Associate with virtual accounts
Payers can be linked to **virtual accounts** to improve reconciliation.
* Assign a dedicated virtual account to a payer
* Automatically match incoming transfers to the correct payer
***
## Payer details
A payer typically includes:
* **Name** (individual or business)
* **Contact information** (email, phone)
* **Country and currency context**
* **Associated payment methods or tokens**
Required fields may vary depending on the **payment method** and **region**.
***
## Payment methods and tokens
Payers can have **stored payment methods** associated with them.
These are typically created through **setup requests** and can be reused for future payments.
This allows you to:
* Avoid re-collecting payment details
* Enable faster repeat payments
* Support off-session payment flows
***
## Reuse across payment flows
Once a payer exists, it can be reused across:
* **Payment requests**
* **Setup requests**
* **Virtual account assignments**
This creates a consistent view of each payer across all collection activity.
***
## Updating payers
Payers can be updated at any time via API or the Console.
Changes may:
* Apply to future payment requests
* Update stored contact or identity details
* Affect how payments are associated and reconciled
***
## Payers vs payment requests
* **Payers** represent who is paying
* **Payment requests** represent what is being paid
A payment request can:
* Reference an existing payer
* Create or update a payer during the payment flow
***
## Tracking and activity
You can track all payment activity associated with a payer.
This includes:
* Completed payments
* Failed payments
* Stored payment methods
* Incoming transfers via virtual accounts
This provides a complete view of each payer’s activity.
***
## Best practices
* **Create payers upfront** when you expect repeat payments
* **Associate saved payment methods** for faster future payments
* **Use virtual accounts** for high-volume or transfer-based workflows
* **Keep payer data accurate** to improve reconciliation and reduce errors
***
## Summary
* Payers represent the **source of incoming funds**
* They unify identity, payment methods, and activity across flows
* Payers can be created directly or collected during payment flows
* Reusing payers improves **efficiency, accuracy, and reconciliation**
# Payment failures
Source: https://docs.withacclaim.com/guides/accept/payment-failures
Understand why payins fail, how failure codes help you diagnose issues, and how to retry or monitor failed payment requests.
Not all payment requests complete successfully. When a payment fails, it reaches the **Failed** final state, no funds are collected, and you receive a specific `failure_code` and message explaining why.
This guide covers what happens when a payment fails, the available failure codes, and how to retry or monitor failed payins safely.
For status transitions and lifecycle context, see [Payment lifecycle](/guides/accept/payment-lifecycle). For post-success returns or chargebacks, see [Refunds](/guides/accept/refunds) and [Disputes](/guides/accept/disputes).
***
## When a payment fails
A payment fails after processing begins and Acclaim cannot complete collection.
At that point:
* The payment request moves to the final **Failed** state and will not be charged
* Acclaim includes a `failure_code` and matching message on the payment request
* No funds are collected from the payer
* You can review the failure in the **Console** or through webhooks and the API
A failed payment is not the same as a [refund](/guides/accept/refunds) or [dispute](/guides/accept/disputes). Those apply after a payment has succeeded.
***
## Failure codes
When a payment fails, Acclaim includes a `failure_code` and matching message. All API codes use the `payin.*` format.
The groups below describe what each failure means in plain language, with the exact code shown for reference.
### Account
* **Account closed** — The account is closed and cannot be charged.\
Code: `payin.account_closed`
* **Account frozen** — The account is frozen and cannot be charged.\
Code: `payin.account_frozen`
* **Invalid account** — The account details are invalid.\
Code: `payin.invalid_account`
* **Account not found** — The account could not be found.\
Code: `payin.account_not_found`
### Amount and limits
* **Insufficient funds** — There are insufficient funds available to complete the payment.\
Code: `payin.insufficient_funds`
* **Invalid amount** — The payment amount is invalid.\
Code: `payin.amount_invalid`
* **Currency not supported** — The selected currency is not supported for this payment.\
Code: `payin.currency_not_supported`
* **Limit exceeded** — The payment exceeds an allowed limit.\
Code: `payin.limit_exceeded`
### Payment method
* **Expired payment method** — The payment method has expired.\
Code: `payin.expired_payment_method`
* **Payment method declined** — The payment method was declined.\
Code: `payin.payment_method_declined`
* **Unsupported payment method** — The payment method is not supported.\
Code: `payin.unsupported_payment_method`
* **Invalid security code** — The security code provided is invalid.\
Code: `payin.invalid_cvc`
* **Address verification failed** — Address verification failed for this payment method.\
Code: `payin.address_verification_failed`
### Authentication
* **Authentication required** — Additional authentication is required to complete the payment.\
Code: `payin.authentication_required`
* **Authentication failed** — Authentication failed and the payment could not be completed.\
Code: `payin.authentication_failed`
* **Unauthorized** — The payment was not authorized by the account holder.\
Code: `payin.unauthorized`
### Compliance and fraud
* **Suspected fraud** — The payment was declined due to suspected fraud.\
Code: `payin.suspected_fraud`
* **Payment blocked** — The payment was blocked and could not be completed.\
Code: `payin.payment_blocked`
* **Compliance blocked** — The payment could not be completed due to compliance requirements.\
Code: `payin.compliance_blocked`
### Request and session
* **Invalid request** — The payment request is invalid.\
Code: `payin.invalid_request`
* **Duplicate payment** — A duplicate payment was detected and was not processed.\
Code: `payin.duplicate_payment`
* **Expired session** — The payment session has expired.\
Code: `payin.expired_session`
* **Configuration error** — The payment could not be completed due to a configuration issue.\
Code: `payin.configuration_error`
### Processing
* **Processor unavailable** — The payment processor is temporarily unavailable. Please try again later.\
Code: `payin.processor_unavailable`
* **Processor failure** — The payment could not be completed due to a processing error.\
Code: `payin.processor_failure`
* **Unknown failure** — The payment could not be completed for an unknown reason.\
Code: `payin.unknown_failure`
***
## Retrying failed payments
After the underlying issue is fixed, you can attempt collection again.
Best practice:
1. Review the `failure_code` and message
2. Correct the issue, such as payment method details or payer information
3. Create a new payment request or prompt the payer to try again
Avoid retrying without changes. The same issue is likely to cause another failure.
***
## Monitoring and alerts
To respond quickly to failed payments:
* Monitor payment requests in the **Console**
* Track status changes via **webhooks**
* Set up internal alerts for **Failed** payments
For webhook and API handling details, see [Accept](/developers/accept).
***
## Summary
* **Failed** is a final state reached when a payment cannot be completed after processing begins
* No funds are collected when a payment fails
* Use `failure_code` and the matching message to diagnose the issue; see [Failure codes](#failure-codes) above
* Most failures can be resolved and retried after correcting the issue
* Refunds and disputes apply to successful payments, not failed payment requests
# Payment lifecycle
Source: https://docs.withacclaim.com/guides/accept/payment-lifecycle
Understand how payments move from request to completion, including status transitions, required actions, and final states.
Every payment moves through a defined lifecycle from **creation** to **completion**.
Statuses reflect the current state of the payment and whether **action is required**, **authorization is complete**, or **funds are in motion**.
## Lifecycle overview
Payments move through four phases:
1. **Requires action** — `RequiresPaymentMethod`, `RequiresAction`
2. **Ready** — `Authorized`
3. **In progress** — `Processing`
4. **Final states** — `Succeeded`, `Failed`, `Canceled`
## Status definitions
### RequiresPaymentMethod
Action required
The payment does not have a valid payment method.
This occurs when:
* No payment method has been provided
* The selected method is incomplete or not supported
How to resolve:
* Provide a payment method through a hosted or embedded flow
* Or update the payment request configuration
***
### RequiresAction
Action required
The payment is waiting for the payer to complete an action.
This occurs when:
* The payer has not completed the payment flow
* Additional steps are required (e.g. entering details or confirming payment)
How to resolve:
* Direct the payer to complete the payment
* Ensure the payment experience is accessible and complete
***
### Authorized
Authorized
The payment method has been successfully authorized.
At this stage:
* Required payer consent or authorization has been captured
* The payment is eligible to be processed
For some methods (such as cards), authorization and processing may occur almost immediately.
***
### Processing
In progress
The payment has been submitted and is being processed.
During this stage:
* Funds are in transit or being confirmed
* External payment networks may be involved
* Status updates occur asynchronously
No action is required while processing.
***
### Succeeded
Completed
The payment has completed successfully.
At this stage:
* The payer has been charged
* Funds are settled or in the process of settlement
* The payment is ready for reconciliation
***
### Failed
Failed
The payment could not be completed.
See [Payment failures](/guides/accept/payment-failures#failure-codes) for the complete list of failure codes and messages.
Next steps:
* Review the failure reason
* Correct any issues
* Retry the payment if appropriate
***
### Canceled
Canceled
The payment was canceled and will not be processed.
This can occur when:
* A user cancels the payment request
* The payment is no longer needed
* A workflow or system action stops execution
Canceled payments are final and will not be processed.
***
## State transitions
Payments move forward as requirements are met and processing progresses.
Typical transitions include:
* **RequiresPaymentMethod** → **RequiresAction** → **Authorized**
* **RequiresAction** → **Authorized** (once the payer completes the flow)
* **Authorized** → **Processing** → **Succeeded**
* **Processing** → **Failed**
* **Authorized** → **Canceled**
Transitions are driven by:
* Payer interaction
* Data completeness
* Payment method behavior
* External network responses
***
## Webhooks and status updates
Payment status changes are communicated via **webhooks**.
Use webhooks to:
* Track payment progress in real time
* Trigger internal workflows
* Handle failures and retries
Each status update corresponds to a lifecycle transition.
***
## Summary
* Payments move through **clear phases** from required actions to final states
* **RequiresPaymentMethod** and **RequiresAction** indicate missing input or payer interaction
* **Authorized** confirms payment method approval
* **Processing** reflects funds in motion
* **Succeeded**, **Failed**, and **Canceled** are final states
Understanding the lifecycle helps you **build reliable workflows**, **handle edge cases**, and **maintain accurate reconciliation**.
# ACH Debit
Source: https://docs.withacclaim.com/guides/accept/payment-methods/ach-debit
Collect USD payments directly from bank accounts in the United States using ACH debit. Suitable for recurring and high-value transactions.
ACH Debit is a direct debit payment method that allows you to **collect USD payments from bank accounts in the United States**.
It is commonly used for **recurring payments**, **bill payments**, and **high-value transactions** where bank-based payment is preferred over cards.
***
## How ACH Debit works
ACH Debit follows the standard direct debit flow: **authorize**, **initiate**, and **settle**.
1. **Collect authorization**
The payer provides consent to debit their bank account. This is typically done through a hosted or embedded flow.
2. **Initiate the debit**
Once authorized, you initiate a payment against the payer’s bank account.
3. **Settle funds**
Funds are transferred through the ACH network over several business days.
***
## Requirements
To process an ACH Debit payment, you typically need:
* Bank account number
* Routing number
* Account holder name
* Authorization (mandate) from the payer
Additional requirements may apply depending on the use case.
***
## Timing and settlement
ACH payments are not instant and follow standard processing windows.
* Settlement typically takes **1–3 business days**
* Processing times may vary based on submission timing and bank cutoffs
* Funds are not guaranteed until settlement is complete
***
## Returns and reversals
ACH payments can be returned after initiation.
Common return reasons include:
* Insufficient funds
* Invalid account details
* Authorization issues
Returns may occur **several days after the original payment**, depending on the return code and rules.
***
## Authorization and mandates
ACH Debit requires payer authorization before initiating a payment.
Authorization includes:
* Consent to debit the account
* Agreement to ACH network rules
* Record of authorization for compliance
Authorization can be collected through a **setup request** or during a payment flow.
***
## When to use ACH Debit
ACH Debit is best suited for:
* Recurring payments
* High-value transactions
* Reducing payment processing costs
* US-based payers using bank accounts
***
## Comparison to cards
| Feature | Cards | ACH Debit |
| -------------- | --------- | ---------------------------- |
| Payment type | Push | Pull |
| Currency | Global | USD |
| Authorization | Immediate | Requires prior authorization |
| Settlement | Fast | 1–3 business days |
| Failure timing | Immediate | Possible delayed return |
***
## Best practices
* Collect and store authorization before initiating payments
* Validate bank details before submission
* Account for settlement delays in your workflows
* Monitor returns and handle them appropriately
***
## Summary
* ACH Debit allows you to collect USD payments from US bank accounts
* It requires payer authorization and operates on a pull model
* Settlement takes 1–3 business days and may include returns
* It is ideal for recurring, high-value, or cost-sensitive payments
# CA PAD
Source: https://docs.withacclaim.com/guides/accept/payment-methods/ca-pad
Collect CAD payments directly from Canadian bank accounts using Pre-Authorized Debit (PAD). Ideal for recurring and bank-based payments in Canada.
CA PAD (Pre-Authorized Debit) is a direct debit payment method that allows you to **collect CAD payments from bank accounts in Canada**.
It is commonly used for **recurring payments**, **bill payments**, and **high-value transactions** where bank-based payment is preferred over cards.
***
## How CA PAD works
CA PAD follows the standard direct debit flow: **authorize**, **initiate**, and **settle**.
1. **Collect authorization**
The payer provides consent to debit their bank account. This is typically done through a hosted or embedded flow.
2. **Initiate the debit**
Once authorized, you initiate a payment against the payer’s bank account.
3. **Settle funds**
Funds are transferred through the Canadian banking network over several business days.
***
## Requirements
To process a CA PAD payment, you typically need:
* Bank account number
* Transit number
* Institution number
* Account holder name
* Authorization (PAD agreement) from the payer
Additional requirements may apply depending on the use case.
***
## Timing and settlement
CA PAD payments are not instant and follow standard processing windows.
* Settlement typically takes **2–3 business days**
* Processing times may vary based on submission timing and bank cutoffs
* Funds are not guaranteed until settlement is complete
***
## Returns and reversals
CA PAD payments can be returned after initiation.
Common return reasons include:
* Insufficient funds
* Invalid account details
* Authorization issues
Returns may occur **several days after the original payment**, depending on network rules.
***
## Authorization and PAD agreements
CA PAD requires payer authorization, often referred to as a **PAD agreement**.
Authorization includes:
* Consent to debit the account
* Agreement to Canadian Payments Association (Payments Canada) rules
* Retention of authorization records for compliance
Authorization can be collected through a **setup request** or during a payment flow.
***
## When to use CA PAD
CA PAD is best suited for:
* Recurring payments
* High-value transactions
* Canadian payers using bank accounts
* Reducing payment processing costs
***
## Comparison to cards
| Feature | Cards | CA PAD |
| -------------- | --------- | ---------------------------- |
| Payment type | Push | Pull |
| Currency | Global | CAD |
| Authorization | Immediate | Requires prior authorization |
| Settlement | Fast | 2–3 business days |
| Failure timing | Immediate | Possible delayed return |
***
## Best practices
* Collect and store PAD agreements before initiating payments
* Validate bank details before submission
* Account for settlement delays in your workflows
* Monitor returns and handle them appropriately
***
## Summary
* CA PAD allows you to collect CAD payments from Canadian bank accounts
* It requires payer authorization and operates on a pull model
* Settlement takes 2–3 business days and may include returns
* It is ideal for recurring, high-value, or cost-sensitive payments
# Cards
Source: https://docs.withacclaim.com/guides/accept/payment-methods/cards
Accept card payments globally with fast authorization and a familiar payer experience. Supports setup and reuse for future payments.
Cards are a widely supported payment method that allow payers to complete payments instantly using credit or debit cards.
They provide a **fast, familiar experience** and are typically the default choice for one-time or immediate payments.
***
## How cards work
Card payments follow a simple flow: **collect details**, **authorize**, and **capture funds**.
1. **Collect card details**
Card information is collected through a hosted page or embedded element.
2. **Authorize payment**
The payer’s bank approves or declines the transaction in real time.
3. **Complete payment**
Funds are captured and the payment is marked as successful.
***
## Supported cards
Acclaim supports major global card networks, including:
* Visa
* Mastercard
* American Express
* Discover
* JCB
* UnionPay
* Diners Club
Availability may vary by region.
***
## When to use cards
Cards are best suited for:
* One-time payments
* Immediate payment confirmation
* Payers who expect a familiar checkout experience
* Global payment acceptance
***
## Authorization and settlement
Card payments are authorized immediately, but settlement may occur later depending on the network and region.
* **Authorization** — real-time approval or decline
* **Settlement** — funds are transferred after processing
***
## Setup and reuse
Cards can be securely stored and reused through **setup requests**.
This allows you to:
* Avoid re-collecting card details
* Enable faster repeat payments
* Support off-session payments
Sensitive card data is not exposed to your systems.
***
## Failures and declines
Failed payments may fail during authorization.
See [Payment failures](/guides/accept/payment-failures) for failure codes and guidance on retrying.
Common reasons include:
* Insufficient funds
* Incorrect card details
* Card restrictions or blocks
Failed payments can typically be retried immediately after correcting the issue.
***
## Disputes
Card payments may be disputed by the payer after completion.
Disputes:
* Are initiated through the card network
* Require evidence and response
* May result in funds being reversed
See **Disputes** for more.
***
## Best practices
* Offer cards for fast and familiar payment experiences
* Use setup requests for repeat payers
* Handle declines gracefully and allow retry
* Monitor disputes and respond promptly
***
## Summary
* Cards provide instant authorization and global coverage
* They are ideal for one-time and immediate payments
* Setup requests enables reuse and faster repeat payments
* Disputes and declines should be handled as part of normal operations
# Payment methods
Source: https://docs.withacclaim.com/guides/accept/payment-methods/index
Understand supported payment methods and choose the right option based on region, speed, and payer experience.
Payment methods define how funds are collected from payers.
They determine the **payer experience**, **required details**, **settlement timing**, and **regional availability**.
Acclaim supports a range of payment methods across cards, direct debit schemes, and local payment networks.
***
## Choosing a payment method
The right payment method depends on:
* **Payer location**
* **Currency**
* **Speed of settlement**
* **Payer experience (push vs pull)**
* **Whether payment details need to be reused**
In many cases, you can offer multiple methods and let the payer choose.
***
## Supported payment methods
| Payment method | Type | Regions | Speed | Best for |
| ----------------------------------------------------------------------------- | ------------------- | ---------------- | --------------------- | -------------------------------- |
| [Cards](/guides/accept/payment-methods/cards) | Push | Global | Instant authorization | One-time or immediate payments |
| [ACH Debit](/guides/accept/payment-methods/ach-debit) | Pull (Direct Debit) | United States | 1–3 business days | Recurring or bank-based payments |
| [SEPA Debit](/guides/accept/payment-methods/sepa-debit) | Pull (Direct Debit) | Europe | 1–2 business days | Eurozone payments |
| [UK Direct Debit](/guides/accept/payment-methods/uk-direct-debit) | Pull (Direct Debit) | United Kingdom | 2–3 business days | GBP recurring payments |
| [Pre-Authorized Debits (PAD)](/guides/accept/payment-methods/ca-pad) | Pull (Direct Debit) | Canada | 2–3 business days | CAD bank debit payments |
| [Local payment methods](/guides/accept/payment-methods/local-payment-methods) | Varies | Country-specific | Varies | Regional payment preferences |
***
## Payment method types
### Cards
Cards are a **push-based payment method** where the payer authorizes the transaction immediately.
* Fast authorization
* Widely supported globally
* Suitable for one-time or immediate payments
***
### Direct debit
Direct debit methods are **pull-based**, meaning you collect funds directly from the payer’s bank account with authorization.
* Lower cost than cards
* Suitable for recurring or large payments
* Settlement takes multiple business days
Direct debit schemes are region-specific:
* ACH Debit (US)
* SEPA Debit (EU)
* UK Direct Debit (UK)
* CA PAD (Canada)
***
### Local payment methods
Local payment methods are **region-specific payment rails**.
* Optimized for local payer preferences
* May offer better conversion in certain markets
* Requirements and behavior vary by country
***
## Method behavior
Payment methods differ across several dimensions:
* **Authorization model** — immediate (cards) vs delayed (debit)
* **Settlement timing** — instant vs multi-day
* **Failure modes** — declines vs returns
* **Reusability** — setup request support
Understanding these differences helps you design the right payment flow.
***
## Using payment methods in Accept
Payment methods are used across all collection flows:
* **Payment requests** — define available methods for the payer
* **Setup requests** — store reusable payment methods
* **Virtual accounts** — enable bank transfer alternatives
You can:
* Offer multiple methods
* Restrict methods by region or use case
* Let the payer select their preferred option
***
## Best practices
* **Match methods to payer geography**
* **Offer multiple options** when possible
* **Use direct debit** for recurring or high-value payments
* **Use cards** for speed and simplicity
* **Monitor performance** by method
***
## Summary
* Payment methods determine how funds are collected
* Cards, direct debit, and local methods each serve different use cases
* Availability depends on country and currency
* Choosing the right method improves conversion, cost, and reliability
# Local payment methods
Source: https://docs.withacclaim.com/guides/accept/payment-methods/local-payment-methods
Use region-specific payment methods to support local payer preferences and improve conversion in selected markets.
Local payment methods are region-specific payment rails that allow payers to complete payments using familiar, market-native experiences.
They are useful when payer expectations, bank infrastructure, or conversion patterns vary by country. In some markets, offering local payment methods can improve completion rates and provide a better payment experience than cards or direct debit alone.
Detailed documentation for supported local payment methods is in progress.
# SEPA Debit
Source: https://docs.withacclaim.com/guides/accept/payment-methods/sepa-debit
Collect EUR payments from bank accounts across the SEPA region using SEPA Direct Debit. Ideal for recurring and cross-border euro payments.
SEPA Debit is a direct debit payment method that allows you to **collect EUR payments from bank accounts across the Single Euro Payments Area (SEPA)**.
It is commonly used for **recurring payments**, **subscriptions**, and **cross-border euro transactions** within Europe.
***
## How SEPA Debit works
SEPA Debit follows the standard direct debit flow: **authorize**, **initiate**, and **settle**.
1. **Collect authorization**
The payer provides consent to debit their bank account through a SEPA mandate.
2. **Initiate the debit**
Once authorized, you initiate a payment against the payer’s bank account.
3. **Settle funds**
Funds are transferred through the SEPA network over several business days.
***
## Requirements
To process a SEPA Debit payment, you typically need:
* IBAN
* Account holder name
* Mandate authorization from the payer
Additional requirements may apply depending on the use case.
***
## SEPA region
SEPA Debit supports payments across countries in the SEPA region.
This includes:
* Eurozone countries
* Additional participating countries outside the eurozone
***
## Timing and settlement
SEPA Debit payments are not instant and follow standard processing timelines.
* Settlement typically takes **1–2 business days**
* Processing times may vary depending on submission timing and scheme rules
* Funds are not guaranteed until settlement is complete
***
## Returns and reversals
SEPA Debit payments can be returned after initiation.
Common return reasons include:
* Insufficient funds
* Invalid account details
* Authorization or mandate issues
Returns may occur **after settlement**, depending on scheme rules and timelines.
***
## Authorization and mandates
SEPA Debit requires a **mandate**, which is the payer’s authorization to debit their account.
A mandate includes:
* Payer consent
* Mandate reference
* Creditor information
* Agreement to SEPA rules
Mandates must be stored and referenced for future debits.
Authorization can be collected through a **setup request** or during a payment flow.
***
## When to use SEPA Debit
SEPA Debit is best suited for:
* Recurring payments in EUR
* Cross-border payments within Europe
* Subscription or invoice-based billing
* Reducing payment processing costs
***
## Comparison to cards
| Feature | Cards | SEPA Debit |
| -------------- | --------- | ----------------------- |
| Payment type | Push | Pull |
| Currency | Global | EUR |
| Geography | Global | SEPA region |
| Authorization | Immediate | Requires mandate |
| Settlement | Fast | 1–2 business days |
| Failure timing | Immediate | Possible delayed return |
***
## Best practices
* Collect and store mandates before initiating payments
* Validate IBANs before submission
* Account for settlement timing and return windows
* Monitor returns and handle them appropriately
***
## Summary
* SEPA Debit allows you to collect EUR payments across the SEPA region
* It requires a mandate and operates on a pull model
* Settlement takes 1–2 business days and may include returns
* It is ideal for recurring and cross-border euro payments
# UK Direct Debit
Source: https://docs.withacclaim.com/guides/accept/payment-methods/uk-direct-debit
Collect GBP payments from UK bank accounts using Direct Debit. Ideal for recurring payments with strong consumer protections and predictable billing.
UK Direct Debit is a direct debit payment method that allows you to **collect GBP payments from bank accounts in the United Kingdom**.
It is widely used for **recurring payments**, **subscriptions**, and **bill payments**, and operates under the Direct Debit scheme managed by Bacs.
***
## How UK Direct Debit works
UK Direct Debit follows the standard direct debit flow: **authorize**, **notify**, **initiate**, and **settle**.
1. **Collect authorization**
The payer provides consent to debit their bank account. This is known as a Direct Debit instruction.
2. **Provide advance notice**
The payer must be notified in advance of the amount and timing of the debit.
3. **Initiate the debit**
Payments are submitted through the Bacs system according to scheme timelines.
4. **Settle funds**
Funds are transferred over multiple business days.
***
## Requirements
To process a UK Direct Debit payment, you typically need:
* Bank account number
* Sort code
* Account holder name
* Direct Debit instruction (authorization)
Additional requirements may apply depending on the use case.
***
## Timing and settlement
UK Direct Debit follows a fixed processing cycle.
* Payments typically settle in **3 business days**
* Submission deadlines apply based on Bacs processing windows
* Funds are not guaranteed until settlement is complete
***
## Advance notice
Before initiating a payment, you must provide **advance notice** to the payer.
This includes:
* Payment amount
* Collection date
* Frequency (for recurring payments)
Advance notice timing may vary depending on your agreement with the payer.
***
## Direct Debit Guarantee
UK Direct Debit includes a **Direct Debit Guarantee**, which provides strong protections for payers.
Under the guarantee:
* Payers can request an immediate refund from their bank
* Refunds may occur even after settlement
* Banks may reverse payments without prior notice
***
## Returns and reversals
UK Direct Debit payments can be returned or refunded.
Common reasons include:
* Insufficient funds
* Authorization issues
* Customer disputes under the Direct Debit Guarantee
Returns and refunds may occur **after settlement**, depending on scheme rules.
***
## Authorization and instructions
Authorization is required before initiating payments.
A Direct Debit instruction includes:
* Payer consent
* Bank account details
* Agreement to scheme rules
Authorization can be collected through a **setup request** or during a payment flow.
***
## When to use UK Direct Debit
UK Direct Debit is best suited for:
* Recurring payments in GBP
* Subscription or billing use cases
* UK-based payers
* Predictable, scheduled collections
***
## Comparison to cards
| Feature | Cards | UK Direct Debit |
| -------------- | --------- | --------------------------------- |
| Payment type | Push | Pull |
| Currency | Global | GBP |
| Geography | Global | United Kingdom |
| Authorization | Immediate | Requires instruction |
| Settlement | Fast | \~3 business days |
| Failure timing | Immediate | Possible delayed return or refund |
***
## Best practices
* Provide clear and timely advance notice to payers
* Collect and store Direct Debit instructions before initiating payments
* Account for processing timelines in your workflows
* Monitor returns and guarantee-related refunds
***
## Summary
* UK Direct Debit allows you to collect GBP payments from UK bank accounts
* It requires authorization and advance notice before collection
* Settlement follows a fixed multi-day cycle and includes strong payer protections
* It is ideal for recurring and scheduled payments in the UK
# Payment requests
Source: https://docs.withacclaim.com/guides/accept/payment-requests
Request and collect payments from payers through hosted or embedded experiences. Define amount, collect details, and track payments from request to settlement.
A payment request represents a request for funds from a payer.
It defines the **amount**, **currency**, and optional **payer**, and provides a way to collect payment through a **hosted page** or **embedded element**.
Payment requests are the core object for collecting funds in Acclaim.
***
## How payment requests work
Payment requests follow a simple flow: **create**, **collect**, **pay**, and **track**.
1. **Create a payment request**
Define the amount, currency, and optionally the payer and available payment methods.
2. **Present the payment experience**
Use a **hosted page (payment link)** or **embedded element** to collect payment details.
3. **Payer completes the payment**
The payer selects a payment method and submits payment.
4. **Track and reconcile**
Monitor status, receive webhooks, and match the payment to your internal records.
***
## Hosted vs embedded
Payment requests can be fulfilled through two integration models:
### Hosted pages
A **hosted page** is a secure, Acclaim-managed payment page accessed via a link.
Use hosted pages to:
* Send payment links via email, SMS, or other channels
* Launch quickly with minimal integration
* Offload UI, validation, and compliance handling
***
### Embedded elements
**Embedded elements** allow you to integrate payment collection directly into your application.
Use embedded elements to:
* Maintain full control over the user experience
* Embed payment forms within your product
* Customize flows while relying on Acclaim for processing
***
## Creating payment requests
You can create payment requests using:
* **API** — programmatically create and manage requests
* **Console** — create and manage payments on behalf of payers
Once created, the payment request can be:
* Presented immediately
* Shared via a hosted link
* Embedded in your application
***
## Payment request details
A payment request typically includes:
* **Amount and currency**
* **Payer (optional)**
* **Allowed payment methods**
* **Metadata for internal tracking**
Additional fields may be required depending on the **payment method** and **region**.
***
## Payment methods
Payment methods determine how the payer can complete the payment.
Examples include:
* Cards
* Bank debit methods
* Local payment methods
Available methods vary by country and currency. See **Payment methods** for more.
***
## Payers
A payment request can be associated with a payer, or completed without predefining one.
* Known payer → prefill details and reuse across requests
* Unknown payer → collect details during the payment flow
***
## Status and tracking
Each payment request has a lifecycle and status that reflects its current state.
Statuses typically include:
* Pending or awaiting payment
* Processing
* Succeeded
* Failed
Use webhooks to:
* Track payment completion
* Update internal systems
* Trigger downstream workflows
***
## When to use payment requests
Use payment requests when you need to:
* Collect funds from a payer interactively
* Control the payment experience (hosted or embedded)
* Track payments from request through settlement
For other collection models:
* Use **virtual accounts** to receive bank transfers
* Use **setup requests** to collect payment details for future use
***
## Best practices
* **Define clear amounts and currency upfront**
* **Limit payment methods** to those relevant for the payer’s region
* **Use hosted pages** for fast implementation
* **Use embedded elements** for full UX control
* **Leverage webhooks** for real-time updates
***
## Summary
* Payment requests are the core object for collecting funds
* They define what is being paid and how payment is collected
* Hosted and embedded experiences handle payer interaction
* Every payment is tracked from request to completion
# Reconciliation
Source: https://docs.withacclaim.com/guides/accept/reconciliation
Match incoming payments to your internal records. Track funds across payment requests and virtual accounts with structured data and reporting.
Reconciliation is the process of **matching incoming funds to your internal records**.
Acclaim provides structured data across payment requests, payers, and virtual accounts so you can **track, match, and report on payments accurately**.
***
## How reconciliation works
Every incoming payment is recorded with consistent identifiers and metadata.
You can use this data to:
* Match payments to invoices, claims, or internal records
* Track payment status and outcomes
* Reconcile totals across balances and reports
***
## Reconciliation by collection method
### Payment requests
Payment requests provide structured, one-to-one mapping between a request and a payment.
* Each request defines the expected amount and currency
* Completed payments are linked directly to the request
* Metadata can be used to associate payments with internal systems
This makes reconciliation straightforward for request-based payments.
***
### Virtual accounts
Virtual accounts enable reconciliation of **incoming bank transfers**.
* Each account can be assigned to a payer or workflow
* Incoming transfers are linked to the virtual account
* Reference data can be used to identify the purpose of a payment
This reduces ambiguity when receiving bank transfers.
***
### Saved payment methods
When using saved payment methods:
* Payments can be associated with a stored payer
* Reuse of payment methods ensures consistent payer identification
* Payment history can be tracked across multiple transactions
***
## Key reconciliation data
Each payment includes structured data to support reconciliation:
* Payment ID
* Amount and currency
* Status (e.g. **Succeeded**, **Failed**)
* Payer (if available)
* Payment method
* Metadata (custom fields)
Use this data to match payments to your internal records.
***
## Using metadata
Metadata allows you to attach your own identifiers to a payment.
Common use cases:
* Internal invoice ID
* Claim or policy reference
* Customer identifier
Including metadata at the time of creation improves reconciliation accuracy.
***
## Reporting and exports
You can export payment data from the Console for reporting and reconciliation.
Exports typically include:
* Payment details and status
* Amounts and currencies
* Payer information
* Timestamps and identifiers
This data can be used in:
* Accounting systems
* Internal reconciliation workflows
* Financial reporting
***
## Webhooks and automation
Webhooks allow you to automate reconciliation workflows.
Use webhooks to:
* Detect when a payment **succeeds**
* Update internal records automatically
* Trigger downstream processes
This reduces manual reconciliation effort.
***
## Best practices
* Include **metadata** for every payment request
* Assign **virtual accounts strategically** to reduce ambiguity
* Track payments using unique identifiers
* Use **webhooks** to automate reconciliation
* Regularly export and review payment data
***
## Summary
* Reconciliation matches incoming payments to your internal records
* Payment requests and virtual accounts provide structured tracking
* Metadata improves accuracy and automation
* Webhooks and exports enable efficient reconciliation workflows
# Refunds
Source: https://docs.withacclaim.com/guides/accept/refunds
Return funds to payers after a completed payment. Issue full or partial refunds and track their status through completion.
Refunds allow you to **return funds to a payer after a payment has been completed**.
They are used to correct errors, handle cancellations, or resolve customer issues.
***
## How refunds work
Refunds follow a simple flow: **initiate**, **process**, and **complete**.
1. **Initiate a refund**
Select a completed payment and specify the amount to return.
2. **Process the refund**
The refund is submitted through the original payment method.
3. **Complete the refund**
Funds are returned to the payer, and the refund reaches a final state.
***
## Full and partial refunds
You can issue:
* **Full refunds** — return the entire payment amount
* **Partial refunds** — return a portion of the payment
Multiple partial refunds can be issued up to the original payment amount.
***
## Eligibility
Refunds can only be issued for payments that have:
* Reached a **Succeeded** state
* Not already been fully refunded
***
## Refund methods
Refunds are typically sent using the **original payment method**.
* Card payments are refunded back to the card
* Direct debit payments are returned to the payer’s bank account
The exact behavior depends on the payment method and network.
***
## Timing
Refund timing depends on the payment method:
* **Cards** — typically processed within a few business days
* **Direct debit** — may take multiple business days
The payer’s bank may also affect how quickly funds are received.
***
## Status and tracking
Refunds are tracked separately from the original payment.
You can:
* View refund status in the **Console**
* Track refund progress via **webhooks**
* Associate refunds with the original payment
Refunds typically move through:
* Processing
* Completed
***
## Impact on reconciliation
Refunds affect your financial records and reporting.
* The refunded amount is deducted from your balance
* The original payment remains recorded
* Refunds are linked to the original transaction
Ensure your reconciliation process accounts for both payments and refunds.
***
## When to issue a refund
Use refunds when:
* A payment was made in error
* A service or transaction is canceled
* You need to return funds to the payer
***
## Best practices
* Confirm the refund amount before initiating
* Use partial refunds when only a portion needs to be returned
* Communicate refund timing to the payer
* Track refunds alongside original payments for reconciliation
***
## Summary
* Refunds return funds to a payer after a completed payment
* They can be full or partial and are tied to the original payment
* Timing depends on the payment method and network
* Refunds should be tracked and reconciled alongside payments
# Settlement
Source: https://docs.withacclaim.com/guides/accept/settlement
Understand how completed payments are transferred into your Treasury balances, including timing, processing, and availability.
Settlement is the process by which **completed payments are transferred into your Treasury balances**.
It determines when funds move from a successful payment to **available funds** that can be used for payouts, withdrawals, or FX.
***
## How settlement works
Settlement occurs after a payment has successfully completed.
1. A payment reaches a **Succeeded** state
2. The payment is processed through the underlying payment network
3. Funds are transferred and credited into your Treasury account
4. The funds become **available balance** once settlement is complete
Settlement timing depends on the payment method and network.
***
## Settlement timing
Settlement is **asynchronous** and varies by payment method.
Typical behavior:
* **Cards** — settle in batches, typically within a few business days
* **Direct debit** — may take several business days depending on the scheme
* **Local payment methods** — timing varies by country and network
During this period:
* Funds may be reflected as **pending balance**
* They are not yet available for use
***
## Settlement to Treasury
Once settlement completes:
* Funds are credited to a **treasury account**
* The account currency matches the payment currency (or configured settlement currency)
* The funds move from **pending** to **available**
This makes the funds usable for:
* Payouts
* Withdrawals
* FX conversions
***
## Settlement sweeps
You can configure **sweeps** to automatically move settled funds out of Treasury.
* Sweeps withdraw funds to a settlement account on a defined schedule
* Typically run daily or at configured intervals
* Apply to available balances after settlement completes
Sweeps are useful for:
* Maintaining minimal balances in Treasury
* Automating cash movement back to your operating accounts
* Simplifying treasury management
***
## Processor and configuration
Settlement behavior depends on your payment processor and configuration.
Factors that may affect settlement:
* Payment method and network
* Processor settlement schedules
* Currency and region
* Funding model (e.g. prefunded vs pass-through)
***
## Reconciliation implications
Settlement is a key part of reconciliation.
You should:
* Match settled payments to Treasury transactions
* Track timing differences between payment success and settlement
* Account for sweep withdrawals when reconciling balances
* Use reports and exports to verify amounts
Settlement timing differences are a common source of reconciliation gaps if not accounted for.
***
## Key behaviors
* Settlement happens **after a payment succeeds**
* Funds are not immediately available upon success
* Settlement timing varies by payment method
* Funds move from **pending** to **available balance**
* Sweeps can automatically withdraw settled funds
* Settlement creates transactions in Treasury
# Setup requests
Source: https://docs.withacclaim.com/guides/accept/setup-requests
Collect and securely store payment details for future use. Save payment methods through hosted or embedded experiences without initiating a payment.
A setup request collects and securely stores a payer’s payment details for future use.
It allows you to save a **payment method as a token** without initiating a payment.
Setup requests are used when you need to **charge later**, **reuse payment methods**, or support **off-session payments**.
***
## How setup requests work
Setup requests follow a simple flow: **create**, **collect details**, **store**, and **reuse**.
1. **Create a setup request**
Define the payer (optional) and supported payment methods.
2. **Present the collection experience**
Use a **hosted page** or **embedded element** to collect payment details.
3. **Payer submits details**
The payer provides payment method information (e.g. card or bank details).
4. **Store payment method**
The payment method is securely stored as a token and can be used in future payment flows.
***
## Hosted vs embedded
Setup requests can be fulfilled through two integration models:
### Hosted pages
A **hosted page** is a secure, Acclaim-managed page accessed via a link.
Use hosted pages to:
* Collect payment details without building UI
* Share links via email or messaging
* Ensure secure handling of sensitive data
***
### Embedded elements
**Embedded elements** allow you to collect payment details directly within your application.
Use embedded elements to:
* Control the user experience
* Embed secure payment forms
* Maintain a consistent product flow
***
## What is stored
When a setup request is completed:
* Payment details are **securely stored and tokenized**
* Sensitive data is **not exposed to your systems**
* A **payment method token** is returned for future use
This token can be used to:
* Create future payment requests
* Initiate payments without re-collecting details
***
## Relationship to payment requests
* **Setup requests** collect and store payment details
* **Payment requests** collect funds
You can combine both flows:
1. Save a payment method
2. Use the stored method in a future payment request
***
## Payment methods
Setup requests support payment methods that can be stored for reuse.
Examples include:
* Cards
* Bank debit methods
Supported methods vary by country and currency.
***
## Payers
A setup request can optionally be associated with a payer.
* Known payer → store and reuse payment methods
* Unknown payer → collect and associate during the flow
***
## Status and tracking
Each setup request has a lifecycle and status.
Statuses typically include:
* Pending or awaiting completion
* Completed
* Failed
Use webhooks to:
* Track completion
* Store tokens in your system
* Trigger follow-up workflows
***
## When to use setup requests
Use setup requests when you need to:
* Collect payment details without charging immediately
* Support future or recurring payments
* Enable off-session payments
* Reduce friction for repeat payers
***
## Best practices
* **Save once, reuse many times**
* **Associate tokens with payers** for easier reuse
* **Limit supported payment methods** to relevant options
* **Use webhooks** to capture completion events
***
## Summary
* Setup requests collect and store payment details for future use
* No funds are moved during saving payment methods
* Payment methods are stored as secure tokens
* Tokens can be reused in future payment flows
# Virtual accounts
Source: https://docs.withacclaim.com/guides/accept/virtual-accounts
Receive bank transfers using dedicated virtual account details. Assign accounts to payers or workflows and automatically reconcile incoming funds.
Virtual accounts are bank account details used to receive incoming transfers from payers.
They allow you to collect funds via **bank transfer** without requiring a hosted or embedded payment experience.
Each virtual account can be used to **identify, route, and reconcile incoming funds** automatically.
***
## How virtual accounts work
Virtual accounts follow a simple flow: **assign**, **receive**, and **reconcile**.
1. **Provision a virtual account**
Create or assign a virtual account with specific bank details.
2. **Share account details**
Provide the account details to a payer or embed them in your workflow.
3. **Receive funds**
The payer sends a bank transfer to the virtual account.
4. **Track and reconcile**
Incoming funds are recorded and can be matched to a payer, payment, or internal reference.
***
## Assigning virtual accounts
Virtual accounts can be used in different ways depending on your workflow:
* **Per payer** — assign a dedicated account to each payer
* **Per payment or invoice** — generate unique details for a specific transaction
* **Shared accounts with references** — use a single account with reference data to identify payments
Assigning accounts strategically improves **matching accuracy** and **operational efficiency**.
***
## Reconciliation
Virtual accounts simplify reconciliation by linking incoming transfers to your system.
You can:
* Match funds to a **payer** or **payment request**
* Use **reference information** to identify payments
* Track incoming transfers in real time
This reduces manual reconciliation and improves accuracy.
***
## Supported transfers
Virtual accounts support incoming transfers through bank payment rails.
Examples include:
* Domestic bank transfers
* International wire transfers (where supported)
Availability depends on **country and currency**. For the current list of supported regions, currencies, and funding methods, see [Virtual accounts (Treasury)](/guides/treasury/virtual-accounts#supported-regions-and-capabilities).
***
## When to use virtual accounts
Use virtual accounts when:
* Payers prefer to **send bank transfers directly**
* You want to **avoid payer-facing payment flows**
* You need **high-confidence reconciliation** for incoming funds
* You are handling **large or recurring transfers**
***
## Relationship to payment requests
* **Virtual accounts** receive funds via transfer
* **Payment requests** collect funds through hosted or embedded experiences
You can combine both:
* Send a payment request for immediate payment
* Provide a virtual account as an alternative payment method
***
## Relationship to payers
Virtual accounts can be associated with payers to improve tracking:
* Assigning a dedicated account per payer simplifies reconciliation
* Incoming funds can be automatically linked to the correct payer
***
## Tracking and status
Incoming transfers are tracked as they are received.
You can:
* Monitor incoming funds in the **Console**
* Receive updates via **webhooks**
* Track payment status and reconciliation
***
## Best practices
* **Assign dedicated accounts** where possible to reduce ambiguity
* **Use reference fields** when sharing accounts across payers
* **Communicate clear instructions** to payers for transfers
* **Monitor incoming funds** and reconcile promptly
***
## Summary
* Virtual accounts enable you to **receive bank transfers directly**
* They provide **structured tracking and reconciliation** for incoming funds
* They are ideal for transfer-based collection workflows
* They complement payment requests and setup requests
***
## Related resources
* [Virtual accounts (Treasury)](/guides/treasury/virtual-accounts) — supported countries, currencies, and funding methods
# Batch payouts
Source: https://docs.withacclaim.com/guides/disburse/batch-payouts
Send and manage a high volume of payouts at once. Use batches to process payouts at scale with visibility into execution, FX, and outcomes.
Batch payouts let you send multiple payouts in a single operation.
They are designed for workflows where you need to **process many payouts together**, such as claims runs, vendor payments, or scheduled disbursements.
Using batches provides **visibility, control, and efficiency** when operating at scale.
***
## When to use batch payouts
Use batch payouts when you need to:
* **Send large volumes of payouts** at once
* **Group related payouts** into a single execution
* **Track outcomes collectively** (e.g. by run, file, or event)
* **Reduce operational overhead** compared to individual payouts
***
## How batch payouts work
A batch groups multiple payouts into a single unit of execution.
1. **Create a batch**
Define a batch and include one or more payouts.
2. **Validate payouts**
Each payout is validated for required details, payout method compatibility, and readiness.
3. **Lock FX (if applicable)**
For cross-border payouts, Acclaim generates a **single FX quote per currency pair within the batch**.
This ensures consistent conversion rates across all payouts sharing the same source and destination currencies.
4. **Process the batch**
Payouts are submitted for processing. Each payout progresses through its own **lifecycle and status**.
5. **Track results**
Monitor outcomes at both the **batch level** and **individual payout level**.
***
## Batch vs individual payouts
* A **batch** is a container for multiple payouts
* Each **payout** inside the batch is processed independently
This means:
* Some payouts may **succeed** while others **fail**
* Failures do not block the entire batch
* Each payout maintains its own **status and lifecycle**
For cross-border payouts:
* FX is **grouped at the batch level**
* Execution and delivery remain **independent per payout**
***
## Creating batch payouts
You can create batch payouts using:
* **API** — programmatically create and submit batches
* **File uploads** — upload a structured file containing payouts
* **Console** — create and review batches manually
File uploads are commonly used for **high-volume batch workflows**.
***
## Validation and readiness
Before processing, each payout in a batch must be in a valid state.
Common requirements:
* Payee details are complete
* A valid payout method is available
* Required approvals are completed (if applicable)
Payouts that are not ready will remain in:
* **RequiresPayeeInfo**
* **RequiresPayoutMethod**
* **NeedsApproval**
Only payouts in **ReadyToProcess** will move into execution.
***
## FX and currency conversion
When a batch includes payouts across currencies:
* A **single FX quote is generated per currency pair** (e.g. USD → EUR)
* All payouts using that pair share the **same rate**
* This ensures **consistency and predictability** across the batch
Benefits:
* Simplified reconciliation
* Consistent recipient outcomes
* Reduced rate fragmentation across payouts
***
## Processing behavior
When a batch is processed:
* Eligible payouts move to **Processing**
* Payouts are sent through their selected payout methods
* Status updates occur asynchronously
Batch execution does not guarantee simultaneous delivery. Timing may vary based on:
* Payout method
* Country and currency
* External payment networks
***
## Tracking batch results
Track batch performance at two levels:
### Batch level
* Total number of payouts
* Number of payouts by status
* FX quotes applied per currency pair
* Overall progress and completion
### Payout level
* Individual payout status
* Failure reasons
* Delivery confirmations
This allows you to quickly identify:
* Which payouts succeeded
* Which require action
***
## Handling failures in batches
Failures are handled at the payout level.
If a payout fails:
* Review the failure reason
* Correct any issues (e.g. payee details, payout method)
* Retry the payout independently
You do not need to reprocess the entire batch.
***
## Best practices
* **Validate data upfront** to minimize failures
* **Group logically related payouts** (e.g. by run or event)
* **Use batches to consolidate FX exposure** across payouts
* **Monitor batch results** during and after processing
* **Use webhooks** to track status changes programmatically
***
## Summary
* Batch payouts enable **scalable payout execution**
* FX is **grouped per currency pair**, ensuring consistent rates
* Each payout maintains its own **lifecycle and status**
* Failures are **isolated and recoverable**
* Batches provide **visibility and operational efficiency** for high-volume workflows
# Albania
Source: https://docs.withacclaim.com/guides/disburse/countries/albania
Payout methods, timing, transaction limits, and required fields for payouts to Albania.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`ALL`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `ALL`, `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^AL[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `AL47212110090000000235698741`
#### Tax ID Type
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### NIPT (business tax ID)
NIPT (Numri i Identifikimit për Personin e Tatueshëm): 10 characters — letter, 8 digits, check letter
**Validation:**
* Exactly 10 characters.
* Must match this regular expression: `^[A-Za-z][0-9]{8}[A-Za-z]$`
**Example:** `A12345678B`
#### Tax ID Type
**Value:** `INDIVIDUAL_TAX_ID`
#### NIPT (personal tax ID)
NIPT (Numri i Identifikimit për Personin e Tatueshëm): 10 characters — letter, 8 digits, check letter
**Validation:**
* Exactly 10 characters.
* Must match this regular expression: `^[A-Za-z][0-9]{8}[A-Za-z]$`
**Example:** `A12345678B`
### Notes
* A beneficiary tax ID is only required when the payout currency is ALL (Albanian lek).
* 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.
# Algeria
Source: https://docs.withacclaim.com/guides/disburse/countries/algeria
Payout methods, timing, transaction limits, and required fields for payouts to Algeria.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `DZD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `DZD`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BNALDZALXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# American Samoa
Source: https://docs.withacclaim.com/guides/disburse/countries/american-samoa
Payout methods, timing, transaction limits, and required fields for payouts to American Samoa.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BOHIASP1`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789`
### 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.
# Andorra
Source: https://docs.withacclaim.com/guides/disburse/countries/andorra
Payout methods, timing, transaction limits, and required fields for payouts to Andorra.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^AD[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `AD1200012030200359100100`
### 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.
# Angola
Source: https://docs.withacclaim.com/guides/disburse/countries/angola
Payout methods, timing, transaction limits, and required fields for payouts to Angola.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BFMXAOLU`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Anguilla
Source: https://docs.withacclaim.com/guides/disburse/countries/anguilla
Payout methods, timing, transaction limits, and required fields for payouts to Anguilla.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `ANGUAIAI`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Antigua & Barbuda
Source: https://docs.withacclaim.com/guides/disburse/countries/antigua-barbuda
Payout methods, timing, transaction limits, and required fields for payouts to Antigua & Barbuda.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `ANCBAGAG`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Argentina
Source: https://docs.withacclaim.com/guides/disburse/countries/argentina
Payout methods, timing, transaction limits, and required fields for payouts to Argentina.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Interbanking Coelsa | ARS | 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.
## Interbanking Coelsa
Argentine Interbanking Coelsa payment system
### Supported currencies
`ARS`
### 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
**Value:** `ArgentinaCoelsa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### CBU (Clave Bancaria Uniforme)
22-digit CBU starting with 3-digit bank code, 4-digit branch code, check digit, and 13-digit account number
**Validation:**
* Exactly 22 characters.
* Must match this regular expression: `^[0-9]{22}$`
**Example:** `1234567890123456789012`
#### Tax ID Type
**Conditional:** Required for Company payees only.
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### CUIT (Business Tax ID)
**Conditional:** Required for Company payees only.
11-digit CUIT (Clave Única de Identificación Tributaria)
**Validation:**
* Exactly 11 characters.
* Must match this regular expression: `^[0-9]{11}$`
**Example:** `20123456789`
#### Personal ID Type
**Conditional:** Required for Individual payees only.
**Value:** One of `INDIVIDUAL_TAX_ID`, `ENTITY_TAX_ID`
Select as registered with the bank account
#### Personal ID Number
**Conditional:** Required for Individual payees only.
11-digit CUIL or CUIT as registered with the bank account
**Validation:**
* Exactly 11 characters.
* Must match this regular expression: `^[0-9]{11}$`
**Example:** `20123456789`
### Notes
* The Argentine government sets a 1.20% tax (Impuesto al cheque: Tax on Credits and Debits) per transaction, which is collected automatically in addition to the payout transaction fee.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NACNARBA`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `2590123456789012345678`
### 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.
# Armenia
Source: https://docs.withacclaim.com/guides/disburse/countries/armenia
Payout methods, timing, transaction limits, and required fields for payouts to Armenia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AMD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AMD`, `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BYBAAM22XXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Aruba
Source: https://docs.withacclaim.com/guides/disburse/countries/aruba
Payout methods, timing, transaction limits, and required fields for payouts to Aruba.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `ARUBAWAX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Australia
Source: https://docs.withacclaim.com/guides/disburse/countries/australia
Payout methods, timing, transaction limits, and required fields for payouts to Australia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| New Payments Platform | AUD | 0-1 business days |
| Direct Entry (BECS) | AUD | 0-2 business days |
| BPAY | AUD | 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.
## New Payments Platform
Australian real-time payment system with PayID
### Supported currencies
`AUD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 AUD |
### Fields
#### Payout Method Type
**Value:** `AustraliaNpp`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Transfer Method
**Value:** One of `bsb`, `phone_number`, `email_address`, `australian_business_number`, `organisation_identifier`
#### Transfer Method Value
Email, mobile number (+61), ABN, or ACN
**Validation:**
* `payid_validation`
**Example:** `john.smith@email.com or +61412345678`
#### Account Number
**Validation:**
* Between 6 and 10 characters (inclusive).
* Must match this regular expression: `^[0-9]{6,10}$`
**Example:** `12345678`
## Direct Entry (BECS)
Australian direct entry bank transfer
### Supported currencies
`AUD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `AustraliaBecs`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bsb`
#### BSB Number
6-digit BSB in XXX-XXX format
**Validation:**
* At most 7 characters.
* Must match this regular expression: `^(?:[0-9]{6}|[0-9]{3}-[0-9]{3})$`
**Example:** `062-001`
#### Account Number
**Validation:**
* Between 6 and 10 characters (inclusive).
* Must match this regular expression: `^[0-9]{6,10}$`
**Example:** `12345678`
## BPAY
Australian BPAY bill payment system
### Supported currencies
`AUD`
### 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
**Value:** `AustraliaBpay`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bpay_biller_code`
#### BPAY Biller Code
Unique number registered on BPAY to identify a biller (up to 10 digits)
**Validation:**
* Between 1 and 10 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,10}$`
**Example:** `75556`
#### Routing Type 2
**Value:** `bpay_customer_reference`
#### Customer Reference Number (CRN)
Unique number that the biller uses to identify your account or invoice (up to 20 digits)
**Validation:**
* Between 1 and 20 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,20}$`
**Example:** `123456789012345678`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NATAAU3302S`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 6 and 20 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{6,20}$`
**Example:** `716978952`
### 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.
# Austria
Source: https://docs.withacclaim.com/guides/disburse/countries/austria
Payout methods, timing, transaction limits, and required fields for payouts to Austria.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^AT[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `AT472011131003101197`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^AT[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `AT472011131003101197`
### 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.
# Azerbaijan
Source: https://docs.withacclaim.com/guides/disburse/countries/azerbaijan
Payout methods, timing, transaction limits, and required fields for payouts to Azerbaijan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `AZN`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `AZN`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^AZ[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `AZ21NABZ00000000137010001944`
#### Tax ID Type
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### TIN / VOEN (business tax ID)
10-digit tax identification number (TIN/VOEN)
**Validation:**
* Exactly 10 characters.
* Must match this regular expression: `^[0-9]{10}$`
**Example:** `1234567890`
#### Tax ID Type
**Value:** `INDIVIDUAL_TAX_ID`
#### TIN / VOEN (personal tax ID)
10-digit tax identification number (TIN/VOEN)
**Validation:**
* Exactly 10 characters.
* Must match this regular expression: `^[0-9]{10}$`
**Example:** `1234567890`
### Notes
* A beneficiary tax ID is only required when the payout currency is AZN (Azerbaijani manat).
* 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.
# Bahamas
Source: https://docs.withacclaim.com/guides/disburse/countries/bahamas
Payout methods, timing, transaction limits, and required fields for payouts to Bahamas.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `BSD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `BSD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BBHMBSNS`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `001523017890`
### 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.
# Bahrain
Source: https://docs.withacclaim.com/guides/disburse/countries/bahrain
Payout methods, timing, transaction limits, and required fields for payouts to Bahrain.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Fawri+ | BHD | 2-3 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.
## Fawri+
Bahrain Fawri+ payment system
### Supported currencies
`BHD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `BahrainFawri`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^BH[0-9]{2}[A-Z]{4}[0-9A-Z]{14}$`
**Example:** `BH02CITI00001077181611`
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `BHD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `BHD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^BH[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `BH67BMAG00001299123456`
### 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.
# Bangladesh
Source: https://docs.withacclaim.com/guides/disburse/countries/bangladesh
Payout methods, timing, transaction limits, and required fields for payouts to Bangladesh.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| NPSB | BDT | 1-2 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.
## NPSB
Bangladesh NPSB payment system
### Supported currencies
`BDT`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 1-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----------- |
| Minimum | 50 BDT |
| Maximum | 200,000 BDT |
### Fields
#### Payout Method Type
**Value:** `BangladeshNpsb`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `routing_number`
#### Routing Number
9-digit number to identify a Bangladeshi bank
**Validation:**
* Exactly 9 characters.
* Must match this regular expression: `^[0-9]{9}$`
**Example:** `260260435`
#### Account Number
**Validation:**
* At most 50 characters.
**Example:** `Enter account number`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `DHBLBDDH`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Barbados
Source: https://docs.withacclaim.com/guides/disburse/countries/barbados
Payout methods, timing, transaction limits, and required fields for payouts to Barbados.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `BBD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `BBD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `FCIBBBBBXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `010134567890`
### 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.
# Belarus
Source: https://docs.withacclaim.com/guides/disburse/countries/belarus
Payout methods, timing, transaction limits, and required fields for payouts to Belarus.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^BY[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `BY13NBRB3600900000002Z00AB00`
### 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.
# Belgium
Source: https://docs.withacclaim.com/guides/disburse/countries/belgium
Payout methods, timing, transaction limits, and required fields for payouts to Belgium.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 16 characters.
* IBAN format; must match: `^BE[0-9]{2}[a-zA-Z0-9]{12}$`
**Example:** `BE46735007997636`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 16 characters.
* IBAN format; must match: `^BE[0-9]{2}[a-zA-Z0-9]{12}$`
**Example:** `BE46735007997636`
### 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.
# Belize
Source: https://docs.withacclaim.com/guides/disburse/countries/belize
Payout methods, timing, transaction limits, and required fields for payouts to Belize.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `BZD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `BZD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BBLZBZBZ`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `100171421`
### 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.
# Benin
Source: https://docs.withacclaim.com/guides/disburse/countries/benin
Payout methods, timing, transaction limits, and required fields for payouts to Benin.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| ----------------------------- | ---------- | ----------------- |
| Central Africa Local Transfer | XOF | 2-3 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.
## Central Africa Local Transfer
Central Africa local bank transfer
### Supported currencies
`XOF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `CentralAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNSNX1`
#### Account Number
Account number (exactly 24 alphanumeric characters)
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[A-Za-z0-9]{24}$`
**Example:** `123456789012345678901234`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `ECOCBJBJ`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[0-9A-Za-z]{24}$`
**Example:** `012345678901234567890123`
### 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.
# Bermuda
Source: https://docs.withacclaim.com/guides/disburse/countries/bermuda
Payout methods, timing, transaction limits, and required fields for payouts to Bermuda.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BNTBBMHMXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `110023456789`
### 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.
# Bhutan
Source: https://docs.withacclaim.com/guides/disburse/countries/bhutan
Payout methods, timing, transaction limits, and required fields for payouts to Bhutan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BNBTBTBTXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `120034567890`
### 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.
# Bolivia
Source: https://docs.withacclaim.com/guides/disburse/countries/bolivia
Payout methods, timing, transaction limits, and required fields for payouts to Bolivia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| ACCL | BOB | 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.
## ACCL
Bolivian ACCL payment system
### Supported currencies
`BOB`
### 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
**Value:** `BoliviaAccl`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
Bank code (1-2 digits). Examples: 1 (Banco Mercantil), 2 (Banco Nacional de Bolivia), 6 (Banco Unión)
**Validation:**
* Between 1 and 2 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,2}$`
**Example:** `1`
#### Routing Type 2
**Value:** `branch_code`
#### Branch Code
Branch code (optional, 1-10 digits)
**Validation:**
* Between 1 and 10 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,10}$`
**Example:** `12345`
#### Account Number
Account number (10-15 digits). Length varies by bank: Banco Mercantil (10), Banco Nacional de Bolivia (10), Banco Unión (14), Other banks (up to 15)
**Validation:**
* Between 10 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9]{10,15}$`
**Example:** `1234567890`
#### Account Type
**Value:** One of `checking`, `savings`, `vista`
#### Tax ID Type
**Conditional:** Required for Company payees only.
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### NIT (Business Tax ID)
**Conditional:** Required for Company payees only.
Tax ID (NIT: Número de Identificación Tributaria) up to 15 digits
**Validation:**
* Between 1 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,15}$`
**Example:** `123456789012345`
#### Personal ID Type
**Conditional:** Required for Individual payees only.
**Value:** One of `NATIONAL_ID`, `FOREIGN_ID`, `INDIVIDUAL_TAX_ID`
Select as registered with the bank account
#### Personal ID Number
**Conditional:** Required for Individual payees only.
ID number as registered with the bank account. Format: National ID (up to 8 digits), Foreign ID (E- followed by up to 8 digits), Tax ID (up to 15 digits).
**Validation:**
* Between 1 and 15 characters (inclusive).
* Must match this regular expression: `^(E-[0-9]{1,8}|[0-9]{1,15})$`
**Example:** `12345678 or E-12345678`
### Notes
* The Bolivian government sets a 0.30% tax (Impuesto a las Transacciones Financieras: Tax on Financial Transactions) per transaction, which is collected automatically in addition to the payout transaction fee.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `BOB`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `BOB`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCPLBOLX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Bosnia & Herzegovina
Source: https://docs.withacclaim.com/guides/disburse/countries/bosnia-herzegovina
Payout methods, timing, transaction limits, and required fields for payouts to Bosnia & Herzegovina.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `BAM`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `BAM`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^BA[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `BA391290079401028494`
### 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.
# Botswana
Source: https://docs.withacclaim.com/guides/disburse/countries/botswana
Payout methods, timing, transaction limits, and required fields for payouts to Botswana.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Botswana Local Transfer | BWP | 2-3 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.
## Botswana Local Transfer
Botswanan local bank transfer
### Supported currencies
`BWP`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `BotswanaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNBWGX`
#### Routing Type
**Value:** `branch_code`
#### Bank Branch Code
6-digit bank branch code
**Validation:**
* Exactly 6 characters.
* Must match this regular expression: `^[0-9]{6}$`
**Example:** `123456`
#### Account Number
Account number (up to 33 alphanumeric characters)
**Validation:**
* Between 1 and 33 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{1,33}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CSERBWG1`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 7 and 20 characters (inclusive).
* Must match this regular expression: `^[0-9]{7,20}$`
**Example:** `1234567890`
### 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.
# Brazil
Source: https://docs.withacclaim.com/guides/disburse/countries/brazil
Payout methods, timing, transaction limits, and required fields for payouts to Brazil.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Pix | BRL | 0-1 business days |
| TED | BRL | 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.
## Pix
Brazil Pix instant payment
### Supported currencies
`BRL`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `BrazilPix`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Pix Key
Phone number, email address, CPF/CNPJ, or random alias
**Validation:**
* At most 255 characters.
**Example:** `+5511987654321`
### Notes
* The Brazilian government sets a 0.38% tax (IOF) per transaction, collected as part of transfer fees.
## TED
Brazil TED bank transfer
### Supported currencies
`BRL`
### 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
**Value:** `BrazilCipSiloc`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
**Value:** One of `644`, `574`, `406`, `332`, `663`, `577`, `272`, `599`, `572`, `349`, `482`, `594`, `513`, `527`, `508`, `562`, `463`, `461`, `188`, `280`, `654`, `330`, `334`, `412`, `266`, `241`, `222`, `626`, `390`, `653`, `426`, `376`, `757`, `719`, `381`, `066`, `007`, `088`, `741`, `120`, `276`, `366`, `082`, `634`, `591`, `378`, `496`, `415`, `720`, `475`, `250`, `768`, `550`, `091`, `144`, `698`, `531`, `377`, `547`, `017`, `383`, `301`, `271`, `126`, `433`, `568`, `173`, `292`, `080`, `246`, `075`, `121`, `025`, `065`, `213`, `413`, `096`, `752`, `208`, `024`, `318`, `107`, `218`, `063`, `036`, `122`, `394`, `237`, `336`, `368`, `473`, `040`, `739`, `233`, `745`, `748`, `756`, `505`, `069`, `707`, `335`, `265`, `224`, `094`, `278`, `612`, `012`, `604`, `077`, `249`, `479`, `184`, `029`, `074`, `217`, `076`, `600`, `456`, `389`, `370`, `746`, `243`, `169`, `212`, `079`, `712`, `623`, `611`, `643`, `747`, `633`, `422`, `033`, `743`, `754`, `630`, `637`, `464`, `387`, `018`, `610`, `393`, `655`, `371`, `119`, `124`, `348`, `003`, `083`, `070`, `300`, `001`, `047`, `037`, `041`, `004`, `081`, `021`, `755`, `268`, `253`, `408`, `465`, `324`, `159`, `098`, `421`, `089`, `016`, `112`, `099`, `584`, `582`, `583`, `580`, `391`, `673`, `430`, `470`, `385`, `328`, `509`, `581`, `362`, `542`, `180`, `402`, `423`, `569`, `379`, `440`, `350`, `273`, `543`, `403`, `427`, `429`, `010`, `452`, `011`, `428`, `321`, `133`, `104`, `288`, `320`, `477`, `163`, `136`, `085`, `281`, `097`, `342`, `435`, `680`, `487`, `575`, `449`, `646`, `134`, `111`, `101`, `676`, `289`, `664`, `532`, `693`, `760`, `534`, `514`, `395`, `196`, `541`, `343`, `510`, `587`, `678`, `382`, `714`, `512`, `450`, `566`, `305`, `661`, `285`, `455`, `589`, `478`, `364`, `703`, `636`, `384`, `064`, `684`, `540`, `458`, `448`, `674`, `523`, `189`, `269`, `312`, `078`, `062`, `157`, `132`, `439`, `398`, `687`, `764`, `492`, `701`, `525`, `143`, `549`, `670`, `597`, `401`, `139`, `341`, `652`, `451`, `488`, `559`, `688`, `399`, `416`, `414`, `469`, `519`, `667`, `397`, `293`, `145`, `484`, `560`, `396`, `511`, `592`, `141`, `467`, `576`, `518`, `567`, `447`, `526`, `259`, `128`, `681`, `544`, `323`, `537`, `358`, `274`, `454`, `536`, `191`, `386`, `140`, `419`, `689`, `753`, `260`, `443`, `546`, `319`, `659`, `535`, `762`, `331`, `613`, `660`, `557`, `555`, `254`, `326`, `679`, `561`, `521`, `553`, `174`, `380`, `529`, `410`, `445`, `468`, `563`, `588`, `290`, `194`, `125`, `306`, `495`, `558`, `329`, `516`, `579`, `283`, `528`, `374`, `522`, `590`, `620`, `506`, `548`, `177`, `539`, `614`, `556`, `117`, `142`, `127`, `060`, `138`, `146`, `113`, `100`, `131`, `130`, `507`, `149`, `105`, `093`, `407`, `545`, `530`, `585`, `578`, `365`, `363`, `615`, `425`, `520`, `692`, `533`, `665`, `462`, `014`, `672`, `554`, `538`, `404`, `481`, `751`, `190`, `183`, `299`, `197`, `322`, `352`, `593`, `360`, `444`, `619`, `438`, `685`, `307`, `095`, `129`, `015`, `460`, `373`, `666`, `457`, `552`, `084`, `195`, `551`, `668`, `411`, `298`, `763`, `296`, `310`, `662`, `524`, `694`, `102`, `632`, `586`, `359`, `418`, `595`, `565`
#### Routing Type 2
**Value:** `branch_code`
#### Branch Code
4-digit branch code, optionally followed by hyphen and up to 2 alphanumeric characters
**Validation:**
* Between 4 and 7 characters (inclusive).
* Must match this regular expression: `^(?:[0-9]{4}|[0-9]{4}-[0-9A-Za-z]{0,2}|[0-9]{4}[0-9A-Za-z]{1,2})$`
**Example:** `1234 or 1234-1`
#### Account Number
Account number (up to 9 digits)
**Validation:**
* Between 1 and 11 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,9}(-[0-9Xx])?$`
**Example:** `12345678 or 12345678-9`
#### Account Type
**Value:** One of `checking`, `savings`
#### Tax ID Type
**Conditional:** Required for Company payees only.
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### CNPJ (Cadastro Nacional de Pessoas Jurídicas)
**Conditional:** Required for Company payees only.
**Validation:**
* Between 14 and 18 characters (inclusive).
* Must match this regular expression: `^[0-9]{14}$|^[0-9]{2}\.[0-9]{3}\.[0-9]{3}/[0-9]{4}-[0-9]{2}$`
**Example:** `12345678000190 or 12.345.678/0001-90`
#### Tax ID Type
**Conditional:** Required for Individual payees only.
**Value:** `INDIVIDUAL_TAX_ID`
#### CPF (Cadastro de Pessoas Físicas)
**Conditional:** Required for Individual payees only.
11 digits
**Validation:**
* Between 11 and 14 characters (inclusive).
* Must match this regular expression: `^[0-9]{11}$|^[0-9]{3}\.[0-9]{3}\.[0-9]{3}-[0-9]{2}$`
**Example:** `12345678901 or 123.456.789-01`
### Notes
* The Brazilian government sets a 0.38% tax (Imposto sobre Operações Financeiras: Tax on Financial Operations) per transaction, which is collected automatically in addition to the payout transaction fee.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BRASBRRJ`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `12345678`
### 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.
# British Virgin Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/british-virgin-islands
Payout methods, timing, transaction limits, and required fields for payouts to British Virgin Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^VG[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `VG96VPVG0000012345678901`
### 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.
# Brunei
Source: https://docs.withacclaim.com/guides/disburse/countries/brunei
Payout methods, timing, transaction limits, and required fields for payouts to Brunei.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BIBDBNBBXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `140056789012`
### 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.
# Bulgaria
Source: https://docs.withacclaim.com/guides/disburse/countries/bulgaria
Payout methods, timing, transaction limits, and required fields for payouts to Bulgaria.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Bulgaria Local Transfer | BGN | 2-3 business days |
| SEPA | EUR | 0-2 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.
## Bulgaria Local Transfer
Bulgarian local bank transfer
### Supported currencies
`BGN`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ---------- |
| Minimum | None |
| Maximum | 30,000 BGN |
### Fields
#### Payout Method Type
**Value:** `BulgariaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^BG[0-9]{2}[A-Z0-9]{4}[0-9]{4}[A-Z0-9]{10}$`
**Example:** `BG18RZBB91550123456789`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^BG[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `BG80BNBG96611020345678`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^BG[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `BG80BNBG96611020345678`
### 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.
# Burkina Faso
Source: https://docs.withacclaim.com/guides/disburse/countries/burkina-faso
Payout methods, timing, transaction limits, and required fields for payouts to Burkina Faso.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| ----------------------------- | ---------- | ----------------- |
| Central Africa Local Transfer | XOF | 2-3 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.
## Central Africa Local Transfer
Central Africa local bank transfer
### Supported currencies
`XOF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `CentralAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNSNX1`
#### Account Number
Account number (exactly 24 alphanumeric characters)
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[A-Za-z0-9]{24}$`
**Example:** `123456789012345678901234`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `AFRIBFBF`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[0-9A-Za-z]{24}$`
**Example:** `012345678901234567890123`
### 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.
# Cambodia
Source: https://docs.withacclaim.com/guides/disburse/countries/cambodia
Payout methods, timing, transaction limits, and required fields for payouts to Cambodia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CPBLKHPP`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Cameroon
Source: https://docs.withacclaim.com/guides/disburse/countries/cameroon
Payout methods, timing, transaction limits, and required fields for payouts to Cameroon.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| West Africa Local Transfer | XAF | 2-3 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.
## West Africa Local Transfer
West African local bank transfer
### Supported currencies
`XAF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 50,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `WestAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNCMX1`
#### Account Number
Account number (exactly 23 alphanumeric characters)
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[A-Za-z0-9]{23}$`
**Example:** `12345678901234567890123`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `UNAFCMCX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[0-9A-Za-z]{23}$`
**Example:** `01234567890123456789012`
### 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.
# Canada
Source: https://docs.withacclaim.com/guides/disburse/countries/canada
Payout methods, timing, transaction limits, and required fields for payouts to Canada.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| EFT | CAD | 0-1 business days |
| Interac e-Transfer | CAD | 0-1 business days |
| Bill Payment | CAD | 3-4 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.
## EFT
Canadian EFT system for domestic transfers
### Supported currencies
`CAD`
### 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 | 2,000,000 CAD |
### Fields
#### Payout Method Type
**Value:** `CanadaEft`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Institution Number
3-digit bank identification number
**Validation:**
* Exactly 3 characters.
* Must match this regular expression: `^[0-9]{3}$`
**Example:** `003`
#### Routing Type
**Value:** `institution_number`
#### Transit Number
5-digit branch identification number
**Validation:**
* Exactly 5 characters.
* Must match this regular expression: `^[0-9]{5}$`
**Example:** `00001`
#### Routing Type 2
**Value:** `transit_number`
#### Account Number
**Validation:**
* Between 7 and 12 characters (inclusive).
* Must match this regular expression: `^[0-9]{7,12}$`
**Example:** `1234567`
## Interac e-Transfer
Email or SMS-based money transfer
### Supported currencies
`CAD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ---------- |
| Minimum | None |
| Maximum | 25,000 CAD |
### Fields
#### Payout Method Type
**Value:** `CanadaInterac`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Email
Email address that will receive funds
**Validation:**
* `email_or_phone`
**Example:** `john@example.com`
## Bill Payment
Canadian Bill Payment system
### Supported currencies
`CAD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 3-4 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `CanadaBillPayment`
#### Routing Type
**Value:** `biller_id`
#### Biller ID
6-digit number to identify the biller
**Validation:**
* Exactly 6 characters.
* Must match this regular expression: `^[0-9]{6}$`
**Example:** `990001`
#### Account Number
**Validation:**
* At most 50 characters.
**Example:** `Enter account number`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CIBCCATT`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 7 and 35 characters (inclusive).
* Must match this regular expression: `^[a-zA-Z0-9]{7,35}$`
**Example:** `7751788`
### 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.
# Canary Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/canary-islands
Payout methods, timing, transaction limits, and required fields for payouts to Canary Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^ES[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `ES7921000813610123456789`
### 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.
# Cape Verde
Source: https://docs.withacclaim.com/guides/disburse/countries/cape-verde
Payout methods, timing, transaction limits, and required fields for payouts to Cape Verde.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CGDICVCPXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `160078901234`
### 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.
# Cayman Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/cayman-islands
Payout methods, timing, transaction limits, and required fields for payouts to Cayman Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `ROYCKYKYXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `170089012345`
### 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.
# Central African Republic
Source: https://docs.withacclaim.com/guides/disburse/countries/central-african-republic
Payout methods, timing, transaction limits, and required fields for payouts to Central African Republic.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| West Africa Local Transfer | XAF | 2-3 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.
## West Africa Local Transfer
West African local bank transfer
### Supported currencies
`XAF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 50,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `WestAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNCMX1`
#### Account Number
Account number (exactly 23 alphanumeric characters)
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[A-Za-z0-9]{23}$`
**Example:** `12345678901234567890123`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CBCACFCFXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[0-9A-Za-z]{23}$`
**Example:** `01234567890123456789012`
### 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.
# Chad
Source: https://docs.withacclaim.com/guides/disburse/countries/chad
Payout methods, timing, transaction limits, and required fields for payouts to Chad.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| West Africa Local Transfer | XAF | 2-3 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.
## West Africa Local Transfer
West African local bank transfer
### Supported currencies
`XAF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 50,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `WestAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNCMX1`
#### Account Number
Account number (exactly 23 alphanumeric characters)
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[A-Za-z0-9]{23}$`
**Example:** `12345678901234567890123`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCCXTDNDXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[0-9A-Za-z]{23}$`
**Example:** `01234567890123456789012`
### 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.
# Chile
Source: https://docs.withacclaim.com/guides/disburse/countries/chile
Payout methods, timing, transaction limits, and required fields for payouts to Chile.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| CCA | CLP | 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.
## CCA
Chilean local bank transfer
### Supported currencies
`CLP`
### 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
**Value:** `ChileCca`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
Bank code (1-3 digits)
**Validation:**
* Between 1 and 3 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,3}$`
**Example:** `504`
#### Routing Type 2
**Value:** `branch_code`
#### Account Number
Beneficiary's bank account number (up to 45 alphanumeric characters)
**Validation:**
* Between 1 and 45 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,45}$`
**Example:** `1234567890`
#### Account Type
**Value:** One of `checking`, `savings`
Type of bank account. Confirm the account type with the recipient to avoid transfer delays.
#### Tax ID Type
**Conditional:** Required for Company payees only.
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### RUT (Business Tax ID)
**Conditional:** Required for Company payees only.
Tax ID (RUT: Rol Único Nacional) up to 9 digits with optional check digit
**Validation:**
* Between 1 and 10 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,9}(-[0-9Kk])?$`
**Example:** `12345678-9`
#### Tax ID Type
**Conditional:** Required for Individual payees only.
**Value:** `INDIVIDUAL_TAX_ID`
#### RUT (Personal Tax ID)
**Conditional:** Required for Individual payees only.
Tax ID (RUT: Rol Único Nacional) up to 9 digits
**Validation:**
* Between 1 and 10 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,9}(-[0-9Kk])?$`
**Example:** `12345678-9`
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CLP`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CLP`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCHICLRM`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# China
Source: https://docs.withacclaim.com/guides/disburse/countries/china
Payout methods, timing, transaction limits, and required fields for payouts to China.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| CNAPS | CNY | 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.
## CNAPS
China National Advanced Payment System (CNAPS)
### Supported currencies
`CNY`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ------------- |
| Minimum | None |
| Maximum | 4,999,999 CNY |
### Fields
#### Payout Method Type
**Value:** `ChinaCnaps`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `cnaps`
#### CNAPS Code
12-digit China National Advanced Payment System (CNAPS) code
**Validation:**
* Exactly 12 characters.
* Must match this regular expression: `^[0-9]{12}$`
**Example:** `102100099996`
#### Account Number
Account number (8-34 digits)
**Validation:**
* Between 8 and 34 characters (inclusive).
* Must match this regular expression: `^[0-9]{8,34}$`
**Example:** `12345678901234567890`
#### Bank Name
**Validation:**
* At most 200 characters.
**Example:** `Enter bank name`
#### Business Registration Number
**Conditional:** Required for Company payees only.
Business registration number (up to 30 characters)
**Validation:**
* At most 30 characters.
**Example:** `Enter business registration number`
#### Legal Representative First Name (Chinese)
**Conditional:** Required for Company payees only.
Legal representative's first name in Chinese (up to 15 characters)
**Validation:**
* At most 15 characters.
**Example:** `Enter first name in Chinese`
#### Legal Representative Last Name (Chinese)
**Conditional:** Required for Company payees only.
Legal representative's last name in Chinese (up to 15 characters)
**Validation:**
* At most 15 characters.
**Example:** `Enter last name in Chinese`
#### Legal Representative ID Number
**Conditional:** Required for Company payees only.
Legal representative's ID number (15 or 18 alphanumeric characters)
**Validation:**
* Between 15 and 18 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{15,18}$`
**Example:** `123456789012345678`
#### Personal ID Type
**Conditional:** Required for Individual payees only.
**Value:** `CHINESE_NATIONAL_ID`
#### Chinese National ID Number
**Conditional:** Required for Individual payees only.
Chinese National ID number (15 or 18 alphanumeric characters)
**Validation:**
* Between 15 and 18 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{15,18}$`
**Example:** `123456789012345678`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `PCBCCNBJSZX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 8 and 34 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{8,34}$`
**Example:** `44250100003700000259`
### 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.
# Colombia
Source: https://docs.withacclaim.com/guides/disburse/countries/colombia
Payout methods, timing, transaction limits, and required fields for payouts to Colombia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| CENIT | COP | 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.
## CENIT
Colombian local bank transfer
### Supported currencies
`COP`
### 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
**Value:** `ColombiaCenit`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
3-digit bank code
**Validation:**
* Exactly 3 characters.
* Must match this regular expression: `^[0-9]{3}$`
**Example:** `001`
#### Routing Type 2
**Value:** `branch_code`
#### Branch Code
Branch code (1-5 digits, optional)
**Validation:**
* Between 1 and 5 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,5}$`
**Example:** `12345`
#### Account Number
Account number (6-20 digits)
**Validation:**
* Between 6 and 20 characters (inclusive).
* Must match this regular expression: `^[0-9]{6,20}$`
**Example:** `1234567890`
#### Account Type
**Value:** One of `checking`, `savings`
#### Tax ID Type
**Conditional:** Required for Company payees only.
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### NIT (Business Tax ID)
**Conditional:** Required for Company payees only.
NIT (Número de Identificación Tributaria) - 9 digits with optional check digit
**Validation:**
* Between 9 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9]{9}(-[0-9])?$`
**Example:** `123456789 or 123456789-0`
#### Personal ID Type
**Conditional:** Required for Individual payees only.
**Value:** One of `NATIONAL_ID`, `FOREIGN_ID`, `INDIVIDUAL_TAX_ID`, `PASSPORT`
Select the ID type as registered with the bank account
#### Personal ID Number
**Conditional:** Required for Individual payees only.
Personal identification number (6-10 digits)
**Validation:**
* Between 6 and 10 characters (inclusive).
* Must match this regular expression: `^[0-9]{6,10}$`
**Example:** `1234567890`
### Notes
* The Colombian government sets a 0.40% tax (Gravamen a los Movimientos Financieros: Tax on Financial Operations) per transaction, which is collected automatically in addition to the payout transaction fee.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `COLOCOBM`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `12345678901`
### 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.
# Congo - Brazzaville
Source: https://docs.withacclaim.com/guides/disburse/countries/congo-brazzaville
Payout methods, timing, transaction limits, and required fields for payouts to Congo - Brazzaville.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| West Africa Local Transfer | XAF | 2-3 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.
## West Africa Local Transfer
West African local bank transfer
### Supported currencies
`XAF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 50,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `WestAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNCMX1`
#### Account Number
Account number (exactly 23 alphanumeric characters)
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[A-Za-z0-9]{23}$`
**Example:** `12345678901234567890123`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCBPCGCGXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[0-9A-Za-z]{23}$`
**Example:** `01234567890123456789012`
### 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.
# Cook Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/cook-islands
Payout methods, timing, transaction limits, and required fields for payouts to Cook Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCKICKCR`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `180098765432`
### 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.
# Costa Rica
Source: https://docs.withacclaim.com/guides/disburse/countries/costa-rica
Payout methods, timing, transaction limits, and required fields for payouts to Costa Rica.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CRC`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CRC`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCRICRSJ`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
#### Tax ID Type
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### Cédula Jurídica (business tax ID)
9–12 digit tax identification number (Cédula Jurídica), up to 15 digits
**Validation:**
* Between 9 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9]{9,15}$`
**Example:** `1234567890`
#### Tax ID Type
**Value:** `INDIVIDUAL_TAX_ID`
#### Tax identification number
9–12 digit personal tax ID (Cédula), up to 15 digits
**Validation:**
* Between 9 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9]{9,15}$`
**Example:** `123456789`
### Notes
* A beneficiary tax ID is only required when the payout currency is CRC (Costa Rican colón).
* 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.
# Côte d’Ivoire
Source: https://docs.withacclaim.com/guides/disburse/countries/cote-d-ivoire
Payout methods, timing, transaction limits, and required fields for payouts to Côte d’Ivoire.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| ----------------------------- | ---------- | ----------------- |
| Central Africa Local Transfer | XOF | 2-3 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.
## Central Africa Local Transfer
Central Africa local bank transfer
### Supported currencies
`XOF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `CentralAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNSNX1`
#### Account Number
Account number (exactly 24 alphanumeric characters)
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[A-Za-z0-9]{24}$`
**Example:** `123456789012345678901234`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `AFRICIABXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[0-9A-Za-z]{24}$`
**Example:** `012345678901234567890123`
### 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.
# Croatia
Source: https://docs.withacclaim.com/guides/disburse/countries/croatia
Payout methods, timing, transaction limits, and required fields for payouts to Croatia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 21 characters.
* IBAN format; must match: `^HR[0-9]{2}[a-zA-Z0-9]{17}$`
**Example:** `HR1210010051863000160`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 21 characters.
* IBAN format; must match: `^HR[0-9]{2}[a-zA-Z0-9]{17}$`
**Example:** `HR1210010051863000160`
### 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.
# Curaçao
Source: https://docs.withacclaim.com/guides/disburse/countries/curacao
Payout methods, timing, transaction limits, and required fields for payouts to Curaçao.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BDCCCWCUXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Cyprus
Source: https://docs.withacclaim.com/guides/disburse/countries/cyprus
Payout methods, timing, transaction limits, and required fields for payouts to Cyprus.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^CY[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `CY39002001360000001100746300`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^CY[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `CY39002001360000001100746300`
### 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.
# Czechia
Source: https://docs.withacclaim.com/guides/disburse/countries/czechia
Payout methods, timing, transaction limits, and required fields for payouts to Czechia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| CERTIS | CZK | 0-1 business days |
| SEPA | EUR | 0-2 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.
## CERTIS
Czech Republic CERTIS payment system
### Supported currencies
`CZK`
### 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 | 1,000,000 CZK |
### Fields
#### Payout Method Type
**Value:** `CzechRepublicCertis`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^CZ[0-9]{22}$`
**Example:** `CZ6508000000192000145399`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^CZ[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `CZ6508000000192000145399`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^CZ[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `CZ6508000000192000145399`
### 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.
# Denmark
Source: https://docs.withacclaim.com/guides/disburse/countries/denmark
Payout methods, timing, transaction limits, and required fields for payouts to Denmark.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Straksclearing | DKK | 0-1 business days |
| SEPA | EUR | 0-2 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.
## Straksclearing
Denmark Straksclearing Instant payment system
### Supported currencies
`DKK`
### 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 | 500,000 DKK |
### Fields
#### Payout Method Type
**Value:** `DenmarkStraksclearing`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
**Validation:**
* Exactly 4 characters.
* Must match this regular expression: `^[0-9]{4}$`
**Example:** `1234`
#### Account Number
**Validation:**
* Between 4 and 10 characters (inclusive).
* Must match this regular expression: `^[0-9]{4,10}$`
**Example:** `1234567890`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^DK[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `DK5000400440116243`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^DK[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `DK5000400440116243`
### 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.
# Djibouti
Source: https://docs.withacclaim.com/guides/disburse/countries/djibouti
Payout methods, timing, transaction limits, and required fields for payouts to Djibouti.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCDJDJJD`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012`
### 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.
# Dominica
Source: https://docs.withacclaim.com/guides/disburse/countries/dominica
Payout methods, timing, transaction limits, and required fields for payouts to Dominica.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NCDMDMDMXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Dominican Republic
Source: https://docs.withacclaim.com/guides/disburse/countries/dominican-republic
Payout methods, timing, transaction limits, and required fields for payouts to Dominican Republic.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `DOP`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `DOP`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^DO[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `DO28BAGR00000001212453611324`
#### Tax ID Type
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### Business tax ID or Registro Mercantil
Tax ID card (7+ digits) or Registro Mercantil from the Chamber of Commerce (9+ digits), up to 15 digits
**Validation:**
* Between 7 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9]{7,15}$`
**Example:** `12345678901`
#### ID type
**Conditional:** Required for Individual payees only.
**Value:** One of `NATIONAL_ID`, `PASSPORT`
Cédula is 11 digits; use passport for non-residents
#### ID number
11-digit cédula or passport number (up to 15 characters)
**Validation:**
* Between 4 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{4,15}$`
**Example:** `40212345678`
### Notes
* A beneficiary tax ID is only required when the payout currency is DOP (Dominican peso).
* 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.
# Ecuador
Source: https://docs.withacclaim.com/guides/disburse/countries/ecuador
Payout methods, timing, transaction limits, and required fields for payouts to Ecuador.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CODSECEQ001`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Egypt
Source: https://docs.withacclaim.com/guides/disburse/countries/egypt
Payout methods, timing, transaction limits, and required fields for payouts to Egypt.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Egypt ACH | EGP | 0-2 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.
## Egypt ACH
Egyptian ACH bank transfer
### Supported currencies
`EGP`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EgyptAch`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 29 characters.
* IBAN format; must match: `^EG[0-9]{2}[A-Z0-9]{4}[0-9]{4}[0-9]{17}$`
**Example:** `EG380019000500000000263180002`
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EGP`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EGP`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 29 characters.
* IBAN format; must match: `^EG[0-9]{2}[A-Z0-9]{4}[0-9]{4}[0-9]{17}$`
**Example:** `EG380019000500000000263180002`
#### Recipient Bank SWIFT/BIC Code
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:** `ABRKEGCA`
### 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.
# El Salvador
Source: https://docs.withacclaim.com/guides/disburse/countries/el-salvador
Payout methods, timing, transaction limits, and required fields for payouts to El Salvador.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CENRSVSS`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Equatorial Guinea
Source: https://docs.withacclaim.com/guides/disburse/countries/equatorial-guinea
Payout methods, timing, transaction limits, and required fields for payouts to Equatorial Guinea.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| West Africa Local Transfer | XAF | 2-3 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.
## West Africa Local Transfer
West African local bank transfer
### Supported currencies
`XAF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 50,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `WestAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNCMX1`
#### Account Number
Account number (exactly 23 alphanumeric characters)
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[A-Za-z0-9]{23}$`
**Example:** `12345678901234567890123`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NAGCGQGQXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Estonia
Source: https://docs.withacclaim.com/guides/disburse/countries/estonia
Payout methods, timing, transaction limits, and required fields for payouts to Estonia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^EE[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `EE792200221006107980`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^EE[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `EE792200221006107980`
### 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.
# Eswatini
Source: https://docs.withacclaim.com/guides/disburse/countries/eswatini
Payout methods, timing, transaction limits, and required fields for payouts to Eswatini.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NESWSZMX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890123`
### 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.
# Ethiopia
Source: https://docs.withacclaim.com/guides/disburse/countries/ethiopia
Payout methods, timing, transaction limits, and required fields for payouts to Ethiopia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CBETETAAXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Falkland Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/falkland-islands
Payout methods, timing, transaction limits, and required fields for payouts to Falkland Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `SCBLFKFK`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `210078901234`
### 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.
# Faroe Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/faroe-islands
Payout methods, timing, transaction limits, and required fields for payouts to Faroe Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^FO[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `FO6264600001631634`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^FO[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `FO6264600001631634`
### 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.
# Fiji
Source: https://docs.withacclaim.com/guides/disburse/countries/fiji
Payout methods, timing, transaction limits, and required fields for payouts to Fiji.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `FJD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `FJD`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `FDEVFJF1XXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Finland
Source: https://docs.withacclaim.com/guides/disburse/countries/finland
Payout methods, timing, transaction limits, and required fields for payouts to Finland.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^FI[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `FI8789199710001136`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^FI[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `FI8789199710001136`
### 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.
# France
Source: https://docs.withacclaim.com/guides/disburse/countries/france
Payout methods, timing, transaction limits, and required fields for payouts to France.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7610278060390002168100137`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7610278060390002168100137`
### 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.
# French Guiana
Source: https://docs.withacclaim.com/guides/disburse/countries/french-guiana
Payout methods, timing, transaction limits, and required fields for payouts to French Guiana.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7630001007941234567890185`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7630006000011234567890189`
### 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.
# French Polynesia
Source: https://docs.withacclaim.com/guides/disburse/countries/french-polynesia
Payout methods, timing, transaction limits, and required fields for payouts to French Polynesia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CEPAPFTP`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# French Southern Territories
Source: https://docs.withacclaim.com/guides/disburse/countries/french-southern-territories
Payout methods, timing, transaction limits, and required fields for payouts to French Southern Territories.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
### 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.
# Gabon
Source: https://docs.withacclaim.com/guides/disburse/countries/gabon
Payout methods, timing, transaction limits, and required fields for payouts to Gabon.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| West Africa Local Transfer | XAF | 2-3 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.
## West Africa Local Transfer
West African local bank transfer
### Supported currencies
`XAF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 50,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `WestAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNCMX1`
#### Account Number
Account number (exactly 23 alphanumeric characters)
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[A-Za-z0-9]{23}$`
**Example:** `12345678901234567890123`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BGFIGALIXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 23 characters.
* Must match this regular expression: `^[0-9A-Za-z]{23}$`
**Example:** `01234567890123456789012`
### 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.
# Gambia
Source: https://docs.withacclaim.com/guides/disburse/countries/gambia
Payout methods, timing, transaction limits, and required fields for payouts to Gambia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Gambia Local Transfer | GMD | 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.
## Gambia Local Transfer
Gambian local bank transfer
### Supported currencies
`GMD`
### 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 | 15 USD |
| Maximum | 100,000 USD |
### Fields
#### Payout Method Type
**Value:** `GambiaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNGMGX`
#### Account Number
Account number (up to 35 alphanumeric characters)
**Validation:**
* Between 1 and 35 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{1,35}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `TBLTGMGM`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `230012345678`
### 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.
# Georgia
Source: https://docs.withacclaim.com/guides/disburse/countries/georgia
Payout methods, timing, transaction limits, and required fields for payouts to Georgia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `GEL`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `GEL`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^GE[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `GE29NB0000000101904917`
### 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.
# Germany
Source: https://docs.withacclaim.com/guides/disburse/countries/germany
Payout methods, timing, transaction limits, and required fields for payouts to Germany.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^DE[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `DE04370502990081288281`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^DE[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `DE04370502990081288281`
### 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.
# Ghana
Source: https://docs.withacclaim.com/guides/disburse/countries/ghana
Payout methods, timing, transaction limits, and required fields for payouts to Ghana.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `GHS`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `GHS`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BAGHGHA2`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `0012345678901`
### 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.
# Gibraltar
Source: https://docs.withacclaim.com/guides/disburse/countries/gibraltar
Payout methods, timing, transaction limits, and required fields for payouts to Gibraltar.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 23 characters.
* IBAN format; must match: `^GI[0-9]{2}[a-zA-Z0-9]{19}$`
**Example:** `GI75NWBK000000007099453`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 23 characters.
* IBAN format; must match: `^GI[0-9]{2}[a-zA-Z0-9]{19}$`
**Example:** `GI75NWBK000000007099453`
### 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.
# Greece
Source: https://docs.withacclaim.com/guides/disburse/countries/greece
Payout methods, timing, transaction limits, and required fields for payouts to Greece.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^GR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `GR8201727940005794064619041`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^GR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `GR8201727940005794064619041`
### 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.
# Greenland
Source: https://docs.withacclaim.com/guides/disburse/countries/greenland
Payout methods, timing, transaction limits, and required fields for payouts to Greenland.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^GL[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `GL8964710123456789`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^GL[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `GL8964710123456789`
### 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.
# Grenada
Source: https://docs.withacclaim.com/guides/disburse/countries/grenada
Payout methods, timing, transaction limits, and required fields for payouts to Grenada.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NCBGGDGD`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Guadeloupe
Source: https://docs.withacclaim.com/guides/disburse/countries/guadeloupe
Payout methods, timing, transaction limits, and required fields for payouts to Guadeloupe.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| ------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 business days |
Please refer to the sections below for the key required fields and other considerations for each supported method.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7610278060390002168100137`
# Guatemala
Source: https://docs.withacclaim.com/guides/disburse/countries/guatemala
Payout methods, timing, transaction limits, and required fields for payouts to Guatemala.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `GTQ`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `GTQ`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^GT[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `GT82TRAJ01020000001210029690`
### 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.
# Guernsey
Source: https://docs.withacclaim.com/guides/disburse/countries/guernsey
Payout methods, timing, transaction limits, and required fields for payouts to Guernsey.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^GG[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `GG30BARC20201530093065`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^GB[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `GB08NWBK60092074079875`
### 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.
# Guinea
Source: https://docs.withacclaim.com/guides/disburse/countries/guinea
Payout methods, timing, transaction limits, and required fields for payouts to Guinea.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BGFIGNCONAK`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `001234567890`
### 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.
# Guinea-Bissau
Source: https://docs.withacclaim.com/guides/disburse/countries/guinea-bissau
Payout methods, timing, transaction limits, and required fields for payouts to Guinea-Bissau.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| ----------------------------- | ---------- | ----------------- |
| Central Africa Local Transfer | XOF | 2-3 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.
## Central Africa Local Transfer
Central Africa local bank transfer
### Supported currencies
`XOF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `CentralAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNSNX1`
#### Account Number
Account number (exactly 24 alphanumeric characters)
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[A-Za-z0-9]{24}$`
**Example:** `123456789012345678901234`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCAOGWG1`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[0-9A-Za-z]{24}$`
**Example:** `012345678901234567890123`
### 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.
# Guyana
Source: https://docs.withacclaim.com/guides/disburse/countries/guyana
Payout methods, timing, transaction limits, and required fields for payouts to Guyana.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `GYD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `GYD`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `DMBKGYGT`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Honduras
Source: https://docs.withacclaim.com/guides/disburse/countries/honduras
Payout methods, timing, transaction limits, and required fields for payouts to Honduras.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HNL`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HNL`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `FCOHHNTEXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
#### Tax ID Type
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### RTN (Registro Tributario Nacional)
13- or 14-digit business tax ID (RTN)
**Validation:**
* Between 13 and 14 characters (inclusive).
* Must match this regular expression: `^[0-9]{13,14}$`
**Example:** `1234567890123`
#### Tax ID Type
**Value:** `NATIONAL_ID`
#### Tarjeta de Identidad (ID number)
13-digit national ID (Tarjeta de Identidad)
**Validation:**
* Exactly 13 characters.
* Must match this regular expression: `^[0-9]{13}$`
**Example:** `1234567890123`
### Notes
* A beneficiary tax ID is only required when the payout currency is HNL (Honduran lempira).
* 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.
# Hong Kong SAR China
Source: https://docs.withacclaim.com/guides/disburse/countries/hong-kong-sar-china
Payout methods, timing, transaction limits, and required fields for payouts to Hong Kong SAR China.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------------- | ------------- | ----------------- |
| Faster Payment System | CNY, HKD | 0-1 business days |
| Real-Time Gross Settlement (RTGS) | CNY, HKD, USD | 0-1 business days |
| ACH | CNY, HKD | 1-2 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.
## Faster Payment System
Hong Kong Faster Payment System (FPS)
### Supported currencies
`CNY`, `HKD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 HKD |
### Fields
#### Payout Method Type
**Value:** `HongKongFps`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Transfer Method
**Value:** One of `bank_code`, `phone_number`, `email_address`, `fps_identifier`, `personal_id_number`
#### Transfer Method Value
Bank code (3 digits), phone (+852-12345678), email, FPS ID (7-9 digits), or HKID (Xnnnnnn(A))
**Example:** `Enter value based on selected method`
#### Account Number
Account number (8-17 digits). Required when using bank code. The first 3 digits are usually a valid branch code from the bank selected
**Validation:**
* Between 8 and 17 characters (inclusive).
* Must match this regular expression: `^[0-9]{8,17}$`
**Example:** `12345678901234567`
#### Currency
**Value:** One of `HKD`, `CNY`
## Real-Time Gross Settlement (RTGS)
Hong Kong Real-Time Gross Settlement (RTGS)
### Supported currencies
`CNY`, `HKD`, `USD`
### 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
**Value:** `HongKongRtgs`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT / BIC Code
8 or 11 character SWIFT code of recipient bank. Should be a valid and supported BIC-8 or BIC-11 code
**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:** `HSBCHKHH`
#### Account Number
Account number (8-17 digits). The first 3 digits are usually a valid branch code from the bank selected
**Validation:**
* Between 8 and 17 characters (inclusive).
* Must match this regular expression: `^[0-9]{8,17}$`
**Example:** `12345678901234567`
#### Currency
**Value:** One of `HKD`, `CNY`, `USD`
## ACH
Hong Kong ACH payment system
### Supported currencies
`CNY`, `HKD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 1-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `HongKongAch`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
3-digit number to identify a bank in Hong Kong
**Validation:**
* Exactly 3 characters.
* Must match this regular expression: `^[0-9]{3}$`
**Example:** `004`
#### Account Number
Account number (8-17 digits). The first 3 digits are usually a valid branch code from the bank selected
**Validation:**
* Between 8 and 17 characters (inclusive).
* Must match this regular expression: `^[0-9]{8,17}$`
**Example:** `12345678901234567`
#### Currency
**Value:** One of `HKD`, `CNY`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `HASEHKHH`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 8 and 17 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{8,17}$`
**Example:** `786005728434`
### 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.
# Hungary
Source: https://docs.withacclaim.com/guides/disburse/countries/hungary
Payout methods, timing, transaction limits, and required fields for payouts to Hungary.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Giro Zrt | HUF | 0-1 business days |
| SEPA | EUR | 0-2 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.
## Giro Zrt
Hungary Giro Zrt payment system
### Supported currencies
`HUF`
### 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 | 10,000,000 HUF |
### Fields
#### Payout Method Type
**Value:** `HungaryGiro`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^HU[0-9]{26}$`
**Example:** `HU42117730161111101800000000`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^HU[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `HU42117730161111101800000000`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^HU[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `HU42117730161111101800000000`
### 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.
# Iceland
Source: https://docs.withacclaim.com/guides/disburse/countries/iceland
Payout methods, timing, transaction limits, and required fields for payouts to Iceland.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 26 characters.
* IBAN format; must match: `^IS[0-9]{2}[a-zA-Z0-9]{22}$`
**Example:** `IS140159260076545510730339`
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `ISK`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `ISK`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 26 characters.
* IBAN format; must match: `^IS[0-9]{2}[a-zA-Z0-9]{22}$`
**Example:** `IS140159260076545510730339`
### 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.
# Supported Payout Countries
Source: https://docs.withacclaim.com/guides/disburse/countries/index
Country-by-country payout capabilities, including methods, timing, transaction limits, and required fields.
## Africa
| Country | Local Payouts | SWIFT Payouts | Instant Payouts |
| ------------------------------------------------------------------------------- | ------------- | ------------- | --------------- |
| [Algeria](/guides/disburse/countries/algeria) | — | Yes | — |
| [Angola](/guides/disburse/countries/angola) | — | Yes | — |
| [Benin](/guides/disburse/countries/benin) | Yes | Yes | — |
| [Botswana](/guides/disburse/countries/botswana) | Yes | Yes | — |
| [Burkina Faso](/guides/disburse/countries/burkina-faso) | Yes | Yes | — |
| [Cameroon](/guides/disburse/countries/cameroon) | Yes | Yes | — |
| [Cape Verde](/guides/disburse/countries/cape-verde) | — | Yes | — |
| [Central African Republic](/guides/disburse/countries/central-african-republic) | Yes | Yes | — |
| [Chad](/guides/disburse/countries/chad) | Yes | Yes | — |
| [Congo - Brazzaville](/guides/disburse/countries/congo-brazzaville) | Yes | Yes | — |
| [Côte d’Ivoire](/guides/disburse/countries/cote-d-ivoire) | Yes | Yes | — |
| [Djibouti](/guides/disburse/countries/djibouti) | — | Yes | — |
| [Egypt](/guides/disburse/countries/egypt) | Yes | Yes | — |
| [Equatorial Guinea](/guides/disburse/countries/equatorial-guinea) | Yes | Yes | — |
| [Eswatini](/guides/disburse/countries/eswatini) | — | Yes | — |
| [Ethiopia](/guides/disburse/countries/ethiopia) | — | Yes | — |
| [Gabon](/guides/disburse/countries/gabon) | Yes | Yes | — |
| [Gambia](/guides/disburse/countries/gambia) | Yes | Yes | — |
| [Ghana](/guides/disburse/countries/ghana) | — | Yes | — |
| [Guinea](/guides/disburse/countries/guinea) | — | Yes | — |
| [Guinea-Bissau](/guides/disburse/countries/guinea-bissau) | Yes | Yes | — |
| [Kenya](/guides/disburse/countries/kenya) | Yes | Yes | — |
| [Lesotho](/guides/disburse/countries/lesotho) | Yes | Yes | — |
| [Liberia](/guides/disburse/countries/liberia) | — | Yes | — |
| [Madagascar](/guides/disburse/countries/madagascar) | Yes | Yes | — |
| [Malawi](/guides/disburse/countries/malawi) | Yes | Yes | — |
| [Mauritania](/guides/disburse/countries/mauritania) | — | Yes | — |
| [Mauritius](/guides/disburse/countries/mauritius) | — | Yes | — |
| [Mayotte](/guides/disburse/countries/mayotte) | Yes | Yes | Yes |
| [Morocco](/guides/disburse/countries/morocco) | Yes | Yes | — |
| [Namibia](/guides/disburse/countries/namibia) | Yes | Yes | — |
| [Niger](/guides/disburse/countries/niger) | Yes | Yes | — |
| [Nigeria](/guides/disburse/countries/nigeria) | Yes | Yes | — |
| [Réunion](/guides/disburse/countries/reunion) | Yes | Yes | Yes |
| [Rwanda](/guides/disburse/countries/rwanda) | Yes | Yes | — |
| [São Tomé & Príncipe](/guides/disburse/countries/sao-tome-principe) | — | Yes | — |
| [Senegal](/guides/disburse/countries/senegal) | Yes | Yes | — |
| [Seychelles](/guides/disburse/countries/seychelles) | — | Yes | — |
| [Sierra Leone](/guides/disburse/countries/sierra-leone) | — | Yes | — |
| [South Africa](/guides/disburse/countries/south-africa) | Yes | Yes | — |
| [St. Helena](/guides/disburse/countries/st-helena) | — | Yes | — |
| [Tanzania](/guides/disburse/countries/tanzania) | — | Yes | — |
| [Togo](/guides/disburse/countries/togo) | Yes | Yes | — |
| [Tunisia](/guides/disburse/countries/tunisia) | — | Yes | — |
| [Uganda](/guides/disburse/countries/uganda) | — | Yes | — |
| [Zambia](/guides/disburse/countries/zambia) | Yes | Yes | — |
| [Zimbabwe](/guides/disburse/countries/zimbabwe) | — | Yes | — |
## APAC
| Country | Local Payouts | SWIFT Payouts | Instant Payouts |
| ------------------------------------------------------------------------------------- | ------------- | ------------- | --------------- |
| [American Samoa](/guides/disburse/countries/american-samoa) | — | Yes | — |
| [Australia](/guides/disburse/countries/australia) | Yes | Yes | Yes |
| [Bangladesh](/guides/disburse/countries/bangladesh) | Yes | Yes | — |
| [Bhutan](/guides/disburse/countries/bhutan) | — | Yes | — |
| [Brunei](/guides/disburse/countries/brunei) | — | Yes | — |
| [Cambodia](/guides/disburse/countries/cambodia) | — | Yes | — |
| [China](/guides/disburse/countries/china) | Yes | Yes | Yes |
| [Cook Islands](/guides/disburse/countries/cook-islands) | — | Yes | — |
| [Fiji](/guides/disburse/countries/fiji) | — | Yes | — |
| [French Polynesia](/guides/disburse/countries/french-polynesia) | — | Yes | — |
| [French Southern Territories](/guides/disburse/countries/french-southern-territories) | — | Yes | — |
| [Hong Kong SAR China](/guides/disburse/countries/hong-kong-sar-china) | Yes | Yes | Yes |
| [India](/guides/disburse/countries/india) | Yes | Yes | Yes |
| [Indonesia](/guides/disburse/countries/indonesia) | Yes | Yes | Yes |
| [Japan](/guides/disburse/countries/japan) | Yes | Yes | Yes |
| [Kazakhstan](/guides/disburse/countries/kazakhstan) | — | Yes | — |
| [Kiribati](/guides/disburse/countries/kiribati) | — | Yes | — |
| [Kyrgyzstan](/guides/disburse/countries/kyrgyzstan) | — | Yes | — |
| [Laos](/guides/disburse/countries/laos) | — | Yes | — |
| [Macao SAR China](/guides/disburse/countries/macao-sar-china) | — | Yes | — |
| [Malaysia](/guides/disburse/countries/malaysia) | Yes | Yes | Yes |
| [Maldives](/guides/disburse/countries/maldives) | — | Yes | — |
| [Marshall Islands](/guides/disburse/countries/marshall-islands) | — | Yes | — |
| [Micronesia](/guides/disburse/countries/micronesia) | — | Yes | — |
| [Mongolia](/guides/disburse/countries/mongolia) | — | Yes | — |
| [Nepal](/guides/disburse/countries/nepal) | Yes | Yes | — |
| [New Caledonia](/guides/disburse/countries/new-caledonia) | — | Yes | — |
| [New Zealand](/guides/disburse/countries/new-zealand) | Yes | Yes | — |
| [Northern Mariana Islands](/guides/disburse/countries/northern-mariana-islands) | — | Yes | — |
| [Pakistan](/guides/disburse/countries/pakistan) | Yes | Yes | — |
| [Palau](/guides/disburse/countries/palau) | — | Yes | — |
| [Papua New Guinea](/guides/disburse/countries/papua-new-guinea) | — | Yes | — |
| [Philippines](/guides/disburse/countries/philippines) | Yes | Yes | Yes |
| [Samoa](/guides/disburse/countries/samoa) | — | Yes | — |
| [Singapore](/guides/disburse/countries/singapore) | Yes | Yes | Yes |
| [Solomon Islands](/guides/disburse/countries/solomon-islands) | — | Yes | — |
| [South Korea](/guides/disburse/countries/south-korea) | Yes | Yes | Yes |
| [Sri Lanka](/guides/disburse/countries/sri-lanka) | Yes | Yes | — |
| [Taiwan](/guides/disburse/countries/taiwan) | — | Yes | — |
| [Tajikistan](/guides/disburse/countries/tajikistan) | — | Yes | — |
| [Thailand](/guides/disburse/countries/thailand) | — | Yes | — |
| [Timor-Leste](/guides/disburse/countries/timor-leste) | — | Yes | — |
| [Tonga](/guides/disburse/countries/tonga) | — | Yes | — |
| [Türkiye](/guides/disburse/countries/turkiye) | Yes | Yes | — |
| [Tuvalu](/guides/disburse/countries/tuvalu) | — | Yes | — |
| [Uzbekistan](/guides/disburse/countries/uzbekistan) | — | Yes | — |
| [Vanuatu](/guides/disburse/countries/vanuatu) | — | Yes | — |
| [Vietnam](/guides/disburse/countries/vietnam) | Yes | Yes | — |
| [Wallis & Futuna](/guides/disburse/countries/wallis-futuna) | — | Yes | — |
## Europe
| Country | Local Payouts | SWIFT Payouts | Instant Payouts |
| --------------------------------------------------------------------- | ------------- | ------------- | --------------- |
| [Albania](/guides/disburse/countries/albania) | — | Yes | — |
| [Andorra](/guides/disburse/countries/andorra) | — | Yes | — |
| [Armenia](/guides/disburse/countries/armenia) | — | Yes | — |
| [Austria](/guides/disburse/countries/austria) | Yes | Yes | Yes |
| [Belarus](/guides/disburse/countries/belarus) | — | Yes | — |
| [Belgium](/guides/disburse/countries/belgium) | Yes | Yes | Yes |
| [Bosnia & Herzegovina](/guides/disburse/countries/bosnia-herzegovina) | — | Yes | — |
| [Bulgaria](/guides/disburse/countries/bulgaria) | Yes | Yes | Yes |
| [Canary Islands](/guides/disburse/countries/canary-islands) | — | Yes | — |
| [Croatia](/guides/disburse/countries/croatia) | Yes | Yes | Yes |
| [Cyprus](/guides/disburse/countries/cyprus) | Yes | Yes | Yes |
| [Czechia](/guides/disburse/countries/czechia) | Yes | Yes | Yes |
| [Denmark](/guides/disburse/countries/denmark) | Yes | Yes | Yes |
| [Estonia](/guides/disburse/countries/estonia) | Yes | Yes | Yes |
| [Faroe Islands](/guides/disburse/countries/faroe-islands) | Yes | Yes | Yes |
| [Finland](/guides/disburse/countries/finland) | Yes | Yes | Yes |
| [France](/guides/disburse/countries/france) | Yes | Yes | Yes |
| [Georgia](/guides/disburse/countries/georgia) | — | Yes | — |
| [Germany](/guides/disburse/countries/germany) | Yes | Yes | Yes |
| [Gibraltar](/guides/disburse/countries/gibraltar) | Yes | Yes | Yes |
| [Greece](/guides/disburse/countries/greece) | Yes | Yes | Yes |
| [Guernsey](/guides/disburse/countries/guernsey) | Yes | Yes | Yes |
| [Hungary](/guides/disburse/countries/hungary) | Yes | Yes | Yes |
| [Iceland](/guides/disburse/countries/iceland) | Yes | Yes | Yes |
| [Ireland](/guides/disburse/countries/ireland) | Yes | Yes | Yes |
| [Isle of Man](/guides/disburse/countries/isle-of-man) | Yes | Yes | Yes |
| [Italy](/guides/disburse/countries/italy) | Yes | Yes | Yes |
| [Jersey](/guides/disburse/countries/jersey) | Yes | Yes | Yes |
| [Kosovo](/guides/disburse/countries/kosovo) | — | Yes | — |
| [Latvia](/guides/disburse/countries/latvia) | Yes | Yes | Yes |
| [Liechtenstein](/guides/disburse/countries/liechtenstein) | Yes | Yes | Yes |
| [Lithuania](/guides/disburse/countries/lithuania) | Yes | Yes | Yes |
| [Luxembourg](/guides/disburse/countries/luxembourg) | Yes | Yes | Yes |
| [Malta](/guides/disburse/countries/malta) | Yes | Yes | Yes |
| [Moldova](/guides/disburse/countries/moldova) | — | Yes | — |
| [Monaco](/guides/disburse/countries/monaco) | Yes | Yes | Yes |
| [Montenegro](/guides/disburse/countries/montenegro) | — | Yes | — |
| [Netherlands](/guides/disburse/countries/netherlands) | Yes | Yes | Yes |
| [North Macedonia](/guides/disburse/countries/north-macedonia) | — | Yes | — |
| [Norway](/guides/disburse/countries/norway) | Yes | Yes | Yes |
| [Poland](/guides/disburse/countries/poland) | Yes | Yes | Yes |
| [Portugal](/guides/disburse/countries/portugal) | Yes | Yes | Yes |
| [Romania](/guides/disburse/countries/romania) | Yes | Yes | Yes |
| [San Marino](/guides/disburse/countries/san-marino) | Yes | Yes | Yes |
| [Serbia](/guides/disburse/countries/serbia) | — | Yes | — |
| [Slovakia](/guides/disburse/countries/slovakia) | Yes | Yes | Yes |
| [Slovenia](/guides/disburse/countries/slovenia) | Yes | Yes | Yes |
| [Spain](/guides/disburse/countries/spain) | Yes | Yes | Yes |
| [Sweden](/guides/disburse/countries/sweden) | Yes | Yes | Yes |
| [Switzerland](/guides/disburse/countries/switzerland) | Yes | Yes | Yes |
| [Ukraine](/guides/disburse/countries/ukraine) | — | Yes | — |
| [United Kingdom](/guides/disburse/countries/united-kingdom) | Yes | Yes | Yes |
| [Vatican City](/guides/disburse/countries/vatican-city) | Yes | Yes | Yes |
## Middle East
| Country | Local Payouts | SWIFT Payouts | Instant Payouts |
| ----------------------------------------------------------------------------- | ------------- | ------------- | --------------- |
| [Azerbaijan](/guides/disburse/countries/azerbaijan) | — | Yes | — |
| [Bahrain](/guides/disburse/countries/bahrain) | Yes | Yes | — |
| [Israel](/guides/disburse/countries/israel) | Yes | Yes | — |
| [Jordan](/guides/disburse/countries/jordan) | — | Yes | — |
| [Kuwait](/guides/disburse/countries/kuwait) | — | Yes | — |
| [Lebanon](/guides/disburse/countries/lebanon) | — | Yes | — |
| [Oman](/guides/disburse/countries/oman) | — | Yes | — |
| [Palestinian Territories](/guides/disburse/countries/palestinian-territories) | — | Yes | — |
| [Qatar](/guides/disburse/countries/qatar) | — | Yes | — |
| [Saudi Arabia](/guides/disburse/countries/saudi-arabia) | — | Yes | — |
| [United Arab Emirates](/guides/disburse/countries/united-arab-emirates) | Yes | Yes | — |
## North America
| Country | Local Payouts | SWIFT Payouts | Instant Payouts |
| ---------------------------------------------------------------------------- | ------------- | ------------- | --------------- |
| [Anguilla](/guides/disburse/countries/anguilla) | — | Yes | — |
| [Antigua & Barbuda](/guides/disburse/countries/antigua-barbuda) | — | Yes | — |
| [Aruba](/guides/disburse/countries/aruba) | — | Yes | — |
| [Bahamas](/guides/disburse/countries/bahamas) | — | Yes | — |
| [Barbados](/guides/disburse/countries/barbados) | — | Yes | — |
| [Belize](/guides/disburse/countries/belize) | — | Yes | — |
| [Bermuda](/guides/disburse/countries/bermuda) | — | Yes | — |
| [British Virgin Islands](/guides/disburse/countries/british-virgin-islands) | — | Yes | — |
| [Canada](/guides/disburse/countries/canada) | Yes | Yes | Yes |
| [Cayman Islands](/guides/disburse/countries/cayman-islands) | — | Yes | — |
| [Costa Rica](/guides/disburse/countries/costa-rica) | — | Yes | — |
| [Curaçao](/guides/disburse/countries/curacao) | — | Yes | — |
| [Dominica](/guides/disburse/countries/dominica) | — | Yes | — |
| [Dominican Republic](/guides/disburse/countries/dominican-republic) | — | Yes | — |
| [El Salvador](/guides/disburse/countries/el-salvador) | — | Yes | — |
| [Greenland](/guides/disburse/countries/greenland) | Yes | Yes | Yes |
| [Grenada](/guides/disburse/countries/grenada) | — | Yes | — |
| [Guadeloupe](/guides/disburse/countries/guadeloupe) | Yes | — | Yes |
| [Guatemala](/guides/disburse/countries/guatemala) | — | Yes | — |
| [Honduras](/guides/disburse/countries/honduras) | — | Yes | — |
| [Jamaica](/guides/disburse/countries/jamaica) | — | Yes | — |
| [Martinique](/guides/disburse/countries/martinique) | Yes | Yes | Yes |
| [Mexico](/guides/disburse/countries/mexico) | Yes | Yes | Yes |
| [Montserrat](/guides/disburse/countries/montserrat) | — | Yes | — |
| [Nicaragua](/guides/disburse/countries/nicaragua) | — | Yes | — |
| [Panama](/guides/disburse/countries/panama) | — | Yes | — |
| [Puerto Rico](/guides/disburse/countries/puerto-rico) | — | Yes | — |
| [St. Barthélemy](/guides/disburse/countries/st-barthelemy) | Yes | Yes | Yes |
| [St. Kitts & Nevis](/guides/disburse/countries/st-kitts-nevis) | — | Yes | — |
| [St. Lucia](/guides/disburse/countries/st-lucia) | — | Yes | — |
| [St. Martin](/guides/disburse/countries/st-martin) | Yes | Yes | Yes |
| [St. Pierre & Miquelon](/guides/disburse/countries/st-pierre-miquelon) | Yes | Yes | Yes |
| [St. Vincent & Grenadines](/guides/disburse/countries/st-vincent-grenadines) | — | Yes | — |
| [Trinidad & Tobago](/guides/disburse/countries/trinidad-tobago) | — | Yes | — |
| [Turks & Caicos Islands](/guides/disburse/countries/turks-caicos-islands) | — | Yes | — |
| [United States](/guides/disburse/countries/united-states) | Yes | Yes | Yes |
## South America
| Country | Local Payouts | SWIFT Payouts | Instant Payouts |
| --------------------------------------------------------------- | ------------- | ------------- | --------------- |
| [Argentina](/guides/disburse/countries/argentina) | Yes | Yes | — |
| [Bolivia](/guides/disburse/countries/bolivia) | Yes | Yes | — |
| [Brazil](/guides/disburse/countries/brazil) | Yes | Yes | Yes |
| [Chile](/guides/disburse/countries/chile) | Yes | Yes | — |
| [Colombia](/guides/disburse/countries/colombia) | Yes | Yes | — |
| [Ecuador](/guides/disburse/countries/ecuador) | — | Yes | — |
| [Falkland Islands](/guides/disburse/countries/falkland-islands) | — | Yes | — |
| [French Guiana](/guides/disburse/countries/french-guiana) | Yes | Yes | Yes |
| [Guyana](/guides/disburse/countries/guyana) | — | Yes | — |
| [Paraguay](/guides/disburse/countries/paraguay) | Yes | Yes | — |
| [Peru](/guides/disburse/countries/peru) | Yes | Yes | — |
| [Suriname](/guides/disburse/countries/suriname) | — | Yes | — |
| [Uruguay](/guides/disburse/countries/uruguay) | Yes | Yes | — |
## Notes
* **Local Payouts** is Yes when the country lists at least one currency in `supported_local_payout_currencies` in the source data.
* **SWIFT Payouts** is Yes when a `SwiftInternational` payout method is available for that country.
* **Instant Payouts** is Yes when at least one payout method has `timing.instant: true`.
* Timing can vary by payout method, bank, currency, corridor, and cut-off times.
* Required fields can differ between individual and business payees.
* Transaction limits and compliance review may vary by payout method.
# India
Source: https://docs.withacclaim.com/guides/disburse/countries/india
Payout methods, timing, transaction limits, and required fields for payouts to India.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| iACH | INR | 0-2 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.
## iACH
India iACH payment system
### Supported currencies
`INR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `IndiaIach`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### IFSC Code
Indian Financial System Code (IFSC): 11-character alphanumeric code to identify an Indian bank branch
**Validation:**
* Exactly 11 characters.
* Must match this regular expression: `^[A-Z]{4}0[A-Z0-9]{6}$`
**Example:** `SBIN0001234`
#### Account Number
Account number (9-18 digits)
**Validation:**
* Between 9 and 18 characters (inclusive).
* Must match this regular expression: `^[0-9]{9,18}$`
**Example:** `123456789012345678`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `ICICINBB`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 9 and 29 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{9,29}$`
**Example:** `127508528`
### 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.
# Indonesia
Source: https://docs.withacclaim.com/guides/disburse/countries/indonesia
Payout methods, timing, transaction limits, and required fields for payouts to Indonesia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SKN / BI-FAST / iACH | IDR | 0-2 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.
## SKN / BI-FAST / iACH
Indonesia SKN / BI-FAST / iACH local IDR payment system
### Supported currencies
`IDR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | --------------- |
| Minimum | None |
| Maximum | 300,000,000 IDR |
### Fields
#### Payout Method Type
**Value:** `IndonesiaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `CENAIDJA`
#### Account Number
Account number (up to 22 digits)
**Validation:**
* Between 1 and 22 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,22}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CENAIDJA`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 22 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,22}$`
**Example:** `12750852`
### 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.
# Ireland
Source: https://docs.withacclaim.com/guides/disburse/countries/ireland
Payout methods, timing, transaction limits, and required fields for payouts to Ireland.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^IE[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `IE82BOFI90001720611511`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^IE[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `IE82BOFI90001720611511`
### 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.
# Isle of Man
Source: https://docs.withacclaim.com/guides/disburse/countries/isle-of-man
Payout methods, timing, transaction limits, and required fields for payouts to Isle of Man.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^IM[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `IM20HBUK40127612345678`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^GB[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `GB61MIDL40193812795388`
### 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.
# Israel
Source: https://docs.withacclaim.com/guides/disburse/countries/israel
Payout methods, timing, transaction limits, and required fields for payouts to Israel.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Masav | ILS | 1-2 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.
## Masav
Israel Masav payment system
### Supported currencies
`ILS`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 1-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 999,999.99 ILS |
### Fields
#### Payout Method Type
**Value:** `IsraelMasav`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 23 characters.
* IBAN format; must match: `^IL[0-9]{2}[0-9]{3}[0-9]{3}[0-9]{13}$`
**Example:** `IL620108000000099999999`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 23 characters.
* IBAN format; must match: `^IL[0-9]{2}[a-zA-Z0-9]{19}$`
**Example:** `IL620108000000099999999`
### 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.
# Italy
Source: https://docs.withacclaim.com/guides/disburse/countries/italy
Payout methods, timing, transaction limits, and required fields for payouts to Italy.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^IT[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `IT67V0306977031100000001893`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^IT[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `IT67V0306977031100000001893`
### 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.
# Jamaica
Source: https://docs.withacclaim.com/guides/disburse/countries/jamaica
Payout methods, timing, transaction limits, and required fields for payouts to Jamaica.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JMD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JMD`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `JNBSJMKNXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Japan
Source: https://docs.withacclaim.com/guides/disburse/countries/japan
Payout methods, timing, transaction limits, and required fields for payouts to Japan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Zengin Transfer | JPY | 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.
## Zengin Transfer
Japanese Zengin domestic bank transfer system
### Supported currencies
`JPY`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ------------- |
| Minimum | None |
| Maximum | 1,000,000 JPY |
### Fields
#### Payout Method Type
**Value:** `JapanZengin`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
4-digit number to identify a Japanese bank
**Validation:**
* Exactly 4 characters.
* Must match this regular expression: `^[0-9]{4}$`
**Example:** `0001`
#### Routing Type 2
**Value:** `branch_code`
#### Branch Code
3-digit number to identify a Japanese bank branch
**Validation:**
* Exactly 3 characters.
* Must match this regular expression: `^[0-9]{3}$`
**Example:** `001`
#### Account Number
Account number (7 digits)
**Validation:**
* Exactly 7 characters.
* Must match this regular expression: `^[0-9]{7}$`
**Example:** `1234567`
#### Account Type
**Value:** One of `checking`, `savings`
Checking: Current (当座) or Savings: Ordinary (普通) account type
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BOTKJPJT`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 5 and 19 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{5,19}$`
**Example:** `5094034`
### 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.
# Jersey
Source: https://docs.withacclaim.com/guides/disburse/countries/jersey
Payout methods, timing, transaction limits, and required fields for payouts to Jersey.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^JE[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `JE80BARC10101000129397`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^GB[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `GB33BUKB20201555555555`
### 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.
# Jordan
Source: https://docs.withacclaim.com/guides/disburse/countries/jordan
Payout methods, timing, transaction limits, and required fields for payouts to Jordan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JOD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JOD`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 30 characters.
* IBAN format; must match: `^JO[0-9]{2}[a-zA-Z0-9]{26}$`
**Example:** `JO94CBJO0010000000000131000302`
### 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.
# Kazakhstan
Source: https://docs.withacclaim.com/guides/disburse/countries/kazakhstan
Payout methods, timing, transaction limits, and required fields for payouts to Kazakhstan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `KZT`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `KZT`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^KZ[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `KZ86125KZT5004100100`
### 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.
# Kenya
Source: https://docs.withacclaim.com/guides/disburse/countries/kenya
Payout methods, timing, transaction limits, and required fields for payouts to Kenya.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Kenya Local Transfer | KES | 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.
## Kenya Local Transfer
Kenyan local bank transfer
### Supported currencies
`KES`
### 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 | 5 USD |
| Maximum | 999,999 KES |
### Fields
#### Payout Method Type
**Value:** `KenyaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNKEXA`
#### Account Number
Account number (8-20 alphanumeric characters)
**Validation:**
* Between 8 and 20 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{8,20}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NBKEKENXXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Kiribati
Source: https://docs.withacclaim.com/guides/disburse/countries/kiribati
Payout methods, timing, transaction limits, and required fields for payouts to Kiribati.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BKIRKIKI`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `100123456789`
### 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.
# Kosovo
Source: https://docs.withacclaim.com/guides/disburse/countries/kosovo
Payout methods, timing, transaction limits, and required fields for payouts to Kosovo.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^XK[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `XK051212012345678906`
### 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.
# Kuwait
Source: https://docs.withacclaim.com/guides/disburse/countries/kuwait
Payout methods, timing, transaction limits, and required fields for payouts to Kuwait.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `KWD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `KWD`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 30 characters.
* IBAN format; must match: `^KW[0-9]{2}[a-zA-Z0-9]{26}$`
**Example:** `KW81CBKU0000000000001234560101`
### 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.
# Kyrgyzstan
Source: https://docs.withacclaim.com/guides/disburse/countries/kyrgyzstan
Payout methods, timing, transaction limits, and required fields for payouts to Kyrgyzstan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `KGS`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `KGS`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `KYRSKG22`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Laos
Source: https://docs.withacclaim.com/guides/disburse/countries/laos
Payout methods, timing, transaction limits, and required fields for payouts to Laos.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `LICBLALA`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `10010123456789`
### 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.
# Latvia
Source: https://docs.withacclaim.com/guides/disburse/countries/latvia
Payout methods, timing, transaction limits, and required fields for payouts to Latvia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 21 characters.
* IBAN format; must match: `^LV[0-9]{2}[a-zA-Z0-9]{17}$`
**Example:** `LV51NDEA0000082414423`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 21 characters.
* IBAN format; must match: `^LV[0-9]{2}[a-zA-Z0-9]{17}$`
**Example:** `LV51NDEA0000082414423`
### 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.
# Lebanon
Source: https://docs.withacclaim.com/guides/disburse/countries/lebanon
Payout methods, timing, transaction limits, and required fields for payouts to Lebanon.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^LB[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `LB05001400000402353234324314`
### 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.
# Lesotho
Source: https://docs.withacclaim.com/guides/disburse/countries/lesotho
Payout methods, timing, transaction limits, and required fields for payouts to Lesotho.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Lesotho Local Transfer | LSL | 2-3 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.
## Lesotho Local Transfer
Lesotho local bank transfer
### Supported currencies
`LSL`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `LesothoLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNLSMX`
#### Account Number
Account number (up to 35 alphanumeric characters)
**Validation:**
* Between 1 and 35 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{1,35}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `FIRNLSMX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 35 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,35}$`
**Example:** `10012345678`
### 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.
# Liberia
Source: https://docs.withacclaim.com/guides/disburse/countries/liberia
Payout methods, timing, transaction limits, and required fields for payouts to Liberia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CBLRLRLA`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `001123456789`
### 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.
# Liechtenstein
Source: https://docs.withacclaim.com/guides/disburse/countries/liechtenstein
Payout methods, timing, transaction limits, and required fields for payouts to Liechtenstein.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 21 characters.
* IBAN format; must match: `^LI[0-9]{2}[a-zA-Z0-9]{17}$`
**Example:** `LI21088100002324013AA`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 21 characters.
* IBAN format; must match: `^LI[0-9]{2}[a-zA-Z0-9]{17}$`
**Example:** `LI21088100002324013AA`
### 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.
# Lithuania
Source: https://docs.withacclaim.com/guides/disburse/countries/lithuania
Payout methods, timing, transaction limits, and required fields for payouts to Lithuania.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^LT[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `LT537044060000544963`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^LT[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `LT537044060000544963`
### 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.
# Luxembourg
Source: https://docs.withacclaim.com/guides/disburse/countries/luxembourg
Payout methods, timing, transaction limits, and required fields for payouts to Luxembourg.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^LU[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `LU870141331362410000`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 20 characters.
* IBAN format; must match: `^LU[0-9]{2}[a-zA-Z0-9]{16}$`
**Example:** `LU870141331362410000`
### 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.
# Macao SAR China
Source: https://docs.withacclaim.com/guides/disburse/countries/macao-sar-china
Payout methods, timing, transaction limits, and required fields for payouts to Macao SAR China.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `TFBLMOMXXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Madagascar
Source: https://docs.withacclaim.com/guides/disburse/countries/madagascar
Payout methods, timing, transaction limits, and required fields for payouts to Madagascar.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Madagascar Local Transfer | MGA | 2-3 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.
## Madagascar Local Transfer
Madagascan local bank transfer
### Supported currencies
`MGA`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 20,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `MadagascarLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^MG[0-9]{2}[A-Z0-9]{23}$`
**Example:** `MG4600005123456789012345678`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^MG[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `MG4600005030071289421016045`
### 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.
# Malawi
Source: https://docs.withacclaim.com/guides/disburse/countries/malawi
Payout methods, timing, transaction limits, and required fields for payouts to Malawi.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Malawi Local Transfer | MWK | 2-3 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.
## Malawi Local Transfer
Malawian local bank transfer
### Supported currencies
`MWK`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `MalawiLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNMWMX`
#### Account Number
Account number (up to 35 alphanumeric characters)
**Validation:**
* Between 1 and 35 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{1,35}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `MBBCMWMW`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `011123456789`
### 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.
# Malaysia
Source: https://docs.withacclaim.com/guides/disburse/countries/malaysia
Payout methods, timing, transaction limits, and required fields for payouts to Malaysia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| iACH / Duitnow / GIRO | MYR | 0-2 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.
## iACH / Duitnow / GIRO
Malaysia iACH / Duitnow Transfer / GIRO payment system
### Supported currencies
`MYR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 MYR |
### Fields
#### Payout Method Type
**Value:** `MalaysiaIach`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `MBBEMYKL`
#### Account Number
Account number (5-19 digits)
**Validation:**
* Between 5 and 19 characters (inclusive).
* Must match this regular expression: `^[0-9]{5,19}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `OCBCMYKL`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 5 and 19 characters (inclusive).
* Must match this regular expression: `^[0-9]{5,19}$`
**Example:** `12750852`
### 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.
# Maldives
Source: https://docs.withacclaim.com/guides/disburse/countries/maldives
Payout methods, timing, transaction limits, and required fields for payouts to Maldives.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `MALBMVMV`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `7701130746102`
### 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.
# Malta
Source: https://docs.withacclaim.com/guides/disburse/countries/malta
Payout methods, timing, transaction limits, and required fields for payouts to Malta.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 31 characters.
* IBAN format; must match: `^MT[0-9]{2}[a-zA-Z0-9]{27}$`
**Example:** `MT84MMEB44853000000085031458002`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 31 characters.
* IBAN format; must match: `^MT[0-9]{2}[a-zA-Z0-9]{27}$`
**Example:** `MT84MMEB44853000000085031458002`
### 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.
# Marshall Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/marshall-islands
Payout methods, timing, transaction limits, and required fields for payouts to Marshall Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BOMDMH22`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1112233445`
### 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.
# Martinique
Source: https://docs.withacclaim.com/guides/disburse/countries/martinique
Payout methods, timing, transaction limits, and required fields for payouts to Martinique.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
### 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.
# Mauritania
Source: https://docs.withacclaim.com/guides/disburse/countries/mauritania
Payout methods, timing, transaction limits, and required fields for payouts to Mauritania.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^MR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `MR1300020001010000123456753`
### 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.
# Mauritius
Source: https://docs.withacclaim.com/guides/disburse/countries/mauritius
Payout methods, timing, transaction limits, and required fields for payouts to Mauritius.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `MUR`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `MUR`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 30 characters.
* IBAN format; must match: `^MU[0-9]{2}[a-zA-Z0-9]{26}$`
**Example:** `MU17BOMM0101101030300200000MUR`
### 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.
# Mayotte
Source: https://docs.withacclaim.com/guides/disburse/countries/mayotte
Payout methods, timing, transaction limits, and required fields for payouts to Mayotte.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
### 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.
# Mexico
Source: https://docs.withacclaim.com/guides/disburse/countries/mexico
Payout methods, timing, transaction limits, and required fields for payouts to Mexico.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SPEI | MXN | 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.
## SPEI
Interbank Electronic Payment System
### Supported currencies
`MXN`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `MexicoSpei`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### CLABE
**Validation:**
* Exactly 18 characters.
* Must match this regular expression: `^[0-9]{18}$`
* `clabe`
**Example:** `002010077777777771`
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `MXN`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `MXN`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BNMXMXMM`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 20 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,20}$`
**Example:** `002123123456789019`
### 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.
# Micronesia
Source: https://docs.withacclaim.com/guides/disburse/countries/micronesia
Payout methods, timing, transaction limits, and required fields for payouts to Micronesia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BOHIFMP1`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012`
### 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.
# Moldova
Source: https://docs.withacclaim.com/guides/disburse/countries/moldova
Payout methods, timing, transaction limits, and required fields for payouts to Moldova.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^MD[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `MD24AG000225100013104168`
### 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.
# Monaco
Source: https://docs.withacclaim.com/guides/disburse/countries/monaco
Payout methods, timing, transaction limits, and required fields for payouts to Monaco.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^MC[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `MC5830003009520002008164641`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^MC[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `MC5830003009520002008164641`
### 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.
# Mongolia
Source: https://docs.withacclaim.com/guides/disburse/countries/mongolia
Payout methods, timing, transaction limits, and required fields for payouts to Mongolia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `AGMOMNUBXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `4500123456789`
### 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.
# Montenegro
Source: https://docs.withacclaim.com/guides/disburse/countries/montenegro
Payout methods, timing, transaction limits, and required fields for payouts to Montenegro.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `TCZBMEPG`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `505120000000265671`
### 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.
# Montserrat
Source: https://docs.withacclaim.com/guides/disburse/countries/montserrat
Payout methods, timing, transaction limits, and required fields for payouts to Montserrat.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BKMOMSMS`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `7700123456789`
### 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.
# Morocco
Source: https://docs.withacclaim.com/guides/disburse/countries/morocco
Payout methods, timing, transaction limits, and required fields for payouts to Morocco.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Morocco SIMT/SRBM | MAD | 1-2 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.
## Morocco SIMT/SRBM
Moroccan SIMT/SRBM bank transfer
### Supported currencies
`MAD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 1-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `MoroccoSimtSrbm`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### RIB (Relevé d'Identité Bancaire)
24-digit RIB starting with a 3-digit bank code
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[0-9]{24}$`
**Example:** `123456789012345678901234`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCMAMAMC`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `002123456789012345678901`
### 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.
# Namibia
Source: https://docs.withacclaim.com/guides/disburse/countries/namibia
Payout methods, timing, transaction limits, and required fields for payouts to Namibia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Namibia Local Transfer | NAD | 2-3 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.
## Namibia Local Transfer
Namibian local bank transfer
### Supported currencies
`NAD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `NamibiaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNNANXCUS`
#### Account Number
Account number (8-13 alphanumeric characters)
**Validation:**
* Between 8 and 13 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{8,13}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `FIRNNANXCUS`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `62251399062`
### 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.
# Nepal
Source: https://docs.withacclaim.com/guides/disburse/countries/nepal
Payout methods, timing, transaction limits, and required fields for payouts to Nepal.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| IBFT/NCHL | NPR | 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.
## IBFT/NCHL
Nepal IBFT/NCHL payment system
### Supported currencies
`NPR`
### 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 | 10 NPR |
| Maximum | 1,000,000 NPR |
### Fields
#### Payout Method Type
**Value:** `NepalIbtfNchl`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
5-character code to identify a Nepalese bank (e.g., NP002 for Agricultural Development Bank)
**Validation:**
* Exactly 5 characters.
* Must match this regular expression: `^[A-Z0-9]{5}$`
**Example:** `NP002`
#### Account Number
Account number (up to 50 alphanumeric characters)
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[A-Z0-9]{1,50}$`
**Example:** `1234567890`
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NPR`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NPR`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `LXBLNPKA`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
#### Tax ID Type
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### PAN (Permanent Account Number)
9-digit Permanent Account Number (PAN)
**Validation:**
* Exactly 9 characters.
* Must match this regular expression: `^[0-9]{9}$`
**Example:** `123456789`
#### Tax ID Type
**Value:** `INDIVIDUAL_TAX_ID`
#### PAN (Permanent Account Number)
9-digit Permanent Account Number (PAN)
**Validation:**
* Exactly 9 characters.
* Must match this regular expression: `^[0-9]{9}$`
**Example:** `123456789`
### Notes
* A beneficiary tax ID is only required when the payout currency is NPR (Nepalese rupee).
* 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.
# Netherlands
Source: https://docs.withacclaim.com/guides/disburse/countries/netherlands
Payout methods, timing, transaction limits, and required fields for payouts to Netherlands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^NL[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `NL26DEUT0436855232`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 18 characters.
* IBAN format; must match: `^NL[0-9]{2}[a-zA-Z0-9]{14}$`
**Example:** `NL26DEUT0436855232`
### 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.
# New Caledonia
Source: https://docs.withacclaim.com/guides/disburse/countries/new-caledonia
Payout methods, timing, transaction limits, and required fields for payouts to New Caledonia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7630006000011234567890189`
### 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.
# New Zealand
Source: https://docs.withacclaim.com/guides/disburse/countries/new-zealand
Payout methods, timing, transaction limits, and required fields for payouts to New Zealand.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Direct Credit | NZD | 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.
## Direct Credit
New Zealand Direct Credit bank transfer
### Supported currencies
`NZD`
### 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 | 99,999,999.99 NZD |
### Fields
#### Payout Method Type
**Value:** `NewZealandDirectCredit`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Account Number
15-17 digit account number starting with a 6-digit bank and branch code (format: BB-bbbb-AAAAAAAA-SSS)
**Validation:**
* Between 15 and 17 characters (inclusive).
* Must match this regular expression: `^[0-9]{15,17}$`
**Example:** `01000012345678901`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `ANZBNZ22`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `010083417212111`
### 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.
# Nicaragua
Source: https://docs.withacclaim.com/guides/disburse/countries/nicaragua
Payout methods, timing, transaction limits, and required fields for payouts to Nicaragua.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NIO`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NIO`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCNINIMA`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `5050123456789`
### 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.
# Niger
Source: https://docs.withacclaim.com/guides/disburse/countries/niger
Payout methods, timing, transaction limits, and required fields for payouts to Niger.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| ----------------------------- | ---------- | ----------------- |
| Central Africa Local Transfer | XOF | 2-3 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.
## Central Africa Local Transfer
Central Africa local bank transfer
### Supported currencies
`XOF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `CentralAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNSNX1`
#### Account Number
Account number (exactly 24 alphanumeric characters)
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[A-Za-z0-9]{24}$`
**Example:** `123456789012345678901234`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCEAOXDKNE`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[0-9A-Za-z]{24}$`
**Example:** `012345678901234567890123`
### 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.
# Nigeria
Source: https://docs.withacclaim.com/guides/disburse/countries/nigeria
Payout methods, timing, transaction limits, and required fields for payouts to Nigeria.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Nigeria Local Transfer | NGN | 2-3 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.
## Nigeria Local Transfer
Nigerian local bank transfer
### Supported currencies
`NGN`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 50,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `NigeriaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNNGLA`
#### Account Number
Account number (7-17 alphanumeric characters)
**Validation:**
* Between 7 and 17 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{7,17}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CITINGLAXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 10 characters.
* Must match this regular expression: `^[0-9]{10}$`
**Example:** `1234567890`
### 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.
# North Macedonia
Source: https://docs.withacclaim.com/guides/disburse/countries/north-macedonia
Payout methods, timing, transaction limits, and required fields for payouts to North Macedonia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 19 characters.
* IBAN format; must match: `^MK[0-9]{2}[a-zA-Z0-9]{15}$`
**Example:** `MK07250120000058984`
### 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.
# Northern Mariana Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/northern-mariana-islands
Payout methods, timing, transaction limits, and required fields for payouts to Northern Mariana Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `GMBKMPM1`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `6500123456789`
### 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.
# Norway
Source: https://docs.withacclaim.com/guides/disburse/countries/norway
Payout methods, timing, transaction limits, and required fields for payouts to Norway.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| NICS | NOK | 0-1 business days |
| SEPA | EUR | 0-2 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.
## NICS
Norway Norwegian Interbank Clearing System
### Supported currencies
`NOK`
### 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 | 25,000,000 NOK |
### Fields
#### Payout Method Type
**Value:** `NorwayNics`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
**Validation:**
* Exactly 4 characters.
* Must match this regular expression: `^[0-9]{4}$`
**Example:** `1234`
#### Account Number
**Validation:**
* Exactly 7 characters.
* Must match this regular expression: `^[0-9]{7}$`
**Example:** `1234567`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 15 characters.
* IBAN format; must match: `^NO[0-9]{2}[a-zA-Z0-9]{11}$`
**Example:** `NO9386011117947`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 15 characters.
* IBAN format; must match: `^NO[0-9]{2}[a-zA-Z0-9]{11}$`
**Example:** `NO9386011117947`
### 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.
# Oman
Source: https://docs.withacclaim.com/guides/disburse/countries/oman
Payout methods, timing, transaction limits, and required fields for payouts to Oman.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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`, `OMR`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `OMR`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `OMABOMRUXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Pakistan
Source: https://docs.withacclaim.com/guides/disburse/countries/pakistan
Payout methods, timing, transaction limits, and required fields for payouts to Pakistan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| RTGS/IBFT | PKR | 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.
## RTGS/IBFT
Pakistan RTGS/IBFT payment system
### Supported currencies
`PKR`
### 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 | 5,000,000 PKR |
### Fields
#### Payout Method Type
**Value:** `PakistanRtgsIbtf`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^PK[0-9]{2}[A-Z0-9]{4}[0-9]{16}$`
**Example:** `PK36SCBL0000001123456702`
## 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`, `PKR`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PKR`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^PK[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `PK36SCBL0000001123456702`
### 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.
# Palau
Source: https://docs.withacclaim.com/guides/disburse/countries/palau
Payout methods, timing, transaction limits, and required fields for payouts to Palau.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BOHIPW21`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `7300123456789`
### 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.
# Palestinian Territories
Source: https://docs.withacclaim.com/guides/disburse/countries/palestinian-territories
Payout methods, timing, transaction limits, and required fields for payouts to Palestinian Territories.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 29 characters.
* IBAN format; must match: `^PS[0-9]{2}[a-zA-Z0-9]{25}$`
**Example:** `PS92PALS000000000400123456702`
### 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.
# Panama
Source: https://docs.withacclaim.com/guides/disburse/countries/panama
Payout methods, timing, transaction limits, and required fields for payouts to Panama.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NAPAPAPAXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Papua New Guinea
Source: https://docs.withacclaim.com/guides/disburse/countries/papua-new-guinea
Payout methods, timing, transaction limits, and required fields for payouts to Papua New Guinea.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `WPACPGPMXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `100012345678`
### 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.
# Paraguay
Source: https://docs.withacclaim.com/guides/disburse/countries/paraguay
Payout methods, timing, transaction limits, and required fields for payouts to Paraguay.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SIPAP | PYG | 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.
## SIPAP
Paraguayan local bank transfer
### Supported currencies
`PYG`
### 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
**Value:** `ParaguaySipap`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Account Number
Recipient's bank account number (up to 35 alphanumeric characters)
**Validation:**
* Between 1 and 35 characters (inclusive).
* Must match this regular expression: `^[a-zA-Z0-9]{1,35}$`
**Example:** `1234567890`
#### SWIFT / BIC Code
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:** `DEUTDEFF`
#### Tax ID Type
**Conditional:** Required for Company payees only.
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### RUC (Business Tax ID)
**Conditional:** Required for Company payees only.
RUC (Registro Único del Contribuyente) - 11 digits
**Validation:**
* Exactly 11 characters.
* Must match this regular expression: `^[0-9]{11}$`
**Example:** `12345678901`
#### Personal ID Type
**Conditional:** Required for Individual payees only.
**Value:** One of `NATIONAL_ID`, `FOREIGN_ID`, `INDIVIDUAL_TAX_ID`
Select the ID type as registered with the bank account
#### Personal ID Number
**Conditional:** Required for Individual payees only.
Personal identification number (4-100 alphanumeric characters)
**Validation:**
* Between 4 and 100 characters (inclusive).
* Must match this regular expression: `^[a-zA-Z0-9]{4,100}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BSUDPYPXXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Peru
Source: https://docs.withacclaim.com/guides/disburse/countries/peru
Payout methods, timing, transaction limits, and required fields for payouts to Peru.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| CCE | PEN | 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.
## CCE
Peruvian CCE (Cámara de Compensación Electrónica) payment system using CCI (Código de Cuenta Interbancario)
### Supported currencies
`PEN`
### 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
**Value:** `PeruCce`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### CCI (Código de Cuenta Interbancario)
CCI (Código de Cuenta Interbancario) - 20-digit number starting with 3-digit bank code
**Validation:**
* Exactly 20 characters.
* Must match this regular expression: `^[0-9]{20}$`
**Example:** `12345678901234567890`
#### Account Type
**Value:** One of `checking`, `savings`, `maestra`
#### Tax ID Type
**Conditional:** Required for Company payees only.
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### RUC (Business Tax ID)
**Conditional:** Required for Company payees only.
RUC (Registro Único del Contribuyente) - 11 digits
**Validation:**
* Exactly 11 characters.
* Must match this regular expression: `^[0-9]{11}$`
**Example:** `12345678901`
#### Personal ID Type
**Conditional:** Required for Individual payees only.
**Value:** One of `NATIONAL_ID`, `FOREIGN_ID`, `PASSPORT`, `INDIVIDUAL_TAX_ID`
Select DNI, CE, Passport, or RUC as registered with the bank account
#### Personal ID Number
**Conditional:** Required for Individual payees only.
Personal identification number. Format: DNI (8 digits or 9 alphanumeric), CE (4-12 alphanumeric), Passport (4-100 alphanumeric), RUC (11 digits)
**Validation:**
* Between 4 and 100 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{4,100}$`
**Example:** `12345678`
### Notes
* The Peruvian government sets a 0.005% tax (Impuesto a las Transacciones Financieras: Tax on Financial Transactions) per transaction, which is collected as part of transfer fees., which is collected automatically in addition to the payout transaction fee.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BCPLPEPL`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `00112345678901234567`
### 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.
# Philippines
Source: https://docs.withacclaim.com/guides/disburse/countries/philippines
Payout methods, timing, transaction limits, and required fields for payouts to Philippines.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Instapay/PesoNet | PHP | 0-1 business days |
| PDDTS/GSRT | USD | 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.
## Instapay/PesoNet
Philippines Instapay/PesoNet payment system
### Supported currencies
`PHP`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `PhilippinesInstapayPesonet`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `BNORPHMM`
#### Account Number
Account number (8-16 digits)
**Validation:**
* Between 8 and 16 characters (inclusive).
* Must match this regular expression: `^[0-9]{8,16}$`
**Example:** `1234567890123456`
## PDDTS/GSRT
Philippines PDDTS/GSRT payment system
### Supported currencies
`USD`
### 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
**Value:** `PhilippinesPddtsGsrt`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `BNORPHMM`
#### Account Number
Account number (8-16 digits)
**Validation:**
* Between 8 and 16 characters (inclusive).
* Must match this regular expression: `^[0-9]{8,16}$`
**Example:** `1234567890123456`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BOPIPHMM`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 8 and 19 characters (inclusive).
* Must match this regular expression: `^[0-9]{8,19}$`
**Example:** `12750852`
### 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.
# Poland
Source: https://docs.withacclaim.com/guides/disburse/countries/poland
Payout methods, timing, transaction limits, and required fields for payouts to Poland.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Elixir | PLN | 0-1 business days |
| SEPA | EUR | 0-2 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.
## Elixir
Poland Elixir payment system
### Supported currencies
`PLN`
### 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 | 150,000 PLN |
### Fields
#### Payout Method Type
**Value:** `PolandElixir`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^PL[0-9]{26}$`
**Example:** `PL61109010140000071219812874`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^PL[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `PL61109010140000071219812874`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 28 characters.
* IBAN format; must match: `^PL[0-9]{2}[a-zA-Z0-9]{24}$`
**Example:** `PL61109010140000071219812874`
### 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.
# Portugal
Source: https://docs.withacclaim.com/guides/disburse/countries/portugal
Payout methods, timing, transaction limits, and required fields for payouts to Portugal.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 25 characters.
* IBAN format; must match: `^PT[0-9]{2}[a-zA-Z0-9]{21}$`
**Example:** `PT50003300004546072693705`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 25 characters.
* IBAN format; must match: `^PT[0-9]{2}[a-zA-Z0-9]{21}$`
**Example:** `PT50003300004546072693705`
### 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.
# Puerto Rico
Source: https://docs.withacclaim.com/guides/disburse/countries/puerto-rico
Payout methods, timing, transaction limits, and required fields for payouts to Puerto Rico.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `FBPRPRSJXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Qatar
Source: https://docs.withacclaim.com/guides/disburse/countries/qatar
Payout methods, timing, transaction limits, and required fields for payouts to Qatar.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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`, `QAR`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `QAR`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 29 characters.
* IBAN format; must match: `^QA[0-9]{2}[a-zA-Z0-9]{25}$`
**Example:** `QA58DOHB00001234567890ABCDEFG`
### 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.
# Réunion
Source: https://docs.withacclaim.com/guides/disburse/countries/reunion
Payout methods, timing, transaction limits, and required fields for payouts to Réunion.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7630006000011234567890189`
### 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.
# Romania
Source: https://docs.withacclaim.com/guides/disburse/countries/romania
Payout methods, timing, transaction limits, and required fields for payouts to Romania.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| TransFonD | RON | 0-1 business days |
| SEPA | EUR | 0-2 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.
## TransFonD
Romania TransFonD SENT ACH payment system
### Supported currencies
`RON`
### 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 | 200,000 RON |
### Fields
#### Payout Method Type
**Value:** `RomaniaTransfond`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^RO[0-9]{2}[A-Z0-9]{4}[0-9]{16}$`
**Example:** `RO49AAAA1B31007593840000`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^RO[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `RO16BREL4354388901234567`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^RO[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `RO16BREL4354388901234567`
### 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.
# Rwanda
Source: https://docs.withacclaim.com/guides/disburse/countries/rwanda
Payout methods, timing, transaction limits, and required fields for payouts to Rwanda.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Rwanda Local Transfer | RWF | 2-3 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.
## Rwanda Local Transfer
Rwandan local bank transfer
### Supported currencies
`RWF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `RwandaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNRWX1`
#### Account Number
Account number (up to 35 alphanumeric characters)
**Validation:**
* Between 1 and 35 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{1,35}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `AFRWRWRW`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `0004567890123`
### 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.
# Samoa
Source: https://docs.withacclaim.com/guides/disburse/countries/samoa
Payout methods, timing, transaction limits, and required fields for payouts to Samoa.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CBSAWSWS`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123400123456`
### 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.
# San Marino
Source: https://docs.withacclaim.com/guides/disburse/countries/san-marino
Payout methods, timing, transaction limits, and required fields for payouts to San Marino.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^SM[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `SM86U0322509800000000270100`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^SM[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `SM86U0322509800000000270100`
### 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.
# São Tomé & Príncipe
Source: https://docs.withacclaim.com/guides/disburse/countries/sao-tome-principe
Payout methods, timing, transaction limits, and required fields for payouts to São Tomé & Príncipe.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 25 characters.
* IBAN format; must match: `^ST[0-9]{2}[a-zA-Z0-9]{21}$`
**Example:** `ST68000100010051845310112`
### 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.
# Saudi Arabia
Source: https://docs.withacclaim.com/guides/disburse/countries/saudi-arabia
Payout methods, timing, transaction limits, and required fields for payouts to Saudi Arabia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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`, `SAR`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SAR`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^SA[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `SA0380000000608010167519`
### 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.
# Senegal
Source: https://docs.withacclaim.com/guides/disburse/countries/senegal
Payout methods, timing, transaction limits, and required fields for payouts to Senegal.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| ----------------------------- | ---------- | ----------------- |
| Central Africa Local Transfer | XOF | 2-3 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.
## Central Africa Local Transfer
Central Africa local bank transfer
### Supported currencies
`XOF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `CentralAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNSNX1`
#### Account Number
Account number (exactly 24 alphanumeric characters)
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[A-Za-z0-9]{24}$`
**Example:** `123456789012345678901234`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `LHSESNDA`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[0-9A-Za-z]{24}$`
**Example:** `123456789012345678901234`
### 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.
# Serbia
Source: https://docs.withacclaim.com/guides/disburse/countries/serbia
Payout methods, timing, transaction limits, and required fields for payouts to Serbia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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`, `RSD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `RSD`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^RS[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `RS35260005601001611379`
### 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.
# Seychelles
Source: https://docs.withacclaim.com/guides/disburse/countries/seychelles
Payout methods, timing, transaction limits, and required fields for payouts to Seychelles.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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`, `SCR`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SCR`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 31 characters.
* IBAN format; must match: `^SC[0-9]{2}[a-zA-Z0-9]{27}$`
**Example:** `SC52BAHL01031234567890123456USD`
### 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.
# Sierra Leone
Source: https://docs.withacclaim.com/guides/disburse/countries/sierra-leone
Payout methods, timing, transaction limits, and required fields for payouts to Sierra Leone.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `SLCBSLFRXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `011234567890`
### 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.
# Singapore
Source: https://docs.withacclaim.com/guides/disburse/countries/singapore
Payout methods, timing, transaction limits, and required fields for payouts to Singapore.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| FAST | SGD | 0-1 business days |
| GIRO | SGD | 1-2 business days |
| MEPS (RTGS) | SGD | 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.
## FAST
Singapore FAST payment system
### Supported currencies
`SGD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----------- |
| Minimum | None |
| Maximum | 200,000 SGD |
### Fields
#### Payout Method Type
**Value:** `SingaporeFast`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `DBSASGGS`
#### Account Number
Account number (7-17 alphanumeric characters)
**Validation:**
* Between 7 and 17 characters (inclusive).
* Must match this regular expression: `^[A-Z0-9]{7,17}$`
**Example:** `12345678901234567`
## GIRO
Singapore GIRO payment system
### Supported currencies
`SGD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 1-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `SingaporeGiro`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `DBSASGGS`
#### Account Number
Account number (7-17 alphanumeric characters)
**Validation:**
* Between 7 and 17 characters (inclusive).
* Must match this regular expression: `^[A-Z0-9]{7,17}$`
**Example:** `12345678901234567`
## MEPS (RTGS)
Singapore MEPS (RTGS) payment system
### Supported currencies
`SGD`
### 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
**Value:** `SingaporeMeps`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `DBSASGGS`
#### Account Number
Account number (6-23 alphanumeric characters)
**Validation:**
* Between 6 and 23 characters (inclusive).
* Must match this regular expression: `^[A-Z0-9]{6,23}$`
**Example:** `12345678901234567890123`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `DBSSSGSG`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 6 and 26 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{6,26}$`
**Example:** `1707625311`
### 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.
# Slovakia
Source: https://docs.withacclaim.com/guides/disburse/countries/slovakia
Payout methods, timing, transaction limits, and required fields for payouts to Slovakia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^SK[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `SK1081800000007000244103`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^SK[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `SK1081800000007000244103`
### 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.
# Slovenia
Source: https://docs.withacclaim.com/guides/disburse/countries/slovenia
Payout methods, timing, transaction limits, and required fields for payouts to Slovenia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 19 characters.
* IBAN format; must match: `^SI[0-9]{2}[a-zA-Z0-9]{15}$`
**Example:** `SI56011006030708574`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 19 characters.
* IBAN format; must match: `^SI[0-9]{2}[a-zA-Z0-9]{15}$`
**Example:** `SI56011006030708574`
### 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.
# Solomon Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/solomon-islands
Payout methods, timing, transaction limits, and required fields for payouts to Solomon Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CBSISBSB`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `012345678901`
### 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.
# South Africa
Source: https://docs.withacclaim.com/guides/disburse/countries/south-africa
Payout methods, timing, transaction limits, and required fields for payouts to South Africa.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| EFT | ZAR | 1-2 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.
## EFT
South African domestic bank transfer
### Supported currencies
`ZAR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 1-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `SouthAfricaEft`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
**Value:** One of `ABSAZAJJ`, `BATHZAJJ`, `AFRCZAJJ`, `ALBRZAJJ`, `BNPAZAJJ`, `ZERMZAJJ`, `BIDBZAJJ`, `CABLZAJJ`, `CITIZAJX`, `DISCZAJJ`, `FBMBZAJJ`, `FIRNZAJB`, `FIRNZAJJ`, `GRIDZAJJ`, `MAMRZAJ1`, `HBZHZAJJ`, `HSBCZAJJ`, `HOBLZAJJ`, `IVESZAJJ`, `MGTCZAJJ`, `LISAZAJJ`, `BOEPZAJ1`, `NEDSZAJJ`, `SASFZAJJ`, `SBZAZAJJ`, `SCBLZAJ2`, `SCBLZAJJ`, `SBINZAJJ`, `CBZAZAJJ`, `YOUBZAJJ`, `UNAAZAJ1`, `VBSMZAJJ`
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:** `ABSAZAJJ`
#### Account Number
**Validation:**
* Between 6 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9]{6,15}$`
**Example:** `1234567890`
#### Account Type
**Value:** One of `checking`, `savings`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BATHZAJJXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 7 and 17 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{7,17}$`
**Example:** `1234567890`
### 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.
# South Korea
Source: https://docs.withacclaim.com/guides/disburse/countries/south-korea
Payout methods, timing, transaction limits, and required fields for payouts to South Korea.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| HOFINET | KRW | 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.
## HOFINET
Korean HOFINET domestic bank transfer system
### Supported currencies
`KRW`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----------------- |
| Minimum | None |
| Maximum | 1,000,000,000 KRW |
### Fields
#### Payout Method Type
**Value:** `KoreaHofinet`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
3-digit number to identify a Korean bank
**Validation:**
* Exactly 3 characters.
* Must match this regular expression: `^[0-9]{3}$`
**Example:** `001`
#### Account Number
Account number (7-16 alphanumeric characters)
**Validation:**
* Between 7 and 16 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{7,16}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `KOEXKRSE`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 7 and 16 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{7,16}$`
**Example:** `39112345612345`
### 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.
# Spain
Source: https://docs.withacclaim.com/guides/disburse/countries/spain
Payout methods, timing, transaction limits, and required fields for payouts to Spain.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^ES[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `ES5120389784526000112078`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^ES[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `ES5120389784526000112078`
### 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.
# Sri Lanka
Source: https://docs.withacclaim.com/guides/disburse/countries/sri-lanka
Payout methods, timing, transaction limits, and required fields for payouts to Sri Lanka.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SLIPS | LKR | 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.
## SLIPS
Sri Lanka SLIPS payment system
### Supported currencies
`LKR`
### 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 | 100 LKR |
| Maximum | 15,000,000 LKR |
### Fields
#### Payout Method Type
**Value:** `SriLankaSlips`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `CCEYLKLX`
#### Account Number
Account number (up to 50 alphanumeric characters)
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[A-Z0-9]{1,50}$`
**Example:** `12345678901234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `UBCLLKLC`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# St. Barthélemy
Source: https://docs.withacclaim.com/guides/disburse/countries/st-barthelemy
Payout methods, timing, transaction limits, and required fields for payouts to St. Barthélemy.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7630006000011234567890189`
### 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.
# St. Helena
Source: https://docs.withacclaim.com/guides/disburse/countries/st-helena
Payout methods, timing, transaction limits, and required fields for payouts to St. Helena.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BHELSHJJ`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `110123456789`
### 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.
# St. Kitts & Nevis
Source: https://docs.withacclaim.com/guides/disburse/countries/st-kitts-nevis
Payout methods, timing, transaction limits, and required fields for payouts to St. Kitts & Nevis.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BNEIKNNE`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `100234567890`
### 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.
# St. Lucia
Source: https://docs.withacclaim.com/guides/disburse/countries/st-lucia
Payout methods, timing, transaction limits, and required fields for payouts to St. Lucia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 32 characters.
* IBAN format; must match: `^LC[0-9]{2}[a-zA-Z0-9]{28}$`
**Example:** `LC14BOSL123456789012345678901234`
### 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.
# St. Martin
Source: https://docs.withacclaim.com/guides/disburse/countries/st-martin
Payout methods, timing, transaction limits, and required fields for payouts to St. Martin.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7630006000011234567890189`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7630006000011234567890189`
### 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.
# St. Pierre & Miquelon
Source: https://docs.withacclaim.com/guides/disburse/countries/st-pierre-miquelon
Payout methods, timing, transaction limits, and required fields for payouts to St. Pierre & Miquelon.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR1420041010050500013M02606`
### 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.
# St. Vincent & Grenadines
Source: https://docs.withacclaim.com/guides/disburse/countries/st-vincent-grenadines
Payout methods, timing, transaction limits, and required fields for payouts to St. Vincent & Grenadines.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NCBVVC22`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `110023456789`
### 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.
# Suriname
Source: https://docs.withacclaim.com/guides/disburse/countries/suriname
Payout methods, timing, transaction limits, and required fields for payouts to Suriname.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CBVSSRPA`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `0123456789012`
### 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.
# Sweden
Source: https://docs.withacclaim.com/guides/disburse/countries/sweden
Payout methods, timing, transaction limits, and required fields for payouts to Sweden.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| DCL | SEK | 0-1 business days |
| SEPA | EUR | 0-2 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.
## DCL
Sweden Dataclearingen (DCL) ACH payment system
### Supported currencies
`SEK`
### 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 | 500,000 SEK |
### Fields
#### Payout Method Type
**Value:** `SwedenDcl`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
**Validation:**
* Between 4 and 5 characters (inclusive).
* Must match this regular expression: `^[0-9]{4,5}$`
**Example:** `1234`
#### Account Number
**Validation:**
* Between 1 and 15 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,15}$`
**Example:** `1234567890`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^SE[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `SE4550000000058398257466`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^SE[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `SE4550000000058398257466`
### 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.
# Switzerland
Source: https://docs.withacclaim.com/guides/disburse/countries/switzerland
Payout methods, timing, transaction limits, and required fields for payouts to Switzerland.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 21 characters.
* IBAN format; must match: `^CH[0-9]{2}[a-zA-Z0-9]{17}$`
**Example:** `CH1804835243807324588`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 21 characters.
* IBAN format; must match: `^CH[0-9]{2}[a-zA-Z0-9]{17}$`
**Example:** `CH1804835243807324588`
### 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.
# Taiwan
Source: https://docs.withacclaim.com/guides/disburse/countries/taiwan
Payout methods, timing, transaction limits, and required fields for payouts to Taiwan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BKTWTWTP`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 8 and 20 characters (inclusive).
* Must match this regular expression: `^[0-9]{8,20}$`
**Example:** `50001121111`
### 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.
# Tajikistan
Source: https://docs.withacclaim.com/guides/disburse/countries/tajikistan
Payout methods, timing, transaction limits, and required fields for payouts to Tajikistan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NATJTJ22XXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Tanzania
Source: https://docs.withacclaim.com/guides/disburse/countries/tanzania
Payout methods, timing, transaction limits, and required fields for payouts to Tanzania.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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`, `TZS`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `TZS`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `TAPBTZTZ`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `003003005283350001`
### 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.
# Thailand
Source: https://docs.withacclaim.com/guides/disburse/countries/thailand
Payout methods, timing, transaction limits, and required fields for payouts to Thailand.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `KASITHBK`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 7 and 19 characters (inclusive).
* Must match this regular expression: `^[0-9]{7,19}$`
**Example:** `2722365445`
### 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.
# Timor-Leste
Source: https://docs.withacclaim.com/guides/disburse/countries/timor-leste
Payout methods, timing, transaction limits, and required fields for payouts to Timor-Leste.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 23 characters.
* IBAN format; must match: `^TL[0-9]{2}[a-zA-Z0-9]{19}$`
**Example:** `TL380010012345678910106`
### 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.
# Togo
Source: https://docs.withacclaim.com/guides/disburse/countries/togo
Payout methods, timing, transaction limits, and required fields for payouts to Togo.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| ----------------------------- | ---------- | ----------------- |
| Central Africa Local Transfer | XOF | 2-3 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.
## Central Africa Local Transfer
Central Africa local bank transfer
### Supported currencies
`XOF`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 10,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `CentralAfricaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNSNX1`
#### Account Number
Account number (exactly 24 alphanumeric characters)
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[A-Za-z0-9]{24}$`
**Example:** `123456789012345678901234`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `UNTBTGTG`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Exactly 24 characters.
* Must match this regular expression: `^[0-9A-Za-z]{24}$`
**Example:** `012345678901234567890123`
### 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.
# Tonga
Source: https://docs.withacclaim.com/guides/disburse/countries/tonga
Payout methods, timing, transaction limits, and required fields for payouts to Tonga.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NRBTTONU`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `987654321001`
### 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.
# Trinidad & Tobago
Source: https://docs.withacclaim.com/guides/disburse/countries/trinidad-tobago
Payout methods, timing, transaction limits, and required fields for payouts to Trinidad & Tobago.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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`, `TTD`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `TTD`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CBTTTTPS`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012`
### 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.
# Tunisia
Source: https://docs.withacclaim.com/guides/disburse/countries/tunisia
Payout methods, timing, transaction limits, and required fields for payouts to Tunisia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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`, `TND`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TND`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 24 characters.
* IBAN format; must match: `^TN[0-9]{2}[a-zA-Z0-9]{20}$`
**Example:** `TN5910006035183598478831`
### 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.
# Türkiye
Source: https://docs.withacclaim.com/guides/disburse/countries/turkiye
Payout methods, timing, transaction limits, and required fields for payouts to Türkiye.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| FAST/EFT | TRY | 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.
## FAST/EFT
Turkey FAST/EFT payment system
### Supported currencies
`TRY`
### 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 | 1 TRY |
| Maximum | 250,000 TRY |
### Fields
#### Payout Method Type
**Value:** `TurkeyFastEft`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 26 characters.
* IBAN format; must match: `^TR[0-9]{2}[A-Z0-9]{4}[0-9]{1}[A-Z0-9]{3}[0-9]{14}$`
**Example:** `TR330006100519786457841326`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 26 characters.
* IBAN format; must match: `^TR[0-9]{2}[a-zA-Z0-9]{22}$`
**Example:** `TR760001000519786457841326`
### 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.
# Turks & Caicos Islands
Source: https://docs.withacclaim.com/guides/disburse/countries/turks-caicos-islands
Payout methods, timing, transaction limits, and required fields for payouts to Turks & Caicos Islands.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `BIBTTCG1`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `100123456789`
### 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.
# Tuvalu
Source: https://docs.withacclaim.com/guides/disburse/countries/tuvalu
Payout methods, timing, transaction limits, and required fields for payouts to Tuvalu.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NABTTVTV`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `12345678`
### 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.
# Uganda
Source: https://docs.withacclaim.com/guides/disburse/countries/uganda
Payout methods, timing, transaction limits, and required fields for payouts to Uganda.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `UGPBUGKAXXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Ukraine
Source: https://docs.withacclaim.com/guides/disburse/countries/ukraine
Payout methods, timing, transaction limits, and required fields for payouts to Ukraine.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `RADAUA2N`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `26003053821700`
### 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.
# United Arab Emirates
Source: https://docs.withacclaim.com/guides/disburse/countries/united-arab-emirates
Payout methods, timing, transaction limits, and required fields for payouts to United Arab Emirates.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| UAEFTS | AED | 2-3 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.
## UAEFTS
United Arab Emirates UAEFTS payment system
### Supported currencies
`AED`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `UnitedArabEmiratesUaefts`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 23 characters.
* IBAN format; must match: `^AE[0-9]{2}[0-9]{3}[0-9]{16}$`
**Example:** `AE070331234567890123456`
## International Wire Transfer
International wire transfer via SWIFT network
### Supported currencies
`AED`, `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
**Value:** `SwiftInternational`
#### Currency
**Value:** One of `AED`, `AUD`, `CAD`, `CHF`, `CNY`, `CZK`, `DKK`, `EUR`, `GBP`, `HKD`, `HUF`, `ILS`, `JPY`, `NOK`, `NZD`, `PLN`, `RON`, `SEK`, `SGD`, `THB`, `TRY`, `USD`, `ZAR`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 23 characters.
* IBAN format; must match: `^AE[0-9]{2}[a-zA-Z0-9]{19}$`
**Example:** `AE070331234567890123456`
### 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.
# United Kingdom
Source: https://docs.withacclaim.com/guides/disburse/countries/united-kingdom
Payout methods, timing, transaction limits, and required fields for payouts to United Kingdom.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Faster Payments | GBP | 0-1 business days |
| CHAPS | GBP | 0-1 business days |
| SEPA | EUR | 0-2 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.
## Faster Payments
UK real-time payment system
### Supported currencies
`GBP`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ------------- |
| Minimum | None |
| Maximum | 1,000,000 GBP |
### Fields
#### Payout Method Type
**Value:** `UnitedKingdomFps`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Sort Code
6-digit sort code in XX-XX-XX format
**Validation:**
* At most 8 characters.
* Must match this regular expression: `^(?:[0-9]{6}|[0-9]{2}-[0-9]{2}-[0-9]{2})$`
**Example:** `20-27-41`
#### Routing Type
**Value:** `sort_code`
#### Account Number
**Validation:**
* Between 6 and 8 characters (inclusive).
* Must match this regular expression: `^[0-9]{6,8}$`
* `modulus_check`
**Example:** `12345678`
## CHAPS
CHAPS same-day payment system for high-value UK transfers
### Supported currencies
`GBP`
### 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
**Value:** `UnitedKingdomChaps`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Sort Code
6-digit sort code in XX-XX-XX format
**Validation:**
* At most 8 characters.
* Must match this regular expression: `^(?:[0-9]{6}|[0-9]{2}-[0-9]{2}-[0-9]{2})$`
**Example:** `20-27-41`
#### Routing Type
**Value:** `sort_code`
#### Account Number
8-digit UK bank account number
**Validation:**
* Exactly 8 characters.
* Must match this regular expression: `^[0-9]{8}$`
* `modulus_check`
**Example:** `12345678`
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^GB[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `GB92CHAS60924250001121`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^GB[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `GB92CHAS60924250001121`
### 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.
# United States
Source: https://docs.withacclaim.com/guides/disburse/countries/united-states
Payout methods, timing, transaction limits, and required fields for payouts to United States.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| FedNow | USD | 0-1 business days |
| ACH | USD | 0-2 business days |
| Wire Transfer | USD | 0-1 business days |
| International Wire Transfer | See below | 0-3 business days |
| Paper Check | USD | 2-6 business days |
Please refer to the sections below for the key required fields and other considerations for each supported method.
## FedNow
FedNow instant payment service for same-day domestic US payments
### Supported currencies
`USD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Same day |
| Typical delivery | 0-1 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----------- |
| Minimum | None |
| Maximum | 500,000 USD |
### Fields
#### Payout Method Type
**Value:** `UnitedStatesFednow`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### ABA Routing Number
9-digit FedNow routing number to identify a bank in the United States
**Validation:**
* Exactly 9 characters.
* Must match this regular expression: `^[0-9]{9}$`
* `routing_number`
**Example:** `021000021`
#### Routing Type
**Value:** `aba`
#### Account Number
Your bank account number (up to 50 alphanumeric characters)
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
## ACH
Automated Clearing House transfer for domestic US payments
### Supported currencies
`USD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----------------- |
| Minimum | None |
| Maximum | 99,999,999.99 USD |
### Fields
#### Payout Method Type
**Value:** `UnitedStatesAch`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### ABA Routing Number
9-digit number found on the bottom of your check
**Validation:**
* Exactly 9 characters.
* Must match this regular expression: `^[0-9]{9}$`
* `routing_number`
**Example:** `021000021`
#### Routing Type
**Value:** `aba`
#### Account Number
Your bank account number
**Validation:**
* Between 4 and 17 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{4,17}$`
**Example:** `1234567890`
#### Account Type
**Value:** One of `checking`, `savings`
## Wire Transfer
Domestic wire transfer for same-day US payments
### Supported currencies
`USD`
### 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
**Value:** `UnitedStatesFedwire`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### ABA Routing Number
9-digit routing number to identify a bank in the United States
**Validation:**
* Exactly 9 characters.
* Must match this regular expression: `^[0-9]{9}$`
* `routing_number`
**Example:** `021000021`
#### Routing Type
**Value:** `aba`
#### Account Number
Your bank account number (up to 26 digits)
**Validation:**
* Between 1 and 26 characters (inclusive).
* Must match this regular expression: `^[0-9]{1,26}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `CHASUS33`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 26 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,26}$`
**Example:** `50001121`
### 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.
## Paper Check
Physical check mailed to your address
### Supported currencies
`USD`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-6 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | ----------------- |
| Minimum | None |
| Maximum | 99,999,999.99 USD |
### Fields
#### Payout Method Type
**Value:** `PaperCheck`
### Notes
* We monitor each check until it is cashed or voided.
* If a check is not cashed within 90 days, it is cancelled and the payout is reversed. The funds return to your Acclaim balance.
# Uruguay
Source: https://docs.withacclaim.com/guides/disburse/countries/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
**Value:** `UruguaySpi`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Routing Type
**Value:** `bank_code`
#### Bank Code
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`
#### Routing Type 2
**Value:** `branch_code`
#### Branch Code
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`
#### Account Number
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`
#### Account Type
**Value:** One of `checking`, `savings`
Type of bank account
#### Tax ID Type
**Conditional:** Required for Company payees only.
**Value:** `BUSINESS_REGISTRATION_NUMBER`
#### RUT (Business Tax ID)
**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`
#### Tax ID Type
**Conditional:** Required for Individual payees only.
**Value:** `NATIONAL_ID`
#### CI Number
**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`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `1234567890`
### 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.
# Uzbekistan
Source: https://docs.withacclaim.com/guides/disburse/countries/uzbekistan
Payout methods, timing, transaction limits, and required fields for payouts to Uzbekistan.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `RVBKUZ22XXX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Vanuatu
Source: https://docs.withacclaim.com/guides/disburse/countries/vanuatu
Payout methods, timing, transaction limits, and required fields for payouts to Vanuatu.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `NBOVVUVU`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Vatican City
Source: https://docs.withacclaim.com/guides/disburse/countries/vatican-city
Payout methods, timing, transaction limits, and required fields for payouts to Vatican City.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| SEPA | EUR | 0-2 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.
## SEPA
Single Euro Payments Area transfer
### Supported currencies
`EUR`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 0-2 business days |
| Business day dependency | Yes |
| Supports instant | Yes |
### Transaction limits
| Limit type | Value |
| ---------- | ----- |
| Minimum | None |
| Maximum | None |
### Fields
#### Payout Method Type
**Value:** `EuropeanUnionSepa`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^VA[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `VA29001000000000000000`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 22 characters.
* IBAN format; must match: `^VA[0-9]{2}[a-zA-Z0-9]{18}$`
**Example:** `VA59001123000012345678`
### 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.
# Vietnam
Source: https://docs.withacclaim.com/guides/disburse/countries/vietnam
Payout methods, timing, transaction limits, and required fields for payouts to Vietnam.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| NAPAS | VND | 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.
## NAPAS
Viet Nam NAPAS payment system
### Supported currencies
`VND`
### 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 | 10,000 VND |
| Maximum | 499,999,999 VND |
### Fields
#### Payout Method Type
**Value:** `VietnamNapas`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
8 or 11 character SWIFT/BIC 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:** `BFTVVNVX`
#### Account Number
Account number (up to 20 alphanumeric characters)
**Validation:**
* Between 1 and 20 characters (inclusive).
* Must match this regular expression: `^[A-Z0-9]{1,20}$`
**Example:** `12345678901234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `SBITVNVX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 20 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,20}$`
**Example:** `12750852`
### 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.
# Wallis & Futuna
Source: https://docs.withacclaim.com/guides/disburse/countries/wallis-futuna
Payout methods, timing, transaction limits, and required fields for payouts to Wallis & Futuna.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### IBAN
**Validation:**
* Exactly 27 characters.
* IBAN format; must match: `^FR[0-9]{2}[a-zA-Z0-9]{23}$`
**Example:** `FR7630006000011234567890189`
### 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.
# Zambia
Source: https://docs.withacclaim.com/guides/disburse/countries/zambia
Payout methods, timing, transaction limits, and required fields for payouts to Zambia.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| Zambia Local Transfer | ZMW | 2-3 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.
## Zambia Local Transfer
Zambian local bank transfer
### Supported currencies
`ZMW`
### Timing
| Attribute | Value |
| ----------------------- | ----------------- |
| Processing window | Business days |
| Typical delivery | 2-3 business days |
| Business day dependency | Yes |
| Supports instant | No |
### Transaction limits
| Limit type | Value |
| ---------- | -------------- |
| Minimum | None |
| Maximum | 50,000,000 USD |
### Fields
#### Payout Method Type
**Value:** `ZambiaLocal`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### SWIFT/BIC Code
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:** `FIRNZMX1`
#### Account Number
Account number (up to 35 alphanumeric characters)
**Validation:**
* Between 1 and 35 characters (inclusive).
* Must match this regular expression: `^[A-Za-z0-9]{1,35}$`
**Example:** `1234567890`
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `SBICZMLX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789012345`
### 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.
# Zimbabwe
Source: https://docs.withacclaim.com/guides/disburse/countries/zimbabwe
Payout methods, timing, transaction limits, and required fields for payouts to Zimbabwe.
## Supported payout methods
| Payout method | Currencies | Typical timing |
| --------------------------- | ---------- | ----------------- |
| 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.
## 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
**Value:** `SwiftInternational`
#### Currency
**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`
#### Account Holder Name
Name on the bank account
**Validation:**
* At most 200 characters.
#### Recipient Bank SWIFT/BIC Code
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:** `SCBLZWHX`
#### Routing Type
**Value:** `bic`
#### Intermediary Bank SWIFT/BIC
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`
#### Account Number
**Validation:**
* Between 1 and 50 characters (inclusive).
* Must match this regular expression: `^[0-9A-Za-z]{1,50}$`
**Example:** `123456789`
### 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.
# Failures and reversals
Source: https://docs.withacclaim.com/guides/disburse/failures-and-reversals
Understand why payouts fail, how failure codes help you diagnose issues, and how Acclaim returns funds when a payout cannot be completed.
Not all payouts complete successfully. When a payout fails, it reaches the **Failed** final state, Acclaim returns the funds to your treasury account, and you receive a specific `failure_code` and message explaining why.
This guide covers what happens when a payout fails, the available failure codes, how returned funds are handled, and how to retry safely.
For status transitions and lifecycle context, see [Payout lifecycle](/guides/disburse/payout-lifecycle).
***
## When a payout fails
A payout fails after processing begins and Acclaim cannot complete delivery.
At that point:
* The payout moves to the final **Failed** state and will not be sent
* Acclaim includes a `failure_code` and matching message on the payout
* Funds are returned to the treasury account that funded the payout
* You can review the failure in the **Console** or through webhooks and the API
Fund return is part of every failed payout, not a separate outcome that applies only in some cases.
***
## Failure codes
When a payout fails, Acclaim includes a `failure_code` and matching message. All API codes use the `payout.*` format.
The groups below describe what each failure means in plain language, with the exact code shown for reference.
### Beneficiary account
* **Account closed** — The beneficiary account is closed and cannot receive funds.\
Code: `payout.beneficiary_account_closed`
* **Invalid account** — The beneficiary account details are invalid.\
Code: `payout.invalid_beneficiary_account`
* **Account not found** — The beneficiary account could not be found.\
Code: `payout.beneficiary_account_not_found`
* **Account inactive** — The beneficiary account is inactive and cannot receive funds.\
Code: `payout.beneficiary_account_inactive`
* **Account restricted** — The beneficiary account is restricted and cannot receive funds.\
Code: `payout.beneficiary_account_restricted`
### Amount and currency
* **Insufficient balance** — There are insufficient funds available to complete the payout.\
Code: `payout.insufficient_balance`
* **Invalid amount** — The payout amount is invalid.\
Code: `payout.amount_invalid`
* **Currency not supported** — The selected currency is not supported for this payout.\
Code: `payout.currency_not_supported`
* **Account currency mismatch** — The beneficiary account does not support the selected payout currency.\
Code: `payout.account_currency_mismatch`
### Bank details
* **Invalid bank information** — The bank account information provided is invalid or incomplete.\
Code: `payout.invalid_bank_information`
* **Invalid routing number** — The routing number provided is invalid.\
Code: `payout.invalid_routing_number`
* **Invalid IBAN** — The IBAN provided is invalid.\
Code: `payout.invalid_iban`
* **Invalid beneficiary name** — The beneficiary name provided is invalid or does not match the account details.\
Code: `payout.invalid_beneficiary_name`
### Compliance
* **Sanctions blocked** — The payout could not be completed due to sanctions restrictions.\
Code: `payout.sanctions_blocked`
* **Compliance blocked** — The payout could not be completed due to compliance requirements.\
Code: `payout.compliance_blocked`
* **Purpose of payment rejected** — The purpose of payment is not valid for this payout.\
Code: `payout.purpose_of_payment_rejected`
### Processing
* **Cutoff missed** — The payout missed the processing cutoff time and could not be completed.\
Code: `payout.cutoff_missed`
* **Duplicate payout** — A duplicate payout was detected and was not processed.\
Code: `payout.duplicate_payout`
* **Bank returned payout** — The beneficiary's bank returned the payout.\
Code: `payout.beneficiary_bank_returned`
* **Recall requested** — A recall was requested for this payout.\
Code: `payout.recall_requested`
* **Processor unavailable** — The payout processor is temporarily unavailable. Please try again later.\
Code: `payout.processor_unavailable`
* **Processor failure** — The payout could not be completed due to a processing error.\
Code: `payout.processor_failure`
* **Unknown failure** — The payout could not be completed for an unknown reason.\
Code: `payout.unknown_failure`
***
## Returned funds
When a payout fails, Acclaim returns the funds to the treasury account that funded the payout. The payout remains in **Failed**, and a treasury transaction records the return when applicable.
Timing depends on the payout method and external network, but the return is automatic. You do not need to request it separately.
### Cross-border and FX payouts
For cross-border payouts, currency conversion may occur before delivery. If the payout fails after FX has already run:
* The returned amount is in the **payment currency**
* Funds are **not automatically converted back** to the original funding currency
* The original FX transaction has already been completed
If the payment currency cannot be held in your treasury account balance, Acclaim automatically converts returned funds back to the funding currency when the payout fails.
You can then:
1. **Retry using the returned funds** — create a new payout funded with the returned payment-currency balance
2. **Convert back to the original currency** — perform a new FX conversion if you need funds in the original funding currency
***
## Retrying failed payouts
After funds are returned and the underlying issue is fixed, you can send the payout again.
Best practice:
1. Review the `failure_code` and message
2. Correct the issue, such as payee details or payout method
3. Create a new payout once funds are available again
Avoid retrying without changes. The same issue is likely to cause another failure.
***
## Monitoring and alerts
To respond quickly to failed payouts:
* Monitor payouts in the **Console**
* Track status changes via **webhooks**
* Set up internal alerts for **Failed** payouts
For webhook and API handling details, see [Failed payouts](/developers/failed-payouts).
***
## Summary
* **Failed** is a final state reached when a payout cannot be completed after processing begins
* Every failed payout returns funds to the treasury account that funded it
* Use `failure_code` and the matching message to diagnose the issue; see [Failure codes](#failure-codes) above
* FX payouts may return funds in the payment currency; currencies that cannot be held in your treasury account are converted back to the funding currency automatically
* Most failures can be resolved and retried after correcting the issue
# Error handling
Source: https://docs.withacclaim.com/guides/disburse/file-uploads/errors
File-level vs row-level errors, what details you get, and how to fix and re-upload safely.
When an upload cannot be fully processed, Acclaim returns errors so you can see **what failed** and **where**. Errors may apply to the whole file or to individual rows.
## Error types
### File-level errors
These stop the upload from being processed at all. Examples:
* Unsupported file type
* Missing or invalid header row
* Template does not match the file
* Required columns missing after mapping
* Unreadable or malformed file
When a file-level error occurs, **reject the whole upload**, fix the file or template, and upload again.
### Row-level errors
These affect **one row** while other rows can still succeed. Examples:
* Missing required field
* Invalid amount format
* Unsupported currency for the method
* Invalid bank details
* Payout method mismatch
* Country-specific validation failure
## Error reporting
You should receive enough detail to correct data quickly, typically including:
* Upload or file identifier
* **Row number**
* **Field** name (when applicable)
* Error code or type
* Human-readable message
Exact fields depend on the Console or API surface you use—align support training with what your team actually sees.
## Common file-level errors
| Error | What it means |
| ------------------------ | ----------------------------------------- |
| Unsupported file type | Not a supported CSV or XLSX |
| Missing headers | No valid header row |
| Invalid template | Template does not match columns or method |
| Missing required columns | One or more required columns are absent |
## Common row-level errors
| Error | What it means |
| ----------------------------------- | ------------------------------------------ |
| Missing required field | Required value blank or absent |
| Invalid format | Value does not match expected pattern |
| Invalid payout method data | Method-specific fields missing or wrong |
| Country-specific validation failure | Fails country or corridor rules |
| Invalid conditional field set | Wrong combination for payee type or method |
## Example row-level errors
| Row | Field | Error |
| --- | --------------------- | ----------------------------------------------- |
| 4 | `bank_account.clabe` | Must be exactly 18 digits |
| 7 | `currency` | Unsupported currency for selected payout method |
| 12 | `payee.business_name` | Required when `payee.type` is `business` |
## Partial success
Uploads often finish with **partial success**: many rows succeed, a few fail. In that case:
* Valid rows continue to payout creation.
* Failed rows are listed with errors.
* You fix only the failed rows (or the file structure) and re-upload as needed.
Do not re-upload successful rows unless your process explicitly requires it—duplicates can create duplicate payouts depending on your safeguards.
## Correcting errors
Open the error report for the upload and note **row** and **field** for each failure.
Fix the spreadsheet or export (or adjust the template if mapping was wrong).
Upload a **new** file containing only corrected rows, or a full file if that is your standard control.
Keep templates stable and validate files internally before upload during high-stakes windows (month-end, regulatory deadlines).
## Related resources
* [File uploads overview](./overview)
* [File format](./file-format)
* [Template configuration](./template-configuration)
* [Validation rules](./validation)
* [Processing flow](./processing)
* [Examples](./examples)
# Examples
Source: https://docs.withacclaim.com/guides/disburse/file-uploads/examples
Sample CSV rows and layouts—plus common mistakes to avoid when building payout files.
Use these examples as **templates** when you build your own files. Always confirm column names and required fields against your **template** and the [supported payout countries](/guides/disburse/countries/index) pages for the destination.
## CSV example
```csv theme={null}
payee.type,payee.first_name,payee.last_name,bank_account.account_holder_name,bank_account.account_number,bank_account.swift_code,amount,currency
individual,Ana,García,Ana García,1234567890,BNMXMXMM,1500,USD
individual,John,Smith,John Smith,9876543210,BOFAUS3N,2500,USD
```
## Same data in a table (Excel-style columns)
If you build the sheet in Excel, use one column per header below:
| payee.type | payee.first\_name | payee.last\_name | bank\_account.account\_holder\_name | bank\_account.account\_number | bank\_account.swift\_code | amount | currency |
| ---------- | ----------------- | ---------------- | ----------------------------------- | ----------------------------- | ------------------------- | ------ | -------- |
| individual | Ana | García | Ana García | 1234567890 | BNMXMXMM | 1500 | USD |
| individual | John | Smith | John Smith | 9876543210 | BOFAUS3N | 2500 | USD |
Save as `.xlsx` with **row 1 = headers** and **row 2+ = data**, matching your template.
## Business payout example
```csv theme={null}
payee.type,payee.business_name,bank_account.account_holder_name,bank_account.account_number,bank_account.swift_code,amount,currency
business,Acme Inc,Acme Inc,1234567890,BOFAUS3N,10000,USD
```
## Mexico SPEI example (CLABE)
```csv theme={null}
payee.type,payee.first_name,payee.last_name,bank_account.account_holder_name,bank_account.clabe,amount,currency
individual,Ana,García,Ana García,032180000118359719,5000,MXN
```
## Common mistakes
### Missing required fields
```csv theme={null}
amount,currency
1000,USD
```
Without payee and bank details, validation fails. Include every column your template marks as required.
### Invalid formats
```csv theme={null}
amount,currency
$1000,USD
```
Do not include currency symbols in the **amount** cell.
### Incorrect field names
```csv theme={null}
firstname,lastname,amount,currency
```
Headers must match expected identifiers (for example `payee.first_name`), not informal labels—unless your **template** maps informal names to Acclaim fields.
Start with **1–5 rows**, confirm success in the Console, then scale to full batches.
## Related resources
* [File uploads overview](./overview)
* [File format](./file-format)
* [Template configuration](./template-configuration)
* [Validation rules](./validation)
* [Processing flow](./processing)
* [Error handling](./errors)
# File format
Source: https://docs.withacclaim.com/guides/disburse/file-uploads/file-format
Structure, columns, and required fields for CSV and Excel payout uploads.
Your upload must follow a defined structure with specific columns and formatting rules. Acclaim supports **CSV** and **Excel** (`.xlsx`); both follow the same logical schema.
## Supported file types
* CSV (`.csv`)
* Excel (`.xlsx`)
## File structure
Each **row** is one payout. A typical row includes:
* Payee information
* Bank or payout-method details
* Amount and currency
* Optional metadata your template allows
## Header row
The first row must be **headers** that map to Acclaim fields (directly or via your template). Example:
```csv theme={null}
payee.type,payee.first_name,payee.last_name,bank_account.account_number,bank_account.swift_code,amount,currency
```
## Column naming
Column names should match Acclaim field identifiers. Use **dot notation** for nested fields:
* `payee.first_name`
* `bank_account.account_number`
* `beneficiary.address.country`
## Required vs optional fields
What is required depends on:
* Payout method
* Destination country
* Payee type (individual or business)
Use the [supported payout countries](/guides/disburse/countries/index) index and each country’s page for method-specific fields and limits.
## Common fields
| Field | Description |
| ---------------------------------- | -------------------------------------------------------- |
| `amount` | Payout amount (numeric; no currency symbols in the cell) |
| `currency` | ISO 4217 currency code |
| `payee.type` | `individual` or `business` |
| `bank_account.account_holder_name` | Name on the account |
## Payee fields
**Individual**
* `payee.first_name`
* `payee.last_name`
**Business**
* `payee.business_name`
## Bank account fields
| Field | Description |
| ----------------------------- | -------------------- |
| `bank_account.account_number` | Local account number |
| `bank_account.swift_code` | SWIFT/BIC |
| `bank_account.iban` | IBAN where supported |
| `bank_account.clabe` | CLABE (Mexico) |
## Data formatting rules
**Currency**
* Valid ISO 4217 code (for example `USD`, `EUR`, `MXN`).
**Amount**
* Numeric only; no currency symbols (for example `1000.50`).
**Strings**
* Trim leading and trailing whitespace.
* Avoid extra special characters unless the field requires them.
**Dates**
* ISO format: `YYYY-MM-DD`.
## Example file
```csv theme={null}
payee.type,payee.first_name,payee.last_name,bank_account.account_holder_name,bank_account.account_number,bank_account.swift_code,amount,currency
individual,Ana,García,Ana García,1234567890,BNMXMXMM,1500,USD
```
Keep column order stable across files so operations teams and templates stay aligned.
## Next steps
* [Template configuration](./template-configuration)
* [Validation rules](./validation)
* [Processing flow](./processing)
* [Error handling](./errors)
* [Examples](./examples)
# File uploads
Source: https://docs.withacclaim.com/guides/disburse/file-uploads/overview
Create payouts in bulk by uploading structured CSV or Excel files—without a full API integration.
File uploads let you create and process **payouts in bulk** by uploading structured files such as CSV or Excel. For many teams, this is the fastest way to send large volumes of payouts without building a full API-based integration.
## When to use file uploads
Use file uploads when:
* You need to send payouts in bulk.
* Your payout data comes from spreadsheets or internal exports.
* You want to go live quickly without a full API integration.
* Operations or finance owns payout execution.
Use the **API** when:
* Payouts are triggered programmatically in real time.
* You need dynamic or event-driven workflows.
* You want tight system-to-system integration.
## How it works
You upload a file (CSV or Excel) in the Acclaim Console.
Acclaim validates the file structure and data against your **template**.
Each row is parsed into payout and payee data.
Valid rows are processed into payouts.
Invalid rows are rejected with row-level errors you can fix and re-upload.
This process is **asynchronous**. Large files may take time to finish.
Do not assume payouts are final until you confirm **processing** and **payout status** in the Console or your usual monitoring workflow.
## Supported file types
* CSV (`.csv`)
* Excel (`.xlsx`)
Files must follow a defined structure and include the fields required for each payout method. Country and method requirements are listed on the [supported payout countries](/guides/disburse/countries/index) pages.
## Key concepts
### Templates
Templates define how your file is interpreted:
* Required columns and how they map to Acclaim fields.
* Payout method configuration.
Each upload is validated against a template. See [Template configuration](./template-configuration).
### Validation
Before processing, Acclaim checks that:
* Required fields are present.
* Formats are correct.
* Payout method and country rules are satisfied.
Errors are reported at the **row** level when possible. See [Validation rules](./validation).
### Processing
After validation, valid rows become payouts and move through execution. You can track status in the Console. See [Processing flow](./processing).
# Processing flow
Source: https://docs.withacclaim.com/guides/disburse/file-uploads/processing
From upload to completed payouts—async processing, partial success, and how to track status.
After a file passes validation, Acclaim **processes** it asynchronously: rows become payees and payouts, then payouts move through execution. This page is the operational view of that pipeline.
## Overview
The flow has these stages:
1. File upload
2. Validation
3. Row processing
4. Payout creation
5. Execution and completion
## Step 1: File upload
You upload the file through the Acclaim Console and select the correct **template**.
At this stage:
* The file is received and stored for processing.
* The chosen template is applied.
* Work is queued **asynchronously**—the UI may return before all rows finish.
## Step 2: Validation
The system runs:
* **File-level** validation (structure, headers, mapping).
* **Row-level** validation (fields, formats, method rules).
Results:
* Valid rows continue.
* Invalid rows are rejected with errors you can use to fix the file.
## Step 3: Row processing
Each valid row is transformed into:
* Payee data (create or update as your setup allows).
* A payout instruction with amount, currency, and destination details.
This step includes mapping fields, applying defaults from the template, and normalizing values.
## Step 4: Payout creation
For each successful row:
* A **payout** is created.
* It is queued for execution on the appropriate rail.
You can track payout records and statuses in the Console.
## Step 5: Execution
Payouts execute according to:
* Payout method and corridor.
* Processing windows and banking cutoffs.
Statuses typically progress through stages such as pending, processing, completed, or failed—use the Console as the source of truth for wording in your org.
Large files take longer. Plan communications and cutoffs so finance and operations know **processing is not instantaneous**.
## Tracking progress
You can monitor:
* **Upload / job** status at the file level.
* **Row** outcomes (success vs error).
* **Payout** status for each created payout.
## Partial success
Mixed results are normal:
* Some rows succeed and become payouts.
* Others fail validation or later processing steps.
Failures on one row **do not** roll back successful rows in the same upload (unless product behavior states otherwise—confirm for your tenant if needed).
## Reprocessing failed rows
For failed rows you should:
* Fix the data using the reported errors.
* Re-upload **only** the corrected rows in a new file when that fits your process.
You do not need to re-upload rows that already succeeded.
Smaller batches give faster feedback when you are tuning templates or onboarding a new corridor.
## Next steps
* [Error handling](./errors)
* [Examples](./examples)
* [Validation rules](./validation)
* [File format](./file-format)
# Template configuration
Source: https://docs.withacclaim.com/guides/disburse/file-uploads/template-configuration
Configure import templates with JSON to map CSV or Excel columns to Acclaim entities.
**Import templates** define how your CSV or Excel file is translated into structured data in Acclaim. You configure them with **JSON**. They control how columns map to entity fields, which rows are processed, validation behavior, and default values.
## Template structure
A template includes:
| Field | Description |
| -------------------- | ---------------------------------------------------- |
| Name | Descriptive template name |
| Object type | Entity being imported (Payee, Payout, Payout method) |
| Header row index | Row containing column headers (0-based) |
| Data start row index | Row where data begins (0-based) |
| Columns | JSON array of column mappings |
## Columns configuration
Each column mapping defines how a file column maps to a field.
### Properties
| Property | Required | Description |
| -------------- | -------- | ------------------------------ |
| `propertyPath` | Yes | Field to map to |
| `headerName` | No | Column name (case-insensitive) |
| `columnIndex` | No | Column position (0-based) |
| `required` | No | Skip row if empty |
| `defaultValue` | No | Fallback value |
If both `headerName` and `columnIndex` are provided, **`columnIndex` takes precedence**.
## Basic example
```json theme={null}
[
{
"propertyPath": "given_name",
"headerName": "First Name",
"required": true
},
{
"propertyPath": "family_name",
"headerName": "Last Name",
"required": true
}
]
```
## Using column index
```json theme={null}
[
{
"propertyPath": "given_name",
"columnIndex": 0,
"required": true
},
{
"propertyPath": "family_name",
"columnIndex": 1,
"required": true
}
]
```
## Default values
```json theme={null}
{
"propertyPath": "company",
"headerName": "Company",
"defaultValue": "Individual"
}
```
## Row configuration
### Header row
Defines where headers are located. Example:
```
headerRowIndex: 0
```
### Data start row
Defines where data begins. Example:
```
dataStartRowIndex: 1
```
## Object types
Each template targets one **object type**: **Payee**, **Payout**, or **Payout method**. That choice controls which `propertyPath` values are valid for column mappings.
## Available parameters
The lists below are generated from `data/importTemplateObjectFields.json` in this repository. Run `npx tsx scripts/generate-import-template-field-docs.ts` after you edit the JSON.
### Payee
Use when the template creates or updates **payee** records. Payout upload rows often use dot paths such as `payee.first_name` instead; see [File format](/guides/disburse/file-uploads/file-format) for that layout.
Given or first name for the payee when you map a single column to this field.
Family or last name for the payee when you map a single column to this field.
Email address for the payee, if your import uses it.
Phone number for the payee, if your import uses it.
Company or organization name when the payee is a business, or a default label such as Individual when you use `defaultValue` in the column mapping.
### Payout
Use when each row represents a **payout**. Required fields depend on payee type, payout method, and destination; see [File format](/guides/disburse/file-uploads/file-format) and [Validation rules](/guides/disburse/file-uploads/validation).
Identifier or external reference that ties the row to a payee, per your template and environment.
Identifier for the treasury account Acclaim should debit when funding this payout.
Your reference or memo for reconciliation and support.
Payout amount as a numeric value without currency symbols in the cell.
ISO 4217 currency code for the payout (for example USD, EUR, MXN).
Alternative column name some templates use for the payout currency; align with `currency` if both appear in your file.
Payout method identifier or selector for the row, when your template separates method choice from bank details.
### Payout method
Use when the template maps **bank or rail identifiers** and related attributes. Exact required fields depend on the method and country; use [Supported payout countries](/guides/disburse/countries) for method-specific requirements.
Method or rail code for the payout (for example values listed on destination country pages).
Name on the account for the payout method.
Local account number where the rail requires it.
SWIFT or BIC code for international transfers where supported.
IBAN where the destination rail uses it.
18-digit CLABE for Mexico where that rail applies.
Country for the beneficiary when your template or rail requires address context.
## Validation behavior
When you process a file against a template, typical outcomes include:
| Situation | Result |
| ----------------------- | --------------------------------------------------------------- |
| Missing required fields | Row skipped (or handled per your template rules) |
| Invalid format | Row rejected |
| Mapping errors | Incorrect or incomplete data—fix the template before large runs |
Prefer **header names** over raw column indexes when possible so files stay readable if columns shift slightly. Test with a **small file** before bulk uploads.
## Best practices
* Use header names instead of indexes when you can.
* Mark required fields explicitly.
* Test with small files first.
* Use defaults to reduce required columns.
## Related resources
* [File uploads overview](./overview)
* [File format](./file-format)
* [Validation rules](./validation)
* [Processing flow](./processing)
* [Error handling](./errors)
# Validation rules
Source: https://docs.withacclaim.com/guides/disburse/file-uploads/validation
How Acclaim validates uploaded files before creating payouts—file-level and row-level checks.
Before payouts are created, Acclaim validates the **file** and each **row**. That way you catch structural problems early and only valid rows consume processing capacity.
## What validation covers
* Required fields are present.
* Values match expected formats.
* Payout method requirements are satisfied.
* Country-specific rules pass.
## Validation stages
### 1. File-level validation
Acclaim checks the file itself:
* Type is supported (CSV or XLSX).
* Headers exist and match what the template expects.
* Required columns can be mapped.
If file-level validation fails, the **entire upload** is rejected—fix the file or template and upload again.
### 2. Row-level validation
Each row is validated **independently**:
* Required fields are populated.
* Formats are correct (amount, currency, bank identifiers, and so on).
* Conditional rules match (for example individual vs business).
Failed rows are rejected **without** blocking other valid rows in the same file.
## Required field validation
Fields marked required must be present and non-empty. Examples often include:
* `amount`
* `currency`
* `payee.type`
## Conditional validation
Some fields are required only in certain situations, for example:
* `payee.first_name` and `payee.last_name` for individuals.
* `payee.business_name` for businesses.
## Format validation
| Field | Rule |
| ------------------------- | ------------------------------ |
| `currency` | ISO 4217 code |
| `amount` | Numeric, no symbols |
| `bank_account.swift_code` | Valid SWIFT/BIC length/pattern |
| `bank_account.clabe` | 18 digits (Mexico CLABE) |
## Payout method validation
Each method has its own required fields (for example CLABE for certain Mexico rails, SWIFT fields for international). Your template ties the upload to that method so validation matches the rail.
## Country-specific validation
Countries can impose extra identifiers or formats. Always cross-check the destination on the [supported payout countries](/guides/disburse/countries/index) pages before large runs.
## Validation results
After validation:
* Valid rows move to **processing**.
* Invalid rows are **rejected** with per-row errors you can export or review in the Console.
## Common validation errors
* Missing required field
* Invalid format (amount, dates, bank IDs)
* Unsupported currency for the method
* Invalid bank details
* Conditional field mismatch (wrong set of fields for payee type)
Pilot new templates with a **small file** (a few rows) before month-end or high-volume batches.
## Next steps
* [Processing flow](./processing)
* [Error handling](./errors)
* [Examples](./examples)
* [Template configuration](./template-configuration)
# Disburse Overview
Source: https://docs.withacclaim.com/guides/disburse/overview
Send payouts globally with control over delivery, timing, and reconciliation. Orchestrate the full lifecycle of outgoing funds.
Send money with precision and control.
Acclaim’s disburse capabilities power payouts to **vendors, policyholders, claimants, and partners** across currencies and payment methods.
From collecting recipient details to confirming delivery, every payout is **tracked, configurable, and reconciled** in one place.
***
## How disburse works
Disburse is built around a simple lifecycle: **create**, **collect details**, **send**, and **track**.
1. **Create a payout**
Define the amount, currency, and recipient. Payouts can be created via API, file upload, or the Console.
2. **Collect recipient details (if needed)**
If required information is missing, Acclaim generates a **payout link** to securely collect and validate details.
3. **Send funds**
Once ready, funds are delivered via the selected **payout method** and currency.
4. **Track and reconcile**
Monitor status, receive webhooks, and access **receipts and remittance details** for reconciliation.
***
## Core concepts
### Payouts
A **payout** represents a transfer of funds to a recipient. It includes the **amount**, **currency**, **recipient**, and **delivery method**.
Payouts move through a lifecycle of statuses, from creation to completion or failure, and are fully traceable.
***
### Payout methods
Payout methods define **how funds are delivered**. Supported methods vary by country and currency.
Acclaim supports payouts across a wide range of regions. See **[supported countries](/guides/disburse/countries)** for full coverage and method availability.
Examples include:
* Bank transfers (local and international)
* Real-time payment networks
* Other region-specific methods
***
### Payout links
A **payout link** is a secure link sent to a recipient to collect required details.
Use payout links when:
* Recipient banking details are missing
* You want recipients to choose their preferred payout method
* You need to validate information before sending funds
Once completed, the payout proceeds automatically.
***
### FX and conversions
When sending cross-border payouts, Acclaim handles **currency conversion** with transparent rates and tracking.
You can control:
* Source and destination currencies
* FX timing and visibility
* Amounts delivered vs. amounts sent
***
### Tracking and status
Every payout includes **real-time status tracking** and event updates.
Track:
* Processing status
* Delivery confirmation
* Failures and retries
Webhooks provide programmatic updates for each stage of the payout lifecycle.
***
## Ways to send payouts
Choose the approach that fits your workflow:
* **API** — automate payout creation and orchestration
* **File uploads** — send payouts in bulk
* **Console** — manage and review payouts manually
***
## Reconciliation
All payouts include **structured data and reporting** to support reconciliation.
* Export payout data
* Match payouts to internal records
* Access receipts and remittance details
# Payees
Source: https://docs.withacclaim.com/guides/disburse/payees
Manage recipients, collect required details, and reuse payee information across payouts with validation and tracking built in.
**Payees are the recipients of funds.**
A payee represents the individual or business you are sending money to, including their **identity details**, **contact information**, and **payout methods**.
By creating and managing payees, you can **reuse recipient information**, reduce errors, and streamline payout workflows.
***
## Why use payees
Using payees allows you to:
* **Store recipient details once** and reuse them across payouts
* **Validate information upfront** to reduce failed payouts
* **Support multiple payout methods** per recipient
* **Track payout history** at the recipient level
***
## How payees work
Payees are flexible and can be created in multiple ways:
### Create directly
Create a payee via API, file upload, or the Console by providing required **identity and payout details**.
***
### Collect details with payout links
If you don’t have full recipient details, you can create a payout and let Acclaim generate a **payout link**.
The payee completes the link to:
* Provide banking or payout details
* Select a preferred payout method (if enabled)
* Validate required information
Once completed, the payee is created or updated automatically.
***
### Reuse across payouts
Once a payee exists, you can reference them in future payouts without re-entering details.
This is useful for:
* Vendors or partners paid repeatedly
* Policyholders receiving multiple disbursements
* High-volume payout workflows
***
## Payee details
A payee typically includes:
* **Name** (individual or business)
* **Contact information** (email, phone)
* **Country and currency context**
* **Payout methods** (bank account, local method, etc.)
Required fields vary depending on the **payout method** and **destination country**.
***
## Managing payout methods
A single payee can have **multiple payout methods**.
For example:
* A bank account for USD payouts
* A local payment method for another currency
You can:
* Add or update payout methods
* Set a default method
* Let the payee choose via payout link
***
## Validation and errors
Acclaim validates payee details based on **country and method requirements**.
This helps:
* Prevent failed payouts
* Ensure compliance with local banking formats
* Catch missing or invalid information early
If details are incomplete, payouts will remain in a **requires information** state until resolved.
***
## Updating payees
Payees can be updated at any time via API or the Console.
Changes may:
* Apply to future payouts
* Trigger re-validation of payout methods
* Require confirmation for certain fields
# Payout lifecycle
Source: https://docs.withacclaim.com/guides/disburse/payout-lifecycle
Understand how payouts move from creation to completion, including status transitions, required actions, and failure states.
Every payout moves through a defined lifecycle from **creation** to **completion**.
Statuses reflect the current state of the payout and whether **action is required**, **approval is pending**, or **funds are in motion**.
## Lifecycle overview
Payouts move through four phases:
1. **Requires action** — `RequiresPayeeInfo`, `RequiresPayoutMethod`
2. **Ready** — `NeedsApproval`, `ReadyToProcess`
3. **In progress** — `Processing`
4. **Final states** — `Succeeded`, `Failed`, `Canceled`
## Status definitions
### RequiresPayeeInfo
Action required
The payout is missing required recipient details.
This occurs when:
* Payee information is incomplete
* A payout link has been sent but not completed
How to resolve:
* Update the payee with required details
* Or complete the payout link
***
### RequiresPayoutMethod
Action required
The payout does not have a valid payout method selected.
This occurs when:
* No payout method is available for the payee
* Existing methods are incomplete or incompatible
How to resolve:
* Add or update a payout method
* Or collect details via a payout link
***
### NeedsApproval
Approval
The payout requires approval before it can be processed.
This is typically used for:
* Internal review workflows
* High-value or sensitive payouts
Once approved, the payout moves to **ReadyToProcess** or one of the action required statuses if information is missing.
***
### ReadyToProcess
Ready
All required information is complete and any approvals have been satisfied.
At this stage:
* The payout is fully validated
* It is eligible to be sent
The payout will move to **Processing** when execution begins.
***
### Processing
In progress
The payout has been submitted and is being processed through the selected payout method.
During this stage:
* Funds are in transit
* External payment networks may be involved
* Status updates occur asynchronously
No action is required while processing.
***
### Succeeded
Delivered
The payout has been completed and funds have been delivered to the recipient.
At this stage:
* Final status is confirmed
* Receipts and remittance details are available
* The payout is ready for reconciliation
***
### Failed
Failed
The payout could not be completed.
Common causes:
* Invalid or incorrect recipient details
* Rejection by the destination bank or network
* Compliance or processing issues
Next steps:
* Review the failure reason
* Correct any issues
* Retry the payout if appropriate
***
### Canceled
Canceled
The payout was canceled and will not be processed.
This can occur when:
* A user cancels the payout before processing
* A workflow or system action stops execution
Canceled payouts are final and will not be sent.
***
## State transitions
Payouts move forward as requirements are met and processing progresses.
Typical transitions include:
* **NeedsApproval** → **RequiresPayeeInfo** / **RequiresPayoutMethod** → **ReadyToProcess**
* **RequiresPayeeInfo** → **ReadyToProcess** (if details are completed directly)
* **ReadyToProcess** → **Processing** → **Succeeded**
* **Processing** → **Failed**
* **ReadyToProcess** → **Canceled**
Transitions are driven by:
* Data completeness
* Approval workflows
* Execution and external network responses
***
## Webhooks and status updates
Payout status changes are communicated via **webhooks**.
Use webhooks to:
* Track payout progress in real time
* Trigger internal workflows
* Handle failures and retries
Each status update corresponds to a lifecycle transition.
***
## Summary
* Payouts move through **clear phases** from required actions to final states
* **RequiresPayeeInfo** and **RequiresPayoutMethod** indicate missing data
* **NeedsApproval** introduces optional approval workflows
* **Processing** reflects funds in motion
* **Succeeded**, **Failed**, and **Canceled** are final states
Understanding the lifecycle helps you **build reliable workflows**, **handle edge cases**, and **maintain accurate reconciliation**.
# Payout links
Source: https://docs.withacclaim.com/guides/disburse/payout-links
Send payouts without collecting banking details upfront by letting recipients choose how they get paid.
**Payout links** let you pay someone without collecting their banking details up front. A payout link is a secure, branded URL you send to the recipient. They use it to:
* Enter payout details
* Choose how they want to be paid
* Claim the payment
Every payout in Acclaim can include a payout link when recipient input is needed.
## How payout links work
Payout links are tied to **payouts**. When a payout is created:
* A payout link is generated automatically.
* If information is still missing, the link is how the recipient supplies it.
* The recipient completes what is required.
* The payout moves forward once the link flow is complete.
Payout links work whether the payout came from the **API**, **file uploads**, or other supported workflows.
## Lifecycle and statuses
Payout links follow the payout lifecycle, with extra states when the recipient must provide information.
### Key statuses
| Status | Description |
| ---------------------- | ------------------------------------------------------- |
| `RequiresPayeeInfo` | Recipient identity or profile details are still missing |
| `RequiresPayoutMethod` | Payout method or destination details are still missing |
When the recipient finishes the link flow:
* Required information is collected.
* The payout leaves the `Requires_` states.
* Execution continues according to the rail and method, assuming all necessary approvals have been met.
## Recipient experience
Recipients get the link through the channels your organization enables, for example **email**, **SMS**, or **WhatsApp** (depending on account configuration).
When they open the link, they can typically:
* Enter required personal or business details
* Select a payout method
* Provide banking or wallet information
* Review the payout, including FX estimates when conversion applies
Validation runs in real time so issues are caught before submission.
## Security and authentication
You can require authentication before a recipient completes a link. Common options include:
* Email one-time passcode (OTP)
* SMS one-time passcode (OTP)
* Security questions
What applies is determined by your **account configuration** in the Acclaim Console.
## Notifications
Links can be sent automatically when a payout **needs recipient input** or **missing data** blocks execution.
Delivery may use **email**, **SMS**, **WhatsApp**, or other configured channels.
## After completion
After the payout is initiated or completes, the same link often becomes a **tracking** experience. Recipients may be able to:
* Track payout status
* View payment details
* Download receipts or remittance advice where available
Exact options depend on product configuration and corridor.
## FX and currency handling
If the payout involves currency conversion, recipients usually see **estimated exchange rates** and amounts in the relevant currencies so expectations are clear before they confirm.
## When to use payout links
Payout links work well when:
* You do not have recipient banking details yet.
* Recipients should pick method or destination (for example bank vs wallet).
* You want a low-friction experience without the recipient using your API.
### Common use cases
* Insurance claim payments to policyholders
* Provider or vendor payments
* Contractor or marketplace payouts
Align your support team on which **channels** (email, SMS, and so on) you use for links so recipients know what to expect.
## Related resources
* [Payout lifecycle](./payout-lifecycle)
* [Payees](./payees)
* [Payout methods](./payout-methods)
* [File uploads overview](./file-uploads/overview)
# Payout methods
Source: https://docs.withacclaim.com/guides/disburse/payout-methods
Understand how funds are delivered to recipients. Choose the right payout method based on country, currency, speed, and requirements.
Payout methods define how funds are delivered to a payee.
They determine the **banking details required**, **delivery speed**, and **supported currencies and countries**.
Choosing the right payout method ensures payouts are **delivered successfully**, **on time**, and with the expected experience for the recipient.
***
## How payout methods work
Each payout is sent using a specific payout method based on:
* **Destination country**
* **Currency**
* **Available payment rails**
* **Recipient details**
Available methods vary by region. See **[supported countries](/guides/disburse/countries)** for full coverage and availability.
***
## Types of payout methods
### Bank transfers
Standard bank transfers are the most widely supported payout method.
* Local transfers for domestic payouts
* International transfers for cross-border payouts
Bank transfers typically require:
* Bank account number or IBAN
* Bank or routing code (e.g. SWIFT, sort code, ABA)
***
### Real-time and local payment networks
Some countries support faster or local payout methods through domestic payment networks.
These methods may offer:
* Faster delivery times
* Lower fees
* Simpler recipient details
Requirements vary by country and network.
***
### Method selection
Payout methods can be selected in different ways:
* **Explicitly** when creating a payout
* **Implicitly** based on available payee details
* **By the recipient** when using a payout link
If multiple methods are available, Acclaim can guide selection based on **compatibility and completeness of details**.
***
## Required details
Each payout method has specific required fields.
Examples include:
* IBAN and SWIFT code for international bank transfers
* Routing number and account number for domestic transfers
* Local identifiers for country-specific methods
Validation is performed automatically to ensure:
* Correct formatting
* Required fields are present
* Compatibility with the selected method
***
## Method compatibility
Not all payout methods support all combinations of:
* Country
* Currency
* Payee type (individual or business)
If a method is not compatible:
* It will not be available for selection
* Or the payout will require additional or corrected details
***
## Using payout methods with payees
Payees can have one or more payout methods associated with them.
You can:
* Store multiple methods for a single payee
* Set a default method
* Let recipients choose their preferred method via payout links
This allows you to **adapt payouts to different regions and scenarios** without recreating payees.
***
## Using payout methods with payout links
When using payout links, recipients can:
* Provide required banking details
* Select from supported payout methods (if enabled)
This ensures the payout method is **valid, complete, and aligned with recipient preference** before funds are sent.
# Sending your first payout
Source: https://docs.withacclaim.com/guides/disburse/sending-your-first-payout
Fund a treasury account, set up a payee, send a payout, and track it in the Console—from sandbox to your first live payment.
A **payout** moves money from one of your **treasury accounts** to a **payee**. Acclaim handles routing, compliance checks, and delivery on the rail. Your job is to make sure the account is funded, the payee is ready, and you confirm status in the **Acclaim Console**.
In **sandbox**, you can walk through the full flow without moving real money.
## Fund a treasury account
Before you send money, the treasury account you plan to use needs enough balance for the payout (and any fees your setup includes).
* Funds usually enter through a linked **settlement account** (your external bank) or other funding flows your organization uses.
* You can add funds from the **Acclaim Console** in **Treasury** → **Funding** or through processes your team has already configured.
* Treasury accounts are **single-currency**; use an account in the same currency as the payout.
For a deeper operations view, see [Funding accounts](/guides/treasury/add-funds).
## Create a payee
A **payee** is the person or organization you pay (for example an agent, provider, member, or vendor).
* Payee records hold payout destination details so you are not storing raw bank data in spreadsheets.
* If you use **payout links**, the recipient can complete or choose payout details through a secure link instead of you entering everything up front.
See [Payees](/guides/disburse/payees) and [Payout links](/guides/disburse/payout-links) for how these fit together.
## Create a payout
When the treasury account has funds and the payee exists, you create a payout with a **treasury account** (source of funds), a **payee**, and the right **currency** for the rail. Amounts are expressed in the **smallest currency unit** for that currency (for example cents for USD), unless the **Acclaim Console** shows a different unit for your role.
### Funding amount and payment amount
A payout involves two related amounts:
* **Funding amount** — how much is **debited** from your treasury account (the side that funds the send).
* **Payment amount** — how much is **paid** to the payee on the recipient side (what they receive in the payout currency).
If there is **currency conversion** or **fees**, those two numbers may not match. You choose which side to **lock** (hold fixed):
* **Lock the funding amount** when you need a fixed debit from treasury; the payment amount is derived from rates and fees.
* **Lock the payment amount** when the payee must receive an exact sum; the funding debit is derived from rates and fees.
The **Console** (or your **API** integration) will show the controls that apply to your payout corridor and currency pair.
You can also use a **payout link** so the recipient picks or confirms how they want to be paid when that fits your process.
Payouts can be created from supported **Console** flows, **file uploads**, or your team’s **API** integration, depending on what your organization uses.
## Track the payout
After the payout is created, Acclaim processes it on the appropriate network. You can monitor progress in the **Acclaim Console** (search the payout, open details, review status and timelines).
If your organization uses **webhooks** or an **API** integration, engineering can subscribe to events such as `payout.created`, `payout.processing`, `payout.succeeded`, and `payout.failed` so internal systems stay in sync. See [Webhooks](/developers/webhooks) and the **API Reference** for technical detail.
## Batch payouts
To send many payouts at once (for example monthly commissions), use a **payout batch** so you can initiate, track, and reconcile them as one run. See [Batch payouts](/guides/disburse/batch-payouts).
## Sandbox and going live
Use **sandbox** to validate funding, payees, payouts, and notifications with test data. When you move to production, switch to **live** keys and funding only as part of your go-live checklist. See [Testing and going live](/guides/getting-started/testing-and-going-live).
# Implementation guide
Source: https://docs.withacclaim.com/guides/getting-started/implementation-guide
Plan, configure, and launch Acclaim. Set up your account structure, workflows, and team before moving money in production.
This guide walks through how to implement Acclaim in a production environment.
It focuses on **planning, configuration, integration, and operational setup**, followed by validating the payment flows your team will use.
***
## Overview
A successful implementation involves more than enabling payments.
You will need to:
* Define how funds should be structured and controlled
* Configure your account and workflows
* Integrate with your systems
* Align internal teams and processes
* Then test and go live
Most teams follow a sequence of **plan → configure → integrate → test → go live**.
***
## Step 1: Define requirements
Start by defining how you intend to use Acclaim.
Consider:
* What types of payments you will support (claims, vendor payments, collections)
* Which countries and currencies are required
* Whether funds are prefunded or collected before payout
* How funds should be separated (by program, entity, or workflow)
* What reporting and reconciliation requirements exist
This step ensures your implementation matches your operational and financial model.
***
## Step 2: Design your account structure
Define how funds will be organized in Treasury.
* Create accounts based on your operating model
* Separate funds by program, entity, or use case
* Plan for multi-currency needs
For example:
* Loss funds for claims
* Subscriber or participant funds
* Operational or clearing accounts
A well-designed account structure makes reconciliation and reporting significantly easier.
**See also**
* [Accounts](/guides/treasury/accounts)
* [Balances](/guides/treasury/balances)
***
## Step 3: Configure access and internal workflows
Set up your team and operational controls.
* Add users and assign appropriate roles
* Define approval workflows (if applicable)
* Establish processes for reviewing and executing payments
* Align responsibilities across operations, finance, and engineering
This ensures your team can operate the system effectively.
***
## Step 4: Configure system settings
Configure platform-level settings before enabling payment flows.
* Add and verify [settlement accounts](/guides/treasury/withdraw-funds#settlement-accounts)
* Configure [webhooks](/developers/webhooks) for event tracking
* Configure [email sending settings](/guides/platform/email-sending) if you want to send from your own domain
* Set up notification preferences
* Review any limits or controls required for your workflows
These settings support reliable and automated operations.
***
## Step 5: Configure payment flows
Define how money will move through the platform.
### Accept (if receiving funds)
* [Payment requests](/guides/accept/payment-requests) (hosted or embedded)
* [Virtual accounts](/guides/accept/virtual-accounts) for bank transfers
* [Setup requests](/guides/accept/setup-requests) for stored payment methods
**See also**
* [Payment methods](/guides/accept/payment-methods/index)
* [Payment failures](/guides/accept/payment-failures)
***
### Disburse (if sending payouts)
* Create and manage [payees](/guides/disburse/payees)
* Configure [payout methods](/guides/disburse/payout-methods)
* Define payout workflows (manual, [batch payouts](/guides/disburse/batch-payouts), or [payout links](/guides/disburse/payout-links))
***
### Treasury
* [Add funds](/guides/treasury/add-funds) or configure incoming funding flows
* Set up [FX](/guides/treasury/fx) if operating across currencies
* Validate balances and availability (see [Balances](/guides/treasury/balances))
***
## Step 6: Integrate with your systems
Connect Acclaim to your internal systems and workflows.
You can choose the integration approach that fits your needs:
* **API integration** — automate payment flows, data sync, and event handling
* **File uploads** — support bulk operations using structured files ([File uploads](/guides/disburse/file-uploads/overview))
* **Console** — manage payments and operations manually in the [Acclaim Console](https://app.withacclaim.com)
Many implementations use a combination of these approaches.
Common integration patterns include:
* Creating payment requests or payouts from internal systems
* Syncing payment and payout status updates via webhooks
* Exporting data for accounting and reconciliation
* Automating batch workflows
**See also**
* [Developer guides](/developers/getting-started)
* [Concepts](/developers/concepts)
***
## Step 7: Train your team
Before going live, ensure your team understands how to operate the platform.
* Train operations on payment workflows
* Train finance on reconciliation and reporting
* Align on how to handle [payment failures](/guides/accept/payment-failures), payout failures, refunds, and disputes
Clear ownership and training reduce operational risk.
***
## Step 8: Test end-to-end workflows
Validate your implementation in a controlled environment.
* Test full payment flows (collect → treasury → disburse)
* Verify balances and transactions
* Confirm reconciliation and reporting outputs
* Validate webhook delivery and automation
**See also**
* [Testing and going live](/guides/getting-started/testing-and-going-live)
***
## Step 9: Go live
Move to production once testing is complete.
* Switch to live API keys
* Run initial transactions with small amounts
* Monitor balances, transactions, and outcomes
* Validate reconciliation against external systems
Gradually increase volume as confidence builds.
***
## Key considerations
* Design your account structure early. It impacts everything downstream.
* Choose the right integration approach for your workflows.
* Align internal teams before enabling payment flows.
* Ensure settlement accounts and funding flows are configured correctly.
* Plan for multi-currency and FX if applicable.
* Use webhooks to automate workflows and reduce manual effort.
***
## Summary
* Start with requirements and account design
* Configure users, settings, and workflows
* Integrate with your systems using API, files, or Console
* Train your team and validate with testing
* Go live in a controlled and monitored way
A structured implementation ensures your payment operations are **reliable, scalable, and easy to manage**.
***
## Related resources
* [Testing and going live](/guides/getting-started/testing-and-going-live)
* [Key concepts](/guides/getting-started/key-concepts)
* [Treasury](/guides/treasury/overview)
# Key concepts
Source: https://docs.withacclaim.com/guides/getting-started/key-concepts
Core terms for payins, payouts, and treasury — written for operators and stakeholders, with pointers to developer docs.
## Accept (payins)
* **Payer** — The person or organization paying you (for example a policyholder). Used to group payment activity and reporting.
* **Payment request** — An instruction to collect a specific amount; it moves through statuses until it succeeds, fails, or is canceled.
* **Payment method** — Saved or collected card or bank details used to charge a payer, without you storing sensitive data yourself.
For implementation details, see the **[Accept](/developers/accept)** and **[Payment request lifecycle](/developers/payment-request-lifecycle)** developer guides.
## Disburse (payouts)
* **Payee** — Anyone you pay: agents, providers, members, vendors.
* **Payout method** — How that payee receives funds (bank account, wallet, and so on), validated for the destination country.
* **Payout** — A single outbound payment; **batch payouts** group many payouts for commissions or bulk runs.
See **[Sending your first payout](/guides/disburse/sending-your-first-payout)** for a Console-oriented walkthrough, and **[Batch payouts](/developers/batch-payouts)** when your team needs the API-focused developer guide.
## Treasury
* **Treasury account** — A balance in one currency used to fund payouts and receive transfers.
* **Settlement account** — Your external bank account linked to Acclaim for funding and withdrawals.
* **Virtual account** — Bank details that attribute inbound wires to a specific treasury account.
See **[Funding](/developers/funding)** for developer-oriented funding flows.
# Welcome
Source: https://docs.withacclaim.com/guides/getting-started/overview
Acclaim powers insurance complex payment workflows from end to end in one unified platform.
It is built for operational use cases like **insurance claims**, **vendor and provider payments**, and other **multi-party disbursements** where collecting details, sending funds, and tracking outcomes all need to work together seamlessly.
From missing payee details to final reconciliation, everything happens in one place.
Acclaim removes the complexity of managing payment methods, coordinating payouts, and stitching together fragmented systems. Instead, you can **orchestrate the full lifecycle of a payment** with clarity and control.
This documentation will help you understand **how Acclaim works** and how to use it effectively, whether you're **integrating via API**, running **bulk operations**, or managing payments day to day in the **Console**.
***
## Ways to use Acclaim
Choose the approach that fits your workflow:
* **API** — build fully automated, end-to-end payment flows
* **File uploads** — execute bulk payments with structured data
* **Payout links** — collect recipient details and let payees choose how they get paid
***
## Using the Console
The [Acclaim Console](https://app.withacclaim.com) is where you manage day-to-day operations like **viewing payouts**, **monitoring balances**, **configuring webhooks**, and **exporting data**.
# Supported client countries
Source: https://docs.withacclaim.com/guides/getting-started/supported-client-countries
View the countries and busienss types where Acclaim supports onboarding.
Acclaim supports onboarding clients in specific countries and regions.
Eligibility is limited to **insurance companies and related service providers**, including:
* Carriers
* MGAs / MGUs
* TPAs
* Brokers and intermediaries
* Claims and risk service providers
If your organization does not fall into these categories, onboarding may not be supported.
***
## Supported countries
Acclaim currently supports onboarding in the following countries:
* Austria
* Belgium
* Brazil
* Canada
* Cayman Islands
* China
* Cyprus
* Denmark
* Finland
* France
* French Guiana
* Germany
* Gibraltar
* Greece
* Guadeloupe
* Hong Kong
* Iceland
* Indonesia
* Ireland
* Isle of Man
* Israel
* Italy
* South Korea
* Liechtenstein
* Luxembourg
* Macau
* Malta
* Marshall Islands
* Martinique
* Mayotte
* Mexico
* Netherlands
* Norway
* Portugal
* Puerto Rico
* Réunion
* Saint Martin
* Samoa
* Seychelles
* Spain
* Sweden
* Switzerland
* Taiwan
* United Kingdom
* United States of America
* Vietnam
* British Virgin Islands
* U.S. Virgin Islands
***
## Eligibility requirements
In addition to being located in a supported country, clients must:
* Operate within the **insurance ecosystem**
* Meet onboarding and compliance requirements
* Provide required business and ownership information
Approval is subject to internal review and third-party verification processes.
***
## Notes on availability
* Supported countries may expand over time
* Availability of specific features (e.g. payment methods or payout capabilities) may vary by region
* Additional restrictions may apply based on regulatory requirements
# Testing and going live
Source: https://docs.withacclaim.com/guides/getting-started/testing-and-going-live
Validate flows in sandbox, then move to production with a practical checklist — for both operations and engineering.
## Sandbox accounts
Use sandbox accounts to rehearse the **full payment lifecycle** — including **funding**, **payees**, **payouts**, **batches**, and **webhooks** — without risk.
Engineering should follow **[Testing and going live](/developers/testing-going-live)** and **[Testing](/developers/testing)** for Accept-specific test data.
Operations and finance should use sandbox to preview **Console workflows**, **exports**, and **reconciliation processes**, so internal processes match production from day one.
**Test realistic scenarios, not just happy paths:**
* Missing or invalid payee details
* Failed payouts and retries
* Webhook delivery and retry behavior
* Partial or delayed batch execution
***
## Before production
Complete this checklist before sending live funds:
1. **Live API keys** are issued, securely stored, and never mixed with test keys
2. **Settlement accounts** are linked and verified for all required currencies
3. **Webhook endpoints** are registered, publicly accessible, and handling retries correctly
4. **Idempotency** is implemented for all payout and payment creation requests
5. **Access controls** are configured in the Console (roles, permissions, API key scope)
6. **Operational ownership** is defined for monitoring, failures, and reconciliation
7. **Small live test** — run a real payin or payout end-to-end and confirm:
* Status updates
* Webhook delivery
* Console visibility
* Downstream reconciliation
***
## Go-live readiness
Before scaling volume, confirm:
* **Balances are funded** and monitored to prevent payout failures
* **Rate limits and throughput** match expected usage
* **Notifications and alerts** are in place for failures or delays
* **Support paths** are defined internally for handling issues
***
## Ongoing operations
Once live, treat payments as a **continuously monitored system**, not a one-time setup.
Monitor the Console for:
* Failed or delayed payouts
* Webhook delivery issues
* Batch execution results
* Balance levels and funding gaps
Align internal owners and processes for:
* **[Payment failures](/guides/accept/payment-failures)**
* **[Handling payout failures](/guides/disburse/failures-and-reversals)**
* **[Reconciliation](/guides/treasury/reconciliation)**
# Account structure
Source: https://docs.withacclaim.com/guides/platform/account-structure
Understand how your organization and accounts are structured in Acclaim.
Acclaim is structured around your **organization and accounts**.
This structure defines how data is organized, how access is controlled, and how your team operates within the platform.
***
## Visual overview
The diagram below shows how your **organization** relates to **users**, multiple **accounts**, and each account's **settings** and **data**, within a **compliance region** for data residency.
![Organization, users, accounts, settings, data, and compliance region]()
***
## Organization
The organization is the top-level entity.
* Represents your company or group
* Owns all accounts, users, and configuration
* Defines the scope of your environment
All activity in Acclaim occurs within an organization.
***
## Organization accounts
Organization accounts are used to structure your data and configuration.
* Define how workflows, settings, and activity are grouped
* Control how users access different parts of the platform
* Support separation across entities, programs, or regions
Organization accounts **do not hold funds**.
They are used for **structure and access**, not balances.
***
## Structuring organization accounts
Organization accounts can be configured to match your operating model.
Common patterns include:
* **Per entity** — separate accounts for different legal entities
* **Per program** — isolate activity for specific programs or lines of business
* **Per region** — separate operations across jurisdictions
* **Per workflow** — organize claims, commissions, or collections
This structure helps maintain clarity across operations and reporting.
***
## Treasury accounts
Treasury accounts are where funds are held and managed.
* Each treasury account holds a balance in a **single currency**
* Balances are tracked as total, available, and pending
* Transactions record all movement of funds
Treasury accounts are separate from organization accounts and are used for **managing money**, not structuring data.
***
## Accounts and users
Users are granted access at the organization and account level.
* Access can be scoped to specific organization accounts
* Permissions define what actions users can perform
* This allows teams to operate within defined boundaries
See [Users and permissions](/guides/platform/users-permissions) for more details.
# Email sending
Source: https://docs.withacclaim.com/guides/platform/email-sending
Configure email sending in Acclaim. Use the default sender or set up a custom from address for branding and enhanced deliverability.
By default, Acclaim sends emails from `no-reply@withacclaim.com`.
If you want emails to come from your own domain, you can configure a custom from address in the Console. A branded sender improves trust and significantly improves deliverability.
***
## Configure a custom from address
To send from your own domain, go to **Settings** > **Email Settings** in the Acclaim Console.
From there, you can:
* Enter the branded from address you want to use
* Optionally enter a return-path domain for bounce handling
* Save your settings to generate the required DNS records
***
## How setup works
Setting up a branded sender follows a short verification flow:
1. Enter the from address you want to use.
2. Save your email settings to create the domain configuration.
3. Add the DNS records exactly as shown in the Console.
4. Refresh verification after DNS propagation finishes.
The exact records vary by domain and account, so use the values shown in your Acclaim environment.
***
## DNS verification
Acclaim shows the DNS records required to verify your sending domain.
These records typically cover:
* **SPF** to authorize sending for your domain
* **DKIM** to sign outbound email
* **Return-path** to customize the bounce handling domain (optional)
Your custom from address is ready to use after these records are added and verified.
***
## What to expect
Before verification is complete, Acclaim continues sending email from `no-reply@withacclaim.com`.
After your domain is verified, Acclaim can send from your branded address instead.
DNS changes can take time to propagate, so verification may not complete immediately after you add the records. If it does not work immediately, then please return to the page later and re-attempt the verification process.
# Users and permissions
Source: https://docs.withacclaim.com/guides/platform/users-permissions
Manage access to your organization and accounts. Control who can view, operate, and configure workflows in Acclaim.
Users and permissions control who can access your organization and what actions they can perform.
This allows teams across operations, finance, and engineering to work within the same system with appropriate levels of access.
***
## How access works
Access in Acclaim is defined by:
* **Organization access** — visibility across the platform
* **Account access** — which accounts a user can view or operate
* **Permissions** — what actions a user can perform
Together, these determine a user’s effective access.
***
## Organization access
Users are invited to your organization.
* Users can belong to one or more organizations
* Organization access defines the overall scope of visibility
* Some users may have administrative privileges
***
## Account access
Access can be scoped to specific accounts.
* Users may be limited to one or more accounts
* This restricts visibility of balances, transactions, and activity
* Helps separate workflows across teams or entities
Account-level access is commonly used to isolate:
* Programs or business units
* Regions or currencies
* Operational responsibilities
***
## Permissions
Permissions define what actions a user can take.
Common permission types include:
* **View** — access balances, transactions, and reports
* **Operate** — create payments, payouts, and workflows
* **Configure** — manage settings, webhooks, and accounts
* **Administer** — manage users and organization-level settings
Permissions can be combined to match different roles.
***
## Roles
Roles group permissions into common access patterns.
Typical roles include:
* **Operations** — manage payments and payouts
* **Finance** — view balances, reconcile, and export data
* **Engineering** — configure integrations and webhooks
* **Admin** — full access across the organization
Roles simplify access management and ensure consistency.
***
## Managing users
You can manage users in the Console.
* Invite new users
* Assign roles and permissions
* Grant or restrict account access
* Update or remove access as needed
Changes take effect immediately.
***
## Best practices
* Grant users access only to the accounts they need
* Use roles to standardize permissions
* Separate operational and administrative responsibilities
* Regularly review and update user access
* Limit administrative access to a small number of users
# Accounts
Source: https://docs.withacclaim.com/guides/treasury/accounts
Understand how funds are structured and held within Treasury. Accounts organize balances and support how money is tracked and managed.
Accounts represent how funds are **structured and held** within Treasury.
They provide a way to organize balances and transactions, giving you control over how money is grouped, tracked, and reported.
***
## How accounts work
Accounts act as containers for your funds.
* Each account holds a balance in a **single currency**
* Transactions are recorded against accounts
* Balances are derived from the activity within each account
Accounts allow you to separate and manage funds across different contexts.
***
## Accounts and balances
Each account maintains a balance in a single currency, with three key views:
* **Total balance** — all funds associated with the account
* **Available balance** — funds that can be used immediately
* **Pending balance** — funds that are not yet available
### Total balance
The total balance represents the full amount of funds in the account.
It includes:
* Available funds
* Pending funds
***
### Available balance
The available balance is the portion of funds that can be used.
You can use available balance to:
* Send payouts
* Withdraw funds
* Perform FX conversions
***
### Pending balance
The pending balance represents funds that are in transit or not yet finalized.
Examples include:
* Payments that are still processing
* Incoming transfers that have not settled
* Funds subject to processing timelines
Pending funds become available once processing is complete.
***
## Accounts and transactions
All fund movements are recorded as transactions within accounts.
Examples include:
* Incoming payments
* Payouts
* Refunds
* FX conversions
* Funding and withdrawals
Transactions provide a complete history of activity for each account.
***
## Using accounts
Accounts can be used to structure funds in ways that match your operations.
Common patterns include:
* **Per entity** — separate accounts for different legal entities
* **Per workflow** — isolate funds for specific use cases
* **Operational separation** — distinguish between types of activity
In insurance and claims workflows, accounts are commonly used for:
* **Loss fund management** — hold and manage funds reserved for claim payments
* **Subscriber fund management** — track and manage funds contributed by subscribers or participants
* **Program or policy-level funds** — separate balances for specific programs, policies, or captives
* **General cash management** — control how funds are allocated, reserved, and deployed
This structure allows you to maintain clear separation of funds while preserving a unified view in Treasury.
***
## Relationship to other Treasury components
Accounts connect the core Treasury concepts:
* **Balances** — what you have within each account
* **Transactions** — what has happened within each account
* **Virtual accounts** — how funds are received into accounts
This structure provides a consistent view of your funds.
***
## Key behaviors
* Each account is tied to a **single currency**
* Accounts maintain **total, available, and pending balances**
* Pending funds become available as transactions settle
* Transactions are recorded at the account level
* Balances are derived from account activity
***
## Summary
* Accounts define how funds are structured within Treasury
* Each account holds funds in a single currency
* Balances are split into total, available, and pending
* Transactions drive all balance changes
* Accounts support insurance-specific funding models and broader cash management use cases
# Add funds
Source: https://docs.withacclaim.com/guides/treasury/add-funds
Fund your Treasury accounts by sending bank transfers to your virtual accounts. Increase available balances for payouts, FX, and other operations.
Adding funds allows you to **increase your Treasury balances** by sending money into your accounts.
Funds are typically added using **bank transfers** to your virtual account details.
***
## How adding funds works
Adding funds follows a simple flow: **send**, **receive**, and **settle**.
1. **Select a virtual account**
Choose the account and currency you want to fund.
2. **Send a bank transfer**
Initiate a transfer from your external bank account using the provided details.
3. **Receive funds**
The transfer is processed through the banking network.
4. **Funds become available**
Once settled, the funds are added to your available balance.
***
## Funding methods
Funds are added through bank transfers using your virtual accounts.
Depending on the region, this may include:
* Domestic bank transfers
* Real-time payment networks
* International wire transfers (SWIFT)
See **Virtual accounts** for supported regions and funding methods.
***
## Timing and availability
Funding timing depends on the payment rail used.
* Some methods are near real-time
* Others take multiple business days
* Funds may appear as **pending** before becoming **available**
Availability depends on settlement completion.
***
## Choosing the right account
Funds must be sent to a virtual account that matches the desired currency.
* Sending funds in USD → use a USD account
* Sending funds in EUR → use a EUR account
If funds are received in a different currency than needed, you can convert them using FX.
***
## Tracking funding activity
You can track funding activity in the Console.
Each funding event creates a transaction that includes:
* Amount and currency
* Status (pending or completed)
* Associated account
* Timestamp
You can also track updates via webhooks.
***
## Reconciliation
Funding transactions are recorded in your ledger and can be reconciled against your external bank activity.
To improve reconciliation:
* Use consistent transfer references
* Match transactions by amount and timing
* Track funding events alongside internal records
***
## Best practices
* Send funds to the correct currency account
* Use clear references when initiating transfers
* Monitor pending funds until settlement
* Plan for settlement timing when funding payouts
***
## Summary
* Add funds by sending bank transfers to your virtual accounts
* Funds are credited to your Treasury balances once settled
* Timing depends on the payment method and region
* Funding transactions are tracked and available for reconciliation
# Balances
Source: https://docs.withacclaim.com/guides/treasury/balances
View and manage your available funds by currency. Balances reflect the current state of your money across all transactions.
Balances represent how much money you have available in Treasury, organized by currency.
They are updated automatically as funds are collected, paid out, converted, or moved.
***
## How balances work
Each currency has its own balance.
Balances change as transactions occur:
* Incoming payments increase balances
* Payouts and withdrawals decrease balances
* Refunds reduce balances
* FX conversions move value between currencies
Balances reflect the current state of your funds at any point in time.
***
## Available balance
The available balance is the amount of funds you can use.
You can use available balance to:
* Send payouts
* Withdraw funds
* Perform FX conversions
Available balance updates as transactions are processed.
***
## Multi-currency balances
Treasury supports multiple currencies.
* Each currency is tracked independently
* Funds must be available in the required currency to be used
* FX conversions can be used to move value between currencies
This allows you to manage funds globally while maintaining currency separation.
***
## How balances update
Balances are updated based on transaction activity.
Examples:
* A completed payment increases your balance in that currency
* A payout decreases your balance when funds are sent
* A refund decreases your balance when funds are returned
* An FX conversion decreases one currency and increases another
All balance changes are recorded as transactions.
***
## Relationship to transactions
Balances are derived from transactions.
* Every balance change corresponds to a transaction
* Transactions provide a detailed record of activity
* Balances provide a summarized view of current funds
Use transactions when you need detail, and balances when you need a snapshot.
***
## Funding and availability
Before sending payouts or making transfers, ensure you have sufficient balance in the required currency.
If funds are not available:
* Add funds to Treasury
* Or convert from another currency using FX
***
## Tracking balances
You can monitor balances in the Console.
You can also:
* Track balance changes through transactions
* Use webhooks to monitor activity
* Export data for reporting
***
## Key behaviors
* Balances are maintained per currency
* Balances update automatically as transactions occur
* FX conversions move value between balances
* Insufficient balance will prevent payouts or transfers
***
## Summary
* Balances show how much money you have available
* Each currency is tracked separately
* Transactions drive all balance changes
* Balances are used to fund payouts, withdrawals, and conversions
# FX
Source: https://docs.withacclaim.com/guides/treasury/fx
Convert funds between currencies and understand how foreign exchange impacts balances, transactions, and payouts.
Foreign exchange (FX) allows you to **convert funds between currencies** within Treasury.
FX is used when you need to:
* Fund payouts in a different currency
* Manage multi-currency balances
* Move value between accounts
***
## How FX works
FX conversions move value between currency accounts.
* Funds are **sold** from one currency account
* Funds are **bought** into another currency account
* The conversion is based on an FX rate at the time of execution
This ensures that currency movements are fully tracked and reflected in your balances.
***
## When FX is used
FX may occur in different scenarios:
* **Manual conversion** — convert balances between currencies
* **Before payouts** — convert funds to the payout currency
* **Batch payouts** — a single FX rate may apply per currency pair
FX allows you to operate across currencies without needing to pre-fund every currency.
***
## Performing a conversion
To convert funds:
1. Select the **sell currency** (the currency you are converting from)
2. Select the **buy currency** (the currency you are converting to)
3. Specify the amount to convert
4. Execute the conversion
The system will apply an FX rate and complete the transaction.
***
## FX rates
Conversions are performed using an FX rate at the time of execution.
* Rates may vary based on market conditions
* The converted amount is calculated at execution
* The rate determines the final amount received in the **buy currency**
***
## FX transactions
Each conversion creates transactions in your ledger.
* A **credit** from the sell currency account
* A **debit** to the buy currency account
This ensures that balances remain accurate and auditable.
***
## Impact on balances
After a conversion:
* The **sell currency** balance decreases
* The **buy currency** balance increases
* The total value is preserved based on the applied rate
Converted funds can be used once they become available.
***
## FX in payouts
FX is commonly used when sending cross-border payouts.
* Funds are converted into the payout currency
* In batch payouts, a **single FX rate** may be applied per currency pair
* Converted funds are then used to complete payouts
***
## Tracking FX activity
You can track FX conversions in the Console.
Each conversion includes:
* Sell and buy currencies
* Amounts before and after conversion
* Applied FX rate
* Associated transactions
***
## Best practices
* Convert funds before initiating payouts when possible
* Monitor FX rates if timing is important
* Ensure sufficient balance in the sell currency
* Track conversions for reconciliation and reporting
***
## Summary
* FX allows you to convert funds between currencies
* Conversions use **sell and buy currencies**
* Transactions are created across accounts to reflect movement
* FX is commonly used for funding payouts and managing multi-currency balances
# Treasury Overview
Source: https://docs.withacclaim.com/guides/treasury/overview
Manage balances, track transactions, and control the movement of funds across currencies. Treasury is the source of truth for your money in Acclaim.
Treasury is where your funds are **held, tracked, and managed**.
It provides a unified view of your **balances**, a complete record of **transactions**, and the tools to **fund, convert, and move money** across currencies.
***
## How Treasury fits into Acclaim
Treasury connects directly to how money flows through the platform.
* **Accept** adds funds to your balances
* **Disburse** uses your balances to send payouts
* **Treasury** tracks and manages everything in between
This makes Treasury the **source of truth for your money**.
***
## Core concepts
### Balances
Balances represent how much money you have available, organized by currency.
* Each currency has its own balance
* Balances update as funds are collected, paid out, or converted
* Available amounts determine what can be used for payouts
***
### Accounts
Accounts represent how funds are held and structured.
* May correspond to settlement or holding accounts
* Support separation of funds across workflows or entities
* Provide structure for tracking and reporting
***
### Transactions
Transactions record every movement of funds.
Examples include:
* Incoming payments
* Payouts
* Refunds
* FX conversions
* Fees
Transactions form a complete **ledger of activity** across your balances.
***
## Funding and withdrawals
You can move funds into and out of Treasury as needed.
* **Add funds** to increase available balances
* **Withdraw funds** to external accounts
These flows are separate from collecting payments or sending payouts.
***
## Multi-currency and FX
Treasury supports multiple currencies.
* Maintain balances in different currencies
* Convert between currencies using FX
* Use converted funds for payouts or withdrawals
FX allows you to manage currency exposure and fund cross-border payments.
***
## Tracking and control
Treasury provides visibility and control over your funds.
You can:
* Monitor balances in real time
* Track every transaction
* Reconcile activity with internal systems
* Export data for reporting
***
## Key behaviors
* Balances update automatically as money moves through the platform
* Transactions provide a complete audit trail
* FX conversions create new transactions and adjust balances
* Funding and withdrawals directly impact available balances
***
## Summary
* Treasury is the **system of record for your funds**
* Balances show what you have
* Transactions show what happened
* Accounts provide structure
* FX and funding enable you to manage and move money across currencies
# Reconciliation
Source: https://docs.withacclaim.com/guides/treasury/reconciliation
Ensure your balances and transactions are accurate. Reconcile Treasury activity with your internal records and external bank accounts.
Reconciliation is the process of ensuring your **accounts, balances, and transactions are accurate and complete**.
In Treasury, reconciliation focuses on verifying that:
* Your **account balances match transaction activity**
* Your **internal records match Acclaim**
* Your **external bank activity aligns with Treasury movements**
***
## How reconciliation works
Treasury is built on a transaction-based ledger.
* Every balance is derived from transactions
* Every movement of funds is recorded
* Accounts provide structure for tracking activity
Reconciliation ensures that these components remain consistent and aligned.
***
## What to reconcile
### Account balances
Verify that account balances match expected values.
* Confirm **total balance = available + pending**
* Validate balances against your internal systems
* Ensure balances reflect all known activity
***
### Transaction activity
Review transactions to ensure completeness and accuracy.
* All expected transactions are present
* Amounts and currencies are correct
* Statuses reflect the correct state (pending or completed)
Transactions should provide a complete audit trail.
***
### External bank activity
Match Treasury activity with your external bank accounts.
* **Funding (add funds)** → match incoming bank transfers
* **Withdrawals** → match outgoing transfers to settlement accounts
* Verify amounts, timing, and references
This ensures alignment between Treasury and your real-world accounts.
***
### FX activity
Reconcile FX conversions across accounts.
* Confirm sell and buy amounts match expectations
* Verify FX rates and resulting balances
* Ensure both sides of the conversion are recorded
FX should always result in balanced transactions across accounts.
***
## Reconciliation workflows
### Daily reconciliation
* Review recent transactions
* Monitor pending vs available balances
* Confirm funding and withdrawals
***
### Period-end reconciliation
* Validate all balances across accounts
* Ensure all transactions are accounted for
* Match Treasury data with accounting systems
***
### Exception handling
When discrepancies occur:
* Identify missing or duplicate transactions
* Check transaction statuses (pending vs completed)
* Verify external bank activity
* Review FX conversions and fees
Resolve discrepancies before proceeding with reporting.
***
## Tools for reconciliation
You can use the following to support reconciliation:
* **Console** — view balances and transaction history
* **Exports** — download transaction data for analysis
* **Webhooks** — track transaction updates in real time
These tools help automate and validate reconciliation processes.
***
## Best practices
* Reconcile accounts regularly (daily or more frequently)
* Use transaction IDs and references for matching
* Monitor pending balances and settlement timing
* Track funding and withdrawals closely
* Validate FX conversions across both currencies
***
## Summary
* Reconciliation ensures your Treasury data is **accurate and complete**
* Balances must align with underlying transactions
* External bank activity should match funding and withdrawals
* FX activity must be balanced across accounts
* Regular reconciliation supports reliable financial operations
# Reporting
Source: https://docs.withacclaim.com/guides/treasury/reporting
Access financial reports and exports to understand activity, track balances, and support accounting and reconciliation workflows.
Reporting provides visibility into your **balances, transactions, and financial activity**.
You can use reports to:
* Export data for accounting systems
* Monitor financial activity over time
* Support reconciliation and audits
***
## How reporting works
Reports are generated from your Treasury data.
* Balances reflect the current state of funds
* Transactions provide detailed activity
* Reports aggregate and structure this data for analysis
Reports can be generated for a **specific date range** or **point in time**, depending on the report.
***
## Treasury reports
### Reconciliation report
Provides a summary and detailed view of Treasury account reconciliation with your general ledger.
* Compare Treasury balances to internal records
* Identify discrepancies
* Support audit and period-end close
**Format:** Date range
***
### Account balances
Shows Treasury account balances at a specific point in time.
Includes:
* Total balance
* Available balance
* Pending balance
Useful for:
* Period-end reporting
* Snapshot of financial position
* Balance verification
**Format:** As of a specific date
***
### Ledger export
Exports all Treasury transactions for a given date range.
Includes:
* Transaction type and amount
* Currency and account
* Status and timestamps
* Related objects (payments, payouts, FX)
Useful for:
* Accounting system imports
* Detailed reconciliation
* Audit trails
**Format:** Date range
***
## Related reports
The following reports include activity that impacts Treasury balances:
### Payout report
Provides details on payouts created within a date range.
Includes:
* Payee
* Status
* Amount and currency
* Payout method
Useful for:
* Tracking outgoing funds
* Reconciling debits from Treasury
***
### Payin report
Provides details on incoming payments within a date range.
Includes:
* Payer
* Status
* Amount and currency
* Payment method
Useful for:
* Tracking inflows
* Reconciling credits to Treasury
***
### Fee report
Summarizes fees and charges over a date range.
* Grouped by fee type
* Reflects costs associated with transactions
Useful for:
* Understanding cost drivers
* Reconciling fee-related balance changes
***
### Audit log
Provides a record of activity and actions taken within the account.
Includes:
* User actions
* System events
* Configuration changes
Useful for:
* Compliance
* Operational audits
* Investigating changes
***
## Using reports
Reports can be used to:
* Export data into accounting systems
* Validate balances and transactions
* Analyze financial activity
* Support audits and compliance
***
## Best practices
* Use **ledger exports** for detailed reconciliation
* Use **account balances** for point-in-time reporting
* Reconcile reports with internal systems regularly
* Track payouts and payins alongside Treasury activity
* Review audit logs for operational transparency
***
## Summary
* Reporting provides structured access to your financial data
* Treasury reports focus on balances and transactions
* Related reports provide visibility into inflows, outflows, and fees
* Reports support reconciliation, accounting, and operational insight
# Transactions
Source: https://docs.withacclaim.com/guides/treasury/transactions
Track every movement of funds across your accounts. Transactions provide a complete ledger of activity and drive all balance changes.
Transactions record every movement of funds within Treasury.
They form a complete **ledger of activity**, allowing you to track how money enters, moves through, and leaves your accounts.
***
## How transactions work
Every change to a balance is recorded as a transaction.
* Transactions are created when funds move
* Each transaction is associated with an account
* Transactions update balances in real time
This ensures that balances are always derived from a consistent source of truth.
***
## Transaction types
Transactions represent different types of financial activity.
Common examples include:
* **Incoming payments** — funds received from Accept
* **Payouts** — funds sent through Disburse
* **Refunds** — funds returned to payers
* **Funding** — funds added to Treasury
* **Withdrawals** — funds moved out of Treasury
* **FX conversions** — value moved between currencies
* **Fees** — charges associated with processing
Each transaction reflects a specific movement of funds.
***
## Debit and credit model
Transactions follow a debit and credit model aligned with **bank account assets**.
* **Debits** increase the balance of an account
* **Credits** decrease the balance of an account
For example:
* An incoming payment or deposit creates a **debit**
* A payout or withdrawal creates a **credit**
This reflects the behavior of accounts as assets in your ledger.
***
## Transaction lifecycle
Transactions may move through states as they are processed.
* Pending — the transaction has been created but not finalized
* Completed — the transaction is finalized and reflected in available balance
Pending transactions contribute to **pending balance** and become **available** once completed.
***
## Relationship to accounts and balances
Transactions are the foundation of Treasury.
* **Accounts** organize where transactions occur
* **Balances** summarize the result of all transactions
* **Transactions** provide the detailed record of activity
If balances answer “what do I have,” transactions answer “what happened.”
***
## FX transactions
FX conversions create multiple transactions.
* A debit from the source currency account
* A credit to the destination currency account
This ensures that currency movements are fully tracked and auditable.
***
## Tracking transactions
You can view transactions in the Console or access them via API.
Each transaction includes:
* Amount and currency
* Type (e.g. payment, payout, FX)
* Status (pending or completed)
* Associated account
* Related objects (e.g. payment, payout)
* Timestamps
This information can be used for reconciliation and reporting.
***
## Using transactions
Transactions are used to:
* Audit fund movements
* Reconcile balances with internal systems
* Investigate issues or discrepancies
* Build financial reporting
They provide a complete and traceable history of all activity.
***
## Key behaviors
* Every balance change is driven by a transaction
* Transactions are recorded at the account level
* Debits decrease balances and credits increase balances
* Pending transactions become available once completed
* FX creates transactions across multiple accounts
***
## Summary
* Transactions are the ledger of all fund movements
* They drive all balance changes
* They provide a complete and auditable history
* They connect accounts, balances, and payment activity
# Virtual accounts
Source: https://docs.withacclaim.com/guides/treasury/virtual-accounts
Open and manage virtual accounts to receive funds in supported countries and currencies. View available regions, funding methods, and capabilities.
Virtual accounts allow you to receive funds into Treasury using local bank details.
They provide account information, such as account numbers or IBANs, that can be shared with payers to receive transfers directly into your balances.
***
## How virtual accounts fit into Treasury
Virtual accounts are part of your Treasury infrastructure.
* They receive incoming bank transfers
* Funds are credited to your balances
* Each account is tied to a specific country and currency
Virtual accounts can be used across workflows, including Accept and funding flows.
***
## Supported regions and capabilities
You can open virtual accounts in the following regions:
| Region | Currency | Local funding methods | SWIFT funding |
| -------------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | ------------- |
| Australia | AUD | Bank Transfer | No |
| Brazil | BRL | PIX, TED | No |
| Canada | CAD | EFT, Interac e-Transfer | No |
| Denmark | DKK, EUR, AUD, AED, CAD, CHF, CNY, CZK, GBP, HKD, HUF, ILS, JPY, MXN, NOK, NZD, PLN, RON, SEK, SGD, USD, ZAR | DKK: Intradagclearing, RTGS (KRONOS2); EUR: SEPA Instant, SEPA | Yes |
| Estonia | EUR | SEPA Instant, SEPA | No |
| Germany | EUR | SEPA Instant, SEPA | No |
| Hong Kong SAR | CNY, EUR, HKD, USD, AUD, GBP, JPY, SGD, CHF, CAD, NZD | CNY/HKD: ACH, RTGS, FPS; EUR/USD: RTGS | Yes |
| Indonesia | IDR | RTGS, SKN, BI-FAST | No |
| Israel | ILS | Faster Payments, MASAV, ZAHAV | No |
| Mexico | MXN | SPEI | No |
| Netherlands | EUR | SEPA Instant, SEPA | No |
| New Zealand | NZD | Direct Credit | No |
| Philippines | PHP | Instapay, PESONet | No |
| Poland | PLN | Elixir, Express Elixir, RTGS (SORBNET) | No |
| Singapore | SGD, USD, AUD, CAD, CHF, CNY, EUR, GBP, HKD, JPY, NOK, NZD, SEK | SGD: GIRO, MEPS, FAST | Yes |
| United Arab Emirates | AED | IPI, RTGS | No |
| United Kingdom | GBP | Faster Payments, BACS, CHAPS | Yes |
| United States | USD | ACH, Fedwire, FedNow, RTP | Yes |
Availability may depend on your specific configuration or region. Some payment methods are only for eligible customers, subject to approval.
***
## How funds are received
When funds are sent to a virtual account:
* The transfer is processed through local or international banking rails
* Funds are credited to your Treasury balance
* A transaction is created in your ledger
Incoming transfers can be tracked in the Console and via webhooks.
***
## Using virtual accounts
Virtual accounts can be used flexibly across workflows:
* Assign accounts to specific payers
* Use accounts for funding Treasury balances
* Support region-specific payment flows
They are especially useful for:
* Receiving bank transfers
* Supporting local payment methods
* Improving reconciliation
***
## Relationship to Accept
Virtual accounts are also used in Accept to receive payments.
* Treasury defines where accounts exist and what is supported
* Accept defines how they are used in payment flows
***
## Key behaviors
* Each virtual account is tied to a specific region and currency
* Funds are credited directly to your balances
* Incoming transfers create transactions in your ledger
* SWIFT support enables cross-border funding in select regions
***
## Summary
* Virtual accounts enable you to receive funds via local and international bank transfers
* Supported regions define where accounts can be opened
* Local and SWIFT funding methods vary by region
* They provide flexible infrastructure for collecting and funding workflows
# Withdraw funds
Source: https://docs.withacclaim.com/guides/treasury/withdraw-funds
Withdraw funds from your Treasury accounts to your external bank account.
Withdrawing funds allows you to **move money from your Treasury accounts to an external settlement account** owned by your entity.
This is used to transfer funds out of Acclaim and back into your bank account.
***
## How withdrawing funds works
Withdrawing funds follows a simple flow: **initiate**, **process**, and **settle**.
1. **Select an account and amount**
Choose the Treasury account and specify the amount to withdraw.
2. **Select a settlement account**
Choose the external bank account where funds will be sent.
3. **Process the withdrawal**
The transfer is initiated through the appropriate banking network.
4. **Funds are delivered**
Once processed, funds arrive in your settlement account.
***
## Settlement accounts
Withdrawals are sent to a **settlement account** owned by your entity.
* Settlement accounts are external bank accounts
* They must be configured and verified
* Funds are transferred directly to these accounts
Settlement accounts are typically used for:
* Moving funds back to your operating bank account
* Managing treasury liquidity outside of Acclaim
***
## Timing and settlement
Withdrawal timing depends on the payment rail and region.
* Some methods may be near real-time
* Others take multiple business days
* Processing timelines depend on banking networks and cutoffs
Funds are debited from your Treasury account when the withdrawal is initiated or processed.
***
## Balance requirements
Withdrawals use your **available balance**.
* You must have sufficient available funds in the selected account
* Pending funds cannot be withdrawn
* Withdrawals reduce your available balance
If funds are not available in the desired currency, you can convert using FX before withdrawing.
***
## Tracking withdrawals
You can track withdrawals in the Console.
Each withdrawal creates a transaction that includes:
* Amount and currency
* Status (pending or completed)
* Source account
* Destination settlement account
* Timestamp
You can also track updates via webhooks.
***
## Reconciliation
Withdrawals should be reconciled against your external bank account.
To reconcile:
* Match withdrawal transactions to bank deposits
* Verify amounts and timing
* Track settlement completion
This ensures alignment between Treasury and your external accounts.
***
## Best practices
* Verify settlement account details before initiating withdrawals
* Ensure sufficient available balance before withdrawing
* Account for settlement timing in your planning
* Monitor withdrawals until completion
***
## Summary
* Withdraw funds by transferring money to a settlement account
* Settlement accounts are external bank accounts owned by your entity
* Withdrawals use available balance and reduce your Treasury funds
* Transactions provide full visibility and reconciliation support