Orco Bank App API integration (Curaçao · Bonaire · Sint Maarten)

Account & balance sync

Mirror the "View and access to all your Orco Bank accounts" capability as a /accounts endpoint returning per-product balances (current, savings, business), currency (XCG, ANG, USD), and account status. Typical use: nightly treasury dashboards and consolidated balance views across Curaçao and Sint Maarten entities.

Transaction history API

Paginated access to transaction lists with filters for date, amount, counterparty and channel. Use cases: automated bookkeeping, ERP posting (Exact, SAP Business One, Odoo), and tax-period statement packs that include both pre- and post-XCG transition entries.

Transfer orchestration

Create local, inter-island and international transfers, maintain an address book of beneficiaries, and route dual-approval flows for corporate accounts. Deliverable includes retry, idempotency and a /transfers/{id}/approve endpoint mapped to the app's "review, approve or cancel pending transaction" step.

Soft-token & MFA

Programmatic soft-token codes for logging into Orco Bank Online® or approving transfer requests, plus biometric-equivalent re-auth for server-side automation. Useful where treasury bots must complete a signed operation without a human opening the Orco Bank App® each time.

Proof-of-payment & document export

Generate the same PDF proof-of-payment the app emails or sends over WhatsApp, plus document upload endpoints that mirror the "Easily upload documents" flow — handy for KYC refresh, loan add-ons and audit archiving.

FX & travel notice utilities

Expose Orco Bank's published exchange rates (XCG / USD / EUR / ANG legacy) and submit a travel notice for a card before a trip. Used by expense platforms that need rate snapshots and by corporate travel systems that auto-enable cards for overseas use.

1. ERP reconciliation for SME in Curaçao

Context: A Willemstad-based trading company runs Odoo and has three Orco Bank current accounts (two XCG, one USD). Data/API: /accounts, /statements?from=&to=, document download for proof-of-payment PDFs. OpenData mapping: nightly pull into Odoo via an OpenBanking-style account-information flow with consent tokens — eliminating manual CSV downloads from Orco Bank Online®.

2. Corporate payout bot with soft-token approval

Context: A tour operator pays 200+ guides across Sint Maarten and Bonaire weekly. Data/API: address-book sync, /transfers batch create, /transfers/{id}/approve with a soft-token code. OpenData mapping: payment-initiation pattern (OpenBanking PIS style) under explicit corporate authorization, with dual-signer policy and full audit trail.

3. XCG transition audit pack

Context: After Orco Bank's April 2025 migration from ANG to the Caribbean Guilder (XCG), auditors need a clean dataset bridging both currencies. Data/API: transaction export with pre_xcg and post_xcg flags, FX snapshots, balance history. OpenData mapping: a normalized JSON feed your audit platform can diff against the general ledger.

4. Treasury dashboard across Caribbean banks

Context: A hotel group holds accounts at Orco Bank plus another Caribbean bank and wants one liquidity view. Data/API: /accounts + /balances normalized behind a unified schema. OpenData mapping: aggregator pattern similar to Plaid / Tink / TrueLayer, which openbankingtracker.com explicitly recommends for Orco Bank integrations today.

5. Compliance & travel-risk automation

Context: A fiduciary services firm must log card-abroad use for AML/KYC and audit. Data/API: travel-notice submission + card transactions filtered by country. OpenData mapping: event-driven webhook feed into the compliance platform whenever a new travel notice is created or expires.

1. Account login & session refresh

POST /api/v1/orcobank/session
Content-Type: application/json

{
  "username": "jdoe",
  "device_fp": "orco-app-v4.1.1-android",
  "mfa": {
    "type": "soft_token",
    "code": "842193"
  }
}

200 OK
{
  "session_id": "sess_01HZXW...",
  "expires_in": 900,
  "scopes": ["accounts.read", "statements.read", "transfers.write"],
  "customer_type": "business"
}

2. Statement query (paginated)

GET /api/v1/orcobank/statements
  ?account_id=ORCO-XCG-000123
  &from_date=2026-01-01
  &to_date=2026-01-31
  &page=1&page_size=200
Authorization: Bearer <SESSION_TOKEN>

200 OK
{
  "account_id": "ORCO-XCG-000123",
  "currency": "XCG",
  "opening_balance": 48210.55,
  "closing_balance": 51734.02,
  "page": 1,
  "items": [
    {
      "tx_id": "TX20260105X91",
      "posted_at": "2026-01-05T13:04:22Z",
      "amount": -1250.00,
      "counterparty": "SUPPLIER N.V.",
      "channel": "LOCAL_TRANSFER",
      "reference": "INV-2025-1188",
      "currency_original": "ANG",
      "xcg_equivalent": -1250.00
    }
  ]
}

3. Transfer + soft-token approval

POST /api/v1/orcobank/transfers
Authorization: Bearer <SESSION_TOKEN>
Idempotency-Key: 2026-04-20-payroll-0042

{
  "debit_account": "ORCO-XCG-000123",
  "beneficiary_id": "BENE-44721",
  "amount": 3200.00,
  "currency": "XCG",
  "purpose": "SALARY",
  "channel": "LOCAL",
  "soft_token_code": "558104"
}

201 Created
{
  "transfer_id": "TR-20260420-0042",
  "status": "PENDING_APPROVAL",
  "approvers_required": 2,
  "proof_url": "/documents/proof/TR-20260420-0042.pdf"
}

4. Webhook: transfer state change

POST https://your.app/webhooks/orco
X-Orco-Signature: t=1713600000,v1=8a...

{
  "event": "transfer.status_changed",
  "transfer_id": "TR-20260420-0042",
  "previous_status": "PENDING_APPROVAL",
  "new_status": "COMPLETED",
  "value_date": "2026-04-20",
  "audit": {
    "approvers": ["jdoe", "msmith"],
    "mfa": "soft_token"
  }
}

Signed webhooks close the loop for ERP systems so reconciliation doesn't depend on polling.

Deliverables checklist

• OpenAPI / Swagger specification for every endpoint shipped
• Protocol & auth flow report (TLS pinning notes, session refresh, soft-token behaviour)
• Runnable source code for account, statement, transfer and soft-token APIs (Python or Node.js)
• Automated integration tests + Postman collection
• Compliance guidance (CBCS, AML/CFT, privacy, retention)
• Deployment guide: Docker, Kubernetes, or managed hosted endpoint

Two engagement models

• Source-code delivery from $300 — you receive runnable API source code and documentation; pay after delivery, upon satisfaction.
• Pay-per-call API billing — use our hosted Orco Bank integration endpoints and pay only for successful calls, no upfront fee. Ideal for usage-driven teams or MVPs.

Both models include an SLA, signed NDA, and scoped, revocable credentials.

Engagement workflow

1. Scope confirmation: you send the app name and the Orco Bank flows you need (e.g. statements, transfer approvals, soft-token).
2. Protocol analysis & API design — typically 2–5 business days.
3. Build & internal validation — 3–8 business days, depending on complexity.
4. Documentation, sample clients, and test cases — 1–2 business days.
5. Delivery & acceptance — source code bundle or hosted endpoint; 5–15 business days overall.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Which programming languages do you ship in?