PSD2 Single Payment Initiation

With the PSD2 Single Payment Initiation API, Certified Payment Initiation Service Providers (PISPs) can create a seamless journey for your users while providing them full control throughout the process, the account holder can always decide which payments are executed.

You can initiate a single credit transfer on behalf of your users using a Rabobank payment account. You can also retrieve the status of the initiated transaction to keep track.

📘

This API can be used through your app or web service.

The API is suited for one-time or recurring single Euro Payments (SEPA) and World Payments (non SEPA). Euro Payments will be credited directly in case the beneficiary bank participates in Instant Payments.

For more information, read PSD2 Single Payment API flow.

🚧

Oauth is not required for this API.

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.

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 POST/v1/payments/sepa-credit-transfers.

You can retrieve the details of payment with GET /xxx-credit-transfers/{paymentId}.

You can retrieve the status of a payment with GET /status (GET/v1/payments/cross-border-credit-transfers/{paymentId}/status)

You can delete a periodic or future dated payment via DELETE /{paymentService}/{paymentProduct}/{paymentId}.

Response

POST Payment for PSD2 Payment Initiation Single Payments

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

After receiving the payment, a response of ACTC 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.

To view the POST parameters, read the following endpoint descriptions:

• POST/v1/payments/cross-border-credit-transfers
• POST/v1/payments/sepa-credit-transfers
• POST/v1/periodic-payments/cross-border-credit-transfers
• POST/v1/periodic-payments/sepa-credit-transfers

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.

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

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 PSD2 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 /paymentsGET/v1/payments/sepa-credit-transfers/{paymentId}/status) to get the mentioned responses.

To view the GET parameters, read the following endpoint descriptions:

• GET/v1/payments/cross-border-credit-transfers/{paymentId}
• GET/v1/payments/sepa-credit-transfers/{paymentId}
• GET/v1/periodic-payments/cross-border-credit-transfers/{paymentId}
• GET/v1/periodic-payments/sepa-credit-transfers/{paymentId}

Below you can find all supported test scenarios.

Note: These codes are for Sandbox only, for testing with the Sandbox example values for Signature add header Date = Thu, 24 May 2022 06:53:05 GMT.

GET Payment Status for PSD2 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.

To view the GET parameters, read the following endpoint descriptions:

• GET/v1/payments/cross-border-credit-transfers/{paymentId}/status
• GET/v1/payments/sepa-credit-transfers/{paymentId}/status
• GET/v1/periodic-payments/cross-border-credit-transfers/{paymentId}/status
• GET/v1/periodic-payments/sepa-credit-transfers/{paymentId}/status

Below you can find all supported test scenarios.

Note: These codes are for Sandbox only.

🚧

The FundsAvailable indicator shows whether funds are available on the customer account for the payment initiated. The availability of the balance is determined immediately after signing by the customer.

If:

• Funds Available = True, at the time of signing, the available balance is found sufficient.
• Funds Available = False, the available balance is not sufficient. You can choose to wait 3 days for the balance to increase or delete the relevant payment using the Delete Payments call. If the account has consistently insufficient funds the payment may get cancelled.
• Funds Available = Anomaly, a different process has been followed, as a result of which the funds available check could not be performed and further processing of the payment is not guaranteed. Please contact Rabobank, if this occurs (frequently).

DELETE Payment for PSD2 Payment Initiation Single Payments

You can cancel the payment created with the Payment Initiation API by using a DELETE payment request.

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

Below you can find all supported test scenarios. The payment IDs are available among all the supported payment services and products.

Note: These codes are for Sandbox only.

Expected response statuses with description