Skip to content

Synopsis

gln [global-options] standing-orders add --file <path>

Options

Argument or flagTypeRequiredDefaultDescription
--filepathyes-JSON payload describing the new standing order to create.

Request file fields

FieldTypeRequiredDescription
source_ibanstringyesIBAN of the account the standing order is debited from.
source_bicstringyesBIC of the source account institution.
source_namestringyesAccount holder name as it should appear on the order.
recipient_ibanstringyesIBAN of the recipient account.
recipient_bicstringyesBIC of the recipient account institution.
recipient_namestringyesRecipient name as it should appear on the order.
amountstringyesDecimal amount (e.g. "1.00").
currencystringyesISO 4217 currency code (e.g. "EUR").
purposestringyesFree-text purpose / remittance line.
first_executionstringyesFirst execution date in YYYYMMDD.
intervalstringyesExecution interval. FinTS uses "M" (monthly), "W" (weekly), "Q", "Y".
execution_daystringyesDay-of-period the order runs on.
end_to_end_referencestringnoEnd-to-end reference string. Omit or leave empty if unused.
last_executionstringnoLast execution date in YYYYMMDD. Omit or leave empty for open-ended.

All fields must be JSON strings. currency and interval are required; the C API defaults of "EUR" / "M" are deliberately not honored by the CLI so the request is fully explicit.

Description

Wires gln_add_standing_order to the FinTS backend resolved via the active profile. The CLI parses the request file, opens the backend with the PIN/secret material from the profile, and submits the standing order. If the backend signals that a TAN is required, the continuation is saved to disk and the response describes how to resume.

Status and exit codes

StatusExitMeaningContinuation
ok0Standing order accepted by the bank.-
action_required10Bank requires a TAN. The response envelope includes a resume_file path.Saved at resume_file.
error1Validation, transport, or backend error.-

See also