Integration options

YAXI offers multiple integration options across a range of platforms.

The integration options are:

Client libraries
HTTP APIs
Drop-in UI flows
UI components

Supported platforms include:

Web
Android and iOS
Windows, macOS and Linux
React Native

Feel free to reach out if you need support for other platforms.

Client libraries

Our client libraries allow you to build all or part of the UI yourself.

The client provides a convenient interface to YAXI’s services and any associated dialogs. Behind the scenes, it handles the following:

Establishing the initial connection to the service.
Verifying that the service is running the expected software in secure, confidential hardware.
Setting up a secure, end-to-end encrypted channel that remains private between the user and their bank.

We currently provide the following bindings:

More bindings are available on demand (C++, Python).

Bank logos

Every connection info carries a logoId that identifies the bank’s brand assets, which are its trademarks. YAXI runs a best-effort logo service that publishes these assets under the base URL https://logos.yaxi.tech/banks/. Each resource in the table below is a path relative to that base.

Resource Description

Resource	Description
`<logoId>.svg`	Vector logo. The service also rasterizes each logo to `<logoId>-<size>.png` in 32, 64, 128, and 256 pixels.
`<logoId>-mask.svg`	Single-color silhouette for tinting or masking, with matching `<logoId>-mask-<size>.png` PNGs. The service omits this variant when the regular logo already works as a mask.
`manifest.json`	Lists the available files and brand colors for every logo. The companion `manifest.schema.json` describes the format.
`catalog.json`	Holds the same metadata with the SVGs inlined, so a single file covers every logo. The companion `catalog.schema.json` describes the format.
`logos-banks.zip`	Bundles every asset into one archive.

<logoId>.svg

Vector logo. The service also rasterizes each logo to <logoId>-<size>.png in 32, 64, 128, and 256 pixels.

<logoId>-mask.svg

Single-color silhouette for tinting or masking, with matching <logoId>-mask-<size>.png PNGs. The service omits this variant when the regular logo already works as a mask.

manifest.json

Lists the available files and brand colors for every logo. The companion manifest.schema.json describes the format.

catalog.json

Holds the same metadata with the SVGs inlined, so a single file covers every logo. The companion catalog.schema.json describes the format.

logos-banks.zip

Bundles every asset into one archive.

For example, Revolut’s logoId is revolut, so its <logoId>.svg resolves to https://logos.yaxi.tech/banks/revolut.svg. If a logoId has no matching asset, fall back to the generic _default.svg or render the bank’s initials.

For a production integration, bundle logos-banks.zip or catalog.json into your application and load each logo from there. Bundling lets your bank list render on every platform without a network round-trip, and it keeps your application independent of the service.

Drop-in UI flows

Drop-in UI flows offer a quick and easy integration with minimal effort, but with limited customization. You provide the necessary parameters, and we handle the user journey, delivering the results to you.

UI components

If you need more control over the flow, you can use our customizable components to render elements like a bank list, a credentials form, and more. You can mix and match components as needed, guiding the user through the process while only using the ones that fit your needs.

HTTP API

If you encounter issues with our client libraries, you can opt to use our HTTP APIs directly. However, we strongly recommend using the libraries, as they handle key features like verification and cryptography for you. Keep in mind that our libraries are open source and fully customizable.

Only consider interacting directly with our HTTP API if you really know what you are doing.