...
Once the domestic-future-dated-payment-consent consents has been authorised by the PSUuser/customer, the PISP can proceed to submitting the domestic-future-dated-payment payments for processing:
This is done by making a POST request to the domestic-future-dated-payments endpoint.
This request is an instruction to the ASPSP (Bank) to begin the domestic future dated payment journey. The PISP must submit the domestic future dated payment immediately, however, there are some scenarios where the ASPSP (Bank) may not warehouse the domestic future dated payment immediately (e.g., busy periods at the ASPSP)
The PISP must ensure that the Initiation and Risk sections of the domestic-future-dated-payment payments match the corresponding Initiation and Risk sections of the domestic-future-dated-payment-consent consents resource. If the two do not match, the ASPSP must ASPSP (Bank) must not process the request and must respond with a 400 (Bad Request).
Any operations on the domestic-future-dated-payment payments resource will not result in a Status change for the domestic-future-dated-payment payments resource
2.1.1 Status
A domestic-future-dated-payment payments can only be created if its corresponding domestic-future-dated-payment-consent consents resource has the status of "Authorised".
The domestic-future-dated-payment payments resource that is created successfully must have one of the following Status codes:
...
A PISP can retrieve the domestic-future-dated-payment payments to check its status.
2.2.1 Status
The domestic-future-dated-payment payments resource must have one of the following Status codes:
...
A PISP can retrieve the Details of the underlying payment transaction via this endpoint. This resource allows ASPSPs (Banks) to return richer list of Payment Statuses, and if available payment scheme related statuses.
...
2.4 PATCH /domestic-future-dated-payments/{DomesticFutureDatedPaymentId}
PSUs Users/Customers can setup, through PISPs, an instruction to their ASPSPs (Banks) to cancel a future dated domestic payment.
...
The state model for the domestic-future-dated-payment payments resource describes the initiation status only. I.e., not the subsequent execution of the domestic-future-dated-payment.
...
The domestic-future-dated-payment payments request object contains the:
ConsentId.
The full Initiation and Risk objects from the domestic-future-dated-payment-consent consents request.
The Initiation and Risk sections of the domestic-future-dated-payment payments request must match the Initiation and Risk sections of the corresponding domestic-future-dated-payment-consent consents request.
3.2.3 Data Dictionary
Name | Occurrence | XPath | Definition | Class/ Datatype | Codes | Pattern |
OBWriteDomesticFutureDatedPayment |
| OBWriteDomesticFutureDatedPayment |
| OBWriteDomesticFutureDatedPayment |
|
|
Data | 1..1 | OBWriteDomesticFutureDatedPayment/Data |
| OBWriteDomesticFutureDatedPayment/Data |
|
|
ConsentId | 1..1 | OBWriteDomesticFutureDatedPayment/Data/ConsentId | OB: Unique identification as assigned by the ASPSP (Bank) to uniquely identify the consent resource. | String |
|
|
Initiation | 1..1 | OBWriteDomesticFutureDatedPayment/Data/Initiation | The Initiation payload is sent by the initiating party to the ASPSP (Bank). It is used to request movement of funds from the debtor account to a creditor for a single future dated domestic payment. | OBDomesticFutureDatedInitiation |
|
|
Risk | 1..1 | OBWriteDomesticFutureDatedPayment/Risk | The Risk section is sent by the initiating party to the ASPSP. It is used to specify additional details for risk scoring for Payments. | OBRisk |
|
|
...
The domestic-future-dated-payment payments response object contains the:
DomesticFutureDatedPaymentId.
ConsentId.
CreationDateTime the domestic-future-dated-payment payments resource was created.
Status and StatusUpdateDateTime of the domestic-future-dated-payment payments resource.
ExpectedExecutionDateTime for the domestic-future-dated-payment payments resource.
ExpectedSettlementDateTime for the domestic-future-dated-payment payments resource.
Refund account details, if requested by PISP as part of the domestic-payment-consents resource.
Charges array - for the breakdown of applicable ASPSP (Bank) charges.
The Initiation object from the domestic-future-dated-payment-consent.
An ASPSP (Bank) should conditionally provide Debtor/Name in the Payment Order Response, even when the Payer user/customer didn't provide the Debtor Account via PISP
...
Name | Occurrence | XPath | Definition | Class/ Datatype | Codes | Pattern |
OBWriteDomesticFutureDatedPaymentResponse |
| OBWriteDomesticFutureDatedPaymentResponse |
| OBWriteDomesticFutureDatedPaymentResponse |
|
|
Data | 1..1 | OBWriteDomesticFutureDatedPaymentResponse/Data |
| OBWriteDomesticFutureDatedPaymentResponse/Data |
|
|
DomesticFutureDatedPaymentId | 1..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/DomesticFutureDatedPaymentId | OB: Unique identification as assigned by the ASPSP (Bank) to uniquely identify the domestic future dated payment resource | String |
|
|
ConsentId | 1..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/ConsentId | OB: Unique identification as assigned by the ASPSP (Bank) to uniquely identify the consent resource | String |
|
|
CreationDateTime | 1..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/CreationDateTime | Date and time at which the message was created | DateTime |
|
|
Status | 1..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/Status | Specifies the status of the payment order resource | String | Enum:
|
|
StatusUpdateDateTime | 1..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/StatusUpdateDateTime | Date and time at which the resource status was updated | DateTime |
|
|
ExpectedExecutionDateTime | 0..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/ExpectedExecutionDateTime | Expected execution date and time for the payment resource | DateTime |
|
|
ExpectedSettlementDateTime | 0..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/ExpectedSettlementDateTime | Expected settlement date and time for the payment resource | DateTime |
|
|
Refund | 0..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/Refund | Unambiguous identification of the refund account to which a refund will be made as a result of the transaction | OBDomesticRefundAccount |
|
|
Charges | 0..n | OBWriteDomesticFutureDatedPaymentResponse/Data/Charges | Set of elements used to provide details of a charge for the payment initiation | OBCharge |
|
|
Initiation | 1..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/Initiation | The Initiation payload is sent by the initiating party to the ASPSP (Bank). It is used to request movement of funds from the debtor account to a creditor for a single future dated domestic payment | OBDomesticFutureDatedInitiation |
|
|
Debtor | 0..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/Debtor | Set of elements used to identify a person or an organisation. | OBWriteDomesticFutureDatedPaymentResponse/Data/Debtor |
|
|
Name | 1..1 | OBWriteDomesticFutureDatedPaymentResponse/Data/Debtor/Name | The account name is the name or names of the account owner(s) represented at an account level, as displayed by the ASPSP's online channels. | String |
|
|
...