With the Business Payment Initiation APIs, you can initiate Single credit transfers or Bulk payment files on behalf of your users with a Rabobank business payment account and retrieve the status of an initiated transaction or file.

Business Payment Initiation is a part of Rabo BoekhoudKoppeling and Rabo Banking Link. This API supports all third parties and direct customers. This API allows you or your clients (with a Rabobank business account) to process single or bulk payments through your application.

Business Payment Initiation consists of two separate APIs:

These APIs can be used through your app or web service to optimize your customer journey. It is suited for Euro Payments (SEPA), World Payments (non-SEPA), and transfers between your own (savings) accounts. After initiating a payment, you can also request its status.

We offer two variations of Business Bulk Payment Initiation (BBPI):

Business Bulk Payment Initiation
- Available with signing for the Rabobank debtor in Rabo Business Banking.
Business Bulk Payment Initiation – STP:
- Straight Through Processing (STP), without signing for the Rabobank debtor.
- Only available for Direct Connectors.

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

IBAN Name Check

With the IBAN name check you enable your software users to check their customer and/or supplier data. This way the user can verify the account name associated with the payment.

You can easily add the IBAN Name Check to your customer journey using Payee Account Check

Payment signing

Single payments

After submitting a single payment order, it must be signed by an authorized user using Rabobank’s interfaces.

Two customer flows are supported:

Redirect - Using this option you can redirect the user to a designated Signing Page for Rabo Business Banking by using redirectionFlag and the IP-redirect-URIparameters. This option is useful when users need to continue their tasks on the platform after signing.
Out-of-band - This is a default option, the user needs to login to Rabo Business Banking separately. This method is useful when signing users are not active on the platform at the moment of payment initiation.

Bulk payments

After submitting a regular bulk payment order, it must be signed by an authorized user using Rabobank’s interfaces. The user needs to login into Rabo Business Banking.

After submitting an STP bulk payment order, signing is not requested and not possible.

Authentication

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

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

With the /authorize endpoint the account holder is requested to give consent for a certain API (scope). After the consent is granted, 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.

Set up using the Authorization Services API .
Read the complete OAuth guide.

Relevant scope(s) for oauth2 access code flow

API	Scope name	Description
Business Single Payment Initiation	bspi.single.read-write	Payments from your payment account.
Business Bulk Payment Initiation	bbpi.bulk.read-write	Send batch payment files, signing in RBB required.
Business Bulk Payment Initiation - STP	bbpi.stp-credittransfer.read-write	Send credit transfer initiation batch payment files using straight through processing (already signed, are executed directly) for Direct Connectors.

Consent required for Third Parties and Direct Connectors:

Third Party
- Performing actions on behalf of your customers (Rabo account holders)
- The account holder must provide consent to the third party to Rabobank on behalf of their organisation for the specified account(s) and scopes (provide access to specific actions). This consent is continuous.
Direct Connector
- Performing actions on/from your own account
- You must provide consent for technical reasons for the specified account(s) and scopes (provide access to specific actions). This is a one time action.

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

Limits

Size limits

Payment files containing multiple batches can be sent to the bank using BBPI or BBPI-STP, with a maximum of 3,000 batches per file. To ensure smooth processing, do not exceed 25,000 payment orders in a one payment file. Larger files—up to 100,000 payment orders—can be processed if compressed using GZIP.

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 the Business Payment Initiation product.

Operation	Type	Limit (API calls / s)	Counts towards shared limit
`POST /v1/single/sepa-credit-transfers`	Shared	6	Yes
`POST /v1/periodic/sepa-credit-transfers`	Shared	6	Yes
`POST /v1/single/cross-border-credit-transfers`	Shared	6	Yes
`POST /v1/periodic/cross-border-credit-transfers`	Shared	6	Yes
`GET /v1/single/sepa-credit-transfers/{paymentId}`	Shared	6	Yes
`GET /v1/periodic/sepa-credit-transfers/{paymentId}`	Shared	6	Yes
`GET /v1/single/cross-border-credit-transfers/{paymentId}`	Shared	6	Yes
`GET /v1/periodic/cross-border-credit-transfers/{paymentId}`	Shared	6	Yes
`GET /v1/single/sepa-credit-transfers/{paymentId}/status`	Shared	6	Yes
`GET /v1/periodic/sepa-credit-transfers/{paymentId}/status`	Shared	6	Yes
`GET /v1/single/cross-border-credit-transfers/{paymentId}`	Shared	6	Yes
`GET /v1/periodic/cross-border-credit-transfers/{paymentId}/status`	Shared	6	Yes
`POST /credit-transfers`	Individual	5	No
`GET /credit-transfers/{paymentId}/status`	Individual	10	No
All (premium) Oauth calls	Shared	6	Yes

The table below describes the rate limiting for the Business Bulk Payment Initiation STP product.

Operation	Type	Limit (API calls / s)	Counts towards shared limit
`POST /bulk-stp/credit-transfers`	Shared	5	Yes
`GET /bulk-stp/credit-transfers/{paymentId}/status`	Shared	10	Yes
All (premium) Oauth calls	Shared	6	Yes