AFGCoin Wallet API integration services (BEP-20 / OpenFinance)

Address & balance API

Query AFGCoin and supported BEP-20 token balances using the standard balanceOf(address) selector 0x70a08231 over a public BSC JSON-RPC endpoint such as https://bsc-dataseed1.binance.org/. We wrap the call in a stable JSON contract, normalize decimals, and add caching so dashboards don't have to learn EVM ABI.

Transfer log API

We index Transfer events from the AFGCoin contract on BSC and merge them with in-app activity (referral payouts, staking credits) into a single chronological feed. Filter by date, counterparty, type, or minimum value; export to JSON, CSV, or Excel.

Staking accrual API

Returns the per-day 0.6% staking yield, the running principal, and the next monthly compounding marker. The endpoint is idempotent so reconciliation jobs can replay a date range without producing duplicate journal entries.

Swap-to-USDT API

Mirrors the in-app fast-swap flow that converts AFGCoin to USDT in under 15 seconds. Each call returns quote, slippage, on-chain transaction hash, and final settled amount, suitable for treasury and tax reporting.

Referral graph API

Exposes the 12-level referral tree as a flat list of (parent, child, depth) rows plus per-period commission totals. Useful for affiliate dashboards and for spotting circular referral patterns during AML monitoring.

Webhook & event stream

An optional webhook layer pushes new transfers, staking credits, and burn events to your backend with HMAC-signed payloads, so back-office systems do not have to poll BSC RPC endpoints around the clock.

1. Balance query (BSC JSON-RPC under the hood)

POST /api/v1/afgcoin/balance
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "address": "0xAbC123...DeF",
  "tokens": ["AFG", "USDT", "BNB"]
}

// Internally we call BSC RPC:
//   eth_call -> data: 0x70a08231 + padded(address)
//   chainId : 56
// then normalize by token decimals.

Response 200:
{
  "address": "0xAbC123...DeF",
  "as_of": "2026-05-04T09:00:00Z",
  "balances": [
    { "symbol": "AFG",  "amount": "12500.000000", "decimals": 18 },
    { "symbol": "USDT", "amount": "  302.450000", "decimals": 18 },
    { "symbol": "BNB",  "amount": "    0.184210", "decimals": 18 }
  ]
}

2. Transaction history with paging

POST /api/v1/afgcoin/transactions
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "address": "0xAbC123...DeF",
  "from_date": "2026-04-01",
  "to_date":   "2026-04-30",
  "types":     ["transfer", "stake", "swap", "referral"],
  "cursor":    null,
  "limit":     200
}

Response 200:
{
  "items": [
    {
      "tx_hash":  "0x9f1a...c3",
      "block":    44210123,
      "type":     "transfer",
      "direction":"out",
      "peer":     "0x0Ff...A2",
      "symbol":   "AFG",
      "amount":   "120.0",
      "fee_bnb":  "0.00018",
      "ts":       "2026-04-12T08:14:31Z"
    }
  ],
  "next_cursor": "eyJibG9jayI6NDQyMDk5OTl9"
}

3. Webhook for staking & burn events

POST https://your-host.example.com/afgcoin-events
X-OFL-Signature: sha256=<hex hmac>
Content-Type: application/json

{
  "event": "stake.accrual",
  "address": "0xAbC123...DeF",
  "principal": "10000.0",
  "rate_daily": "0.006",
  "amount":     "60.0",
  "period":     "2026-05-03",
  "ts":         "2026-05-04T00:01:11Z"
}

// Verify HMAC: sha256(body, shared_secret) must match X-OFL-Signature.
// Idempotency: replay the same (event, period, address) safely.

Regulatory alignment

Crypto wallet integrations are sensitive: FATF Recommendation 16, commonly called the FATF Travel Rule, requires originator and beneficiary information to travel with virtual-asset transfers between obliged entities, and is now enforced in 99+ jurisdictions. The EU's Transfer of Funds Regulation took effect in December 2024 and imposes uniform rules across member states. Our APIs surface the required transfer fields so a regulated operator can satisfy the rule without re-engineering the wallet flow.

Privacy & key handling

We never store seed phrases or private keys. Read-only address binding, OAuth-style session tokens for any in-app endpoints, and per-tenant encryption-at-rest are the default. GDPR-style data minimization — collect only what the customer has authorized — is built into the data model. Audit logs record every export with a hashed actor identifier.

Trust Wallet

A multi-chain self-custodial wallet with native BSC support and an integrated DApp browser. Users who hold AFG alongside other BEP-20 assets often need a unified transaction export across both wallets.

MetaMask

Originally an Ethereum browser extension, MetaMask supports BSC via custom network configuration. Joint AFGCoin + MetaMask portfolios commonly need normalized balance feeds keyed by chain ID.

Coinbase Wallet

A self-custodial mobile wallet supporting thousands of tokens, with around 3.2M monthly active users in 2025. Bridge data flows are common where users move funds between AFGCoin Wallet and Coinbase Wallet.

Atomic Wallet

A multi-chain wallet with built-in atomic swaps. Holders frequently rebalance AFG positions through Atomic and need consolidated swap histories for accounting.

SafePal

Hardware-backed wallet with strong BSC support. Treasury integrations often combine SafePal cold storage with AFGCoin Wallet hot balances in a single dashboard.

Tangem

Card-based seedless hardware wallet with mobile companion apps. Asset reconciliation across Tangem cards and AFGCoin Wallet is a common operational use case.

Exodus

Multi-chain desktop and mobile wallet with built-in exchange. Useful as a comparison point for how swap and balance data can be exported from a consumer wallet.

Phantom Wallet

Originally Solana-focused, now multi-chain. Cross-chain reporting where AFG (BSC) and Phantom-held assets are aggregated into one ledger is a recurring request.

Rabby Wallet

An EVM-focused wallet with strong chain awareness. Useful as a reference design for how to expose chain-aware balances and transaction lists.

Bitget Wallet

A multi-chain wallet with deep BSC and DeFi support. Joint integration projects often unify AFG transfers and Bitget Wallet swap history into a single view.

Zengo Wallet

MPC-based keyless wallet. Mentioned alongside AFGCoin Wallet when teams compare custody models for retail-facing integrations.

Deliverables checklist

• OpenAPI 3.1 specification for the AFGCoin Wallet endpoints
• Protocol & auth-flow report covering session tokens and BSC RPC calls
• Runnable Python and Node.js source for balance, transaction, and staking APIs
• Webhook reference implementation with HMAC verification
• Automated tests, Postman collection, and human-readable docs
• Compliance notes mapping fields to FATF Travel Rule data points

Engagement workflow

1. Scope confirmation: which AFGCoin Wallet flows (login, balance, history, staking, swap, referral) you need.
2. Protocol analysis & API design (2–5 business days).
3. Build & internal validation against real BSC mainnet (3–8 business days).
4. Documentation, sample requests, and acceptance tests (1–2 business days).
5. Typical first delivery in 5–15 business days. Pay only after delivery upon satisfaction.

About OpenFinance Lab

OpenFinance Lab is an independent studio specializing in mobile app interface analysis and authorized API integration. The team blends backgrounds in fintech, custody, payment gateways, and protocol reverse engineering, and ships end-to-end financial APIs under security and compliance constraints.

• Crypto wallets, exchanges, and DeFi data pipelines
• OpenBanking-style account information services for traditional banks
• Custom Python / Node.js / Go SDKs and test harnesses
• Source-code delivery from $300, paid after delivery upon satisfaction
• Pay-per-call hosted APIs for teams that prefer usage-based pricing

Contact

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

Contact page