# Feature Availability

What every tenant can use today, what Aurea turns on for your tenant when you ask, and what is coming. The other pages mark a feature of the second kind with [Coming soon, upon request](https://docs.aureahub.com/docs/feature-availability.md).

## Overview

- **On for every tenant**: call it now. Some features still depend on how your tenant is set up — its wallet mode, the chains and tokens enabled for it — and your tenant's own settings, which its pages describe.
- **Coming soon, upon request**: ask your Aurea contact ([contact us](https://www.aureahub.com/contact)). Until it is on, the feature's routes answer as its page says — usually a refusal with a stable `details.code`, or an empty list — and nothing else changes for your tenant.
- **Institutional tenants.** A tenant on the institutional security profile has every control of *Recorded Today, Enforced on Request* at its strongest, by its profile, and signs with [server credentials](https://docs.aureahub.com/docs/guide-server-credentials.md). The profile is agreed with Aurea.
- **Coming**: not offered in production yet. These features are not documented beyond their line below.
- Adding a feature to your tenant never changes what your existing calls answer: see [Versioning](https://docs.aureahub.com/docs/versioning.md), and the [Changelog](https://docs.aureahub.com/docs/changelog.md) for what changed when.

## On for Every Tenant

- **Sign-in**: register, password sign-in, Google and Apple sign-in, refresh, server-side logout — [Users & Sign-In](https://docs.aureahub.com/docs/guide-user-onboarding.md). Users, the thirteen roles and [groups](https://docs.aureahub.com/docs/guide-policy-sets.md).
- **Credentials**: the API key and secret and their rotation, [server credentials](https://docs.aureahub.com/docs/guide-server-credentials.md) — [Credentials & Rotation](https://docs.aureahub.com/docs/guide-credentials.md).
- **Wallets** in your tenant's wallet mode — custodial, client-side or MPC — on the chains enabled for your tenant; import, primary wallets, balances, the move of a custodial key to the user's device — [Wallets & Custody](https://docs.aureahub.com/docs/guide-non-custodial-keys.md). MPC: the backup proof, acknowledged relay reads, and your own co-signer, which your administrators switch on — [Institution Callback & Co-Signer](https://docs.aureahub.com/docs/guide-institution-callback.md).
- **Accounts**, bulk account creation, and [account structures](https://docs.aureahub.com/docs/guide-account-structures.md) declared per network (segregated today; see Coming for the omnibus processing).
- **Payments**: sending, fees and spendable amounts, address checks, the transaction feed, the Travel Rule data of a transfer — [Send & Receive](https://docs.aureahub.com/docs/guide-send-transaction.md). Swaps on EVM chains and custodial swaps on Solana — [Token Swaps](https://docs.aureahub.com/docs/guide-swap.md). The [asset & chain registry](https://docs.aureahub.com/docs/guide-asset-registry.md) and your token list.
- **Governance**: [policy sets](https://docs.aureahub.com/docs/guide-policy-sets.md), groups in policy rules, the [address book](https://docs.aureahub.com/docs/guide-address-book.md) (entries cool from their request, with no approval step), [freezes and quarantines](https://docs.aureahub.com/docs/guide-freezes.md).
- **Events**: webhook endpoints and the environment webhook — [Webhooks & Events](https://docs.aureahub.com/docs/guide-events.md) — with the `ramp.*`, `transaction.*`, `wallet.*`, `account.*`, `address_book.*`, `policy.*`, `approval.*`, `aml_case.*`, `earn.*` and `server_credential.revoked` types, each to the endpoints that name it.
- **Limits**: the per-route [rate limits](https://docs.aureahub.com/docs/rate-limiting.md); an unknown API key is answered as a wrong signature (`401` `Invalid signature`).

## Modules

Your tenant's offer is the base product — users and sign-in, accounts, wallets, payments and operations, the address book, compliance, credentials and webhooks — which is always on, plus modules that Aurea switches on or off for your tenant as agreed with you. A module only opens its routes: the product behind it still answers by your tenant's own setup for it, as its pages say.

- `bank_ramp` — the bank ramp: `/v1/ramp/bank/*`, and the same routes under their earlier paths.
- `card_onramp` — the card onramp: `/v1/ramp/card/*`, and the same routes under their earlier paths.
- `fiat` — fiat banking: `/v1/fiat/*`.
- `earn` — Earn: `/v1/earn/*`.
- `tokenized` — tokenized assets: `/v1/tokenized-assets/*`.
- `swap_dapps` — swaps and the dApps browser: `/v1/swap/*`, `/v1/dapps/*`.
- `ai_agents` — agent payments: `/v1/agent-payments/*`. While it is off, its routes keep their own answer (`404`), as before.
- `remittance` — [Remittance](https://docs.aureahub.com/docs/guide-remittance.md) [Coming soon, upon request](https://docs.aureahub.com/docs/feature-availability.md), for licensed companies: its payouts' `remittance.payout.*` events. Off for every tenant until it is asked for.
- `identity_verification` — [Identity Verification](https://docs.aureahub.com/docs/guide-identity.md) [Coming soon, upon request](https://docs.aureahub.com/docs/feature-availability.md): `/v1/identity/*`. Off for every tenant until it is asked for.
- Your tenant's ramp webhooks belong to `bank_ramp` and `card_onramp` both: they stay open while either is on.

- **A module that is off** answers every call of your tenant's users and servers on its routes with `403` and `details.code` `MODULE_NOT_ENABLED`, naming it in `details.module` — before the product's own answers, after authentication and the role's permission (a missing or bad credential still answers `401`, a role without the permission `403` as before). Don't retry: ask your Aurea contact.
- **A module that is on changes nothing** on its routes. Every tenant had every module on when modules came, so nothing your integration called changed.
- **Read your tenant's modules** with [Available Features](https://docs.aureahub.com/docs/tenant-features.md) (`modules`), for showing or hiding parts of your app.
- A module that needs a verified licence for your tenant is switched on only once the licence is on record; asked before, it is refused with `409` `MODULE_REQUIRES_LICENCE`.

## Coming soon, upon request

- **Products**

  - The [bank ramp](https://docs.aureahub.com/docs/guide-bank-customers.md) — pay-in to a virtual account, payout from a wallet or a proven address, the customer routes, and the [local rails](https://docs.aureahub.com/docs/guide-bank-local.md) and [desk orders](https://docs.aureahub.com/docs/guide-bank-desk.md) in local currencies.
  - The [card onramp](https://docs.aureahub.com/docs/guide-card-onramp.md) — for your app's users, and for your own wallets.
  - [Earn](https://docs.aureahub.com/docs/guide-earn.md) — yield products for your users' stablecoins.
  - [Tokenized assets](https://docs.aureahub.com/docs/guide-tokenized-assets.md) — buy, hold and sell tokenized securities and yield assets (on request; [contact the Aurea team](https://www.aureahub.com/contact)).
  - [Payment cards and a EUR account](https://docs.aureahub.com/docs/guide-cards.md) for your users — `eurAccountIban` in [Available Features](https://docs.aureahub.com/docs/tenant-features.md); showing a card's number is set up separately.
  - [Lending](https://docs.aureahub.com/docs/guide-lending.md) of EUR.e — `lumenEnabled`.
  - The [dApps browser](https://docs.aureahub.com/docs/guide-dapps.md).
  - [Agent Payments](https://docs.aureahub.com/docs/agentic-payments.md), and their [MPC delegated signing](https://docs.aureahub.com/docs/agentic-mpc-delegation.md) — an agent pays from an MPC wallet within the on-chain mandate the wallet signed.
  - [Remittance](https://docs.aureahub.com/docs/guide-remittance.md), for licensed companies — payouts for your company's customers, approved by a second administrator, and their `remittance.payout.*` events.
  - [Identity verification](https://docs.aureahub.com/docs/guide-identity.md) — KYC of persons and KYB of companies on a verification page, with the `identity.verification.updated` event; it can decide the bank ramp's local rails' verification.
  - The [embedded wallet](https://docs.aureahub.com/docs/guide-embedded-wallet.md) — your users' MPC wallets inside your own web pages with `@aureahub/wallet-embed`, beside the API.
  - [Device preparation](https://docs.aureahub.com/docs/guide-device-preparation.md) (preview) — a new MPC wallet ready in seconds: the device prepares it in the background, on the web and in native apps.
  - More chains and tokens.
- **Sign-in**

  - [Two-factor sign-in](https://docs.aureahub.com/docs/guide-two-factor.md) for your administrators.
  - Your tenant's own passkey address, for passkeys and the step-up in your own apps — [Your Passkey Address](https://docs.aureahub.com/docs/passkey-address.md). Passkeys on Aurea's web address are every tenant's ([Passkeys & Step-Up](https://docs.aureahub.com/docs/guide-passkeys.md)).
  - Password reset by email — [Forgot Password](https://docs.aureahub.com/docs/auth-forgot-password.md).
- **Payments**

  - Gasless swaps — [Execute Gasless](https://docs.aureahub.com/docs/swap-gasless.md).
  - Client-side swaps on Solana — [Broadcast Solana Swap](https://docs.aureahub.com/docs/swap-broadcast-solana.md).
  - The [Gas Station](https://docs.aureahub.com/docs/guide-gas-station.md)'s mode.
  - Operation records — [Operations & Fees](https://docs.aureahub.com/docs/guide-operations.md), your own operation id (`X-External-Tx-Id`), the `operation.*` events, and the `202` answer of an operation held for an approval, a review or your callback.
- **Governance**

  - [Institution callbacks](https://docs.aureahub.com/docs/guide-institution-callback.md).
  - Designated signers.
  - [Reports](https://docs.aureahub.com/docs/guide-reports.md).
  - The [audit trail](https://docs.aureahub.com/docs/audit-events.md).
  - The MPC recovery key — [Register a Recovery Key](https://docs.aureahub.com/docs/mpc-recovery-key-register.md).
  - The MPC wallet setup rules — receiving only once the backup is confirmed ([MPC Wallet Setup](https://docs.aureahub.com/docs/guide-wallet-setup.md)); a bank account opened by itself on the verification's approval.
  - Mutual TLS on webhook deliveries.

## Recorded Today, Enforced on Request

These controls run for every tenant today in an observing mode: they record what they would refuse and refuse nothing. Your tenant can have them refuse, on request — an institutional tenant does by its profile.

- **Screening** of every counterparty against the public sanctions lists; held for review, refused, and [AML cases](https://docs.aureahub.com/docs/guide-screening.md) where enforced.
- **Your tenant's quorum** on administrators' actions ([Your Tenant's Quorum](https://docs.aureahub.com/docs/guide-tenant-quorum.md)), and the passkey step-up before an approval or a policy publication.
- **The address book at the signing points**: a destination outside it recorded, refused where enforced.
- **The [signing rules](https://docs.aureahub.com/docs/guide-signing-rules.md)**: the message rules, swaps built on the server, your swap routes. Exact token approvals and the transaction simulation are off until requested.
- **Stable error codes** on every error ([Errors & Codes](https://docs.aureahub.com/docs/errors.md)), **quotas per category** ([Rate Limits](https://docs.aureahub.com/docs/rate-limiting.md)), the current password asked for one's own password or email change, and administrators' direct edits of another user's password or email refused ([Update User](https://docs.aureahub.com/docs/users-update.md)).

## Coming

- **Fiat banking**, on request: KYC and KYB of your users, multi-currency balances, FX conversions with a quote, transfers to bank accounts, and local receiving accounts in USD, CAD, EUR and GBP.
- Bank payouts in production through the bank ramp's hosted payout page.
- Speeding up or dropping a sent transaction (replacement by fee).
- Records of the transfers your wallets receive, their `transfer.inbound.*` events, and the omnibus account structure's processing — sweeps, the customer sub-ledger and pool withdrawals.
- [Tokenized assets](https://docs.aureahub.com/docs/guide-tokenized-assets.md) held in your tenant's wallet for its users: each user's holding kept in a sub-ledger, deliveries to the user's own wallet and returns from it.
- [Tokenized assets](https://docs.aureahub.com/docs/guide-tokenized-assets.md) through the issuer's own flows: market and instant orders, moves between chains, in-kind exchanges, and the registration of your users' wallets with the issuer.
- [Tokenized assets](https://docs.aureahub.com/docs/guide-tokenized-assets.md) on Solana: the secondary market there, and the operations a Solana wallet signs.
- Event types published in the catalogue but not sent yet: `ramp.iban.updated`, `ramp.payout_order.updated`; and a JWS signature header on webhook deliveries.

---

Web version: https://docs.aureahub.com/#feature-availability