Product Overview

The Business Instant Payout API (BIP API) is a fully automated payment solution for businesses. You can seamlessly integrate trigger-based instant payouts to be processed instantly, no manual approval required from Rabo Business Banking.

A standard payment order requires authorization in Rabo Business Banking whereas a BIP transaction is processed using certificates, eliminating the need for authorization within the online banking-environment. By checking the payout status, you can determine whether the recipient has received the funds. Using BIP, you can initiate both Euro Payments and World Payments.

👍
Optional service Payee Account Check:
To further improve the processing of your payments, BIP offers an additional optional service: Payee Account Check. This feature allows you to verify whether the provided beneficiary name matches the IBAN before submitting the payment instruction. It helps prevent failed transactions and manual interventions during payment processing.

Prerequisites

To ensure a smooth start with the Business Instant Payout API, your business should meet the following conditions:

High degree of automation.
Professional IT environment and good infrastructure.
Permanently available security expertise to use Accounts & Payments APIs and safeguarding its security.
An EV SSL certificate for transport .
An EV SSL signing certificate for signing messages.
An active Rabobank business account.

How to connect with the Business Instant Payout API

📘
The API can be used in two ways, depending on your use case.
The options below explain each approach:

If you execute API requests from your own account, then you are a Direct Connector (DC).

If you execute API requests on behalf of your customers (Rabo account holders), then you are a Third Party (TP).

If you decide to use both options of this API (Direct Connector AND Third Party), you must create separate Apps. One app with a subscription on the DC product and the other app with a subscription on the TP product.
More information: Rabo Banking Link manual for third parties, Rabo Banking Link manual for direct connectors

Direct Connector:

Subscribe your application to Business Instant Payout for Direct Connectors.
Use the OAuth scope: bip.payments.write.

Third Party:

Subscribe your application to Business Instant Payout for Third Parties.
Use the OAuth scope: bip.paymentsbiptp.write.

Authentication & Authorization

The APIs use token-based authentication, which consists of 2 things:

Consent granted by the account holder.
Access token, with the integrated consent.

To set this up use the Authorization Services API.

With the /authorize endpoint the account holder is requested to give consent for a certain API (scope). After consent, an authorization code is returned. This authorization code should be used in the /token call to retrieve an access token. This access token is a Bearer token that you use in the Authorization header of each request.

Relevant scope for oauth2 access code flow

Scope name	Description
bip.payments.write	Payments from your payment account for Direct Connectors.
bip.paymentsbiptp.write	Payments from your payment account for Third Parties.

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

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
`POST /v3/payments/single-credit-transfers`	Shared	12	Yes
`POST /v3/payments/cross-border-credit-transfers`	Shared	12	Yes
`GET /v3/payments/single-credit-transfers/{paymentId}/status`	Shared	12	Yes
`GET /v3/payments/cross-border-credit-transfers/{paymentId/status`	Shared	12	Yes
`POST /payments/single-payee-verification`	Shared	12	Yes
All (premium) Oauth calls	Shared	12	Yes