Creation of a payment order of type periodic cross border Credit Transfer

post

https://api.rabobank.nl/openapi/payments/payment-initiation/pis/v1/periodic-payments/cross-border-credit-transfers

This API can be used to create a payment initiation request at Rabobank. Rabobank will validate on eIDAS certificate, request syntax tpp role and semantics before returning the SCA redirect URL for authentication by the PSU (Redirect SCA approach).

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Periodic Cross Border Credit Transfer Payment Initiation

Standing Order information

clearingSystem

object

Clearing System

creditorAccount

object

required

Creditor account.It will be bban for USD.It will be either iban or bban for GBP.

creditorAddress

object

required

Information over creditor address.

creditorAgent

string

required

creditorName

string

required

length between 2 and 70

Name of Creditor.

debtorAccount

object

Debtor account.

endToEndIdentification

string

length between 0 and 35

end to end identification.

instructedAmount

object

required

Instructed amount for given currency.

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)-. In case the Purpose of Payment (PoP) is required the PoP has to be entered at the beginning of the remittanceInformationUnstructured.

requestedExecutionDate

date

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

chargeBearer

string

enum

required

Charge Bearer. ChargeBearerType1Code from ISO20022

Allowed:

endDate

date

The last applicable day of execution. If not given, it is an infinite standing order.

frequency

string

enum

required

The frequency of the recurring payment resulting from this standing order.

startDate

date

required

The first applicable day of execution starting from this date is the first payment.

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 TPP. If not available, the TPP shall use the IP Address used by the TPP when submitting this request.

TPP-Signature-Certificate

string

required

public certificate of the TPP that corresponds with the signature made by the TPP

Date

string

required

Standard https header element with date, time and timezone.

TPP-Redirect-URI

string

required

URI of the TPP, where the transaction flow shall be redirected to after a Redirect.

Signature

string

required

Signature is made up of the headers - date, digest, x-request-id and tpp-redirect-uri. 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).

Responses

503

Service Unavailable

201The payment initiation of the tpp is created.

400Bad Request

401Unauthorised

405Method Not Allowed