Satsails API integration services (Bitcoin / Lightning / Liquid / DePix)

Deliverables checklist

• API specification (OpenAPI / Swagger) for accounts, statements, swaps and DePix events
• Protocol and authorization-flow report (token / session / descriptor-watcher chain, Liquid asset registry usage)
• Runnable source for the login, balance and statement endpoints (Python / Node.js)
• Automated tests, Postman collection and written API documentation
• Compliance guidance: LGPD data-minimization, Brazilian Virtual Assets Law alignment, retention and audit logging

Two engagement models

Source code delivery from $300 — you receive runnable API source code plus full documentation; you pay after delivery once you are satisfied. Or pay-per-call API billing — call our hosted Satsails-integration endpoints and pay only for the calls you make, with no upfront fee, which suits teams that prefer usage-based pricing for a pilot before committing to a full build.

Either way you also get a short architecture note describing how the Satsails data lands in your environment and how to keep it in sync.

Engagement workflow

1. Scope confirmation: which networks, which assets, which events (balances, statements, DePix PIX, swaps).
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build and internal validation against test wallets and Liquid testnet (3–8 business days).
4. Docs, samples and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; third-party approvals or PIX-provider sandbox waits may extend it.

1. Accounting & tax export for a Bitcoin-paid freelancer or SME

Context: a Brazilian contractor receives sats over Lightning and holds part of the balance as DePix. Data/API: the statement endpoint returns every Lightning payment and DePix movement with timestamp, asset, fee and counterparty reference; an exporter writes XLSX/CSV. OpenFinance mapping: this is the "account information" pattern — a consented, read-only feed that an accounting platform or the Receita Federal DeCripto report can consume, the same way Open Banking account aggregators pull bank statements.

2. Treasury dashboard for a company holding BTC + stablecoins

Context: finance wants one screen for Bitcoin on-chain, L-BTC and USDT/EURx/DePix exposure. Data/API: the balance endpoint aggregates per-network and per-asset balances (using Liquid asset IDs) and a webhook pushes new confirmations. OpenFinance mapping: a multi-account "balances" resource similar to PSD2 AISP balance calls, extended to Bitcoin Layer 2 assets, feeding a BI tool or ERP.

3. DePix PIX bridge reconciliation

Context: an operator needs to match each PIX inflow to the DePix issued and the on-chain Liquid settlement. Data/API: the DePix-events endpoint returns brl_amount, depix_amount, fee_bps, pix_e2e_id and liquid_txid; a reconciliation job joins these against the bank's PIX statement. OpenFinance mapping: this is a payment-initiation-and-confirmation loop — PIX is Brazil's instant-payment rail, and DePix is the on-chain leg, so the join is the crypto-native equivalent of matching a payment order to a bank credit.

4. AML / risk screening on inbound deposits

Context: a compliance team wants to flag high-velocity DePix purchases or large Liquid inflows. Data/API: a real-time webhook on new transactions plus the address/descriptor endpoint lets a rules engine score each event by amount, network and source. OpenFinance mapping: transaction-monitoring on a consented data stream — the same posture regulators expect from VASPs under the Banco Central do Brasil resolutions, just wired into an automated pipeline.

5. Portfolio & cost-basis app pulling Satsails alongside other wallets

Context: a user tracks Satsails next to a hardware wallet and an exchange account. Data/API: the swap-receipts and transaction endpoints expose quoted rate and amounts so the app can compute realized/unrealized P&L; a normalized JSON schema makes Satsails one more source in a unified portfolio. OpenFinance mapping: account aggregation across providers — the heart of OpenData — with Satsails contributing its Bitcoin-L2 and stablecoin positions.

A. Register a read-only watcher (auth)

// Self-custody: we watch, we never hold keys.
POST /api/v1/satsails/watchers
Content-Type: application/json
Authorization: Bearer <PARTNER_TOKEN>

{
  "label": "treasury-main",
  "descriptors": {
    "bitcoin": "wpkh([fingerprint/84h/0h/0h]xpub.../<0;1>/*)",
    "liquid":  "ct(slip77(...),elwpkh([fingerprint/84h/1776h/0h]xpub.../<0;1>/*))"
  },
  "assets": ["BTC", "L-BTC", "USDT", "EURx", "DEPIX"]
}

200 OK
{ "watcher_id": "wtch_8f2a...", "status": "syncing",
  "access": { "scope": "read", "expires_in": 3600 } }

B. Fetch a multi-network statement

GET /api/v1/satsails/watchers/wtch_8f2a.../statement
  ?from=2026-04-01&to=2026-04-30
  &networks=onchain,lightning,liquid
  &assets=BTC,DEPIX&page=1&page_size=100
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "page": 1, "has_more": true,
  "items": [
    { "ts": "2026-04-03T14:22:11Z", "network": "lightning",
      "asset": "BTC", "direction": "in", "amount_sats": 21000,
      "fee_sats": 1, "status": "settled", "ref": "ln_inv_..." },
    { "ts": "2026-04-09T09:01:40Z", "network": "liquid",
      "asset": "DEPIX", "direction": "in", "amount": "350.00",
      "fee": "5.25", "status": "confirmed", "txid": "..." }
  ]
}
// 401 invalid_token | 409 watcher_syncing | 429 rate_limited

C. DePix PIX on-ramp webhook

// We POST signed events to your endpoint.
POST https://your-app.example/hooks/satsails
X-Satsails-Signature: sha256=...   // HMAC over raw body

{
  "type": "depix.onramp.completed",
  "id": "evt_5c1d...",
  "data": {
    "order_id": "dpx_2026_0044",
    "brl_amount": "500.00",
    "depix_amount": "490.00",
    "fee_bps": 200,            // 1.5% (150) with affiliate code
    "pix_e2e_id": "E1234567890...",
    "liquid_txid": "a1b2c3...",
    "completed_at": "2026-04-12T18:30:05Z"
  }
}
// Respond 2xx within 5s or we retry with backoff.

D. Export to Excel / accounting (Python)

import requests, pandas as pd

tok = "ACCESS_TOKEN"
url = "https://api.example/api/v1/satsails/watchers/WID/statement"
rows, page = [], 1
while True:
    r = requests.get(url, params={"from":"2026-01-01","to":"2026-04-30",
                                  "page":page,"page_size":200},
                     headers={"Authorization": f"Bearer {tok}"}, timeout=30)
    r.raise_for_status()
    body = r.json(); rows += body["items"]
    if not body["has_more"]: break
    page += 1

pd.DataFrame(rows).to_excel("satsails_q1_2026.xlsx", index=False)

Regulatory alignment

We integrate only under your written authorization or with documented public/authorized APIs, and we keep consent records and access logs. For Satsails' primary market, work is aligned with Brazil's Virtual Assets Law No. 14.478/2022 (the "Marco Legal dos Criptoativos") and the Banco Central do Brasil VASP resolutions published in 2025 (Resolutions 519/520/521), which place virtual-asset service providers and self-hosted-wallet transfers under supervision and the FX regime. Reporting flows are designed to feed Receita Federal's crypto reporting (the DeCripto regime, based on the OECD Crypto-Asset Reporting Framework). DePix, being PIX-pegged, also touches the Pix instant-payment rulebook.

Data protection & minimization

Personal and wallet data is handled under Brazil's LGPD (Lei Geral de Proteção de Dados) and equivalent rules in other regions where you operate. We default to data-minimization: read-only descriptors instead of keys, scoped tokens, short token lifetimes, field-level redaction options, configurable retention windows, and signed webhooks. NDAs are signed on request, and we provide a deletion/rotation runbook so consent can be revoked cleanly.

• Blockstream Green — Bitcoin on-chain plus native Liquid Network support with confidential transactions; users often need Liquid asset balances exported alongside Satsails' L-BTC and DePix data.
• AQUA Wallet (JAN3) — non-custodial Bitcoin, Lightning (via Boltz) and Liquid; like Satsails it spans Layer 2, so swap receipts and multi-network history are the common reconciliation points.
• Bull Bitcoin — an instant-payments wallet built natively on Liquid with Boltz-based Lightning; transaction and settlement records pair naturally with Satsails for a combined Liquid view.
• Phoenix Wallet (ACINQ) — self-custodial Lightning with automated channels/splicing; holds Lightning payment history that a portfolio app would merge with Satsails' Lightning tab.

• Zeus Wallet — connects to or runs a self-hosted Lightning node; node-level invoice and channel data complements Satsails' simpler in-app Lightning balance.
• Breez — open-source non-custodial Lightning wallet; payment and POS-style records are another source for the same unified-statement use case.
• Muun — Bitcoin and Lightning with submarine swaps; its on-chain-backed Lightning entries are useful to normalize next to Satsails' sats-precision history.
• Wallet of Satoshi — a widely used Lightning wallet; users who hold balances there frequently want a single export that also covers their Satsails activity.
• BlueWallet — Bitcoin on-chain and Lightning with watch-only support; descriptor/xpub monitoring is the bridge between BlueWallet data and a Satsails watcher.

About us

We are an independent studio focused on fintech and open-data API integration. Our team includes engineers from banks, payment gateways, exchanges and protocol-analysis backgrounds, and we ship end-to-end financial APIs under security and compliance constraints.

• Payments, digital banking, crypto wallets and cross-border settlement
• Enterprise API gateways, watch-only wallet infrastructure and security reviews
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance handover
• Source code delivery from $300 — runnable API source code and documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — hosted endpoints, pay only per call, no upfront cost

Contact

For a quote, or to submit your target app and requirements, open our contact page. Tell us which networks (Bitcoin / Lightning / Liquid), which assets (BTC, L-BTC, USDT, EURx, DePix) and which events (balances, statements, DePix PIX, swaps) you need, and whether you want source-code delivery or pay-per-call.

Contact page

FAQ

What do you need from me to start a Satsails integration?

How long does delivery take?

How do you handle compliance with Brazilian rules?

Can you export Satsails transaction history to Excel or accounting tools?

Recent changes & why it matters for integrators

In 2024 Satsails shipped its headline feature: native DePix support, letting users buy the BRL-pegged stablecoin via PIX inside the wallet and convert it to Bitcoin in seconds, all on the Liquid Network. It also added EURx and USDT as Liquid assets and rolled out an affiliate-code model (1.5% conversion fee with a code, 2% without). For an integration, that means the wallet now records a clean fiat-to-Bitcoin bridge — PIX e2e id, DePix amount, fee tier and Liquid txid — which is far richer than a plain bank line and is exactly what reconciliation, AML and tax workflows want. The team has also said an iOS build is on the way, which widens the addressable user base for any partner tooling.