# Banxa Native

Banxa Native is headless ramp infrastructure for partners building deeply integrated fiat ↔ crypto experiences inside their own product. Partners retain full control over the user experience; Banxa provides the regulated payments, compliance, and settlement infrastructure behind the scenes. Native card and wallet support is available on mobile today via the React Native SDK, with a JS SDK for web in active development.

Banxa Native is built for partners with user accounts, KYC capability, and engineering resource. See the [Integration Overview](/enterprise-api/v0-beta/how-it-works/integration-overview) to check if it's the right fit for your product, then jump straight to the [Integration Guide](/enterprise-api/v0-beta/integration-guide) when you're ready to build.

## Core Capabilities

Identities
Manage customer identity and compliance state through Banxa Native.

Identity can be established through:

- a persistent partner-managed `identityReference`
- KYC provider token sharing (e.g. Sumsub)
- identity reliance using partner-provided customer data
- document verification


Identity must be established before eligibility and payment can proceed.

Eligibility
Evaluate whether a specific transaction can proceed.

Eligibility checks consider factors such as:

- identity state
- payment method
- transaction type
- fiat / crypto pair
- blockchain
- regulatory context


Eligibility responses may indicate that additional verification is required before the transaction can continue.

Limits
Retrieve applicable transaction limits for a given identity and transaction context.

Limits may reflect:

- provider-level constraints
- customer-tier limits
- time-based usage windows (daily, weekly, monthly, annual)


Limits are typically evaluated prior to transaction initiation.

Price
Retrieve real-time pricing and fee breakdowns prior to order creation.

Used for transaction estimation and user-facing quotes.

Ramps
Create and manage on-ramp and off-ramp transactions.

Capabilities include:

- transaction creation
- transaction retrieval
- funding instructions where applicable
- lifecycle status tracking


Depending on the payment rail, transactions may be created directly through the API or via SDK-assisted payment flows.

Webhooks
Receive real-time notifications for:

- Ramp lifecycle state changes
- Compliance-related customer status changes


Webhook deliveries require a 2xx response. Non-2xx responses will trigger retry attempts.