A valid request URL is required to generate request examples{
"Data": {
"AccountId": "<string>",
"ScheduledPayment": [
{
"ScheduledPaymentId": "<string>",
"ScheduledType": "Arrival",
"ScheduledPaymentDateTime": "2023-11-07T05:31:56Z",
"InstructedAmount": {
"Amount": "<string>",
"Currency": "AED"
},
"AccountHolderName": "<string>",
"AccountHolderShortName": "<string>",
"CreditorReference": "<string>",
"DebtorReference": "<string>",
"CreditorAgent": {
"SchemeName": "BICFI",
"Identification": "<string>"
},
"CreditorAccount": [
{
"SchemeName": "IBAN",
"Identification": "<string>"
}
]
}
]
},
"Links": {
"Self": "<string>",
"First": "<string>",
"Prev": "<string>",
"Next": "<string>",
"Last": "<string>"
},
"Meta": {
"TotalPages": 1
}
}{
"Errors": [
{
"Code": "AccessToken.Unauthorized",
"Message": "<string>",
"Path": "<string>",
"Url": "<string>"
}
]
}{
"Errors": [
{
"Code": "AccessToken.Unauthorized",
"Message": "<string>",
"Path": "<string>",
"Url": "<string>"
}
]
}{
"Errors": [
{
"Code": "AccessToken.Unauthorized",
"Message": "<string>",
"Path": "<string>",
"Url": "<string>"
}
]
}Get Scheduled Payments
The list below outlines the Consent Permissions that are applicable to this resource:
- ReadScheduledPaymentsBasic
- ReadScheduledPaymentsDetail
Refer to Customer Experience Guidelines, Account Information, Data Groups for further information.
A valid request URL is required to generate request examples{
"Data": {
"AccountId": "<string>",
"ScheduledPayment": [
{
"ScheduledPaymentId": "<string>",
"ScheduledType": "Arrival",
"ScheduledPaymentDateTime": "2023-11-07T05:31:56Z",
"InstructedAmount": {
"Amount": "<string>",
"Currency": "AED"
},
"AccountHolderName": "<string>",
"AccountHolderShortName": "<string>",
"CreditorReference": "<string>",
"DebtorReference": "<string>",
"CreditorAgent": {
"SchemeName": "BICFI",
"Identification": "<string>"
},
"CreditorAccount": [
{
"SchemeName": "IBAN",
"Identification": "<string>"
}
]
}
]
},
"Links": {
"Self": "<string>",
"First": "<string>",
"Prev": "<string>",
"Next": "<string>",
"Last": "<string>"
},
"Meta": {
"TotalPages": 1
}
}{
"Errors": [
{
"Code": "AccessToken.Unauthorized",
"Message": "<string>",
"Path": "<string>",
"Url": "<string>"
}
]
}{
"Errors": [
{
"Code": "AccessToken.Unauthorized",
"Message": "<string>",
"Path": "<string>",
"Url": "<string>"
}
]
}{
"Errors": [
{
"Code": "AccessToken.Unauthorized",
"Message": "<string>",
"Path": "<string>",
"Url": "<string>"
}
]
}Authorizations
OAuth2 PAR flow, it is required when the User needs to perform SCA with the LFI when a TPP wants to access an LFI resource owned by the User. Please refer to OpenID FAPI Security Profile 1.0 -Part 2 Advanced - 5.2.2 point 14 - shall authenticate the confidential client using one of the following methods private_key_jwt and OpenID Connect Core 1.0 9. Client Authentication private_key_jwt
Headers
An authorization Token as per https://tools.ietf.org/html/rfc6750
The time when the User last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
^(Mon|Tue|Wed|Thu|Fri|Sat|Sun), \d{2} (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec) \d{4} \d{2}:\d{2}:\d{2} (GMT|UTC)$The User's IP address if the User is currently logged in with the TPP.
An RFC4122 UID used as a correlation id.
Indicates the user-agent that the User is using.
Path Parameters
AccountId
Was this page helpful?

