Creation of an instant payout order of type Cross Border Credit Transfer

post

https://api.rabobank.nl/openapi/bip/v3/payments/cross-border-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

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Cross Border Credit Transfer Payment Initiation. It can have either 'RemittanceInformationUnstructured' or 'RemittanceInformationStructured'.

Cross Border Credit Transfer information.

chargeBearer

string

enum

required

Charge Bearer. ChargeBearerType1Code from ISO20022

Allowed:

clearingSystem

object

Clearing System

creditorAccount

object

required

Creditor account.

creditorAddress

object

required

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

creditorAgent

string

required

creditorName

string

required

length between 2 and 70

Name of Creditor.

debtorAccount

object

required

Debtor account.

debtorAgent

string

BIC of the 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. 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)-

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

uniqueRequestorReference

uuid

required

This field is to fill it with a UUID value. Field is 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

Content-Type

string

required

Content type of the request (application/json).

X-Request-ID

uuid

required

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

PSU-IP-Address

string

required

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

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.

Signature

string

required

Signature is made up of the headers: date, digest and 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).

Responses

503

Service Unavailable

201The payment initiation of the client is created.

400Bad Request

401Unauthorised

405Method Not Allowed

422Unprocessable Entity

500Internal Server Error