title: Landsbankinn Connector Capabilities - Agent Guide audience: developer, integrator keywords: landsbankinn, cloud events, payment batch, payment result, unpaid invoice, payment slip, claim mapping, account verify, agent workflow

locale: en-us

Landsbankinn Connector Capabilities - Agent Guide

This guide summarizes the Landsbankinn capabilities exposed by the connector and gives agent-safe execution patterns.

Capability Groups

Group	Primary message types	Purpose
Discovery and contracts	`Help.Landsbankinn.Get`, `Help.Implementation.Get`	Find available subjects and load exact request/response contract before execution.
Account and card read APIs	`Landsbankinn.Account.Verify`, `Landsbankinn.Card.Query`, `Landsbankinn.Skema.Statement.Get`, `Landsbankinn.Statement.Get`	Verify accounts and read card/account statement information.
Claims and unpaid invoices	`Landsbankinn.UnpaidInvoice.Query`, `Landsbankinn.PaymentSlip.Query`, claim query message types	Discover claim candidates and read payable amount details.
Payments (async)	`Landsbankinn.Payment.Batch`, `Landsbankinn.Payment.Result`, `Landsbankinn.Payment.ResultBatch`	Submit payment batches and poll final per-line outcomes.
Market/reference data	`Landsbankinn.CurrencyRates.Get`, `Landsbankinn.Index.Get`	Retrieve exchange rates and index values.

Agent-Safe Execution Pattern

Call Help.Landsbankinn.Get to discover subjects.
Call Help.Implementation.Get with the exact subject before sending business payload.
Run pre-checks:

Transfer line destination checks: Landsbankinn.Account.Verify
Claim line candidate checks: Landsbankinn.UnpaidInvoice.Query
Claim line amount details: Landsbankinn.PaymentSlip.Query

Submit one Landsbankinn.Payment.Batch request per user intent unless user explicitly asks for multiple submissions.
Persist paymentsId and logEntryNo.
Poll with Landsbankinn.Payment.Result or Landsbankinn.Payment.ResultBatch until terminal status.

Confirmed Learnings Reflected in Current Help Contracts

Landsbankinn.Payment.Batch claim lines:

JSON uses kind = "PaymentSlip"
Connector maps to PaymentTypes wire element Claim
Agents must use JSON contract, not handcrafted SOAP XML

Payment slip query key date:

Use gjalddagi as the lookup key date
eindagi may differ and must not be substituted

Unpaid invoice matching:

Connector applies exact-first remaining-amount matching
Then uses tolerance matching when needed
Use matchingAmountDifference and matchingUsedTolerance for explainability

Tracking evidence:

Always capture paymentsId and logEntryNo
Poll result message types are authoritative for final status and line outcomes
In environments where internal tracking tables are protected from generic reads, rely on result payloads and request-log linkage

Payment Batch Pre-check Policy

Use this policy by default:

Transfer lines: run Landsbankinn.Account.Verify
Claim/payment-slip lines: run Landsbankinn.UnpaidInvoice.Query, then Landsbankinn.PaymentSlip.Query

This policy reduces avoidable bank rejections and produces clearer agent decision evidence.

Terminal Status Interpretation

Status	Meaning
`InProgress`	Bank is still processing. Continue polling.
`NotConfirmed`	Waiting for online bank approval.
`Completed`	All lines succeeded.
`CompletedWithErrors`	Mixed outcome. Read per-line errors.
`OnHold`	Scheduled for future date.
`Cancelled`	Cancelled before execution.

Implementation Notes for Integrators

Normalize accounts and kennitala values to digits when preparing requests.
Use ISO dates (YYYY-MM-DD) in all request dates.
Treat returned amounts/costs as source of truth; do not recalculate bank totals in code.
Keep correlation IDs or subject values unique per user intent to simplify traceability.