ABN AMRO API & Open Banking Integration

ERP and accounting sync (Business Account Insight)

Business clients need automated export of transactions into ERP and treasury systems. ABN AMRO’s Business Account Insight API provides real-time account details, balances, and transaction data for Dutch Business Current & Savings Accounts. We deliver implementations that consume this API (or replicate its data model via protocol analysis) so you get transaction lists with date, amount, type, and counterparty—mapping directly to Open Banking: structured account and transaction data with TLS and contract-based access. Typical flow: list accounts → get balances → get transactions (with optional batch details).

PSD2 Account Information and aggregation

Third-party providers (TPPs) and aggregators need to show ABN AMRO accounts alongside ING, Rabobank, and other banks. We implement or document the PSD2 Account Information flow: consent → access token → accounts list → balances and transactions. Fields include accountId, iban, balance, currency, and transaction arrays with bookingDate, amount, remittanceInformation. This fits the same landscape as ING and Rabobank open banking; all require EIDAS QWAC and PSD2 licence from De Nederlandsche Bank for production.

Statement export and compliance archive

Personal and business users download statements via the app or Internet Banking (PDF from 2004; transactions up to 18 months in PDF, TXT, XLS, MT940, CAMT.053). We deliver an API or scripted flow that requests statement export for a given period and normalizes output for your archive or compliance tooling. Data flow: user consent → session (app or Internet Banking) → request statement → parse/store. Relevant for audit, tax (e.g. annual financial summary), and regulatory retention.

Payment initiation and order confirmation

E-commerce and B2B platforms need to initiate payments via iDEAL and confirm status. ABN AMRO supports PSD2 Payment Initiation; we implement the payment-creation and status-polling flow so your system can trigger iDEAL payments and receive status (e.g. completed, rejected). Combined with Business Account Notification, you get real-time push when a payment is booked—useful for order fulfilment and settlement visibility.

Tikkie and P2P payment request tracking

Tikkie is ABN AMRO’s P2P payment-request app (works with any Dutch bank account). Use case: track Tikkie requests sent or received, match incoming iDEAL payments to requests, and sync with invoicing or expense tools. We deliver protocol analysis and API-style access to Tikkie request metadata and payment completion where available, aligning with Open Finance data portability for P2P and receipt matching.

Account Information (PSD2) — list accounts

GET /v1/accounts
Authorization: Bearer <ACCESS_TOKEN>
X-Request-ID: <uuid>

Response 200:
{
  "accounts": [
    {
      "resourceId": "account-id",
      "iban": "NL91ABNA0417164300",
      "currency": "EUR",
      "name": "Current Account",
      "cashAccountType": "CACC"
    }
  ]
}

Business Account Insight — transactions

GET /v2/accounts/{accountId}/transactions
  ?dateFrom=2025-01-01&dateTo=2025-01-31
Authorization: Bearer <ACCESS_TOKEN>

Response 200:
{
  "transactions": [
    {
      "transactionId": "...",
      "bookingDate": "2025-01-15",
      "amount": "-50.00",
      "currency": "EUR",
      "remittanceInformation": "iDEAL payment",
      "creditorName": "Merchant B.V."
    }
  ]
}

Error handling and consent

// Typical error responses
401 Unauthorized — token expired, refresh or re-consent
403 Forbidden — insufficient scope or consent revoked
429 Too Many Requests — rate limit; retry with backoff

// Consent: PSD2 requires explicit user consent
// (AIS consent for account/transaction access).
// Store consent_id and scope for audit.

Delivery checklist

• API specification (OpenAPI / Swagger) for the implemented endpoints
• Protocol and auth flow analysis (OAuth2, session, consent)
• Runnable source code (e.g. Python / Node.js) for account, transaction, and optional payment flows
• Automated test scripts and interface documentation
• Compliance notes (PSD2, GDPR, consent and retention)

Focus integration areas

Account and balance sync, transaction history and statement export (PDF, XLS, MT940, CAMT.053), PSD2 Account Information and Payment Initiation, Business Account Insight and Notification, iDEAL and Tikkie flows. We support bulk and multi-account use where applicable. Transparent pricing from $300; optional deliver-first, pay-on-satisfaction.

About us

We are a technical service studio specializing in app interface integration and authorized API integration for global clients. Our team has hands-on experience in mobile applications and fintech. We offer protocol analysis, interface refactoring, Open Data integration, third-party interface integration, and automated data scripting with interface documentation. We are familiar with PSD2, EIDAS, and European privacy requirements and deliver compliant implementations. Services start at $300 with an option to deliver results first and pay upon satisfaction.

Contact

For enquiries, quotes, or to submit a target app name and requirements, please use the link below:

Contact us

Process

1. Confirm requirements: integration scenario and desired data (e.g. transactions, balances, payments).
2. Protocol analysis and API design (typically 2–5 working days).
3. Development and internal validation (3–8 working days).
4. Delivery of documentation, examples, and tests (1–2 working days).
5. First delivery often within 5–15 working days; complex or multi-API projects may take longer.

FAQ

What do I need to provide?

How long until delivery?

How do you ensure compliance?