Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • ConsentId.

  • CreationDateTime the domestic-future-dated-payment-consents resource was created.

  • Status and StatusUpdateDateTime of the domestic-future-dated-payment-consents resource.

  • Permission field in the original request.

  • ReadRefundAccount field in the original request.

  • CutOffDateTime Behaviour is explained in the Payment Initiation API Profile, Section - Payment Restrictions -> CutOffDateTime Behaviour.

  • ExpectedExecutionDateTime for the domestic-future-dated-payment resource if created before CutOffDateTIme - the expected DateTime the payment is executed against the Debtor Account. If populated, the ASPSP must update the value with any changes (e.g., after user/customer authorisation).

  • ExpectedSettlementDateTime for the domestic-future-dated-payment resource if created before CutOffDateTIme - the expected DateTime the payment will be received at the Creditor Account. If populated, the ASPSP must update the value with any changes (e.g., after user/customer authorisation).

  • Charges array - for the breakdown of applicable ASPSP charges.

  • Post successful Useruser/Customer customer Authentication, an ASPSP may provide Debtor/Name in the Payment Order Consent Response, even when the Payer did not provide the Debtor Account via PISP

...