Creation of a payment order of type Sepa Credit Transfer

post

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

This API can be used to create a payment initiation request at Rabobank.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

SEPA Credit Transfer Payment Initiation

creditorAccount

object

required

Creditor account.

creditorAddress

object

Information over creditor address.

creditorAgent

string

creditorName

string

required

length between 2 and 70

Name of Creditor.

debtorAccount

object

required

Debtor account.

debtorName

string

required

length between 2 and 70

Name of the Debtor.

endToEndIdentification

string

length between 0 and 35

end to end identification.

instructedAmount

object

required

Instructed amount for given currency.

remittanceInformationStructured

object

Remittance Information Structured.It can have either 'RemittanceInformationUnstructured' or 'RemittanceInformationStructured'

remittanceInformationUnstructured

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)-.

requestedExecutionDate

date

A ISO8601 date of the excution of the payment initiation. (must be future/current date)

Headers

Content-Type

string

required

Content type of the request (application/json)

X-Request-ID

uuid

required

This is the unique ID of Initiating Party for the request.

PSU-IP-Address

string

required

The forwarded IP Address header field consists of the corresponding HTTP request IP Address field between PSU and Initiating Party. If not available, the Initiating Party shall use the IP Address used by the Initiating Party when submitting this request.

Signature-Certificate

string

required

public certificate of the Initiating Party that corresponds with the signature made by the Initiating Party

Date

string

required

Standard https header element with date, time and timezone.

IP-Redirect-URI

string

URI of the Initiating Party, where the transaction flow shall be redirected to after a Redirect. Note: This parameter becomes mandatory only when the parameter 'redirectionFlag' is sent as 'Yes'.

Signature

string

required

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

Digest

string

required

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

redirectionFlag

string

Defaults to No

The user can decide if a payment should be signed immediately or in RBB. This flag value should be 'Yes' or 'No' and the default value is 'No' which means signing in RBB. Note: The parameter 'IP-Redirect-URI' becomes mandatory when this parameter is sent as 'Yes'.

Responses

503

Service Unavailable

201The payment initiation of the Initiating Party is created.

400Bad Request

401Unauthorised

405Method Not Allowed

500Internal Server Error