# Banxa Native API

Banxa Native API is Banxa’s API-driven integration model for partners building deeply integrated digital asset experiences within their own product.

It enables platforms to orchestrate pricing, identity, eligibility, and transaction flows through APIs, while Banxa provides the regulated payments, compliance, and settlement infrastructure behind the scenes.

Partners retain full control over:

- front-end UX
- authentication and session management
- onboarding and identity flows
- transaction orchestration


Banxa provides:

- compliance and identity services
- eligibility and limits evaluation
- transaction processing
- settlement and asset delivery


Banxa Native separates **transaction orchestration** from **payment execution**.

Transaction orchestration (pricing, identity, eligibility, and ramp creation) is performed through the API.  Payment execution depends on the selected payment method.

### Payment execution models

Banxa Native supports two execution models depending on the payment rail:

**Fully API-driven**

Bank transfers and similar rails can be completed entirely through the API without any embedded UI components.

**SDK-assisted native payments**

Cards, Apple Pay, and Google Pay require SDK-based secure payment handling.
In these cases, your platform orchestrates identity, pricing, and eligibility via the API, and the Banxa SDK is invoked to securely create the transaction and initiate payment.

## Core Capabilities

Identities
Manage customer identity and compliance state through Banxa Native.

Depending on the integration model, identity can be established through:

- a persistent partner-managed `identityReference`
- Banxa-resolved identity established during the flow
- KYC provider token sharing (e.g. Sumsub)
- identity reliance using partner-provided customer data
- Banxa-managed 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.