Sorry, you need to enable JavaScript to visit this website.

Payment Initiation

The Payment Initiation product provides certified parties with access to their clients’ payment accounts to initiate single- or bulk- payments in a safe and secure way. Create a seamless journey for your clients, who remain in full control throughout. The account holder always decides who gains access.

Features

Access to Rabobank accounts
Initiate single or bulk payments
PSD2 compliant

What is Single Payment Initiation?

With the Payment Initiation API, you can initiate a single credit transfer on behalf of your users from a Rabobank payment account to another account. You can retrieve the status of the initiated transaction to keep track.

The API can be used through your app or web service to optimize your customer journey. A payment can only be intiated from an account when the account holder authorizes this payment.

The current version is suited for single Euro Credit Transfers (SEPA)*, Recurring payments, Cross Border Payments (non-SEPA) and gives you extended status information of the initiated payments.

What is Bulk Payment Initiation?

With the Bulk Payment Initiation API, you can initiate bulk payments by means of sending payment order files through API’s on behalf of your organisations from a Rabobank business payment account to other accounts. 

The API can only be used through your web service to optimize your customer journey. To send payment order files you need approval from the account holder first. The current version is suited for payment files (PAIN.001) which may contain batches with Euro Payments and Urgent Euro Payments. The Bulk Payment Initiation API will be expanded in the near future to include World payments (payments outside the SEPA area).

You can retrieve the status of the submitted bulk and the individual payments via the status request endpoint that provides a PAIN.002 file.

Who can use it?

The product is designed for use by Certified Payment Initiation Service Providers (PISPs).

What do you need?

As a Certified Payment initiation Service Provider you require:

  • Authorization of the National Competent Authority in order to be able to use the APIs.
  • Our PSD2 enrollment product which enables certified parties to enroll themselves automatically at Rabobank.
  • Consent from the accountholder (only for Bulk Initiation API)

How does the Single Payment API work?

  1. The customer instructs the PISP to have the payment transaction executed by Rabobank
  2. The PISP sends the details of the payment transaction to Rabobank via the PIS API
  3. Rabobank will provide an URL to the PISP, which can be used by the customer to authorise the payment transaction for execution
  4. The PISP directs the customer to Rabobank by means of the provided URL
  5. The customer will authenticate itself in the secured and trusted Rabobank environment
  6. The customer can simply select a debit account out of the list of its payment accounts, if no account is provided by the PISP
  7. The customer authorises the payment in the secured and trusted Rabobank environment
  8. After a successful authorisation (step 7), Rabobank has received the payment and starts processing the payment transaction
  9. The customer is automatically directed back to the PISP
  10. The PISP can retrieve the status of the payment through the status API to keep track.

How does the Bulk API work?

  1. Prior sending payment order files, the account holder must give approval to the PISP for sending payment files to Rabobank on behalf of their organisation for the specified payment account(s). This approval is continuous. 
  2. The PISP sends payment order files (containing batches with payment orders) via the PIS Bulk Initiation API
  3. The Rabobank provides the PISP with the status on the submitted bulk upload (‘’RECEIVED’’ or ‘’REJECTED’’);
  4. If the status is ‘’RECEIVED’’, Rabobank will provide the PISP a URL which can be used by the customer to authorize the bulk payments for execution 
  5. The PISP directs the customer to Rabobank by means of the provided URL (note: for large PAIN files it can take up to 90 seconds before the payment can be signed)
  6. The customer will authenticate itself in the in the secured and trusted Rabobank environment
  7. The customer authorizes the bulk payment in the secured and trusted Rabobank environment**
  8. After a successful authorisation, Rabobank will start processing the bulk files
  9. The customer is directed back to the PISP
  10. The PISP can retrieve the status of the individual payments in the batches through PAIN-002;

* Single Credit Transfers will be credited directly in case the beneficiary bank participates in Instant Payments (only applicable for participating beneficiary banks within the Netherlands).
** A possible second signature for the bulk payment can only be authorized within Rabo Internet Banking (Professional).  


Rabobank understands that having the right tools is essential to bring your ideas to life. Use the Developer Portal to get access to our API’s and start creating now.