Brightwell Navigator API integration services

1 · Crewing platform payroll sync

Context: a manning agency runs a crew-management system and needs each seafarer's confirmed net pay per voyage. Data/API: the wage-statement endpoint (GET /v1/payroll/statements) returning cycle_id, net_amount, currency, posted_at, employer_ref. OpenFinance mapping: behaves like an account-information "transactions" feed scoped to payroll credits — consent-bound, read-only, replayable.

2 · OceanPay balance & spend dashboard

Context: a welfare organisation offers financial-wellness coaching and wants opt-in balance and spend trends. Data/API: GET /v1/cards/{id}/balance plus paged GET /v1/cards/{id}/transactions with from/to filters and MCC grouping. OpenFinance mapping: mirrors OpenBanking "account balance" and "transaction" resources for a prepaid product, with category enrichment added on our side.

3 · Remittance reconciliation & FX audit

Context: a fintech partner co-markets transfers and must reconcile every payout to bank, cash pickup or wallet across 130+ countries. Data/API: GET /v1/transfers and GET /v1/transfers/{id} exposing send_amount, receive_amount, fx_rate, fee, payout_partner (Western Union / MoneyGram / Transfast), status. OpenFinance mapping: a payment-initiation status feed, exported to Excel/JSON for finance and to an audit store for AML review.

4 · Disputed-charge & card-lock automation

Context: a support desk wants to flag suspicious card activity and let crew lock the OceanPay card instantly. Data/API: transaction webhook → risk rules → POST /v1/cards/{id}/lock. OpenFinance mapping: an event-driven extension of the transaction resource plus a controlled write action, all gated by the crew member's authorization.

5 · Onboarding / offboarding identity sync

Context: when a crew member signs on or off a vessel, the employer's HR system must reflect the Navigator account state. Data/API: GET /v1/profile for identity, employer assignment and login method, with delta polling or webhooks. OpenFinance mapping: account-detail resource used for lifecycle automation rather than ad-hoc lookups.

Auth: establish a session (token validation)

POST /v1/auth/session
Content-Type: application/json

{
  "device_id": "dvc_8f1c2e",
  "method": "facecheck",        // or "authenticator_totp"
  "assertion": "<signed_video_selfie_or_totp>",
  "username": "crew_id_or_email"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_9a7...",
  "expires_in": 900,
  "account_id": "acct_4421",
  "card_id": "card_77a2"
}

Read: paged wage statements

GET /v1/payroll/statements?from=2026-01-01&to=2026-04-30&limit=50
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "items": [
    {
      "cycle_id": "pc_2026_07",
      "posted_at": "2026-04-15T08:02:11Z",
      "net_amount": 2185.00,
      "currency": "USD",
      "employer_ref": "CCL-VESSEL-12",
      "method": "oceanpay_card"
    }
  ],
  "next_cursor": "eyJvIjoxMD..."
}

# error handling
401 -> refresh token, retry once
429 -> honour Retry-After header (backoff)
409 -> consent expired, re-run /v1/auth/session

Webhook: transaction posted

POST https://your-app.example.com/hooks/brightwell
X-Signature: sha256=...

{
  "event": "card.transaction.posted",
  "account_id": "acct_4421",
  "card_id": "card_77a2",
  "transaction": {
    "id": "txn_5fd11",
    "amount": -42.17,
    "currency": "USD",
    "merchant": "PORT WIFI KIOSK",
    "mcc_hint": "4814",
    "status": "posted",
    "occurred_at": "2026-05-10T19:44:03Z"
  }
}

# respond 2xx within 5s; we retry with exponential backoff otherwise

Action: lock the OceanPay card

POST /v1/cards/card_77a2/lock
Authorization: Bearer <ACCESS_TOKEN>
Idempotency-Key: lock-2026-05-12-001

{ "reason": "suspected_fraud" }

200 OK
{ "card_id": "card_77a2", "state": "locked", "locked_at": "2026-05-12T03:10:00Z" }

Regulatory context

Brightwell is a technology provider, not a bank — OceanPay® Visa® Prepaid Cards are issued by The Bancorp Bank, N.A., Member FDIC, and USD balances are eligible for FDIC pass-through insurance up to $250,000 when registration requirements are met. Any integration we build respects that structure and aligns with the Bank Secrecy Act and AML expectations, OFAC sanctions screening, and the CFPB prepaid account rule (Regulation E) governing fee disclosures and error resolution. For crew members based in the EU/EEA, GDPR data-subject rights and PSD2-style consent patterns apply to any beneficiary or transaction data we touch.

How we keep it lawful

• Authorized access only — employer agreement, the crew member's own consent, or documented public/partner APIs; no scraping without permission.
• Data minimization — we request the narrowest scopes that satisfy the use case and drop fields you do not need.
• Consent & audit logging — every read is timestamped and attributable; revocation is honoured immediately.
• Encryption in transit and at rest, secrets in a managed vault, least-privilege service accounts.
• NDAs and a documented data-processing agreement on request.

Deliverables checklist

• API specification (OpenAPI / Swagger) covering auth, balance, transactions, statements, transfers and webhooks
• Protocol & auth-flow report (token / refresh / FaceCheck handshake chain)
• Runnable source for login, balance and statement endpoints in Python and Node.js
• Webhook receiver sample with signature verification and retry handling
• Automated tests, Postman collection and a written test plan
• Compliance guidance (FDIC pass-through, BSA/AML, OFAC, CFPB prepaid rule, GDPR notes) and data-retention recommendations

Engagement workflow

1. Scope confirmation — which data and actions (payroll, balance, transactions, transfers, card lock) and what authorization exists.
2. Protocol analysis & API design — 2 to 5 business days depending on complexity.
3. Build & internal validation — 3 to 8 business days.
4. Docs, samples and test cases — 1 to 2 business days.
5. First delivery typically 5 to 15 business days; third-party or employer approvals may extend timelines.

• Wise (formerly TransferWise) — multi-currency accounts and low-cost international transfers; holds balance, conversion and transfer-status data many treasury tools want unified with payroll feeds.
• Revolut — a digital banking app with cards, FX and transfers; transaction and balance data frequently sit alongside crew-pay records in personal-finance dashboards.
• Remitly — remittance specialist serving expatriates; transfer history, payout method and delivery status mirror the Navigator "send money" flow.
• WorldRemit — online remittances to 130+ countries; corridor, fee and status data overlap closely with cross-border payouts from a payroll card.
• Xe Money Transfer — FX rates plus transfers; rate and transaction data are often reconciled against remittances initiated elsewhere.

• MoneyGram — cash pickup and bank/wallet payouts; one of the disbursement networks crew use, so its transfer records pair naturally with Navigator data.
• Western Union — global cash-pickup and account payouts; a common payout partner for Navigator transfers, making unified status tracking valuable.
• Wisely by ADP — a payroll card used by US employers; balance and transaction data invite the same reconciliation patterns as OceanPay.
• Netspend (Skylight ONE) — prepaid payroll-card accounts; spend and load history are routinely exported for budgeting and accounting.
• Payoneer — cross-border payouts for contractors and marketplaces; users juggling Payoneer and a payroll card often want one transaction export across both.

Contact

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

Contact page

Engagement models

• Source code delivery — from $300; you receive runnable API source and docs, pay on satisfaction.
• Pay-per-call API — use our hosted endpoints, billed per call, no upfront fee.
• NDA and data-processing agreement available on request.