With single payment initiation, you can initiate Single credit transfers on behalf of your users with a Rabobank business payment account and retrieve the status of an initiated transaction or file.

Single payments step-by-step

Before initiating single payments, the account holder must provide consent to the third party for sending single payment orders to Rabobank on behalf of their organisation for the specified payment account(s). This consent is continuous.

The account holder initiates the payment order to be executed by Rabobank using your platform.
Rabobank provides the API user (third party) with the status on the submitted upload.
The customer authorizes the payment:
- in Rabo Business Banking or Rabo Business Banking Pro using Sign/Sign orders from the menu, or
- directly from your platform, using the redirect URL that you received from us (optional, on request) after submitting the payment order.
After successful authorisation, Rabobank starts processing the payment order following its payment process same as if the payment is submitted using a Rabobank channel. Example:
- If a payment order is refused due to insufficient funds, we may check one or more times, up to and including three working days after the date of refusal, whether the reason for refusal still exists. If we believe that there is no longer a reason for refusal, we may restart processing the payment order on behalf of our customer.
- When processing a Euro Payment, we check whether the beneficiary's bank is reachable for Instant Payments. If true, we process the payment order as an Instant Payment. If false, we process the payment order as a normal SEPA Credit Transfer. etc.
The third party can retrieve the status of the payment through the status endpoint to keep track.

Requests

The POST Payment and GET Status 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.

You can initiate a payment with Creation of a payment order of type Sepa Credit Transfer

POST https://api-sandbox.rabobank.nl/openapi/sandbox/payments/v1/single/sepa-credit-transfers

Endpoints for initiating single payments:
Creation of a payment order of type Sepa Credit Transfer
POST /payments/v1/single/sepa-credit-transfers

Creation of a periodic payment order of type Sepa Credit Transfer
POST /payments/v1/periodic/sepa-credit-transfers

Creation of a payment order of type Cross Border Credit Transfer
POST /payments/v1/single/cross-border-credit-transfers

Creation of a payment order of type Periodic Cross Border Credit Transfer
POST /payments/v1/periodic/cross-border-credit-transfers

You can retrieve the status of a payment with Status of a single sepa payment

GET https://api-sandbox.rabobank.nl/openapi/sandbox/payments/v1/single/cross-border-credit-transfers/123e4567-e89b-42d3-a456-556642440005/status

Endpoints for retrieving the status of single payments:

Status of a single sepa payment
GET /payments/v1/single/sepa-credit-transfers/{paymentId}/status

Status of a periodic sepa payment
GET /payments/v1/periodic/sepa-credit-transfers/{paymentId}/status

Status of a cross border payment
GET /payments/v1/single/cross-border-credit-transfers/{paymentId}/status

Status of a periodic cross border payment
GET /payments/v1/periodic/cross-border-credit-transfers/{paymentId}/status

After the payment is signed by the account holder, you can retrieve the details of a payment with Details of a single sepa payment

GET https://api-sandbox.rabobank.nl/openapi/sandbox/payments/v1/single/sepa-credit-transfers/123e4567-e89b-42d3-a456-556642440005

Endpoints for retrieving the details of single payments:

Details of a single sepa payment
GET /payments/v1/single/sepa-credit-transfers/{paymentId}

Details of a periodic sepa payment
GET /payments/v1/periodic/sepa-credit-transfers/{paymentId}

Details of a cross border payment
GET /payments/v1/single/cross-border-credit-transfers/{paymentId}

Details of a periodic cross border payment
GET /payments/v1/periodic/cross-border-credit-transfers/{paymentId}

Transfer between Payment accounts and Piggy banks

For single and periodic SEPA credit transfers, you are able to transfer money between payment accounts and piggy banks using the following:

From IBAN payment account to IBAN savings account: add Amount and enter naar: piggy bank name in the unstructured remittance information.
From IBAN savings account to IBAN payment account: add Amount and enter van: piggy bank name in the unstructured remittance information.

🚧
Money transfer from a piggy bank to an IBAN payment account is allowed only when both accounts are within the same agreement.
In case the piggy bank name is not spelled correctly, then the amount is transferred to the GENERAL piggy bank of the savings account.

To retrieve the balance information on piggy banks, use the BAI Balances API.

Response

POST Payment for Business Payment Initiation Single Payments

You can initiate a Single Business payment using a POST payments request.

After receiving the payment, a response of PDNG or RJCT is returned. You can use the {paymentId} endpoint to get the details of the payment and the status endpoint to get the latest status of the payment.

Example (POST /payments/v1/single/sepa-credit-transfers):

{
  "paymentId": "123e4567-e89b-42d3-a456-456789345678",
  "transactionStatus": "PDNG"
}

Below you can find all supported test scenarios. In order to test these scenarios, call the API by using the examples for the fields provided in the endpoint description for POST/sepa-credit-transfers.

Supported Scenarios

Scenario	endToEndId/Error message	amt.currency	amt.content	creditorName	credAc.iban	credAc.currency	dbtrAc.iban	dbtrAc.currency	remStrType	remStrIssuer	remStrReference	Remarks
201 CREATED	PI-123456789	EUR	10.25	Company	NL10RABO0123456789	EUR	NL10RABO0912345678	EUR	SCOR	CUR	1515140706132013
400 Bad Request	PI-123456789	EUR	10.25	Company		EUR		EUR	SCOR	CUR	1515140706132013	Send a transfer with leaving one of the fields empty, for example IBAN
400 Bad Request
ERROR MESSAGE	PI-123456789											Paymentfailed response
401 Unauthorised
CERTIFICATE_INVALID	PI-123456789											Use the value invalid for the header: TPP-Signature-Certificate.
401 Unauthorised
CERTIFICATE_EXPIRED	PI-123456789											Use the value expired for the header: TPP-Signature-Certificate.
401 Unauthorised
CERTIFICATE_BLOCKED	PI-123456789											Use the value blocked for the header: TPP-Signature-Certificate.
401 Unauthorised
CERTIFICATE_REVOKED	PI-123456789											Use the value revoked for the header: TPP-Signature-Certificate.
404 Not Found	PI-123456789											Change the URL to payments/sepa-credit-transfers
405 Method Not Allowed	PI-123456789											Use POST instead of GET
503 Service Unavailable	PI-123456789											Add shown info to EndtoEnd ID in body

Note: These codes are for Sandbox only.

To create a recurring payment, you need to use the API contains periodic with the following extra content.

Attribute	Description	Value
startDate	ISO date	2023-01-25
endDate	ISO date	2025-01-25
frequency	Enum value	Monthly

The difference between single SEPA credit transfer and recurring payment is the startDate and frequency are mandatory. The rest of the scenarios are the same as single SEPA credit transfers.

GET Payment details for Business Payment Initiation Single Payments

You can retrieve the detail information for a payment initiation using a GET {paymentId} request.

Some scenarios, as mentioned below, require specific paymentId(s) in the URL, example: (GET /payments/v1/single/sepa-credit-transfers/{paymentId}) to get the mentioned responses.

Example (/payments/v1/single/sepa-credit-transfers/{paymentId}):

{
    "creditorAccount": {
        "iban": "NL10RABO0123456789"
    },
    "creditorName": "Company",
    "debtorAccount": {
        "currency": "EUR",
        "iban": "NL10RABO0912345678"
    },
    "debtorName": "Mason Stevens",
    "instructedAmount": {
        "content": "10.25"
    }
}

Below you can find all supported test scenarios:

Scenario	Remarks	payment-id	amt.currency	amt.content	credAc.iban	credAc.bban	credAc.currency	dbtrAc.iban	dbtrAc.currency	creditorName	debtorName	startDate	frequency
200 OK	Single Sepa	123e4567-e89b-42d3-a456-556642440005	EUR	10.25	NL10RABO0123456789		EUR	NL10RABO0912345678	EUR	Company	Mason Stevens
200 OK	Single CB IBAN	6509c408-eb8e-40a5-83d9-05b78cc51009	GBP	11.25	GB60BARC48291709876543		GBP	NL10RABO0912345678	EUR	Company1	Ina Copeland
200 OK	Single CB BBAN	1709c408-eb8e-40a5-83d9-05b78cc51b41		11.25		02100002112345678901234567		NL10RABO0912345678	EUR	Company1	Ina Copeland
200 OK	Periodic Sepa	4982e122-57e1-4f3f-b39a-43b50dc734b5	EUR	12.25	NL10RABO0123456789		EUR	NL10RABO0912345678	EUR	Company2	Allen Dawson	2023-01-25	Daily
200 OK	Periodic CB IBAN	1f22d0e0-a4d5-459f-992e-1ccb4bcbc70e	GBP	13.25	GB60BARC48291709876543		GBP	NL10RABO0123456789	EUR	Company3	Logan Bowen	2023-01-25	Quarterly
200 OK	Periodic CB BBAN	4522d0e0-a4d5-459f-992e-1ccb4bcbc654		13.25		48291709876543		NL10RABO0123456789	EUR	Company3	Logan Bowen	2023-01-25	Quarterly
400 Bad Request		123e4567-e89b-42d3-a456-556642440006
404 Not Found		123e4567-e89b-42d3-a456-556642440007
503 Service Unavailable		123e4567-e89b-42d3-a456-556642440003

Note: These codes are for Sandbox only, for testing with the Sandbox example values for Signature add header Date = Tue, 24 Jan 2023 06:53:05 GMT

GET Payment Status for Business Payment Initiation Single Payments

You can retrieve the status information for a payment initiation using a GET status request.

Some scenarios, as mentioned below, require specific paymentId(s) in the URL, example: GET /payments/v1/single/sepa-credit-transfers/{paymentId}/status to get the mentioned responses.

Example

{
    "transactionStatus": "PDNG"
}

Below you can find all supported test scenarios:

Scenario	responseStatus	payment-id	remark
200 OK	PDNG	123e4567-e89b-42d3-a456-556642440002
200 OK	ACSP	123e4567-e89b-42d3-a456-556642440003
200 OK	RJCT	123e4567-e89b-42d3-a456-556642440004
200 OK	ACSC	123e4567-e89b-42d3-a456-556642440005
200 OK	ACCC	123e4567-e89b-42d3-a456-556642440006
200 OK (Not implemented)	CANC	123e4567-e89b-42d3-a456-556642440014
200 OK	ACSP	123e4567-e89b-42d3-a456-556642440018
200 OK	ACSP	123e4567-e89b-42d3-a456-556642440020
400 BAD REQUEST		123e4567-e89b-42d3	PaymentId is not a valid UUID
400 BAD REQUEST*		123e4567-e89b-42d3-a456-556642440008	Header: X-Request-ID (123e4567) is not UUID
401 Unauthorised	CERTIFICATE_INVALID	123e4567-e89b-42d3-a456-556642440000	Use the value invalid for the header: `TPP-Signature-Certificate`
401 Unauthorised	CERTIFICATE_EXPIRED	123e4567-e89b-42d3-a456-556642440000	Use the value expired for the header: `TPP-Signature-Certificate`
401 Unauthorised	CERTIFICATE_BLOCKED	123e4567-e89b-42d3-a456-556642440000	Use the value blocked for the header: `TPP-Signature-Certificate`
401 Unauthorised	CERTIFICATE_REVOKED	123e4567-e89b-42d3-a456-556642440000	Use the value revoked for the header: `TPP-Signature-Certificate`
404 NOT_FOUND		123e4567-e89b-42d3-a456-556642440009	Forced status not found.
405 Method Not Allowed		123e4567-e89b-42d3-a456-556642440001	Use POST instead of GET
503 SERVICE_UNAVAILABLE		123e4567-e89b-42d3-a456-556642440010	Forced service unavailable.

Note: These codes are for Sandbox only.

Here is a description of the expected response statuses:

Status	Full name	Description
ACCC	AcceptedSettlementCompleted	This status is only applicable for instant payments. Settlement on the creditor's account has been completed.
ACSC	AcceptedSettlementCompleted	Settlement on the debtor's account has been completed. Also applicable when: A recurring payment has passed the end date. A recurring payment has been withdrawn.
ACSP	AcceptedSettlementInProcess	All preceding checks such as technical validation and customer profile were successful. The payment initiation was successfully signed. The payment initiation has been accepted for execution, but before settlement on the debtor’s account. Note: Execution is not guaranteed after this status. There are a number of reasons that may lead to its rejection.
ACTC	AcceptedTechnicalValidation	Authentication and syntactical and semantical validation (Technical validation) are successful. Payment is not signed yet.
RCVD	Received	Payment initiation has been received by the receiving agent. Technical validation has started.
PDNG	Pending	Payment initiation or individual transaction included in the payment initiation is pending and in progress for signing. Further checks (and status update) will be performed.
RJCT	Rejected	Payment initiation or individual transaction included in the payment initiation has been rejected.
CANC	Cancelled	Payment initiation has been cancelled before execution. This status is only applicable for future dated payments that have been successfully cancelled.