routex-client
v0.5.0
Published
YAXI routex client
Readme
routex-client
A client for YAXI's Open Banking services.
Changelog
[0.5.0] - 2026-02-20
Added
RoutexClient.systemVersionRoutexClient.transfer,RoutexClient.respondTransfer,RoutexClient.confirmTransfer
Removed
RoutexClient.measurement
Fixed
AccountFilter.anywith more than two elementsPaymentFailedException.userMessagewas alwaysundefined
[0.4.8] - 2026-02-04
Added
ConnectionInfo.password
[0.4.7] - 2026-01-12
Added
encryptedIbanSearchFilterencryptedIbanincollectPayment'saccountaccepts a Base64-encoded string as alternative to theUint8Array
[0.4.6] - 2025-12-08
Fixed
collectPaymentwithout givenaccountargument
[0.4.5] - 2025-11-25
Added
encryptedIbanas alternative toibanincollectPayment'saccountoption
[0.4.4] - 2025-11-09
Fixed
- Use production environment if no explicit URL is passed to
RoutexClient
[0.4.3] - 2025-11-06
Fixed
yaxi-ticket-idheader value in requests
[0.4.2] - 2025-09-23
Fixed
- Build failures with recent @noble packages
[0.4.1] - 2025-09-11
Fixed
recurringConsentsis now optional
[0.4.0] - 2025-09-11
Added
recurringConsentsoption forRoutexClient.accounts,RoutexClient.collectPayment, andRoutexClient.transactionsRoutexClient.balances,RoutexClient.respondBalances,RoutexClient.confirmBalancesDialogContext.VopConfirmation,DialogContext.VopCheckConfirmation.pollingDelaySecsTicketExceptionCodehas two new variants:ExpiredKey: The API key is expired.KeyEnvironmentMismatch: The API key cannot be used for this environment.
- The
RoutexClientconstructor now takes an optionalrequestRetryFactoryoption to retry failed requests. You can pass a factory for custom policies or useretryRequestExceptionNTimesPolicyto retry operations that failed due to aRequestException. For example,{ requestRetryFactory: () => retryRequestExceptionNTimesPolicy(1) }would retry one time.
Removed
InvalidRedirectUriException
Fixed
- The required version for
routex-settlementis now0.1.3. This fixes a bug that if the first requests happened concurrently, some of them could result in aTicketException: Invalid "yaxi-ticket" header. - Initialization of
UnsupportedProductException
Changed
RoutexClientnow takes an object of options instead of a single URL as argument. For backwards compatibility, it's still possible to pass a URL as a single argument.
[0.3.4] - 2025-06-25
Changed
TypeErrors from thefetchmethod get translated toRequestExceptions
Fixed
- Parsing of service errors
[0.3.3] - 2025-06-11
Added
ServiceBlockedException.code,ServiceBlockedCodeUnsupportedProductException.reason,UnsupportedProductException.userMessage,UnsupportedProductReason
[0.3.2] - 2025-05-28
Added
DialogContext.PaymentStatus
[0.3.1] - 2025-05-27
Added
ProviderErrorException,ProviderErrorCode
[0.3.0] - 2025-05-23
Added
RoutexClient.setRedirectUriRoutexClient.transactions,RoutexClient.respondTransactions,RoutexClient.confirmTransactionsremoveCredentialsOBResponseAccountStatus
Changed
- This is a pure JS library now, i.e., does not include WebAssembly anymore
ResponseException.responseis now of typeResponsestoreCredentialsandloadCredentialstake an identifier argument nowResult,Dialog,Redirect, andRedirectHandlenow extendOBResponse, providingfromJSONandtoJSONmethods
Removed
RoutexClientInterfaceResponsetype (seeOBResponseclass)ConnectionType
Fixed
PaymentFailedException.name
[0.2.0] - 2025-01-29
Added
RoutexClient.collectPaymenttakes an optionalcurrencyattributeDialogContext.Redirectfor redirect pollingTicketExceptionfor any error related to the provided ticketcodeanduserMessageonPaymentFailedException- Inherit docs for
RoutexClient storeCredentialsandloadCredentialsto store encrypted credentials in the user's browser
Changed
- The
traceIdmethod does not return aPromiseanymore, but an immediate result - Renamed
errorMessageon exception classes touserMessage - Removed support for Node.js 18
Removed
Confirmation.primaryLabelSelection.primaryLabelField.primaryLabelActionssourceon exception classesUnexpectedValueException.errorMessage
