Package-level declarations
YAXI Open Banking wire DTOs (services, tickets, credentials, dialogs, responses, errors).
Types
Account access exceeded the user's consent. Only the non-interactive transactions refresh path raises this error; the interactive transactions flow does not.
Payment account exposed by a service connection.
Per-account container holding zero or more typed balances.
Field of an Account that can be referenced in filters or requested from the service.
Predicate applied to accounts when invoking the accounts service.
Identifier of an account, used when referencing creditor or debtor accounts in payment-related requests.
Reference to an account by IBAN, with an optional ISO 4217 currency code for multi-currency accounts.
Authenticated result of a successful accounts service call.
Request body for the interactive accounts service.
Status of an Account.
Type of an Account (mostly aligned with ISO 20022 ExternalCashAccountType1Code).
Monetary amount paired with an ISO 4217 currency code.
Wrapper around an authenticated YAXI service response carried as a JWT.
Thrown when a JWT-bearing response cannot be decoded, the JWT is structurally malformed, its body is not valid JSON, the data claim is missing, or the claim's value does not match the expected typed payload shape.
Single account balance reported by the balances service.
Top-level payload returned by the balances service.
Authenticated result of a successful balances service call.
Request body for the interactive balances service.
Kind of balance reported for an account.
Bank transaction code attached to a Transaction.
Per-transaction batch metadata: count of grouped transactions plus their individual details where the provider supplied them.
Per-entry details for a transaction inside a batch. Same fields as Transaction minus the booking dates and status (those are carried by the parent transaction).
The user canceled the flow (rejecting an SCA prompt or letting it time out). Ask whether the user wants to start again.
Who bears the charges for a transfer.
Authenticated result of a successful collect-payment service call.
Request body for the interactive collect-payment service.
Opaque context returned alongside a Confirmation dialog, a Redirect, or a RedirectHandle. Pass it back to one of the confirm* methods on RoutexClient to continue the flow.
Opaque connection data returned by a successful interactive service call.
Optional extra fields a search may request the server to populate on each returned ConnectionInfo.
Identifier of a specific service connection (bank or other provider integration).
Metadata describing a single service connection (bank or other provider integration).
Type of connections to consider when searching.
The recurring consent attached to the call's ConnectionData has expired. The YAXI service emits this only when the call carried Credentials.connectionData (or, for RoutexRefreshClient, a stored ConnectionData). Restart the flow without ConnectionData so the user can renew consent.
ISO 3166-1 ALPHA-2 country code.
User credentials for a given service connection.
Requirements for user identifier and password a connection accepts.
Postal address of a creditor.
Reference to a debtor account for the collect-payment service.
Serializes a BigDecimal as a plain JSON string ("-12.34", "1200.00"; never scientific notation), preserving the original number of fractional digits.
User dialog returned by an interactive service call.
Context of a user dialog, distinguishing what the dialog is asking the user about.
Data defining the interactive part of a Dialog.
Single option inside a DialogInput.Selection.
Reference to a debtor account by encrypted-IBAN ciphertext, for the collect-payment service. Opaque on the client; the ciphertext is produced by the caller's backend with its API secret following the Opaque Data protocol so the frontend never sees the underlying IBAN.
Currency conversion attached to a Transaction.
Fee attached to a transaction, transfer detail, or batch entry.
Fallback error carrying the raw HTTP status and response body. Returned by RoutexErrorDispatcher.dispatch when no typed error variant matches; typically when the YAXI service introduces a new error variant ahead of an updated SDK. Display a generic technical-error message; report internally if it recurs.
Image data for a dialog.
Opaque context returned alongside a Selection or Field dialog input. Pass it back to one of the respond* methods on RoutexClient together with the user-supplied response to continue the flow.
Type of an input field. May be used for showing hints or dedicated keyboard layouts and for applying input restrictions or validation.
Marks declarations that are internal in the Routex client API. Their signatures and semantics may change between releases without warnings and without providing migration aids; external use is unsupported.
The service call requires user interaction to complete.
The bank rejected the supplied user identifier, password, or TAN input. Show userMessage if present and let the user re-enter their credentials.
Thrown when a raw JWT string is not a valid Routex ticket (bad structure, missing claims, or a service claim that does not match the typed Ticket subclass).
Date-or-date-time value as used by the transfer service's requestedExecutionDate.
Request body for the non-interactive accounts endpoint.
Request body for the non-interactive balances endpoint.
Envelope for non-interactive service responses returned by RoutexRefreshClient.
Request body for the non-interactive transactions endpoint.
The requested resource was not found. On transactions this typically means the supplied AccountReference is unknown to the bank: verify the reference. info and trace also raise this.
Counterparty (creditor or debtor) referenced by a Transaction.
Reason why a payment failed.
The bank rejected the payment (for example, an exceeded transfer limit). Show userMessage if present; code carries a machine-readable reason. Specific to collectPayment.
Payload returned by the collect-payment service.
Payment product used when initiating a transfer.
Progress status of a payment initiated via a service.
Requested time period falls outside what the bank supports. Show userMessage if present. The transactions flow raises this.
The bank reported a technical failure (often maintenance). For payment-style services this does not guarantee the operation failed: the transaction may still have executed. Tell the user a technical error occurred and to retry later.
Transient condition on the provider side.
User redirect.
Incomplete user redirect.
Base class for all typed errors returned by the YAXI Open Banking services.
Decodes wire-form error responses from the YAXI service into typed RoutexError subclasses. Falls back to NotFound for HTTP 404 and to HttpResponse for any status whose body the dispatcher cannot recognize as a known variant.
Authenticated result wrapper carried in the JWT body's data claim of every service response.
Predicate applied when searching for service connections.
Level of secrecy for an input field.
The bank blocked the service for this user. Common causes: the user must accept new terms, change their password, or the account itself is blocked. Show userMessage if present; otherwise pick a generic message based on code.
Reason why a service is blocked for the user.
Opaque session token returned by a YAXI Open Banking service call.
Services an account can be filtered by for potential support.
A Routex service ticket. The raw string is a JWT whose data.service claim names the specific service it authenticates; the subclasses pin that service at the type level so the Kotlin compiler rejects passing an Accounts ticket to balances() and vice versa.
The routex service rejected the Ticket. When code is TicketErrorCode.EXPIRED, the user took too long to finish the flow: issue a fresh ticket and start over. Any other code indicates a configuration error in the calling application (wrong key, environment mismatch, ticket / service mismatch).
Reason why a ticket was rejected.
Single transaction returned by the transactions service. Most fields are optional; provider coverage varies and a typical Transaction populates a small subset. The required fields are status and amount.
Authenticated result of a successful transactions service call.
Request body for the interactive transactions service.
Status of a single Transaction.
Payload returned by the transfer service.
Details of a single credit transfer inside a TransferServiceRequest.
Authenticated result of a successful transfer service call.
Request body for the interactive transfer service.
The bank refused the recurring consent attached to the call's ConnectionData. The YAXI service raises this only when the call carries Credentials.connectionData. Restart the flow without Credentials.connectionData so the user can grant a fresh consent.
The bank or another upstream returned a response YAXI could not process. For payment-style services this does not guarantee the operation failed: the transaction may still have executed. Show userMessage if present, then consider prompting the user to share a diagnostics archive with YAXI.
A value passed to the call was malformed (for example, an invalid IBAN). The error field explains what was wrong. This error targets the application developer: validate inputs before submitting them, especially when they came from the user.
The bank cannot perform the requested operation for this combination of inputs. Examples: an instant payment was requested but the bank only supports the standard variant, or the connection does not support the chosen service. See Instant by default. Show userMessage if present.
Reason why a payment product is not supported for a given request.
Properties
Functions
Build an IsoDateTimeOrDate.Date from a java.time.LocalDate.
Build an IsoDateTimeOrDate.NaiveDateTime from a java.time.LocalDateTime.
Build an IsoDateTimeOrDate.OffsetDateTime from a java.time.OffsetDateTime.
Convert a java.math.BigDecimal to the multiplatform BigDecimal used in Amount, Balance, and other monetary fields.
Convert this multiplatform BigDecimal to a java.math.BigDecimal, preserving the original number of fractional digits.