API Reference

Creation of a payment order of type Sepa Credit Transfer

post
https://api.rabobank.nl/openapi/bip/v3/payments/single-credit-transfers

This API can be used to initiate a payment for Business Instant Payout. Rabobank will validate on certificate and signature information as well as the order details and consent, before executing the payment. | NOTE: Supported characters allowed are A-Z, a-z, 0-9 and special characters includes ; . / \ +? ( ) , +E(at) - colon. No Diacritics letters or characters allowed.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Supports only Instant Payments. If not possible to process them, then they will be rejected

creditorAccount
object
required

Creditor account.

creditorAddress
object

Information about the creditor address. Characters allowed for Town and Address Line are a-z A-Z 0-9 and special characters ./+?semicolon(),'E(at)-

string

BIC of the Creditor Account.

string
required
length between 2 and 70

Name of the Creditor.

debtorAccount
object
required

Debtor account.

string

BIC of the Debtor Account.

string
required
length between 2 and 70

Name of the Debtor.

string
length between 0 and 35

End to End identification. Characters allowed are a-z A-Z 0-9 and special characters ./+?semicolon(),'E(at)-

instructedAmount
object
required

Instructed amount for given currency.

remittanceInformationStructured
object

Remittance Information Structured. Either Remittance Information Unstructured or Structured can be used, but not both. Characters allowed are a-z A-Z 0-9 and special characters ./+?semicolon(),'E(at)-

string
length between 0 and 140

Remittance Information Unstructured. Either Remittance Information Unstructured or Structured can be used, but not both. Characters allowed are a-z A-Z 0-9 and special characters ./+?semicolon(),'E(at)-. In case the Purpose of Payment (PoP) is required the PoP has to be entered at the beginning of the remittanceInformationUnstructured

uuid
required

This field (UUID value) is the paymentId returned for the payment initiated and meant to provide a retry mechanism for the customer when a payment order has been rejected/cancelled. In case of a retry the same uniqueRequestorReference value has to be entered. If previous payment order has been executed then this will be detected and second attempt will be rejected as a duplicate payment.

Headers
string
required

Content type of the request (application/json).

uuid
required

ID of the request, unique to the call, as determined by the initiating party.

string
required

The forwarded IP Address header field consists of the corresponding http request IP Address field of the Initiating Party.

string
required

Public certificate of the Initiating Party that corresponds with the signature made by the Initiating Party.

string
required

Standard https header element with date, time and timezone.

string
required

Signature is made up of the headers: date, digest and x-request-id. For more information see additional documentation in portal.

string
required

The digest is a base64 encoded hash of the body (SHA-512 or SHA-256 is allowed).

string

Option that will enable the user to make use of the reroute functionality to execute the payment instruction as a SEPA CT transaction in case it is not possible to execute it instantly. Possible values are : Yes/No

string

This field allows the user to indicate whether Rabobank should perform the Verification of Payee (VoP) check. Enter "no" if the user does not want the bank to carry out this verification. By default, Rabobank performs a Verification of Payee check for every payment instruction, verifying whether the account number matches the provided account holder name. If there is a mismatch, the bank will reject the payment instruction. Use this field if the user has already conducted the verification, for example by using the Payee Account Check. Possible values are : yes/no

string

This field allows the user to indicate whether the payment instruction can be processed without strict time constraints. When set to "yes," Rabobank will attempt to process the payment instantly if possible, but there is no guarantee that the payment will be completed within 10 seconds. Using this option the payment will be executed as a non-instant Euro Payment. If set to "no," the payment will follow the standard processing flow but payments might get rejected when payment cannot be executed within 10 seconds.
Use this field when the payment does not require guaranteed immediate execution but can benefit from faster processing when available.

Responses

503

Service Unavailable

Updated 4 days ago

Language
Credentials
Missing 1 required scope
URL
LoadingLoading…
Response
Choose an example:
application/json

Updated 4 days ago