IBEx Wallet

📖 Documentation

Introduction

IBEx Wallet provides wallet solutions for users who want to perform blockchain transactions, simplified by:

• Gas sponsorship — on-chain write fees are covered by the platform (Bundler & Paymaster).
• Secure & simplified key management — authentication powered by FIDO2 passkeys, with deterministic key derivation for Safe smart wallets and EOA wallets (EIP-7702).
• Configurable privacy — anonymity level decided based on account usage (optional KYC, domain-scoped data isolation).

Range of Services

The IBEx.Fi API sign-up / sign-in flow issues a session token (JWT). Present this token in the Authorization header (Bearer) to access a range of services:

• KYC — manage your personal data allowing you access to permissioned services.
• Wallet modules — recovery, multi-sig, allowance, threshold.
• Paymaster — sponsored wallet operations.
• RPC — wallet-related chain operations (sign, transfer, swap).
• FIAT — card/bank transfer payment acquisition on dedicated & nominative EU IBAN account.

Set of API

IBEx.Fi groups endpoints into three categories for clarity:

• Authentication — sign-up/in, session, refresh.
• Privacy — domain-scoped user data and consented information.
• Blockchain — balances, transactions, Safe operations.

Multichain note: whenever a schema includes blockchainId, clients may pass it via the X-Blockchain-Id header (preferred) or as a query parameter.

WTF is rpId?

The rpId (Relying Party Identifier) is a WebAuthn concept that scopes passkeys to a specific domain. In IBEx, the rpId acts as your tenant identifier: it isolates your users, passkeys, wallets, and data from other tenants while using the same wallet as a service platform to easily deploy self-custody wallets and sponsor their transactions. Everything in IBEx is organized around the rpId.

1. The rpId is your domain

Your rpId is extracted from the request hostname and defines your tenant space (passkeys, users, wallets).

• https://foo.domain → rpId: foo.domain
• https://app.foo.domain → rpId: app.foo.domain

2. Subdomains inherit the parent rpId

A passkey created for foo.domain will work on any subdomain of that domain:

• https://foo.domain → rpId: foo.domain
• https://app.foo.domain or https://baz.foo.domain → can use rpId: foo.domain

3. Calling IBEx API: direct URL or CNAME

Your application can call the IBEx API directly, or through a CNAME that you control allowing white label integration:

• https://foo.domain → calls https://passkeys.ibex.fi (direct)
• https://foo.domain → calls https://passkeys.foo.domain which is a CNAME to passkeys.ibex.fi

The CNAME can follow any naming convention — there is no required prefix.

4. Cross-domain passkeys with Related Origin Requests (ROR)

ROR allows a passkey created on one domain to authenticate on a completely different domain:

• https://foo.domain → rpId: bar.domain

See the full ROR documentation for setup and configuration.

Bundler / Paymaster

IBEx.Fi implements the ERC-4337 (Account Abstraction) standard for gasless transactions:

• Bundler — collects UserOperations and bundles them into a single on-chain transaction via eth_sendUserOperation.
• Paymaster — sponsors gas fees for UserOperations via pm_sponsorUserOperation.

See the full Account Abstraction documentation for setup and configuration.

IBX Token

Within a given rpId (tenant / Builder), the IBX token pays for API services and on-chain operations. Gas fees are sponsored by the bundler/paymaster. Service costs are charged in IBX tokens, managed by the Builder. See the Builders page for details.

Reference Pages

• Supported Blockchains
• Safe Global Wallets
• Related Origin Requests (ROR)
• Passkey-based wallets
• EOA Wallets (EIP-7702)
• Key Derivation (KDF) based wallets
• Bundler & Paymaster
• BlockChainReader Endpoints
• IBEx Safe Endpoints
• Solana Integration
• Bitcoin Integration

---

🔨 How to Build

Create your dApp in minutes with our step-by-step integration guides. Learn how to deploy wallets, deliver IBANs, and implement token swaps.