Standing Orders - Varinomics

Standing-order operations are C API surfaces backed by FinTS. They use typed request structs and return list or submission handles borrowed from gln_backend_result_t.

Operations

Operation	Request	Result accessor
`gln_retrieve_standing_orders`	`gln_list_standing_orders_request_t`	`gln_get_backend_result_standing_orders`
`gln_add_standing_order`	`gln_add_standing_order_request_t`	`gln_get_backend_result_standing_order_submission`
`gln_modify_standing_order`	`gln_modify_standing_order_request_t`	`gln_get_backend_result_standing_order_submission`
`gln_delete_standing_order`	`gln_delete_standing_order_request_t`	`gln_get_backend_result_standing_order_submission`

Backend Support

Operation	Supported backends
`list_standing_orders`	FinTS
`add_standing_order`	FinTS
`modify_standing_order`	FinTS
`delete_standing_order`	FinTS

Probe support at runtime with gln_check_backend_operation_support before enabling a command against an arbitrary backend handle.

List Request and Result

gln_list_standing_orders_request_t request = {0};
gln_default_list_standing_orders_request(&request);
request.iban = "DE02120300000000202051";

gln_retrieve_standing_orders returns gln_standing_orders_t.

Accessor	Meaning
`gln_get_standing_orders_count`, `gln_get_standing_order_at`	Enumerate borrowed order rows.
`gln_get_standing_order_recipient_name`, `gln_get_standing_order_recipient_iban`	Recipient identity.
`gln_get_standing_order_amount`, `gln_get_standing_order_currency`	Payment amount.
`gln_get_standing_order_purpose`	Payment purpose.
`gln_get_standing_order_first_execution`, `gln_get_standing_order_next_execution`, `gln_get_standing_order_last_execution`	Schedule dates.
`gln_get_standing_order_interval`, `gln_get_standing_order_execution_day`	Schedule cadence.
`gln_get_standing_order_reference`	Bank order reference used for modify/delete.

Add, Modify, and Delete Requests

The three request structs share the payment and schedule shape. Modify and delete additionally require order_reference, so a delete request carries the bank order reference plus the full standing-order payload and schedule fields.

Field group	Required	Meaning
Source identity	yes	`source_iban`, `source_bic`, `source_name`.
Recipient identity	yes	`recipient_iban`, `recipient_bic`, `recipient_name`.
Payment detail	yes	`amount`, `currency`, `purpose`.
Optional reference	no	`end_to_end_reference_or_null`.
Schedule	yes	`first_execution`, `interval`, `execution_day`; optional last execution.

gln_add_standing_order_request_t request = {0};
gln_default_add_standing_order_request(&request);
request.source_iban = "DE02120300000000202051";
request.source_bic = "BYLADEM1001";
request.source_name = "Example GmbH";
request.recipient_iban = "DE89370400440532013000";
request.recipient_bic = "COBADEFFXXX";
request.recipient_name = "Landlord GmbH";
request.amount = "875.00";
request.purpose = "Rent";
request.first_execution = "2026-06-01";
request.execution_day = "01";

gln_default_add_standing_order_request, gln_default_modify_standing_order_request, and gln_default_delete_standing_order_request initialize currency to "EUR" and interval to "M".

Submission Result

gln_add_standing_order, gln_modify_standing_order, and gln_delete_standing_order return gln_standing_order_submission_t.

Accessor	Meaning
`gln_get_standing_order_submission_status`	Summary status.
`gln_get_standing_order_submission_vop_id`	VoP id when the bank produced one.
`gln_get_standing_order_submission_vop_result_code`	VoP result code.
`gln_get_standing_order_submission_vop_alternate_name`	Alternate recipient name.
`gln_get_standing_order_submission_vop_explanatory_text`	Bank explanatory text.

Standing-order writes can pause for TAN, decoupled approval, or VoP confirmation. Resume them with gln_resume_continuation.