Platform overview
A map of the Azari Select member experience end to end, and where the public API surface sits alongside it. This page describes behavior your integration can rely on -- not internal implementation. For request and response shapes, use the API reference and the sandbox.
1. Member journey
Every member account moves through the same sequence before it can transact. Each step must complete before the next becomes available.
Sign up & confirm contact details
A new member registers with an email address and phone number and confirms both before continuing. Unconfirmed accounts cannot proceed to verification.
Identity verification
The member submits a government-issued ID and a liveness check through a licensed
identity verification partner. Verification outcomes are
pending, verified, or rejected; a rejected
attempt can be retried.
Account activation
Activation requires both a verified identity and an active account status. Either condition failing blocks every financial action with a distinct, specific error rather than a generic denial.
Keeping identity details accurate
A member whose legal name, date of birth, or other bound identity fields change (for example after a legal name change) can submit a correction request. Corrections go through staff review before taking effect, and an approved correction re-runs verification against the updated details.
2. Everyday features
Once activated, a member account can use the following. Availability of each feature to a given account can be further scoped by the account's assigned capabilities.
Bill pay
Browse billers, resolve a target account, and submit a payment.
FX & transfers
Resolve a recipient at a listed institution and submit a cross-institution transfer.
Virtual cards
Issue and list virtual cards, and manage card-level controls.
Catalog, vouchers & concierge
Browse partner offers and events, redeem vouchers, and raise concierge or support requests.
3. External partners
Identity verification, card issuance, and payment settlement are each provided by licensed third-party partners rather than performed in-house. Azari Select owns the member-facing experience and the decision logic that gates account activation on the outcome of those partner calls; it does not expose partner-specific integration detail publicly.
4. Public API surface
The endpoint groups below are documented in the API reference and runnable against the sandbox without a credential. Production access requires an approved application credential scoped to the capabilities it needs.
Customers & institutions
Create and read an owned external customer, list accounts, resolve a beneficiary, request a statement, and list institutions.
Transfers & FX
Create a transfer intent, check its status, and read available FX pairs.
Bill pay & cards
List billers and submit payments; list, issue, fund, and withdraw from virtual cards.
Catalog, vouchers, support & webhooks
Browse offers, partners, and events; validate and redeem vouchers; open support and concierge requests; read notifications; register webhooks.