Account Notification Service provides real-time notifications for changes on your payment account. You can configure triggers for specific credit or debit entries. In addition to notifications, ANS delivers bank statements, enabling seamless integration and improved data handling within your ERP or TMS software.

To know more read the manual that connects to your use case:

Relevant scope(s) for oauth2 access code flow

Scope name	Description
ans.subscription.read-write	Allow read and write for account notifications service subscriptions
bai.accountinformation.read	Allow read from Business Account Insight services

📘
Make sure that you use the Authorization and Token URL as provided by the Authorization Services.

🚧
The Delete subscriptions endpoint does NOT require an access token.

Rate Limiting

A default rate limit plan is set for all APIs. The rate limit can be shared or individual (defined per operation). The table below describes the rate limiting for this product.

Operation	Type	Limit (API calls / s)	Counts towards shared limit
`GET /transactions/{notificationId}`	Individual	20	No
`GET /subscriptions`	Shared	6	Yes
`POST /subscriptions`	Shared	6	Yes
`GET /subscriptions/{subscriptionId}`	Shared	6	Yes
`PUT /subscriptions/{subscriptionId}`	Shared	6	Yes
`DELETE /subscriptions/{subscriptionId}`	Shared	6	Yes
All (premium) Oauth calls	Shared	6	Yes

Subscriptions

With the subscription endpoints you can retrieve, create, update, or delete subscriptions.

To get a subscription, go to GET / subscription
To create a subscription, go to POST /subscription
To update a subscription, go to PUT /subscriptions/{subscriptionId}
To delete a subscription, go to DELETE /subscriptions/{subscriptionId}

The POST/GET/PUT/DELETE subscriptions requests must contain a digital signature. You can generate this digital signature using the private key of your certificate. For the Sandbox environment, you can use an example certificate available in the Signing documentation.

Subscribe to event-based notifications

Subscription request

To set up triggers for specific events, subscribe to events for receiving real-time notifications. You can customize these triggers based on a set of rules such as range of amount, credit/debit, or a transaction attribute. When a subscribed event is triggered, you should instantly receive a notification using the location as specified in pushUri field.

{
  "account": {
    "accountNumber": "NL52RABO0125618484",
    "currencyCode": "EUR"
  },
  "transactionCriteria": [
    {
      "amount": {
        "minTransactionAmount": 100,
        "maxTransactionAmount": 500
      },
      "remittanceInformationUnstructured": "Invoice*"
    }
  ],
  "endDate": "2024-12-01T14:07:56.302663",
  "pushUri": "https://tpp.com/notify"
}

In the above example an amount range and transactionId description is used with a wildcard.

📘
A wildcard (*) is a symbol that can stand in for one or more characters. In the API ANS, you can use wildcards to make triggers more flexible. For example, if you want to match any transaction subscription name that starts with certain letters, use a wildcard. This allows you to create more flexible and powerful triggers for receiving instant notifications.

Notification message

When a subscribed event is triggered, you should instantly receive a notification using the location as specified in pushUri field.

👍
Acknowledge notifications as soon as possible. Delays slows down the processing of subsequent notifications, causing longer wait times and unnecessary retries.

{
  "subscriptionId": "59bca412-6d40-469f-9b39-59f4617e95dd",
  "timestamp": "2024-02-27T11:10:00",
  "notificationType": "TRANSACTION",
  "notificationId": "URTr9CEFoW1oopHI780kuX0gz59mW9WEbz56RhiwHoK-qdzBCUIg4v_Sbng33Xg3KdyCMwGbOb8P_Mh1BKQ-cTXa2phM5WNXWvY2.9"
}

Request transaction details

📘
For each transaction that matches the notification subscription, a notification with corresponding notificationId is sent to the pushUri.

Make a GET transactions call to retrieve the transaction details belonging to a notificationId .

To retrieve transaction details of a specific notification using a GET transactions/{notificationId} request, you use the notificationId in the URL:

GET https://api.rabobank.nl/openapi/payments/insight/transactions/URTr9CEFoW1oopHI780kuX0gz59mW9WEbz56RhiwHoK-qdzBCUIg4v_Sbng33Xg3KdyCMwGbOb8P_Mh1BKQ-cTXa2phM5WNXWvY2.9

Response

To retrieve the transaction details connected to a notification use a GET transactions request.

{
  "account": {
    "currency": "EUR",
    "iban": "NL52RABO0125618484"
  },
  "transactions": {
    "booked": {
      "bookingDate": "2020-01-01",
      "creditorAccount": {
        "currency": "EUR",
        "iban": "NL52RABO0125618484"
      },
      "creditorAgent": "RABONL2U",
      "debtorAccount": {
        "iban": "NL02RABO0368909954"
      },
      "debtorName": "My Company",
      "entryReference": "1",
      "initiatingPartyName": "Paper Boy",
      "raboBookingDateTime": "2020-01-01T14:21Z",
      "raboDetailedTransactionType": "133",
      "raboTransactionTypeName": "sp",
      "remittanceInformationUnstructured": "Betaling\nCadeau\nverjaardag",
      "transactionAmount": {
        "value": "109.0",
        "currency": "EUR"
      },
      "ultimateCreditor": "Ultimate One",
      "ultimateDebtor": "Ultimate Deb",
      "valueDate": "2020-01-01",
      "balanceAfterBooking": {
        "balanceType": "InterimBooked",
        "balanceAmount": {
          "value": "109.0",
          "currency": "EUR"
        }
      }
    }
  }
}

Subscribe to statement notifications

🚧
Statement notifications are coming soon.

Subscription request

You can subscribe to receive CAMT.053 end-of-day statements as part of your notifications.

{
"accounts": [
{
"iban": NL52RABO0125618484",
"currencyCode": "EUR"
},
{
"iban": NL80RABO1127000002",
"currencyCode": "EUR"
}
],
  "statementCriteria": 
{
"type": "EOD"
},
  "encryption": 
{
  
  "keyId": "key-2025-09",
  "publicKey": "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A..."

},
"pushURI": "https://tpp.com/notify"

}

Response

{
"subscriptionId": "12345",
"accounts": [{
"iban": NL52RABO0125618484",
"currencyCode": "EUR"  }]
}

Notification message

When a subscribed event is triggered, you receive an instant notification containing the CAMT.053 statement at the location specified in the pushUri field.

📘
CAMT.053 end-of-day statements are generated after midnight, after the transactions for that day have been processed.

{
    "MetaData": {
        "NotificationId": "b97344bd-f3e5-48d4-a68a-d220515c1cf5",
        "SubscriptionId": "33af98b3-22fc-4823-a26d-62664edd19fe",
        "TotalReportsInMsg": "1",
        "Timestamp": "2025-09-12T08:15:25.28330948",
        "KeyId": "key-2025-09",
        "EncryptedAESKey" : "<Encrypted decryption key>"
    },
    "AccountList": [
        {
            "Account": "NL52RABO0125618484",
            "NumberOfTransactions": 240,
            "CCY": "EUR"
        }
    ],
    "Payload": {
        "EncryptedData": "<Encrypted Based64 encode of CAMT>"
    }
}

Retry mechanism

To ensure optimal service, it is crucial to maintain high availability due to the fast exchange of data. Therefore, measures must be taken to ensure the pushURI is accessible when a notification is sent. In case, we are unable to deliver the notification to the pushURI, we attempt retry up to three times:

First retry: after 2 minutes
Second retry: after 13 minutes
Third and final retry: after 29 minutes

Sandbox accounts

Accounts present in the Sandbox environment:

IBAN
NL52RABO0125618484
NL80RABO1127000002