Taptap Send API integration services (Remittance / OpenFinance)

Sender authentication

OAuth-style token exchange that mirrors the in-app SMS OTP flow. Includes refresh-token handling, device fingerprint replay, and 2FA challenge interception. Used to power agent-side dashboards where one back-office user manages multiple sender profiles.

Recipient directory

Read/write API for the recipient address book: phone number (mobile wallet), IBAN, bank account number, and KYC-tier metadata. Use this to deduplicate beneficiaries across remittance providers and prefill payout templates.

Quote & FX endpoint

Returns the exact send amount, receive amount, applied exchange rate, and fee for any (source, destination, corridor) tuple. Snapshotted at quote creation so it can be used as a price-disclosure log under FCA and DFSA conduct rules.

Transfer lifecycle

Submit, track, and cancel a transfer with explicit status codes: QUOTED → FUNDED → IN_TRANSIT → DELIVERED → SETTLED. Each transition is timestamped so finance teams can attribute float and identify stuck transactions.

Statement export

Date-bounded transaction history with paging, corridor filter, status filter, and recipient filter. Output as JSON for data warehouses, CSV/Excel for accountants, or PDF for end-user disclosure copies.

Compliance log feed

Stream KYC-uplift events, sanctioned-name hits, and threshold breaches into your AML case manager. Every payload is signed and tied back to the regulator-of-record (FCA, NBB, FinCEN, FINTRAC, DFSA) for the corridor it was issued in.

1) Sender authentication (SMS OTP exchange)

POST /api/v1/taptap/auth/login
Content-Type: application/json

{
  "phone_e164": "+447700900123",
  "device_id":  "a8f3c2-...",
  "client_app": "com.taptapsend"
}

200 OK
{
  "challenge_id": "ch_8f2d1a",
  "expires_in":   180,
  "next_step":    "submit_otp"
}

POST /api/v1/taptap/auth/otp
{ "challenge_id":"ch_8f2d1a", "code":"483921" }

200 OK
{
  "access_token":  "eyJhbGciOi...",
  "refresh_token": "rt_4f1c...",
  "expires_in":    3600,
  "sender_id":     "snd_01HV9..."
}

2) Statement query

POST /api/v1/taptap/statement
Authorization: Bearer <ACCESS_TOKEN>

{
  "sender_id": "snd_01HV9...",
  "from_date": "2026-03-01",
  "to_date":   "2026-03-31",
  "corridor":  "GBP-NGN",
  "status":    ["SETTLED","DELIVERED"],
  "page":      1,
  "page_size": 100
}

200 OK
{
  "page": 1, "total": 248,
  "transfers": [
    {
      "transfer_id":   "tx_01HVA...",
      "created_at":    "2026-03-04T11:22:01Z",
      "send":    {"currency":"GBP","amount":"100.00"},
      "receive": {"currency":"NGN","amount":"203450.00"},
      "fx_rate":  "2034.50",
      "fee":      {"currency":"GBP","amount":"0.99"},
      "payout":   {"method":"mobile_wallet","partner":"OPAY","reference":"OP-99127"},
      "status":   "SETTLED",
      "settled_at":"2026-03-04T11:22:48Z"
    }
  ]
}

3) Payout webhook (signed)

POST https://your-app.example.com/webhooks/taptap
X-TapTap-Signature: t=1711193880,v1=8c1f...
Content-Type: application/json

{
  "event":       "transfer.settled",
  "transfer_id": "tx_01HVA...",
  "corridor":    "EUR-XOF",
  "partner":     "ORANGE_MONEY_SN",
  "settled_at":  "2026-03-22T08:31:20Z",
  "regulator":   "NBB"
}

# Verify signature with HMAC-SHA256(webhook_secret, t + "." + body)
# Reject if |now - t| > 300 seconds.

Compliance & privacy

Taptap Send Payments Co. is registered with FinCEN (MSB number 31000306745734, NMLS ID 2108069), licensed by the New York DFS, and authorised in Massachusetts as a Foreign Transmittal Agency. In the UK it operates as an Electronic Money Institution under the FCA (firm reference 900842); in the EU through the National Bank of Belgium (NBB); in Canada through FINTRAC; and in the UAE through the DFSA.

Our integrations are designed to live inside that perimeter rather than outside it. PSD2 strong customer authentication is mirrored, GDPR data-minimisation is applied at the field level, and the compliance-log feed is structured so it can be replayed as evidence under the FCA's PSR 2017 conduct rules or the New York DFS Part 417 record-keeping requirements. Every endpoint accepts a customer-supplied retention window so PII can be expired on schedule.

Data flow / architecture

A typical pipeline looks like:

1. Client app / agent terminal — Source of authentication, quote, and submit calls.
2. Integration gateway — Token broker, request signer, rate limiter; mirrors the Taptap Send mobile-app contract.
3. Event bus — Fan-out for transaction lifecycle and payout webhooks (Kafka, SQS, or PubSub).
4. Storage & analytics — Time-series store for FX, columnar warehouse for transactions, signed archive for compliance events.
5. Downstream consumers — Accounting, payroll, AML case manager, treasury dashboards, customer-support helpdesk.

About us

We are an independent technical studio focused on App protocol analysis and authorized API integration. The team has shipped fintech integrations across remittance, neobanking, OpenBanking, and merchant acquiring, with engineers drawn from money-transfer operators, mobile-wallet platforms, and cloud security backgrounds.

• Remittance, mobile-wallet, and cross-border payment specialists
• Familiar with FCA, FinCEN, NBB, FINTRAC, and DFSA expectations
• Custom Python / Node.js / Go SDKs, OpenAPI specs, and webhook receivers
• End-to-end pipeline: protocol analysis → build → validation → compliance review
• Source code delivery from $300 — runnable API source code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost

Contact

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

Contact page

Engagement workflow

1. Scope confirmation: corridors, payout types, and data needs (auth, statements, webhooks).
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build and internal validation against sandbox and production traffic (3–8 business days).
4. Documentation, OpenAPI spec, and end-to-end test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; partner approvals may extend timelines.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?