Renamed to Implementer's Draft. Client Registration section moved to OB Directory Specification
Implementer's Draft v1.0.1
Open Banking Read/Write API Team
Recreating document from up to date sub sections.
Clarifications to Implementation Guide
Enhanced Payments API Sequence Diagram to improve readability
Enhanced Accounts API Sequence Diagram to improve readability and add in the GET and DELETE flows for Account Requests
Removing the need to repeat the API scopes when the exchanging of an Authorization Code for an Access Token for Payments and Accounts API requests in the Sequence Diagram and example HTTP Requests
Implementer's Draft v1.1
Open Banking Read/Write API Team
Reflecting changes to the R/W API specifications for v1.1:
Updated Account Identification SchemeName and structure from BBAN to SortCodeAccountNumber
Corrected -00:00 timezone format to +00:00
Updated format for fields within Meta and Links sections to upper camel case
Corrected "AwaitingAuthentication" to "AwaitingAuthorisation” in non-normative example
Removed x-jws-signature headers from non-normative examples
Errata to add redirect_uri to header for the Request : Access Token Request using Authorization Code
UK Open Banking OIDC Security Profile
...
1. The PISP can query for the status of a Payment-Submission by invoking the /payment-submissions using the known PaymentSubmissionId. This can use an existing access token with payments scope or the PISP can obtain a fresh access token by replaying the client credentials grant request as per Step 2 - Setup Single Payment Initiation.
2. A PISP can also optionally query for the status of a Payment resource by invoking /payments/{PaymentId}. This can use an existing access token with payments scope or the PISP can obtain a fresh access token by replaying the client credentials grant request as per Step 2 - Setup Single Payment Initiation.