Edge Wallet API integration & OpenFinance services

1. Crypto-native bookkeeping & tax

An accounting SaaS that already imports bank feeds wants to ingest Edge wallets so a self-employed user can close their books in one tool. We map the statement endpoint into the SaaS chart of accounts, attach fiat value at execution for every leg, and pre-classify swap pairs so the tax engine produces correct cost basis under FIFO/HIFO. Exports cover Form 8949 in the US and country equivalents in the EU.

2. Treasury & NAV reporting for crypto SMBs

A small fund or DAO holds operating cash across BTC, ETH, USDC on Polygon and HBAR. The integration polls balances every 60 seconds, reconciles them against custody policy thresholds, and alerts via webhook if a wallet drains beyond a watermark. NAV snapshots feed an internal Looker board.

3. Merchant checkout & subscription billing

An e-commerce platform issues HD receive addresses per invoice, watches confirmations through the Edge plugin layer, and fires order-paid events into Shopify or WooCommerce. For recurring billing, we generate fresh addresses per period and emit reminder webhooks before grace expires.

4. Compliance & AML monitoring

For regulated counterparties, every outgoing transfer is screened against Travel Rule thresholds and the relevant VASP messaging protocol (TRISA, TRUST or Notabene). The integration emits a consent receipt and a hashed counterparty record so MiCA-aligned audit trails remain reconstructable for at least five years.

5. DeFi position dashboards

A risk team that lets staff use Edge for personal-but-business-adjacent activity wants visibility into Aave loan health and Maya cross-chain positions opened from the wallet. We expose a read-only positions feed with collateral ratios and liquidation distance, refreshed via on-chain calls rather than third-party indexers, so data stays verifiable.

Bootstrap an Edge context (Node.js)

// Load the Edge core, register currency & swap plugins
import { makeEdgeContext } from 'edge-core-js'
import bitcoin from 'edge-currency-bitcoin'
import ethereum from 'edge-currency-ethereum'

const context = await makeEdgeContext({
  apiKey: process.env.EDGE_API_KEY,
  appId: 'co.openfinance.edge-bridge',
  plugins: { bitcoin: true, ethereum: true }
})

const account = await context.loginWithPassword(username, password, {
  otp: process.env.EDGE_OTP
})
const btcWallet = await account.waitForCurrencyWallet(account.activeWalletIds[0])

Statement export endpoint (REST wrapper)

POST /api/v1/edge/statement
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "wallet_id": "BTC-bip49-xprv...redacted",
  "from": "2026-04-01T00:00:00Z",
  "to":   "2026-04-30T23:59:59Z",
  "format": "csv",
  "include_fiat": true,
  "fiat_currency": "USD"
}

200 OK
{
  "wallet_id": "BTC-...",
  "count": 142,
  "transactions": [{
    "txid": "9b2f...e7",
    "height": 894012,
    "timestamp": "2026-04-12T08:14:00Z",
    "amount_sats": -2350000,
    "fee_sats": 920,
    "counterparty": "bc1q...8h",
    "fiat_value_at_execution": -1571.42,
    "memo": "supplier invoice 2026-04-12"
  }]
}

Swap-execution webhook (signed)

POST https://your-app.example.com/hooks/edge-swap
X-Edge-Signature: t=1746243600,v1=8c7d...
Content-Type: application/json

{
  "event": "swap.completed",
  "provider": "changelly",
  "from": { "wallet": "BTC-...", "amount_sats": 2500000 },
  "to":   { "wallet": "ETH-...", "amount_wei": "412300000000000000" },
  "rate": 0.06173,
  "slippage_bps": 14,
  "tx_in":  "9b2f...e7",
  "tx_out": "0xab12...90"
}

Regulatory alignment

Edge integrations operate under user authorisation and use only documented public or sanctioned interfaces. For EU-facing deployments the implementation respects the Markets in Crypto-Assets Regulation (MiCA) and the EU Transfer of Funds Regulation, which became fully enforceable on 30 December 2024 and applies a zero-threshold Travel Rule to all crypto-asset transfers. US deployments respect the FinCEN $3,000 Travel Rule threshold and BSA record-keeping. Where required we plug transfer screening into TRISA, TRUST or Notabene messaging.

Privacy posture

Edge's zero-knowledge model means neither Edge nor any third party can read user funds, keys or transaction data. Our integration preserves that posture: seeds and OTP secrets stay on the user's device or in a hardware-backed KMS, address books are encrypted client-side before sync, and our REST wrapper logs only opaque request IDs and counterparty hashes — never private keys, mnemonics or raw contact lists.

Data flow / architecture

A typical pipeline looks like: Edge mobile client → edge-core-js bridge (Node.js or React Native) → OpenFinance API gateway with auth, rate limits and Travel-Rule screening → Storage (Postgres for normalised statements + S3/object store for exports) → Downstream consumers (BI, accounting, treasury, compliance). Webhooks fan out swap and transfer events; a nightly reconciliation job replays on-chain confirmations against the database to catch reorgs and dropped transactions.

Market positioning & user profile

Edge ships on Android and iOS and is positioned as a privacy-first, self-custody mobile wallet for retail users worldwide. Power users include Bitcoin and privacy-coin holders (notably Monero), DeFi participants using Aave, Maya and Botanix, and US users who value the in-app debit-card off-ramp launched in late 2023. Our integration clients tend to be accounting platforms, crypto-native fintechs, regulated VASPs, and SMBs that want to plug a non-custodial wallet into existing OpenBanking-style stacks.

Deliverables checklist

• OpenAPI / Swagger specification for every exposed endpoint
• Protocol & auth flow report (edge-core-js login, OTP, plugin loading)
• Runnable source for wallet bootstrap, statement, balance and swap APIs (Node.js / Python)
• Webhook contract with signed payloads and replay protection
• Automated integration tests against an Edge sandbox account
• Compliance brief (Travel Rule thresholds, MiCA record-keeping, GDPR data classes)

Engagement workflow

1. Scope confirmation — which wallets, chains and use cases (1–2 days)
2. Protocol & SDK review — edge-core-js and plugin landscape (2–4 days)
3. Build & internal validation against sandbox accounts (3–8 days)
4. Docs, samples, signed webhook, compliance brief (1–2 days)
5. First delivery typically ships in 5–15 business days; complex DeFi or multi-region scopes may extend.

About us

OpenFinance Lab is an independent studio focused on mobile fintech, non-custodial crypto and OpenBanking-style integrations. Our engineers come from banks, payment gateways, blockchain infrastructure and protocol-analysis backgrounds, and we ship end-to-end APIs under privacy and compliance constraints from day one.

• Crypto wallets, exchanges, payments and cross-border rails
• Custom Node.js / Python / Go SDKs and signed webhook contracts
• Protocol analysis, traffic capture and authorised reverse engineering
• Source code delivery from $300 — runnable code and full docs; pay after delivery upon satisfaction
• Pay-per-call hosted API — usage-based pricing, no upfront cost, ideal for early-stage teams

Contact

For quotes or to submit your target app and requirements, open our contact page:

Contact page

FAQ

Does Edge expose an official API for third parties?

Can I export my Edge transaction history programmatically?

How do you handle the FATF Travel Rule and MiCA compliance?

What does delivery look like?

Why work with us on Edge specifically

Edge has been open source since the Airbitz days and ships a serious plugin architecture, but production integration still needs careful work: API-key provisioning, OTP handling, plugin selection per chain, swap-provider failover, signed webhooks, and Travel-Rule plumbing. We do that work once and hand you a stable surface, instead of every team re-discovering the same edge cases.