---
title: "Understand payout settings"
description: "Understand payout schedules, destinations, aging rules, and automatic payout mode."
canonical: "https://studio.inttegro.com/guides/understand-payout-settings"
format: inttegro-machine-docs/v1
language: "Go"
sdk_version: "v11.0.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/go/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 508
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "curated"
recommended_mcp_tools: ["get_payout_settings","get_payout"]
estimated_tokens: 3364
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Read one account’s payout mode, aging rule, and currency-to-destination map before explaining or changing settlement; a stored FX flag is not cross-currency authorization.

### Five questions

#### Q1. What scope does the settings response describe?

The settings belong to the account used for the request, not every account in an organization. Use [payout settings](https://studio.inttegro.com/machine/go/api/payouts.md#get-payout-settings) to read the current mode and routing before acting.

#### Q2. What does automatic versus manual mean?

Automatic means Inttegro creates eligible payouts on the configured cadence; manual stops automatic creation and requires explicit scheduling. Neither mode bypasses the same transaction aging and destination checks. See [schedule](https://studio.inttegro.com/machine/go/guides/understand-payout-settings.md#schedule).

#### Q3. When does a transaction become eligible?

Read the returned aging rule; the documented default is an exact 168 hours after settlement, not merely the next calendar week. The next payout after that time may include it if other checks pass. See [aging rule](https://studio.inttegro.com/machine/go/guides/understand-payout-settings.md#aging-rule).

#### Q4. What if a currency has no destination key?

Automatic payouts cannot be created for that currency. Confirm the mapped financial account is active, same-currency, and push-enabled; a manual schedule still supplies a destination ID directly. See [destinations](https://studio.inttegro.com/machine/go/guides/understand-payout-settings.md#destinations).

#### Q5. Can MCP fix settings or approve FX?

No. [get_payout_settings](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#get_payout_settings) is a read tool; use the [Payouts API](https://studio.inttegro.com/machine/go/api/payouts.md) for changes. A stored FX flag is informational unless the specific payout operation supports the cross-currency path; current destinations must match payout currency.

## Document content

# Understand payout settings

Payout settings answer two questions: when Inttegro should create automatic payouts, and which financial account should receive each currency. They apply to one Inttegro account, not the whole organization.

> Mcp Guide Callout is interactive content. Use the canonical page to view it.

Use [Get payout settings](https://studio.inttegro.com/machine/go/api/payouts.md#get-payout-settings) for the exact response. Use this guide to interpret the fields.

## The settings object

The read response returns a [`Settings`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) object.

| Field                                                                                  | Meaning                                                                                      |
| -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| [`Settings.Schedule`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup)     | Current payout mode and timing. Omitted only if a schedule cannot be resolved.               |
| [`Settings.Destinations`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) | Map of currency code to financial account ID. Always present and may be empty.               |
| [`Settings.FxEnabled`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup)   | Stored FX setting when present. It does not make cross-currency payouts available by itself. |

Lookup and mutation responses expose slightly different schedule shapes. When you are implementing a request or parser, follow the [Payouts API reference](https://studio.inttegro.com/machine/go/api/payouts.md) for the operation you call.

## Schedule

[`Settings.Schedule`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) tells you whether Inttegro creates payouts automatically.

| Field                                                                                          | Automatic mode                                                                                                 | Manual mode                                                                                                    |
| ---------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| [`Settings.Schedule.Type`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup)        | `"automatic"`      | `"manual"`         |
| [`Settings.Schedule.Name`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup)        | Usually `"weekly"` | Usually `"manual"` |
| [`Settings.Schedule.Interval`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup)    | `"weekly"`     | `"manual"`     |
| [`Settings.Schedule.ScheduleOn`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) | `"sunday"`  | `"manual"`  |
| [`Settings.Schedule.Description`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) | Human-readable schedule summary.                                                                               | Human-readable schedule summary.                                                                               |

When [`Settings.Schedule.Type`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) is `"automatic"`, Inttegro creates payouts on the configured cadence when eligible funds and destinations exist. The default automatic schedule runs weekly on Sunday at midnight UTC.

When [`Settings.Schedule.Type`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) is `"manual"`, Inttegro does not create automatic payouts. You create them yourself with [Schedule a payout](https://studio.inttegro.com/machine/go/api/payouts.md#schedule-a-payout).

## Aging rule

[`Settings.Schedule.AgingSpec`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) controls when balance transactions become payout-eligible.

| Field                                                                                                | Meaning                                                                                                                                                                                     |
| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`Settings.Schedule.AgingSpec.TPlus`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) | Minimum age before a balance transaction can be included. The default is `"168h"`. |
| [`Settings.Schedule.AgingSpec.Label`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup)  | Stable label for the aging rule, such as `"168_hours"`.                             |
| [`Settings.Schedule.AgingSpec.Abide`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup)  | Enforcement mode. Public settings currently use strict enforcement.                                                                                                                         |

The aging window is exact. If a payment settles Monday at 15:00 UTC and [`Settings.Schedule.AgingSpec.TPlus`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) is `"168h"`, it becomes eligible the following Monday at 15:00 UTC. The next payout after that moment can include it.

## Destinations

[`Settings.Destinations`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) maps payout currencies to financial accounts:

```json
{
  "destinations": {
    "ghs": "fa_H3cNv7pQf9WbLt2mJs6yXrPq4Kz1Vd5G0aEiUo"
  }
}
```

Read it as “send eligible GHS payouts to this financial account.”

Destination rules:

- Currency keys are lowercase currency codes.
- The financial account must be connected to the same Inttegro account.
- The account currency must match the map key.
- The account must be active and able to receive payouts.
- A missing currency key means automatic payouts cannot be created for that currency.
- Updating the map affects future payouts, not payouts that are already scheduled or executing.

Manual payout requests still provide [`DestinationID`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#ScheduleParams.DestinationID) directly. The settings map is primarily automatic-routing configuration, not a reason to omit the destination from a manual payout request.

## FX setting

[`Settings.FxEnabled`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) may appear when a setting has been stored. Treat it as informational unless the
API reference for the payout operation explicitly supports the cross-currency
flow you need.

Today, payout destinations must use the same currency as the funds being paid out.

## Operational checks

Use payout settings to answer common operations questions.

| Question                             | Check                                                                                                                                                                                                        |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Are automatic payouts on?            | [`Settings.Schedule.Type`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) should be `"automatic"`. |
| Which day do automatic payouts run?  | [`Settings.Schedule.ScheduleOn`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup).                                                                                                              |
| How long do funds age before payout? | [`Settings.Schedule.AgingSpec.TPlus`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup).                                                                                                        |
| Will GHS funds route anywhere?       | [`Settings.Destinations.Ghs`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup) should be present and point to an active GHS financial account.                                                   |
| Why did no automatic payout run?     | Check [`Settings.Schedule.Type`](https://pkg.go.dev/github.com/inttegro/inttegro-sdk-go/v11@v11.0.1/payout#SettingsLookup), the destination map, eligible balance transactions, and open payouts for the destination.                     |
| Can I pay out in another currency?   | Confirm both supported currency coverage and a same-currency destination.                                                                                                                                    |

## Related resources

- [Payouts API reference](https://studio.inttegro.com/machine/go/api/payouts.md) - Exact settings, scheduling, and destination contracts.
- [How payouts use your balance](https://studio.inttegro.com/machine/go/guides/understand-payouts.md) - Selection, refund interactions, statuses, and reconciliation.
- [Manage payout destinations](https://studio.inttegro.com/machine/go/guides/manage-payout-destinations.md) - Connect and route payout accounts.
- [Enable automatic payouts](https://studio.inttegro.com/machine/go/guides/enable-automatic-payouts.md) - Switch back to automatic weekly settlement.
- [Disable automatic payouts](https://studio.inttegro.com/machine/go/guides/disable-automatic-payouts.md) - Switch to manual settlement.
