"openapi: 3.0.1\ninfo:\n title: Payment Initiation\n x-technical-name: ob-payment-initiation-v31\n x-api-type: System\n x-santander-catalogation:\n bian-landscape-version: 8\n bian-business-area: Sales and Service\n bian-business-domain: Servicing\n bian-service-domain: Payment Initiation\n description: \"This API provides the ability for authorised payment initiation service providers (PISPs, TPPs - third party providers) to initiate and set up new domestic, international and file based payments. The TPPs will be able to initiate requests directly from the customer's (PSU - Payment Service User) current, personal or business - accounts, after being granted consent. Within Domestic Payments, Faster and CHAPS immediate payments can be initiated.\"\n termsOfService: 'https:\/\/www.openbanking.org.uk\/terms'\n contact:\n name: Open Banking Support\n email: PaymentsAPIsSupport@santander.co.uk\n url: 'https:\/\/directory.openbanking.org.uk\/obieservicedesk\/s\/'\n license:\n name: open-licence\n url: 'https:\/\/www.openbanking.org.uk\/open-licence'\n version: v3.1.10\nx-portal-category: Payment\nservers:\n - url: https:\/\/personal-api-ob.omni.slz.santander.co.uk\n - url: https:\/\/business-api-ob.omni.slz.santander.co.uk\npaths:\n #### Open Banking endpoints ####\n \/awspis\/open-banking\/v3.1\/pisp\/domestic-payment-consents:\n post:\n tags:\n - Domestic Payments\n summary: 'Create a new domestic payment consent resource'\n description: 'This endpoint allows the PISP to ask an ASPSP to create a new domestic\n\n payment consent resource. The POST action indicates to the ASPSP that a domestic payment consent has been staged. At this point, the PSU may not have been identified by the ASPSP, and the request payload may not contain any information of the account that should be debited. The endpoint allows the PISP to send a copy of the consent (between PSU and PISP) to the ASPSP for the PSU to authorise. The ASPSP creates the domestic payment consent resource and responds with a unique ConsentId to refer to the resource.'\n operationId: CreateDomesticPaymentConsent\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticConsent4'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticConsent4'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201DomesticPaymentConsentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-payment-consents\/{consent_id}':\n get:\n tags:\n - Domestic Payments\n summary: 'Retrieve a payment consent resource to check the status'\n description: 'Returns the detail of a previously submitted and accepted consent resource, reflecting its latest status. Once the PSU authorises the payment consent resource, the status of the payment consent resource will be Authorised. If the consent was rejected or failed later validations, the status will be Rejected. Once a payment has been successfully created using the consent, the status will be Consumed.'\n operationId: GetDomesticPaymentConsents\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200DomesticPaymentConsentsConsentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-payment-consents\/{consent_id}\/funds-confirmation':\n get:\n tags:\n - Domestic Payments\n summary: 'Confirm funds on a domestic payment consent resource'\n description: 'An ASPSP can only respond to a funds confirmation request if the domestic payment consent resource has an Authorised status. If the status is not Authorised, an ASPSP must respond with a 400 (Bad Request) and a UK.OBIE.Resource.InvalidConsentStatus error code. Confirmation of funds requests do not affect the status of the domestic payment consent resource'\n operationId: GetDomesticPaymentConsentsFundsConfirmation\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200DomesticPaymentConsentsConsentIdFundsConfirmationRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/domestic-payments:\n post:\n tags:\n - Domestic Payments\n summary: 'Submit a domestic payment for processing'\n description: 'Once the domestic payment consent has been authorised by the PSU, the PISP can proceed to submitting the domestic payment for processing. This request is an instruction to the ASPSP to begin the domestic single immediate payment journey. The domestic payment must be submitted immediately where possible. The PISP must ensure that the Initiation and Risk sections of the domestic payment match that of the corresponding consent resource. If the two do not match, the ASPSP must not process the request and must respond with a 400 (Bad Request). Any operations on the domestic payment resource will not result in a status change for the domestic payment resource.'\n operationId: CreateDomesticPayment\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomestic2'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomestic2'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201DomesticPaymentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-payments\/{payment_id}':\n get:\n tags:\n - Domestic Payments\n summary: 'Retrieval of a domestic payment to check its status'\n description: 'Retrieves the latest execution status of a previously, successfully submitted domestic payment. Status could be Pending, Rejected, AcceptedSettlementInProcess, AcceptedSettlementCompleted, AcceptedWithoutPosting or AcceptedCreditSettlementCompleted.'\n operationId: GetDomesticPayments\n parameters:\n - $ref: '#\/components\/parameters\/payment_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200DomesticPaymentsDomesticPaymentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/domestic-scheduled-payment-consents:\n post:\n tags:\n - Domestic Scheduled Payments\n summary: 'Create a new domestic scheduled payment consent resource'\n description: 'The POST action indicates to the ASPSP that a domestic payment consent has been staged. At this point, the PSU may not have been identified by the ASPSP, and the request payload may not contain any information of the account that should be debited. The endpoint allows the PISP to send a copy of the consent (between PSU and PISP) to the ASPSP for the PSU to authorise. The ASPSP creates the domestic scheduled payment consent resource and responds with a unique ConsentId to refer to the resource.'\n operationId: CreateDomesticScheduledPaymentConsents\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledConsent4'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledConsent4'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201DomesticScheduledPaymentConsentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-scheduled-payment-consents\/{consent_id}':\n get:\n tags:\n - Domestic Scheduled Payments\n summary: 'Retrieve a scheduled payment consent resource to check its status'\n description: 'Returns the detail of a previously submitted and accepted consent resource, reflecting its latest status. Once the PSU authorises the payment consent resource, the status of the payment consent resource will be Authorised. If the consent was rejected or failed later validations, the status will be Rejected. Once a scheduled payment has been successfully created using the consent, the status will be Consumed.'\n operationId: GetDomesticScheduledPaymentsConsents\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200DomesticScheduledPaymentConsentsConsentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/domestic-scheduled-payments:\n post:\n tags:\n - Domestic Scheduled Payments\n summary: 'Submit a domestic scheduled payment for processing'\n description: 'This request is an instruction to the ASPSP to begin the domestic scheduled payment journey. The PISP must submit the domestic scheduled payment immediately where possible. The PISP must ensure that the Initiation and Risk sections of the domestic scheduled payment match that of the corresponding consent resource. If the two do not match, the ASPSP must not process the request and must respond with a 400 (Bad Request). Any operations on the domestic scheduled payment resource will not result in a Status change for the domestic scheduled payment resource.'\n operationId: CreateDomesticScheduledPayments\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduled2'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduled2'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201DomesticScheduledPaymentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-scheduled-payments\/{payment_id}':\n get:\n tags:\n - Domestic Scheduled Payments\n summary: 'Retrieval of a domestic scheduled payment to check its status'\n description: 'Retrieves the latest status of a previously, successfully submitted domestic scheduled payment. Status could be InitiationPending, InitiationFailed, InitiationCompleted or Cancelled.'\n operationId: GetDomesticScheduledPayments\n parameters:\n - $ref: '#\/components\/parameters\/payment_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200DomesticScheduledPaymentsDomesticScheduledPaymentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/domestic-standing-order-consents:\n post:\n tags:\n - Domestic Standing Orders\n summary: 'Create a new domestic standing order payment consent resource.'\n description: 'The POST action indicates to the ASPSP that a domestic payment consent has been staged. At this point, the PSU may not have been identified by the ASPSP, and the request payload may not contain any information of the account that should be debited. The endpoint allows the PISP to send a copy of the consent (between PSU and PISP) to the ASPSP for the PSU to authorise. The ASPSP creates the domestic standing order payment consent resource and responds with a unique ConsentId to refer to the resource.'\n operationId: CreateDomesticStandingOrderConsents\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderConsent5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderConsent5'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201DomesticStandingOrderConsentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-standing-order-consents\/{consent_id}':\n get:\n tags:\n - Domestic Standing Orders\n summary: 'Retrieve a standing order payment consent resource to check its status'\n description: 'Returns the detail of a previously submitted and accepted consent resource, reflecting its latest status. Once the PSU authorises the payment consent resource, the status of the payment consent resource will be Authorised. If the consent was rejected or failed later validations, the status will be Rejected. Once a standing order payment has been successfully created using the consent, the status will be Consumed.'\n operationId: GetDomesticStandingOrderConsents\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200DomesticStandingOrderConsentsConsentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/domestic-standing-orders:\n post:\n tags:\n - Domestic Standing Orders\n summary: 'Submit a domestic standing order payment for processing'\n description: 'This request is an instruction to the ASPSP to begin the domestic standing order journey. The PISP must submit the domestic standing order immediately where possible. The PISP must ensure that the Initiation and Risk sections of the domestic standing order match that of the corresponding consent resource. If the two do not match, the ASPSP must not process the request and must respond with a 400 (Bad Request). Any operations on the domestic standing order resource will not result in a Status change for the domestic standing order resource.'\n operationId: CreateDomesticStandingOrders\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrder3'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrder3'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201DomesticStandingOrdersCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-standing-orders\/{payment_id}':\n get:\n tags:\n - Domestic Standing Orders\n summary: 'Retrieval of a domestic standing order payment to check its status'\n description: 'Retrieves the latest status of a previously, successfully submitted domestic sranding order payment. Status could be InitiationPending, InitiationFailed, InitiationCompleted or Cancelled.'\n operationId: GetDomesticStandingOrders\n parameters:\n - $ref: '#\/components\/parameters\/payment_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200DomesticStandingOrdersDomesticStandingOrderIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/file-payment-consents:\n post:\n tags:\n - File Payments\n summary: 'Create a new file payment consent resource'\n description: 'The POST action indicates to the ASPSP that a file payment consent has been staged. At this point, the PSU may not have been identified by the ASPSP and the request payload may not contain any information of the account(s) that should be debited. The endpoint allows the PISP to send metadata of the consent (between PSU and PISP) to the ASPSP. The metadata of the consent must include the FileType of the request. The metadata of the consent must include the FileHash, which is a base64 encoding of a SHA256 hash of the file to be uploaded. The ASPSP creates the file payment consent resource and responds with a unique ConsentId to refer to the resource.'\n operationId: CreateFilePaymentConsents\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileConsent3'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileConsent3'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201FilePaymentConsentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/file-payment-consents\/{consent_id}':\n get:\n tags:\n - File Payments\n summary: 'Retrieve a file payment consent resource to check its status'\n description: 'Once the PSU authorises the file payment consent resource, the Status of the file payment consent resource will be updated with Authorised. If the PSU rejects the consent or the file payment consent has failed some other ASPSP validation, the Status will be set to Rejected. Once a file payment has been successfully created using the file payment consent, the Status of the file payment consent will be set to Consumed.'\n operationId: GetFilePaymentConsents\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200FilePaymentConsentsConsentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/file-payment-consents\/{consent_id}\/file':\n post:\n tags:\n - File Payments\n summary: 'Upload a file to an ASPSP, against a file payment consent resource'\n description: 'This endpoint allows the PISP to upload a file to an ASPSP, against a\n\n file payment consent resource. The file structure must match the FileType in the file payment consent request. An ASPSP must confirm the hash of the file matches with the FileHash provided in the file payment consent Metadata. The metadata for the file-payment-consent must match the contents of the uploaded file. If the content of the metadata does not match the content of the file, the ASPSP must reject the file payment consent. The file is sent in the HTTP request body. HTTP headers (e.g. Content-Type) are used to describe the file.'\n operationId: PostFilePaymentConsentsFile\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/File'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/File'\n required: true\n #consumes:\n # - '*\/*'\n responses:\n '200':\n $ref: '#\/components\/responses\/200FilePaymentConsentsConsentIdFileCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n get:\n tags:\n - File Payments\n summary: 'Retrieve a file payment consent resource to check its status'\n description: 'This endpoint allows a PISP to retrieve a file payment consent resource\n\n that they have created to check its status. Once the PSU authorises the file payment consent resource, the Status of the file payment consent resource will be updated with Authorised. If the PSU rejects the consent or the file payment consent has failed some other ASPSP validation, the Status will be set to Rejected. Once a file payment has been successfully created using the file payment consent, the Status of the file payment consent will be set to Consumed.'\n operationId: GetFilePaymentConsentsFile\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200FilePaymentConsentsConsentIdFileRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/file-payments:\n post:\n tags:\n - File Payments\n summary: 'Submit a payment file for processing'\n description: 'Allows a file to be submitted for execution, once the file has been\n\n uploaded, accepted as valid and the associated file payment consent has been authorised.'\n operationId: CreateFilePayments\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFile2'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFile2'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201FilePaymentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/file-payments\/{file_payment_id}':\n get:\n tags:\n - File Payments\n summary: 'Retrieval of execution status for a submitted payment file'\n description: 'Retrieves the latest, overall status of a previously, successfully submitted payment file. Status could be InitiationPending, InitiationFailed or InitiationComplete.'\n operationId: GetFilePayments\n parameters:\n - $ref: '#\/components\/parameters\/file_payment_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200FilePaymentsFilePaymentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/file-payments\/{file_payment_id}\/report-file':\n get:\n tags:\n - File Payments\n summary: 'Download a payment report for a previously submitted payment file'\n description: 'This endpoint allows the PISP to download a payment report for a previously submitted payment file. This provides more detailed status information than the get status consent endpoint and returns a report on the processing results of Payments within the file. The report is returned in the HTTP response body.'\n operationId: GetFilePaymentsReport\n parameters:\n - $ref: '#\/components\/parameters\/file_payment_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200FilePaymentsFilePaymentIdReportFileRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/international-payment-consents:\n post:\n tags:\n - International Payments\n summary: 'Create a new international payment consent resource'\n description: 'The POST action indicates to the ASPSP that a domestic payment consent has been staged. At this point, the PSU may not have been identified by the ASPSP, and the request payload may not contain any information of the account that should be debited. The endpoint allows the PISP to send a copy of the consent (between PSU and PISP) to the ASPSP for the PSU to authorise. The ASPSP creates the international payment consent resource and responds with a unique ConsentId to refer to the resource.'\n operationId: CreateInternationalPaymentConsents\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalConsent5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalConsent5'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201InternationalPaymentConsentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/international-payment-consents\/{consent_id}':\n get:\n tags:\n - International Payments\n summary: 'Retrieve an international payment consent resource to check its status'\n description: 'Returns the detail of a previously submitted and accepted consent resource, reflecting its latest status. Once the PSU authorises the payment consent resource, the status of the payment consent resource will be Authorised. If the consent was rejected or failed later validations, the status will be Rejected. Once an international payment has been successfully created using the consent, the status will be Consumed.'\n operationId: GetInternationalPaymentConsents\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200InternationalPaymentConsentsConsentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/international-payment-consents\/{consent_id}\/funds-confirmation':\n get:\n tags:\n - International Payments\n summary: 'Confirm funds on an international payment consent resource'\n description: 'An ASPSP can only respond to a funds confirmation request if the international-payment-consent resource has an Authorised status. If the status is not Authorised, an ASPSP must respond with a 400 (Bad Request) and a UK.OBIE.Resource.InvalidConsentStatus error code. Confirmation of funds requests do not affect the status of the international payment consent resource.'\n operationId: GetInternationalPaymentConsentsFundsConfirmation\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200InternationalPaymentConsentsConsentIdFundsConfirmationRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/international-payments:\n post:\n tags:\n - International Payments\n summary: 'Submit an international payment for processing'\n description: 'Once the international payment consent has been authorised by the PSU, the PISP can proceed to submitting the international payment for processing. This request is an instruction to the ASPSP to begin the international single immediate payment journey. The international payment must be submitted immediately where possible. The PISP must ensure that the Initiation and Risk sections of the international payment match that of the corresponding consent resource. If the two do not match, the ASPSP must not process the request and must respond with a 400 (Bad Request). Any operations on the international payment resource will not result in a status change for the international payment resource.'\n operationId: CreateInternationalPayments\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternational3'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternational3'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201InternationalPaymentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/international-payments\/{payment_id}':\n get:\n tags:\n - International Payments\n summary: 'Retrieval of an international payment to check its status'\n description: 'Retrieves the latest status of a previously, successfully submitted international payment. Status could be Pending, Rejected, AcceptedSettlementInProcess, AcceptedSettlementCompleted, AcceptedWithoutPosting or AcceptedCreditSettlementCompleted.'\n operationId: GetInternationalPayments\n parameters:\n - $ref: '#\/components\/parameters\/payment_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200InternationalPaymentsInternationalPaymentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/international-scheduled-payment-consents:\n post:\n tags:\n - International Scheduled Payments\n summary: 'This endpoint allows the PISP to ask an ASPSP to create a new international scheduled payment consent resource.'\n description: 'The POST action indicates to the ASPSP that a domestic payment consent has been staged. At this point, the PSU may not have been identified by the ASPSP, and the request payload may not contain any information of the account that should be debited. The endpoint allows the PISP to send a copy of the consent (between PSU and PISP) to the ASPSP for the PSU to authorise. The ASPSP creates the international scheduled payment consent resource and responds with a unique ConsentId to refer to the resource.'\n operationId: CreateInternationalScheduledPaymentConsents\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledConsent5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledConsent5'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201InternationalScheduledPaymentConsentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/international-scheduled-payment-consents\/{consent_id}':\n get:\n tags:\n - International Scheduled Payments\n summary: 'This endpoint allows a PISP to retrieve a international scheduled payment consent resource that they have created to check its status.'\n description: 'Returns the detail of a previously submitted and accepted consent resource, reflecting its latest status. Once the PSU authorises the payment consent resource, the status of the payment consent resource will be Authorised. If the consent was rejected or failed later validations, the status will be Rejected. Once an international scheduled payment has been successfully created using the consent, the status will be Consumed.'\n operationId: GetInternationalScheduledPaymentConsents\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n responses:\n '200':\n $ref: '#\/components\/responses\/200InternationalScheduledPaymentConsentsConsentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/international-scheduled-payment-consents\/{consent_id}\/funds-confirmation':\n get:\n tags:\n - International Scheduled Payments\n summary: 'Confirm funds on an international scheduled payment consent resource where the payment is for immediate debit'\n description: 'An ASPSP can only respond to a funds confirmation request if the international scheduled payment consent resource has an Authorised status. If the status is not Authorised, an ASPSP must respond with a 400 (Bad Request) and a UK.OBIE.Resource.InvalidConsentStatus error code. Confirmation of funds requests do not affect the status of the international scheduled payment consent resource.'\n operationId: GetInternationalScheduledPaymentConsentsFundsConfirmation\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n responses:\n '200':\n $ref: '#\/components\/responses\/200InternationalScheduledPaymentConsentsConsentIdFundsConfirmationRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/international-scheduled-payments:\n post:\n tags:\n - International Scheduled Payments\n summary: 'Submit an international scheduled payment for processing'\n description: 'Once the international scheduled payment consent has been authorised by the PSU, the PISP can proceed to submitting the international scheduled payment for processing. This request is an instruction to the ASPSP to begin the international scheduled payment payment journey. The international scheduled payment must be submitted immediately where possible. The PISP must ensure that the Initiation and Risk sections of the international scheduled payment match that of the corresponding consent resource. If the two do not match, the ASPSP must not process the request and must respond with a 400 (Bad Request). Any operations on the international scheduled payment resource will not result in a status change for the international scheduled payment resource.'\n operationId: CreateInternationalScheduledPayments\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduled3'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduled3'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201InternationalScheduledPaymentsCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/international-scheduled-payments\/{payment_id}':\n get:\n tags:\n - International Scheduled Payments\n summary: 'Retrieval of an international scheduled payment to check its status'\n description: 'Retrieves the latest status of a previously, successfully submitted international scheduled payment. Status could be InitiationPending, InitiationFailed, InitiationCompleted or Cancelled.'\n operationId: GetInternationalScheduledPayments\n parameters:\n - $ref: '#\/components\/parameters\/payment_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n responses:\n '200':\n $ref: '#\/components\/responses\/200InternationalScheduledPaymentsInternationalScheduledPaymentIdRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/domestic-vrp-consents:\n post:\n tags:\n - Domestic VRP Consents\n summary: 'Create a new domestic variable recurring payment consent resource'\n description: 'The endpoint allows the TPP to send a copy of the consent (between PSU and TPP) to the ASPSP for the PSU to authorise. The ASPSP creates the resource and responds with a unique ConsentId to refer to the resource. The default\/initial Status of the resource is set to AwaitingAuthorisation. The request payload may contain Debtor Accounts, but the PSU may not have been identified by the ASPSP. If the parameters specified by the TPP in this resource are not valid, or fail any rules, the ASPSP must return a 400 Bad Request. In such a situation a resource is not created. The ASPSP must allow a PSU to have multiple VRP consents for a given account. This could include multiple consents with the same PISP. The ASPSP must reject a consent request that has Data.ControlParameters.SupplementaryData that it cannot process.'\n operationId: CreateDomesticVRPConsents\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPConsentRequest'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPConsentRequest'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201OBDomesticVRPConsentCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-vrp-consents\/{consent_id}':\n get:\n tags:\n - Domestic VRP Consents\n summary: 'Retrieve a variable recurring payment consent resource to check its status'\n description: 'Returns the detail of a previously submitted and accepted consent resource, reflecting its latest status. Once the PSU authorises the payment consent resource, the status of the payment consent resource will be Authorised. If the consent was rejected or failed later validations, the status will be Rejected. VRP consents are long lived and are never Consumed.'\n operationId: GetDomesticVRPConsents\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200OBDomesticVRPConsentRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n delete:\n tags:\n - Domestic VRP Consents\n summary: 'Delete a previously created VRP consent resource'\n description: 'This endpoint allows a TPP to request the deletion of a previously submitted and accepted variable recurring payment consent resource.'\n operationId: DeleteDomesticVRPConsents\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '204':\n description: Domestic Vrp Consent Delete Successful\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-vrp-consents\/{consent_id}\/funds-confirmation':\n post:\n tags:\n - Domestic VRP Consents\n summary: 'Confirm funds on the DebtorAccount associated with the domestic vrp consent'\n description: 'An ASPSP can only respond to a funds confirmation request if the resource has a Status of Authorised. If resource has any other Status, the ASPSP must respond with a 400 (Bad Request) and a UK.OBIE.Resource.InvalidConsentStatus error code.'\n operationId: PostDomesticVRPConsentsFundsConfirmation\n parameters:\n - $ref: '#\/components\/parameters\/consent_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBVRPFundsConfirmationRequest'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBVRPFundsConfirmationRequest'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201OBDomesticVRPFundsConfirmationRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n \/awspis\/open-banking\/v3.1\/pisp\/domestic-vrps:\n post:\n tags:\n - Domestic VRPs\n summary: 'Submit a domestic variable recurring payment for processing'\n description: 'This request is an instruction to the ASPSP to begin the domestic single immediate payment journey. The domestic payment must be executed immediately where possible. The TPP must ensure that the Initiation and Risk section matches the values specified in the consent. The ASPSP must ensure that the payment instruction adheres to the limitations set by the corresponding VRP consents ControlParameters. When a payment would breach a limitation set by one or more ControlParameters, the ASPSP must return an error details of the rule(s) that were breached.'\n operationId: CreateDomesticVRPPayments\n parameters:\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-jws-signature'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n - $ref: '#\/components\/parameters\/x-idempotency-key'\n requestBody:\n description: Default\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPRequest'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPRequest'\n required: true\n responses:\n '201':\n $ref: '#\/components\/responses\/201OBDomesticVRPCreated'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n '\/awspis\/open-banking\/v3.1\/pisp\/domestic-vrps\/{payment_id}':\n get:\n tags:\n - Domestic VRPs\n summary: 'Retrieval of an domestic variable recurring payment to check its status'\n description: 'Retrieves the latest status of a previously, successfully domestic variable recurring payment payment. Status could be Pending, Rejected, AcceptedSettlementInProcess, AcceptedSettlementCompleted, AcceptedWithoutPosting or AcceptedCreditSettlementCompleted.'\n operationId: GetDomesticVrps\n parameters:\n - $ref: '#\/components\/parameters\/payment_id'\n - $ref: '#\/components\/parameters\/x-fapi-auth-date'\n - $ref: '#\/components\/parameters\/x-fapi-customer-ip-address'\n - $ref: '#\/components\/parameters\/x-fapi-interaction-id'\n - $ref: '#\/components\/parameters\/Authorization'\n - $ref: '#\/components\/parameters\/x-customer-user-agent'\n responses:\n '200':\n $ref: '#\/components\/responses\/200OBDomesticVRPRead'\n '400':\n $ref: '#\/components\/responses\/400Error'\n '401':\n $ref: '#\/components\/responses\/401Error'\n '403':\n $ref: '#\/components\/responses\/403Error'\n '404':\n $ref: '#\/components\/responses\/404Error'\n '405':\n $ref: '#\/components\/responses\/405Error'\n '406':\n $ref: '#\/components\/responses\/406Error'\n '415':\n $ref: '#\/components\/responses\/415Error'\n '429':\n $ref: '#\/components\/responses\/429Error'\n '500':\n $ref: '#\/components\/responses\/500Error'\n '502':\n $ref: '#\/components\/responses\/502Error'\n '503':\n $ref: '#\/components\/responses\/503Error'\n '504':\n $ref: '#\/components\/responses\/504Error'\n #### END Open Banking endpoints ####\n#### END One Europe App endpoints ####\ncomponents:\n parameters:\n consent_id:\n name: consent_id\n in: path\n description: consent_id\n required: true\n schema:\n type: string\n payment_id:\n name: payment_id\n in: path\n description: payment_id\n required: true\n schema:\n type: string\n file_payment_id:\n name: file_payment_id\n in: path\n description: file_payment_id\n required: true\n schema:\n type: string\n Authorization:\n in: header\n name: Authorization\n required: true\n description: 'An Authorisation Token as per https:\/\/tools.ietf.org\/html\/rfc6750'\n schema:\n type: string\n x-customer-user-agent:\n in: header\n name: x-customer-user-agent\n description: Indicates the user-agent that the PSU is using.\n required: false\n schema:\n type: string\n x-fapi-customer-ip-address:\n in: header\n name: x-fapi-customer-ip-address\n required: false\n description: 'The PSU''s IP address if the PSU is currently logged in with the TPP.'\n schema:\n type: string\n x-fapi-auth-date:\n in: header\n name: x-fapi-auth-date\n required: false\n description: \"The time when the PSU last logged in with the TPP. \\nAll dates in the HTTP headers are represented as RFC 7231 Full Dates. \\nAn example is below: \\nSun, 10 Sep 2017 19:43:31 UTC\"\n schema:\n pattern: '^(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)$'\n type: string\n x-fapi-interaction-id:\n in: header\n name: x-fapi-interaction-id\n required: false\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-idempotency-key:\n name: x-idempotency-key\n in: header\n description: |-\n Every request will be processed only once per x-idempotency-key. The\n Idempotency Key will be valid for 24 hours.\n required: true\n schema:\n type: string\n pattern: ^(?!\\s)(.*)(\\S)$\n maxLength: 40\n x-jws-signature:\n in: header\n name: x-jws-signature\n schema:\n type: string\n required: true\n description: A detached JWS signature of the body of the payload.\n responses:\n 201DomesticPaymentConsentsCreated:\n description: Domestic Payment Consents Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticConsentResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticConsentResponse5'\n 200DomesticPaymentConsentsConsentIdRead:\n description: Domestic Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticConsentResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticConsentResponse5'\n 200DomesticPaymentConsentsConsentIdFundsConfirmationRead:\n description: Domestic Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFundsConfirmationResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFundsConfirmationResponse1'\n 201DomesticPaymentsCreated:\n description: Domestic Payments Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticResponse5'\n 200DomesticPaymentsDomesticPaymentIdRead:\n description: Domestic Payments Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticResponse5'\n 200DomesticPaymentsDomesticPaymentIdPaymentDetailsRead:\n description: Payment Details Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n 201DomesticScheduledPaymentConsentsCreated:\n description: Domestic Scheduled Payment Consents Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledConsentResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledConsentResponse5'\n 200DomesticScheduledPaymentConsentsConsentIdRead:\n description: Domestic Scheduled Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledConsentResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledConsentResponse5'\n 201DomesticScheduledPaymentsCreated:\n description: Domestic Scheduled Payments Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledResponse5'\n 200DomesticScheduledPaymentsDomesticScheduledPaymentIdRead:\n description: Domestic Scheduled Payments Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticScheduledResponse5'\n 200DomesticScheduledPaymentsDomesticScheduledPaymentIdPaymentDetailsRead:\n description: Payment Details Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n 201DomesticStandingOrderConsentsCreated:\n description: Domestic Standing Order Consents Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderConsentResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderConsentResponse6'\n 200DomesticStandingOrderConsentsConsentIdRead:\n description: Domestic Standing Order Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderConsentResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderConsentResponse6'\n 201DomesticStandingOrdersCreated:\n description: Domestic Standing Orders Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderResponse6'\n 200DomesticStandingOrdersDomesticStandingOrderIdRead:\n description: Domestic Standing Orders Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteDomesticStandingOrderResponse6'\n 200DomesticStandingOrdersDomesticStandingOrderIdPaymentDetailsRead:\n description: Payment Details Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n 201FilePaymentConsentsCreated:\n description: File Payment Consents Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileConsentResponse4'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileConsentResponse4'\n 200FilePaymentConsentsConsentIdFileCreated:\n description: File Payment Consents Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n 200FilePaymentConsentsConsentIdRead:\n description: File Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileConsentResponse4'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileConsentResponse4'\n 200FilePaymentConsentsConsentIdFileRead:\n description: File Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/File'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/File'\n 201FilePaymentsCreated:\n description: File Payments Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileResponse3'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileResponse3'\n 200FilePaymentsFilePaymentIdRead:\n description: File Payments Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileResponse3'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFileResponse3'\n 200FilePaymentsFilePaymentIdReportFileRead:\n description: File Payments Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/File'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/File'\n 200FilePaymentsFilePaymentIdPaymentDetailsRead:\n description: Payment Details Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n 201InternationalPaymentConsentsCreated:\n description: International Payment Consents Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalConsentResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalConsentResponse6'\n 200InternationalPaymentConsentsConsentIdRead:\n description: International Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalConsentResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalConsentResponse6'\n 200InternationalPaymentConsentsConsentIdFundsConfirmationRead:\n description: International Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFundsConfirmationResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFundsConfirmationResponse1'\n 201InternationalPaymentsCreated:\n description: International Payments Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalResponse5'\n 200InternationalPaymentsInternationalPaymentIdRead:\n description: International Payments Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalResponse5'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalResponse5'\n 200InternationalPaymentsInternationalPaymentIdPaymentDetailsRead:\n description: Payment Details Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n 201InternationalScheduledPaymentConsentsCreated:\n description: International Scheduled Payment Consents Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledConsentResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledConsentResponse6'\n 200InternationalScheduledPaymentConsentsConsentIdRead:\n description: International Scheduled Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledConsentResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledConsentResponse6'\n 200InternationalScheduledPaymentConsentsConsentIdFundsConfirmationRead:\n description: International Scheduled Payment Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFundsConfirmationResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteFundsConfirmationResponse1'\n 201InternationalScheduledPaymentsCreated:\n description: International Scheduled Payments Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledResponse6'\n 200InternationalScheduledPaymentsInternationalScheduledPaymentIdRead:\n description: International Scheduled Payments Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledResponse6'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalScheduledResponse6'\n 200InternationalScheduledPaymentsInternationalScheduledPaymentIdPaymentDetailsRead:\n description: Payment Details Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n 201InternationalStandingOrderConsentsCreated:\n description: International Standing Order Consents Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalStandingOrderConsentResponse7'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalStandingOrderConsentResponse7'\n 200InternationalStandingOrderConsentsConsentIdRead:\n description: International Standing Order Consents Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalStandingOrderConsentResponse7'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalStandingOrderConsentResponse7'\n 201InternationalStandingOrdersCreated:\n description: International Standing Orders Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalStandingOrderResponse7'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalStandingOrderResponse7'\n 200InternationalStandingOrdersInternationalStandingOrderPaymentIdRead:\n description: International Standing Orders Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalStandingOrderResponse7'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWriteInternationalStandingOrderResponse7'\n 200InternationalStandingOrdersInternationalStandingOrderPaymentIdPaymentDetailsRead:\n description: Payment Details Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBWritePaymentDetailsResponse1'\n 201OBDomesticVRPConsentCreated:\n description: Domestic Vrp Consent Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPConsentResponse'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPConsentResponse'\n 200OBDomesticVRPConsentRead:\n description: Domestic Vrp Consent Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPConsentResponse'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPConsentResponse'\n 201OBDomesticVRPFundsConfirmationRead:\n description: Domestic Vrp Funds Confirmation Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBVRPFundsConfirmationResponse'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBVRPFundsConfirmationResponse'\n 201OBDomesticVRPCreated:\n description: Domestic Vrp Created\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPResponse'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPResponse'\n 200OBDomesticVRPRead:\n description: Domestic Vrp Read\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPResponse'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBDomesticVRPResponse'\n 400Error:\n description: Bad request\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 401Error:\n description: Unauthorized\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 403Error:\n description: Forbidden\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 404Error:\n description: Not found\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 405Error:\n description: Method Not Allowed\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 406Error:\n description: Not Acceptable\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 409Error:\n description: Conflict\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 415Error:\n description: Unsupported Media Type\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 429Error:\n description: Too Many Requests\n headers:\n Retry-After:\n description: Number in seconds to wait\n schema:\n type: integer\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 500Error:\n description: Internal Server Error\n headers:\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n schema:\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n schema:\n type: string\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 501Error:\n description: Not Implemented\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 502Error:\n description: Bad gateway\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 503Error:\n description: The service is temporarily unavailable\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n 504Error:\n description: Gateway Timeout\n content:\n application\/json; charset=utf-8:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n application\/jose+jwe:\n schema:\n $ref: '#\/components\/schemas\/OBErrorResponse1'\n schemas:\n Error:\n description: An error\n properties:\n code:\n type: string\n example: '1400'\n path:\n type: string\n example: body.id\n message:\n type: string\n example: Input Validation Error\n description:\n type: string\n example: Invalid body parameter id\n Errors:\n description: An error\n type: array\n items:\n $ref: '#\/components\/schemas\/Error'\n x-fapi-interaction-id:\n description: An RFC4122 UID used as a correlation id.\n type: string\n x-jws-signature:\n description: Header containing a detached JWS signature of the body of the payload.\n type: string\n Retry-After:\n description: Number in seconds to wait\n type: integer\n ActiveOrHistoricCurrencyCode:\n description: 'A code allocated to a currency by a Maintenance Agency under an international identification scheme, as described in the latest edition of the international standard ISO 4217 \"Codes for the representation of currencies and funds\".'\n type: string\n pattern: '^[A-Z]{3,3}$'\n BuildingNumber:\n description: Number that identifies the position of a building on a street.\n type: string\n minLength: 1\n maxLength: 16\n CountryCode:\n description: Nation with its own government.\n type: string\n pattern: '^[A-Z]{2,2}$'\n CountrySubDivision:\n description: 'Identifies a subdivision of a country such as state, region, county.'\n type: string\n minLength: 1\n maxLength: 35\n Department:\n description: Identification of a division of a large organisation or building.\n type: string\n minLength: 1\n maxLength: 70\n File:\n type: object\n additionalProperties: false\n properties: {}\n ISODateTime:\n description: \"All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Identification_0:\n description: Identification assigned by an institution to identify an account. This identification is known by the account owner.\n type: string\n minLength: 1\n maxLength: 256\n Identification_1:\n description: Unique and unambiguous identification of a financial institution or a branch of a financial institution.\n type: string\n minLength: 1\n maxLength: 35\n Links:\n type: object\n additionalProperties: false\n description: Links relevant to the payload\n properties:\n Self:\n type: string\n format: uri\n First:\n type: string\n format: uri\n Prev:\n type: string\n format: uri\n Next:\n type: string\n format: uri\n Last:\n type: string\n format: uri\n required:\n - Self\n Meta:\n title: MetaData\n type: object\n additionalProperties: false\n description: Meta Data relevant to the payload\n properties:\n TotalPages:\n type: integer\n format: int32\n FirstAvailableDateTime:\n $ref: '#\/components\/schemas\/ISODateTime'\n LastAvailableDateTime:\n $ref: '#\/components\/schemas\/ISODateTime'\n VrpMeta:\n title: MetaData\n type: object\n description: Meta Data relevant to the payload. At present no fields are used for VRP.\n Name:\n description: Name by which an agent is known and which is usually used to identify that agent.\n type: string\n minLength: 1\n maxLength: 140\n OBActiveCurrencyAndAmount_SimpleType:\n description: A number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217.\n type: string\n pattern: '^\\d{1,13}$|^\\d{1,13}\\.\\d{1,5}$'\n OBActiveOrHistoricCurrencyAndAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: Amount of money associated with the charge type.\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n OBAddressTypeCode:\n description: Identifies the nature of the postal address.\n type: string\n enum:\n - Business\n - Correspondence\n - DeliveryTo\n - MailTo\n - POBox\n - Postal\n - Residential\n - Statement\n OBChargeBearerType1Code:\n description: Specifies which party\/parties will bear the charges associated with the processing of the payment transaction.\n type: string\n enum:\n - BorneByCreditor\n - BorneByDebtor\n - FollowingServiceLevel\n - Shared\n OBError1:\n type: object\n additionalProperties: false\n properties:\n ErrorCode:\n description: 'Low level textual error code, e.g., UK.OBIE.Field.Missing'\n type: string\n x-namespaced-enum:\n - UK.OBIE.Field.Expected\n - UK.OBIE.Field.Invalid\n - UK.OBIE.Field.InvalidDate\n - UK.OBIE.Field.Missing\n - UK.OBIE.Field.Unexpected\n - UK.OBIE.Header.Invalid\n - UK.OBIE.Header.Missing\n - UK.OBIE.Reauthenticate\n - UK.OBIE.Resource.ConsentMismatch\n - UK.OBIE.Resource.InvalidConsentStatus\n - UK.OBIE.Resource.InvalidFormat\n - UK.OBIE.Resource.NotFound\n - UK.OBIE.Rules.AfterCutOffDateTime\n - UK.OBIE.Rules.DuplicateReference\n - UK.OBIE.Rules.FailsControlParameters\n - UK.OBIE.Signature.Invalid\n - UK.OBIE.Signature.InvalidClaim\n - UK.OBIE.Signature.Malformed\n - UK.OBIE.Signature.Missing\n - UK.OBIE.Signature.MissingClaim\n - UK.OBIE.Signature.Unexpected\n - UK.OBIE.UnexpectedError\n - UK.OBIE.Unsupported.AccountIdentifier\n - UK.OBIE.Unsupported.AccountSecondaryIdentifier\n - UK.OBIE.Unsupported.Currency\n - UK.OBIE.Unsupported.Frequency\n - UK.OBIE.Unsupported.LocalInstrument\n - UK.OBIE.Unsupported.Scheme\n Message:\n description: |-\n A description of the error that occurred. e.g., 'A mandatory field isn't supplied' or 'RequestedExecutionDateTime must be in future'\n OBIE doesn't standardise this field\n type: string\n minLength: 1\n maxLength: 500\n Path:\n description: 'Recommended but optional reference to the JSON Path of the field with error, e.g., Data.Initiation.InstructedAmount.Currency'\n type: string\n minLength: 1\n maxLength: 500\n Url:\n description: 'URL to help remediate the problem, or provide more information, or to API Reference, or help etc'\n type: string\n required:\n - ErrorCode\n - Message\n minProperties: 1\n OBErrorResponse1:\n description: 'An array of detail error codes, and messages, and URLs to documentation to help remediation.'\n type: object\n additionalProperties: false\n properties:\n Code:\n description: 'High level textual error code, to help categorize the errors.'\n type: string\n minLength: 1\n maxLength: 40\n Id:\n description: 'A unique reference for the error instance, for audit purposes, in case of unknown\/unclassified errors.'\n type: string\n minLength: 1\n maxLength: 40\n Message:\n description: 'Brief Error message, e.g., ''There is something wrong with the request parameters provided'''\n type: string\n minLength: 1\n maxLength: 500\n Errors:\n items:\n $ref: '#\/components\/schemas\/OBError1'\n type: array\n minItems: 1\n required:\n - Code\n - Message\n - Errors\n OBExternalAccountIdentification4Code:\n description: 'Name of the identification scheme, in a coded form as published in an external list.'\n type: string\n x-namespaced-enum:\n - UK.OBIE.BBAN\n - UK.OBIE.IBAN\n - UK.OBIE.PAN\n - UK.OBIE.Paym\n - UK.OBIE.SortCodeAccountNumber\n OBExternalFinancialInstitutionIdentification4Code:\n description: 'Name of the identification scheme, in a coded form as published in an external list.'\n type: string\n x-namespaced-enum:\n - UK.OBIE.BICFI\n OBExternalLocalInstrument1Code:\n description: |-\n User community specific instrument.\n Usage: This element is used to specify a local instrument, local clearing option and\/or further qualify the service or service level.\n type: string\n x-namespaced-enum:\n - UK.OBIE.BACS\n - UK.OBIE.BalanceTransfer\n - UK.OBIE.CHAPS\n - UK.OBIE.Euro1\n - UK.OBIE.FPS\n - UK.OBIE.Link\n - UK.OBIE.MoneyTransfer\n - UK.OBIE.Paym\n - UK.OBIE.SEPACreditTransfer\n - UK.OBIE.SEPAInstantCreditTransfer\n - UK.OBIE.SWIFT\n - UK.OBIE.Target2\n OBExternalPaymentChargeType1Code:\n description: 'Charge type, in a coded form.'\n type: string\n x-namespaced-enum:\n - UK.OBIE.CHAPSOut\n - UK.OBIE.BalanceTransferOut\n - UK.OBIE.MoneyTransferOut\n OBPostalAddress6:\n type: object\n additionalProperties: false\n description: Information that locates and identifies a specific address, as defined by postal services.\n properties:\n AddressType:\n $ref: '#\/components\/schemas\/OBAddressTypeCode'\n Department:\n $ref: '#\/components\/schemas\/Department'\n SubDepartment:\n $ref: '#\/components\/schemas\/SubDepartment'\n StreetName:\n $ref: '#\/components\/schemas\/StreetName'\n BuildingNumber:\n $ref: '#\/components\/schemas\/BuildingNumber'\n PostCode:\n $ref: '#\/components\/schemas\/PostCode'\n TownName:\n $ref: '#\/components\/schemas\/TownName'\n CountrySubDivision:\n $ref: '#\/components\/schemas\/CountrySubDivision'\n Country:\n $ref: '#\/components\/schemas\/CountryCode'\n AddressLine:\n type: array\n items:\n description: 'Information that locates and identifies a specific address, as defined by postal services, presented in free format text.'\n type: string\n minLength: 1\n maxLength: 70\n minItems: 0\n maxItems: 7\n OBDebtorIdentification1:\n type: object\n additionalProperties: false\n description: Set of elements used to identify a person or an organisation.\n properties:\n Name:\n type: string\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n minLength: 0\n maxLength: 350\n OBRisk1:\n type: object\n additionalProperties: false\n description: The Risk section is sent by the initiating party to the ASPSP. It is used to specify additional details for risk scoring for Payments.\n properties:\n PaymentContextCode:\n description: Specifies the payment context\n type: string\n enum:\n - BillingGoodsAndServicesInAdvance\n - BillingGoodsAndServicesInArrears\n - PispPayee\n - EcommerceMerchantInitiatedPayment\n - FaceToFacePointOfSale\n - TransferToSelf\n - TransferToThirdParty\n - BillPayment\n - EcommerceGoods\n - EcommerceServices\n - Other\n - PartyToParty\n MerchantCategoryCode:\n description: 'Category code conform to ISO 18245, related to the type of services or goods the merchant provides for the transaction.'\n type: string\n minLength: 3\n maxLength: 4\n MerchantCustomerIdentification:\n description: The unique customer identifier of the PSU with the merchant.\n type: string\n minLength: 1\n maxLength: 70\n ContractPresentIndicator:\n description: Indicates if Payee has a contractual relationship with the PISP\n type: boolean\n BeneficiaryPrepopulatedIndicator:\n description: Indicates if PISP has immutably prepopulated payment details in for the PSU\n type: boolean\n PaymentPurposeCode:\n description: 'Category code, related to the type of services or goods that corresponds to the underlying purpose of the payment that conforms to Recommended UK Purpose Code in ISO 20022 Payment Messaging List'\n type: string\n minLength: 3\n maxLength: 4\n BeneficiaryAccountType:\n $ref: '#\/components\/schemas\/OBExternalExtendedAccountType1Code'\n DeliveryAddress:\n type: object\n additionalProperties: false\n required:\n - TownName\n - Country\n description: 'Information that locates and identifies a specific address, as defined by postal services or in free format text.'\n properties:\n AddressLine:\n type: array\n items:\n description: 'Information that locates and identifies a specific address, as defined by postal services, that is presented in free format text.'\n type: string\n minLength: 1\n maxLength: 70\n minItems: 0\n maxItems: 2\n StreetName:\n $ref: '#\/components\/schemas\/StreetName'\n BuildingNumber:\n $ref: '#\/components\/schemas\/BuildingNumber'\n PostCode:\n $ref: '#\/components\/schemas\/PostCode'\n TownName:\n $ref: '#\/components\/schemas\/TownName'\n CountrySubDivision:\n $ref: '#\/components\/schemas\/CountrySubDivision'\n Country:\n description: 'Nation with its own government, occupying a particular territory.'\n type: string\n pattern: '^[A-Z]{2,2}$'\n OBSupplementaryData1:\n type: object\n properties: {}\n additionalProperties: true\n description: Additional information that can not be captured in the structured fields and\/or any other specific block.\n OBExternalExtendedAccountType1Code:\n description: Specifies the extended type of account.\n type: string\n enum:\n - Business\n - BusinessSavingsAccount\n - Charity\n - Collection\n - Corporate\n - Ewallet\n - Government\n - Investment\n - ISA\n - JointPersonal\n - Pension\n - Personal\n - PersonalSavingsAccount\n - Premier\n - Wealth\n OBWriteDomestic2:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single domestic payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.\\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: |-\n Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.\n Usage: This amount has to be transported unchanged through the transaction chain.\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money.\\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteDomesticConsent4:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - Initiation\n properties:\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single domestic payment.\n properties:\n InstructionIdentification:\n description: |-\n Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.\n Usage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n 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.\n Note, the account name is not the product name or the nickname of the account.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n The account name is the name or names of the account owner(s) represented at an account level.\n Note, the account name is not the product name or the nickname of the account.\n OB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system.\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended tosettle, such as commercial invoices in an accounts''receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction.\\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money.\\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: |-\n Specifies a character string with a maximum length of 40 characters.\n Usage: This field indicates whether the PSU was subject to SCA performed by the TPP\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteDomesticConsentResponse5:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of consent resource in code form.\n type: string\n enum:\n - Authorised\n - AwaitingAuthorisation\n - Consumed\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n CutOffDateTime:\n description: \"Specified cut-off date and time for the payment consent. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedExecutionDateTime:\n description: \"Expected execution date and time for the payment resource. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedSettlementDateTime:\n description: \"Expected settlement date and time for the payment resource. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single domestic payment.\n properties:\n InstructionIdentification:\n description: |-\n Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.\n Usage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction.\\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n 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.\n Note, the account name is not the product name or the nickname of the account.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level.\\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: |-\n Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction.\n Usage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money.\n If the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification\n should be quoted in the end-to-end transaction identification.\n OB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: |-\n Specifies a character string with a maximum length of 40 characters.\n Usage: This field indicates whether the PSU was subject to SCA performed by the TPP\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: |-\n Specifies a character string with a maximum length of 140 characters.\n Usage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\n type: string\n minLength: 1\n maxLength: 128\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteDomesticResponse5:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - DomesticPaymentId\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n DomesticPaymentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the domestic payment resource.'\n type: string\n minLength: 1\n maxLength: 40\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the message was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of the payment information group.\n type: string\n enum:\n - AcceptedCreditSettlementCompleted\n - AcceptedSettlementCompleted\n - AcceptedSettlementInProcess\n - AcceptedWithoutPosting\n - Pending\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedExecutionDateTime:\n description: \"Expected execution date and time for the payment resource. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedSettlementDateTime:\n description: \"Expected settlement date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Refund:\n type: object\n additionalProperties: false\n required:\n - Account\n description: Unambiguous identification of the refund account to which a refund will be made as a result of the transaction.\n properties:\n Account:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify an account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n Name of the account, as assigned by the account servicing institution.\n Usage: The account name is the name or names of the account owner(s) represented at an account level. The account name is not the product name or the nickname of the account.\n OB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single domestic payment.\n properties:\n InstructionIdentification:\n description: |-\n Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.\n Usage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n 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.\n Note, the account name is not the product name or the nickname of the account.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry withthe items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should providethis reference in the structured remittance information,to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n MultiAuthorisation:\n type: object\n additionalProperties: false\n required:\n - Status\n description: The multiple authorisation flow response from the ASPSP.\n properties:\n Status:\n description: Specifies the status of the authorisation flow in code form.\n type: string\n enum:\n - Authorised\n - AwaitingFurtherAuthorisation\n - Rejected\n NumberRequired:\n description: Number of authorisations required for payment order (total required at the start of the multi authorisation journey).\n type: integer\n NumberReceived:\n description: Number of authorisations received.\n type: integer\n LastUpdateDateTime:\n description: \"Last date and time at the authorisation flow was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpirationDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteDomesticScheduled2:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - RequestedExecutionDateTime\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single scheduled domestic payment.\n properties:\n InstructionIdentification:\n description: |-\n Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction.\n Usage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.\\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: |-\n Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.\n Usage: This amount has to be transported unchanged through the transaction chain.\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n 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.\n Note, the account name is not the product name or the nickname of the account.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: |-\n Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level.\\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteDomesticScheduledConsent4:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - Permission\n - Initiation\n properties:\n Permission:\n description: Specifies the Open Banking service request types.\n type: string\n enum:\n - Create\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - RequestedExecutionDateTime\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single scheduled domestic payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.\\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: |-\n Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.\n Usage: This amount has to be transported unchanged through the transaction chain.\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money.\\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteDomesticScheduledConsentResponse5:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Permission\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of consent resource in code form.\n type: string\n enum:\n - Authorised\n - AwaitingAuthorisation\n - Consumed\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the consent resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Permission:\n description: Specifies the Open Banking service request types.\n type: string\n enum:\n - Create\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n CutOffDateTime:\n description: \"Specified cut-off date and time for the payment consent.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedExecutionDateTime:\n description: \"Expected execution date and time for the payment resource. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedSettlementDateTime:\n description: \"Expected settlement date and time for the payment resource. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - RequestedExecutionDateTime\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single scheduled domestic payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the accountowner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system.\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, tounambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteDomesticScheduledResponse5:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - DomesticScheduledPaymentId\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n DomesticScheduledPaymentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the domestic schedule payment resource.'\n type: string\n minLength: 1\n maxLength: 40\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the message was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of the payment order resource.\n type: string\n enum:\n - Cancelled\n - InitiationCompleted\n - InitiationFailed\n - InitiationPending\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedExecutionDateTime:\n description: \"Expected execution date and time for the payment resource. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedSettlementDateTime:\n description: \"Expected settlement date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Refund:\n type: object\n additionalProperties: false\n required:\n - Account\n description: |-\n Unambiguous identification of the refund account to which a refund will be made as a result of the transaction.\n properties:\n Account:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify an account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"Name of the account, as assigned by the account servicing institution. \\nUsage: The account name is the name or names of the account owner(s) represented at an account level. The account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - RequestedExecutionDateTime\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single scheduled domestic payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.\\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the paymen transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account.\\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transactionidentification.\\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n MultiAuthorisation:\n type: object\n additionalProperties: false\n required:\n - Status\n description: The multiple authorisation flow response from the ASPSP.\n properties:\n Status:\n description: Specifies the status of the authorisation flow in code form.\n type: string\n enum:\n - Authorised\n - AwaitingFurtherAuthorisation\n - Rejected\n NumberRequired:\n description: Number of authorisations required for payment order (total required at the start of the multi authorisation journey).\n type: integer\n NumberReceived:\n description: Number of authorisations received.\n type: integer\n LastUpdateDateTime:\n description: \"Last date and time at the authorisation flow was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpirationDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteDomesticStandingOrder3:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n Initiation:\n type: object\n additionalProperties: false\n required:\n - Frequency\n - FirstPaymentDateTime\n - FirstPaymentAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a domestic standing order.\n properties:\n Frequency:\n description: \"Individual Definitions:\\nEvryDay - Every day\\nEvryWorkgDay - Every working day\\nIntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07)\\nWkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07)\\nIntrvlMnthDay - An interval specified in months (between 01 to 06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31)\\nQtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). \\nENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. \\nSCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November.\\nRECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. \\nIndividual Patterns:\\nEvryDay (ScheduleCode)\\nEvryWorkgDay (ScheduleCode)\\nIntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek)\\nWkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth + DayInWeek)\\nIntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth)\\nQtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay\\nThe regular expression for this element combines five smaller versions for each permitted pattern. To aid legibility - the components are presented individually here:\\nEvryDay\\nEvryWorkgDay\\nIntrvlWkDay:0[1-9]:0[1-7]\\nWkInMnthDay:0[1-5]:0[1-7]\\nIntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01])\\nQtrDay:(ENGLISH|SCOTTISH|RECEIVED)\\nFull Regular Expression:\\n^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\"\n type: string\n pattern: |-\n ^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlDay:((0[2-9])|([1-2][0-9])|3[0-1]))$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\n Reference:\n description: |-\n Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction.\n Usage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money.\n If the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\n type: string\n minLength: 1\n maxLength: 35\n NumberOfPayments:\n description: Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.\n type: string\n minLength: 1\n maxLength: 35\n FirstPaymentDateTime:\n description: \"The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n RecurringPaymentDateTime:\n description: \"The date on which the first recurring payment for a Standing Order schedule will be made. \\nUsage: This must be populated only if the first recurring date is different to the first payment date.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FinalPaymentDateTime:\n description: \"The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FirstPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the first Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n RecurringPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the recurring Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n FinalPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the final Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Provides the details to identify the debtor account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Identification assigned by an institution to identify an account. This identification is known by the account owner.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteDomesticStandingOrderConsent5:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - Permission\n - Initiation\n properties:\n Permission:\n description: Specifies the Open Banking service request types.\n type: string\n enum:\n - Create\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - Frequency\n - FirstPaymentDateTime\n - FirstPaymentAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a domestic standing order.\n properties:\n Frequency:\n description: \"Individual Definitions: \\nEvryDay - Every day \\nEvryWorkgDay - Every working day \\nIntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07) \\nWkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07) \\nIntrvlMnthDay - An interval specified in months (between 01 to 06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31)\\nQtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). \\nENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. \\nSCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November. \\nRECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. \\nIndividual Patterns: \\nEvryDay (ScheduleCode) \\nEvryWorkgDay (ScheduleCode) \\nIntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek)\\nWkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth + DayInWeek) \\nIntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth) \\nQtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay \\nThe regular expression for this element combines five smaller versions for each permitted pattern. To aid legibility - the components are presented individually here:\\nEvryDay \\nEvryWorkgDay \\nIntrvlWkDay:0[1-9]:0[1-7] \\nWkInMnthDay:0[1-5]:0[1-7] \\nIntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]) \\nQtrDay:(ENGLISH|SCOTTISH|RECEIVED) \\nFull Regular Expression: \\n^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\"\n type: string\n pattern: |-\n ^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlDay:((0[2-9])|([1-2][0-9])|3[0-1]))$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\"\n type: string\n minLength: 1\n maxLength: 35\n NumberOfPayments:\n description: Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.\n type: string\n minLength: 1\n maxLength: 35\n FirstPaymentDateTime:\n description: \"The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n RecurringPaymentDateTime:\n description: \"The date on which the first recurring payment for a Standing Order schedule will be made. \\nUsage: This must be populated only if the first recurring date is different to the first payment date.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FinalPaymentDateTime:\n description: \"The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FirstPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the first Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n RecurringPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the recurring Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n FinalPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the final Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Provides the details to identify the debtor account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n 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.\n Note, the account name is not the product name or the nickname of the account.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Identification assigned by an institution to identify an account. This identification is known by the account owner.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: |-\n Specifies a character string with a maximum length of 40 characters.\n Usage: This field indicates whether the PSU was subject to SCA performed by the TPP\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteDomesticStandingOrderConsentResponse6:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Permission\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of consent resource in code form.\n type: string\n enum:\n - Authorised\n - AwaitingAuthorisation\n - Consumed\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Permission:\n description: Specifies the Open Banking service request types.\n type: string\n enum:\n - Create\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n CutOffDateTime:\n description: \"Specified cut-off date and time for the payment consent.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - Frequency\n - FirstPaymentDateTime\n - FirstPaymentAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a domestic standing order.\n properties:\n Frequency:\n description: \"Individual Definitions: \\nEvryDay - Every day \\nEvryWorkgDay - Every working day \\nIntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07) \\nWkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07) \\nIntrvlMnthDay - An interval specified in months (between 01 to06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31) \\nQtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). \\nENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. \\nSCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November. \\nRECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. \\nIndividual Patterns: \\nEvryDay (ScheduleCode) \\nEvryWorkgDay (ScheduleCode) \\nIntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek) \\nWkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth + DayInWeek) \\nIntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth) \\nQtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay \\nThe regular expression for this element combines five smaller versions for each permitted pattern. To aid legibility - the components are presented individually here: \\nEvryDay \\nEvryWorkgDay \\nIntrvlWkDay:0[1-9]:0[1-7] \\nWkInMnthDay:0[1-5]:0[1-7] \\nIntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]) \\nQtrDay:(ENGLISH|SCOTTISH|RECEIVED) \\nFull Regular Expression: \\n^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\"\n type: string\n pattern: |-\n ^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlDay:((0[2-9])|([1-2][0-9])|3[0-1]))$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction.\\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification hould be quoted in the end-to-end transaction identification.\"\n type: string\n minLength: 1\n maxLength: 35\n NumberOfPayments:\n description: Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.\n type: string\n minLength: 1\n maxLength: 35\n FirstPaymentDateTime:\n description: \"The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n RecurringPaymentDateTime:\n description: \"The date on which the first recurring payment for a StandingOrder schedule will be made. \\nUsage: This must be populated only if the first recurring date is different to the first payment date.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FinalPaymentDateTime:\n description: \"The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FirstPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the first Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n RecurringPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the recurring Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n FinalPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the final Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Provides the details to identify the debtor account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Identification assigned by an institution to identify an account. This identification is known by the account owner.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: |-\n Specifies a character string with a maximum length of 140 characters.\n Usage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\n type: string\n minLength: 1\n maxLength: 128\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteDomesticStandingOrderResponse6:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - DomesticStandingOrderId\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n DomesticStandingOrderId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the domestic standing order resource.'\n type: string\n minLength: 1\n maxLength: 40\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of the payment order resource.\n type: string\n enum:\n - Cancelled\n - InitiationCompleted\n - InitiationFailed\n - InitiationPending\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Refund:\n type: object\n additionalProperties: false\n required:\n - Account\n description: Unambiguous identification of the refund account to which a refund will be made as a result of the transaction.\n properties:\n Account:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify an account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"Name of the account, as assigned by the account servicing institution.\\nUsage: The account name is the name or names of the account owner(s) represented at an account level. The account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - Frequency\n - FirstPaymentDateTime\n - FirstPaymentAmount\n - CreditorAccount\n description: |-\n The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a domestic standing order.\n properties:\n Frequency:\n description: \"Individual Definitions: \\nEvryDay - Every day \\nEvryWorkgDay - Every working day \\nIntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07)\\nWkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07) \\nIntrvlMnthDay - An interval specified in months (between 01 to 06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31) \\nQtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). \\nENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. \\nSCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November. \\nRECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. \\nIndividual Patterns: \\nEvryDay (ScheduleCode) \\nEvryWorkgDay (ScheduleCode) \\nIntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek) \\nWkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth+ DayInWeek) \\nIntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth) \\nQtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay \\nThe regular expression for this element combines five smaller versions for each permitted pattern. To aid legibility - the components are presented individually here: \\nEvryDay \\nEvryWorkgDay \\nIntrvlWkDay:0[1-9]:0[1-7] \\nWkInMnthDay:0[1-5]:0[1-7] \\nIntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]) \\nQtrDay:(ENGLISH|SCOTTISH|RECEIVED) \\nFull Regular Expression: \\n^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\"\n type: string\n pattern: |-\n ^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlDay:((0[2-9])|([1-2][0-9])|3[0-1]))$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\"\n type: string\n minLength: 1\n maxLength: 35\n NumberOfPayments:\n description: Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.\n type: string\n minLength: 1\n maxLength: 35\n FirstPaymentDateTime:\n description: \"The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n RecurringPaymentDateTime:\n description: \"The date on which the first recurring payment for a Standing Order schedule will be made. \\nUsage: This must be populated only if the first recurring date is different to the first payment date.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FinalPaymentDateTime:\n description: \"The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FirstPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the first Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n RecurringPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the recurring Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n FinalPaymentAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: The amount of the final Standing Order\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Provides the details to identify the debtor account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Identification assigned by an institution to identify an account. This identification is known by the account owner.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n MultiAuthorisation:\n type: object\n additionalProperties: false\n required:\n - Status\n description: The multiple authorisation flow response from the ASPSP.\n properties:\n Status:\n description: Specifies the status of the authorisation flow in code form.\n type: string\n enum:\n - Authorised\n - AwaitingFurtherAuthorisation\n - Rejected\n NumberRequired:\n description: Number of authorisations required for payment order (total required at the start of the multi authorisation journey).\n type: integer\n NumberReceived:\n description: Number of authorisations received.\n type: integer\n LastUpdateDateTime:\n description: \"Last date and time at the authorisation flow was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpirationDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteFile2:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n Initiation:\n type: object\n additionalProperties: false\n required:\n - FileType\n - FileHash\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds using a payment file.\n properties:\n FileType:\n description: Specifies the payment file type.\n type: string\n x-namespaced-enum:\n - UK.OBIE.PaymentInitiation.3.1\n - UK.OBIE.pain.001.001.08\n FileHash:\n description: A base64 encoding of a SHA256 hash of the file to be uploaded.\n type: string\n minLength: 1\n maxLength: 44\n FileReference:\n description: Reference for the file.\n type: string\n minLength: 1\n maxLength: 40\n NumberOfTransactions:\n description: Number of individual transactions contained in the payment information group.\n type: string\n pattern: '[0-9]{1,15}'\n ControlSum:\n description: Total of all individual amounts included in the group, irrespective of currencies.\n type: number\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n OBWriteFileConsent3:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - Initiation\n properties:\n Initiation:\n type: object\n additionalProperties: false\n required:\n - FileType\n - FileHash\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds using a payment file.\n properties:\n FileType:\n description: Specifies the payment file type.\n type: string\n x-namespaced-enum:\n - UK.OBIE.PaymentInitiation.3.1\n - UK.OBIE.pain.001.001.08\n FileHash:\n description: A base64 encoding of a SHA256 hash of the file to be uploaded.\n type: string\n minLength: 1\n maxLength: 44\n FileReference:\n description: Reference for the file.\n type: string\n minLength: 1\n maxLength: 40\n NumberOfTransactions:\n description: Number of individual transactions contained in the payment information group.\n type: string\n pattern: '[0-9]{1,15}'\n ControlSum:\n description: Total of all individual amounts included in the group, irrespective of currencies.\n type: number\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor towhich a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the accountowner(s) represented at an account level, as displayed bythe ASPSP's online channels. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n OBWriteFileConsentResponse4:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of consent resource in code form.\n type: string\n enum:\n - Authorised\n - AwaitingAuthorisation\n - AwaitingUpload\n - Consumed\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the consent resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n CutOffDateTime:\n description: \"Specified cut-off date and time for the payment consent.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: |-\n Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - FileType\n - FileHash\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds using a payment file.\n properties:\n FileType:\n description: Specifies the payment file type.\n type: string\n x-namespaced-enum:\n - UK.OBIE.PaymentInitiation.3.1\n - UK.OBIE.pain.001.001.08\n FileHash:\n description: A base64 encoding of a SHA256 hash of the file to be uploaded.\n type: string\n minLength: 1\n maxLength: 44\n FileReference:\n description: Reference for the file.\n type: string\n minLength: 1\n maxLength: 40\n NumberOfTransactions:\n description: Number of individual transactions contained in the payment information group.\n type: string\n pattern: '[0-9]{1,15}'\n ControlSum:\n description: Total of all individual amounts included in the group, irrespective of currencies.\n type: number\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliationof an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should providethis reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteFileResponse3:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - FilePaymentId\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n FilePaymentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the file payment resource.'\n type: string\n minLength: 1\n maxLength: 40\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the message was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of the payment order resource.\n type: string\n enum:\n - InitiationCompleted\n - InitiationFailed\n - InitiationPending\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - FileType\n - FileHash\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds using a payment file.\n properties:\n FileType:\n description: Specifies the payment file type.\n type: string\n x-namespaced-enum:\n - UK.OBIE.PaymentInitiation.3.1\n - UK.OBIE.pain.001.001.08\n FileHash:\n description: A base64 encoding of a SHA256 hash of the file to be uploaded.\n type: string\n minLength: 1\n maxLength: 44\n FileReference:\n description: Reference for the file.\n type: string\n minLength: 1\n maxLength: 40\n NumberOfTransactions:\n description: Number of individual transactions contained in the payment information group.\n type: string\n pattern: '[0-9]{1,15}'\n ControlSum:\n description: Total of all individual amounts included in the group, irrespective of currencies.\n type: number\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited. All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n MultiAuthorisation:\n type: object\n additionalProperties: false\n required:\n - Status\n description: The multiple authorisation flow response from the ASPSP.\n properties:\n Status:\n description: Specifies the status of the authorisation flow in code form.\n type: string\n enum:\n - Authorised\n - AwaitingFurtherAuthorisation\n - Rejected\n NumberRequired:\n description: Number of authorisations required for payment order (total required at the start of the multi authorisation journey).\n type: integer\n NumberReceived:\n description: Number of authorisations received.\n type: integer\n LastUpdateDateTime:\n description: \"Last date and time at the authorisation flow was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpirationDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteFundsConfirmationResponse1:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n properties:\n FundsAvailableResult:\n type: object\n additionalProperties: false\n required:\n - FundsAvailableDateTime\n - FundsAvailable\n description: Result of a funds availability check.\n properties:\n FundsAvailableDateTime:\n description: \"Date and time at which the funds availability check was generated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FundsAvailable:\n description: Flag to indicate the availability of funds given the Amount in the consent request.\n type: boolean\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteInternational3:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single international payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructionPriority:\n description: Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction.\n type: string\n enum:\n - Normal\n - Urgent\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list publishedseparately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - RateType\n description: Provides details on the currency exchange rate and contract.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of thetransaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n 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.\n Note, the account name is not the product name or the nickname of the account.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: Financial institution servicing an account for the creditor.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry withthe items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money.\\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteInternationalConsent5:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - Initiation\n properties:\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single international payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.\\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructionPriority:\n description: Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction.\n type: string\n enum:\n - Normal\n - Urgent\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - RateType\n description: Provides details on the currency exchange rate and contract.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: Financial institution servicing an account for the creditor.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transactionidentifier of the previous payment occurrence so that theASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteInternationalConsentResponse6:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of consent resource in code form.\n type: string\n enum:\n - Authorised\n - AwaitingAuthorisation\n - Consumed\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n CutOffDateTime:\n description: \"Specified cut-off date and time for the payment consent.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedExecutionDateTime:\n description: \"Expected execution date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedSettlementDateTime:\n description: \"Expected settlement date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-timeformat. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - ExchangeRate\n - RateType\n description: Further detailed information on the exchange rate that has been used in the payment transaction.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and thedebtor agent.\n type: string\n minLength: 1\n maxLength: 256\n ExpirationDateTime:\n description: \"Specified date and time the exchange rate agreement will expire.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single international payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.\\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructionPriority:\n description: Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction.\n type: string\n enum:\n - Normal\n - Urgent\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - RateType\n description: Provides details on the currency exchange rate and contract.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: Financial institution servicing an account for the creditor.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteInternationalResponse5:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - InternationalPaymentId\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n InternationalPaymentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the international payment resource.'\n type: string\n minLength: 1\n maxLength: 40\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the message was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of the payment information group.\n type: string\n enum:\n - AcceptedCreditSettlementCompleted\n - AcceptedSettlementCompleted\n - AcceptedSettlementInProcess\n - AcceptedWithoutPosting\n - Pending\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedExecutionDateTime:\n description: \"Expected execution date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedSettlementDateTime:\n description: \"Expected settlement date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Refund:\n type: object\n additionalProperties: false\n required:\n - Account\n properties:\n Creditor:\n type: object\n additionalProperties: false\n description: Set of elements used to identify a person or an organisation.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n Agent:\n type: object\n additionalProperties: false\n description: Set of elements used to uniquely and unambiguously identify a financial institution or a branch of a financial institution.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n Account:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify an account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"Name of the account, as assigned by the account servicing institution. \\nUsage: The account name is the name or names of the account owner(s) represented at an account level. The account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - ExchangeRate\n - RateType\n description: Further detailed information on the exchange rate that has been used in the payment transaction.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n ExpirationDateTime:\n description: \"Specified date and time the exchange rate agreement will expire.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single international payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructionPriority:\n description: Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction.\n type: string\n enum:\n - Normal\n - Urgent\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - RateType\n description: Provides details on the currency exchange rate and contract.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: Financial institution servicing an account for the creditor.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money.\\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n MultiAuthorisation:\n type: object\n additionalProperties: false\n required:\n - Status\n description: The multiple authorisation flow response from the ASPSP.\n properties:\n Status:\n description: Specifies the status of the authorisation flow in code form.\n type: string\n enum:\n - Authorised\n - AwaitingFurtherAuthorisation\n - Rejected\n NumberRequired:\n description: Number of authorisations required for payment order (total required at the start of the multi authorisation journey).\n type: integer\n NumberReceived:\n description: Number of authorisations received.\n type: integer\n LastUpdateDateTime:\n description: \"Last date and time at the authorisation flow was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpirationDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteInternationalScheduled3:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - RequestedExecutionDateTime\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single scheduled international payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructionPriority:\n description: Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction.\n type: string\n enum:\n - Normal\n - Urgent\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particulargeopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - RateType\n description: Provides details on the currency exchange rate and contract.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: Financial institution servicing an account for the creditor.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteInternationalScheduledConsent5:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - Permission\n - Initiation\n properties:\n Permission:\n description: Specifies the Open Banking service request types.\n type: string\n enum:\n - Create\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - RequestedExecutionDateTime\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single scheduled international payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructionPriority:\n description: |-\n Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction.\n type: string\n enum:\n - Normal\n - Urgent\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - RateType\n description: Provides details on the currency exchange rate and contract.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: |-\n 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.\n Note, the account name is not the product name or the nickname of the account.\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: Financial institution servicing an account for the creditor.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteInternationalScheduledConsentResponse6:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Permission\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of consent resource in code form.\n type: string\n enum:\n - Authorised\n - AwaitingAuthorisation\n - Consumed\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Permission:\n description: Specifies the Open Banking service request types.\n type: string\n enum:\n - Create\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n CutOffDateTime:\n description: \"Specified cut-off date and time for the payment consent.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedExecutionDateTime:\n description: \"Expected execution date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedSettlementDateTime:\n description: \"Expected settlement date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - ExchangeRate\n - RateType\n description: Further detailed information on the exchange rate that has been used in the payment transaction.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n ExpirationDateTime:\n description: \"Specified date and time the exchange rate agreement will expire.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - RequestedExecutionDateTime\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single scheduled international payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructionPriority:\n description: Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction.\n type: string\n enum:\n - Normal\n - Urgent\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: |-\n Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - RateType\n description: Provides details on the currency exchange rate and contract.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 350\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: Financial institution servicing an account for the creditor.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: |-\n Specifies a character string with a maximum length of 140 characters.\n Usage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\n type: string\n minLength: 1\n maxLength: 128\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteInternationalScheduledResponse6:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - InternationalScheduledPaymentId\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n InternationalScheduledPaymentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the international scheduled payment resource.'\n type: string\n minLength: 1\n maxLength: 40\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the message was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of the payment order resource.\n type: string\n enum:\n - Cancelled\n - InitiationCompleted\n - InitiationFailed\n - InitiationPending\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedExecutionDateTime:\n description: \"Expected execution date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpectedSettlementDateTime:\n description: \"Expected settlement date and time for the payment resource.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Refund:\n type: object\n additionalProperties: false\n required:\n - Account\n properties:\n Creditor:\n type: object\n additionalProperties: false\n description: Set of elements used to identify a person or an organisation.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n Agent:\n type: object\n additionalProperties: false\n description: |-\n Set of elements used to uniquely and unambiguously identify a financial institution or a branch of a financial institution.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n Account:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify an account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"Name of the account, as assigned by the account servicing institution. \\nUsage: The account name is the name or names of the account owner(s) represented at an account level. The account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - ExchangeRate\n - RateType\n description: Further detailed information on the exchange rate that has been used in the payment transaction.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n ExpirationDateTime:\n description: \"Specified date and time the exchange rate agreement will expire.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Initiation:\n type: object\n additionalProperties: false\n required:\n - InstructionIdentification\n - RequestedExecutionDateTime\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single scheduled international payment.\n properties:\n InstructionIdentification:\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. \\nIt can be included in several messages related to the instruction.\"\n type: string\n minLength: 1\n maxLength: 35\n EndToEndIdentification:\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.\"\n type: string\n minLength: 1\n maxLength: 35\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructionPriority:\n description: Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction.\n type: string\n enum:\n - Normal\n - Urgent\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n RequestedExecutionDateTime:\n description: \"Date at which the initiating party requests the clearing agent to process the payment. \\nUsage: This is the date on which the debtor's account is to be debited.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n CurrencyOfTransfer:\n description: |-\n Specifies the currency of the to be transferred amount, which is different from the currency of the debtor's account.\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: |-\n Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n ExchangeRateInformation:\n type: object\n additionalProperties: false\n required:\n - UnitCurrency\n - RateType\n description: Provides details on the currency exchange rate and contract.\n properties:\n UnitCurrency:\n description: Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.\n type: string\n pattern: '^[A-Z]{3,3}$'\n ExchangeRate:\n description: |-\n The factor used for conversion of an amount from one currency to another. This reflects the price at which one currency was bought with another currency.\n type: number\n RateType:\n description: Specifies the type used to complete the currency exchange.\n type: string\n enum:\n - Actual\n - Agreed\n - Indicative\n ContractIdentification:\n description: |-\n Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party\/creditor and the debtor agent.\n type: string\n minLength: 1\n maxLength: 256\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 140\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: Financial institution servicing an account for the creditor.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n RemittanceInformation:\n type: object\n additionalProperties: false\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n type: string\n minLength: 1\n maxLength: 140\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. \\nOB: The Faster Payments Scheme can only accept 18 characters for the ReferenceInformation field - which is where this ISO field will be mapped.\"\n type: string\n minLength: 1\n maxLength: 35\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n MultiAuthorisation:\n type: object\n additionalProperties: false\n required:\n - Status\n description: The multiple authorisation flow response from the ASPSP.\n properties:\n Status:\n description: Specifies the status of the authorisation flow in code form.\n type: string\n enum:\n - Authorised\n - AwaitingFurtherAuthorisation\n - Rejected\n NumberRequired:\n description: Number of authorisations required for payment order (total required at the start of the multi authorisation journey).\n type: integer\n NumberReceived:\n description: Number of authorisations received.\n type: integer\n LastUpdateDateTime:\n description: \"Last date and time at the authorisation flow was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpirationDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteInternationalStandingOrder4:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n Initiation:\n type: object\n additionalProperties: false\n required:\n - Frequency\n - FirstPaymentDateTime\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for an international standing order.\n properties:\n Frequency:\n description: \"Individual Definitions: \\nEvryDay - Every day \\nEvryWorkgDay - Every working day \\nIntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07) \\nWkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07) \\nIntrvlMnthDay - An interval specified in months (between 01 to 06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31) \\nQtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). \\nENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. \\nSCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November. \\nRECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. \\nIndividual Patterns: \\nEvryDay (ScheduleCode) \\nEvryWorkgDay (ScheduleCode) \\nIntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek) \\nWkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth + DayInWeek) \\nIntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth) \\nQtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay \\nThe regular expression for this element combines five smaller versions for each permitted pattern. To aid legibility - the components are presented individually here: \\nEvryDay \\nEvryWorkgDay \\nIntrvlWkDay:0[1-9]:0[1-7] \\nWkInMnthDay:0[1-5]:0[1-7] \\nIntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]) \\nQtrDay:(ENGLISH|SCOTTISH|RECEIVED) \\nFull Regular Expression: \\n^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\"\n type: string\n pattern: |-\n ^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlDay:((0[2-9])|([1-2][0-9])|3[0-1]))$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\"\n type: string\n minLength: 1\n maxLength: 35\n NumberOfPayments:\n description: Number of the payments that will be made in completing this frequency sequence including any executed since the sequencestart date.\n type: string\n minLength: 1\n maxLength: 35\n FirstPaymentDateTime:\n description: \"The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FinalPaymentDateTime:\n description: \"The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone.\\nAn example is below:\\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: |-\n Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Provides the details to identify the debtor account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 350\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: \"Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account. \\nThis is the servicer of the beneficiary account.\"\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n description: Unique and unambiguous identification of the servicing institution.\n type: string\n minLength: 1\n maxLength: 35\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify the beneficiary account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteInternationalStandingOrderConsent6:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - Permission\n - Initiation\n properties:\n Permission:\n description: Specifies the Open Banking service request types.\n type: string\n enum:\n - Create\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - Frequency\n - FirstPaymentDateTime\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for an international standing order.\n properties:\n Frequency:\n description: \"Individual Definitions: \\nEvryDay - Every day \\nEvryWorkgDay - Every working day \\nIntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07) \\nWkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07) \\nIntrvlMnthDay - An interval specified in months (between 01 to 06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31) \\nQtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). \\nENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. \\nSCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November. \\nRECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. \\nIndividual Patterns: \\nEvryDay (ScheduleCode) \\nEvryWorkgDay (ScheduleCode) \\nIntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek) \\nWkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth + DayInWeek) \\nIntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth) \\nQtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay \\nThe regular expression for this element combines five smaller versions for each permitted pattern. To aid legibility - the components are presented individually here: \\nEvryDay \\nEvryWorkgDay \\nIntrvlWkDay:0[1-9]:0[1-7] \\nWkInMnthDay:0[1-5]:0[1-7]\\nIntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]) \\nQtrDay:(ENGLISH|SCOTTISH|RECEIVED) \\nFull Regular Expression: \\n^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\"\n type: string\n pattern: |-\n ^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlDay:((0[2-9])|([1-2][0-9])|3[0-1]))$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\"\n type: string\n minLength: 1\n maxLength: 35\n NumberOfPayments:\n description: Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.\n type: string\n minLength: 1\n maxLength: 35\n FirstPaymentDateTime:\n description: \"The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone.\\nAn example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FinalPaymentDateTime:\n description: \"The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone.\\nAn example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: |-\n Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Provides the details to identify the debtor account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 350\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: |-\n Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.\n This is the servicer of the beneficiary account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n description: Unique and unambiguous identification of the servicing institution.\n type: string\n minLength: 1\n maxLength: 35\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify the beneficiary account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBWriteInternationalStandingOrderConsentResponse7:\n type: object\n additionalProperties: false\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Permission\n - Initiation\n properties:\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of resource in code form.\n type: string\n enum:\n - Authorised\n - AwaitingAuthorisation\n - Consumed\n - Rejected\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Permission:\n description: Specifies the Open Banking service request types.\n type: string\n enum:\n - Create\n ReadRefundAccount:\n description: Specifies to share the refund account details with PISP\n type: string\n enum:\n - 'No'\n - 'Yes'\n CutOffDateTime:\n description: \"Specified cut-off date and time for the payment consent.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - Frequency\n - FirstPaymentDateTime\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for an international standing order.\n properties:\n Frequency:\n description: \"Individual Definitions: \\nEvryDay - Every day \\nEvryWorkgDay - Every working day \\nIntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07) \\nWkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07) \\nIntrvlMnthDay - An interval specified in months (between 01 to 06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31) \\nQtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). \\nENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. \\nSCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November. \\nRECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. \\nIndividual Patterns: \\nEvryDay (ScheduleCode) \\nEvryWorkgDay (ScheduleCode) \\nIntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek) \\nWkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth+ DayInWeek) \\nIntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth)\\nQtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay \\nThe regular expression for this element combines five smaller versions for each permitted pattern. To aid legibility - the components are presented individually here: \\nEvryDay \\nEvryWorkgDay \\nIntrvlWkDay:0[1-9]:0[1-7] \\nWkInMnthDay:0[1-5]:0[1-7] \\nIntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]) \\nQtrDay:(ENGLISH|SCOTTISH|RECEIVED) \\nFull Regular Expression: \\n^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\"\n type: string\n pattern: |-\n ^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlDay:((0[2-9])|([1-2][0-9])|3[0-1]))$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\n Reference:\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\"\n type: string\n minLength: 1\n maxLength: 35\n NumberOfPayments:\n description: Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.\n type: string\n minLength: 1\n maxLength: 35\n FirstPaymentDateTime:\n description: \"The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FinalPaymentDateTime:\n description: \"The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Provides the details to identify the debtor account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 350\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: \"Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account. \\nThis is the servicer of the beneficiary account.\"\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n description: Unique and unambiguous identification of the servicing institution.\n type: string\n minLength: 1\n maxLength: 35\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify the beneficiary account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n Authorisation:\n type: object\n additionalProperties: false\n required:\n - AuthorisationType\n description: The authorisation type request from the TPP.\n properties:\n AuthorisationType:\n description: Type of authorisation flow requested.\n type: string\n enum:\n - Any\n - Single\n CompletionDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n SCASupportData:\n type: object\n additionalProperties: false\n description: 'Supporting Data provided by TPP, when requesting SCA Exemption.'\n properties:\n RequestedSCAExemptionType:\n description: This field allows a PISP to request specific SCA Exemption for a Payment Initiation\n type: string\n enum:\n - BillPayment\n - ContactlessTravel\n - EcommerceGoods\n - EcommerceServices\n - Kiosk\n - Parking\n - PartyToParty\n AppliedAuthenticationApproach:\n description: \"Specifies a character string with a maximum length of 40 characters. \\nUsage: This field indicates whether the PSU was subject to SCA performed by the TPP\"\n type: string\n enum:\n - CA\n - SCA\n ReferencePaymentOrderId:\n description: \"Specifies a character string with a maximum length of 140 characters. \\nUsage: If the payment is recurring then the transaction identifier of the previous payment occurrence so that the ASPSP can verify that the PISP, amount and the payee are the same as the previous occurrence.\"\n type: string\n minLength: 1\n maxLength: 128\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWriteInternationalStandingOrderResponse7:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n required:\n - InternationalStandingOrderId\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n properties:\n InternationalStandingOrderId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the international standing order resource.'\n type: string\n minLength: 1\n maxLength: 40\n ConsentId:\n description: 'OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.'\n type: string\n minLength: 1\n maxLength: 128\n CreationDateTime:\n description: \"Date and time at which the resource was created.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Status:\n description: Specifies the status of resource in code form.\n type: string\n enum:\n - Cancelled\n - InitiationCompleted\n - InitiationFailed\n - InitiationPending\n StatusUpdateDateTime:\n description: \"Date and time at which the resource status was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Refund:\n type: object\n additionalProperties: false\n required:\n - Account\n properties:\n Creditor:\n type: object\n additionalProperties: false\n description: Set of elements used to identify a person or an organisation.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 350\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n Agent:\n type: object\n additionalProperties: false\n description: Set of elements used to uniquely and unambiguously identify a financial institution or a branch of a financial institution.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_1'\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n Account:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify an account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"Name of the account, as assigned by the account servicing institution. \\nUsage: The account name is the name or names of the account owner(s) represented at an account level. The account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Charges:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Set of elements used to provide details of a charge for the payment initiation.\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n Initiation:\n type: object\n additionalProperties: false\n required:\n - Frequency\n - FirstPaymentDateTime\n - CurrencyOfTransfer\n - InstructedAmount\n - CreditorAccount\n description: The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for an international standing order.\n properties:\n Frequency:\n description: \"Individual Definitions: \\nEvryDay - Every day \\nEvryWorkgDay - Every working day \\nIntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07) \\nWkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07) \\nIntrvlMnthDay - An interval specified in months (between 01 to 06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31) \\nQtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). \\nENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. \\nSCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November. \\nRECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. \\nIndividual Patterns: \\nEvryDay (ScheduleCode) \\nEvryWorkgDay (ScheduleCode) \\nIntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek)\\nWkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth + DayInWeek) \\nIntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth) \\nQtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay \\nThe regular expression for this element combines five smallerversions for each permitted pattern. To aid legibility - the components are presented individually here: \\nEvryDay \\nEvryWorkgDay \\nIntrvlWkDay:0[1-9]:0[1-7] \\nWkInMnthDay:0[1-5]:0[1-7] \\nIntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]) \\nQtrDay:(ENGLISH|SCOTTISH|RECEIVED) \\nFull Regular Expression: \\n^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\"\n type: string\n pattern: |-\n ^(EvryDay)$|^(EvryWorkgDay)$|^(IntrvlDay:((0[2-9])|([1-2][0-9])|3[0-1]))$|^(IntrvlWkDay:0[1-9]:0[1-7])$|^(WkInMnthDay:0[1-5]:0[1-7])$|^(IntrvlMnthDay:(0[1-6]|12|24):(-0[1-5]|0[1-9]|[12][0-9]|3[01]))$|^(QtrDay:(ENGLISH|SCOTTISH|RECEIVED))$\n Reference:\n description: \"Unique reference, as assigned by the creditor, tounambiguously refer to the payment transaction. \\nUsage: If available, the initiating party should provide this reference in the structured remittance information, to enablereconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\"\n type: string\n minLength: 1\n maxLength: 35\n NumberOfPayments:\n description: Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.\n type: string\n minLength: 1\n maxLength: 35\n FirstPaymentDateTime:\n description: \"The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n FinalPaymentDateTime:\n description: \"The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone.\\nAn example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Purpose:\n description: \"Specifies the external purpose code in the format of character string with a maximum length of 4 characters. \\nThe list of valid codes is an external code list published separately. \\nExternal code sets can be downloaded from www.iso20022.org.\"\n type: string\n minLength: 1\n maxLength: 4\n ExtendedPurpose:\n description: |-\n Specifies the purpose of an international payment, when there is no corresponding 4 character code available in the ISO20022 list of Purpose Codes.\n type: string\n minLength: 1\n maxLength: 140\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n CurrencyOfTransfer:\n description: 'Specifies the currency of the to be transferred amount, which is different from the currency of the debtor''s account.'\n type: string\n pattern: '^[A-Z]{3,3}$'\n DestinationCountryCode:\n description: Country in which Credit Account is domiciled. Code to identify a country, a dependency, or another area of particular geopolitical interest, on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).\n type: string\n pattern: '[A-Z]{2,2}'\n InstructedAmount:\n type: object\n additionalProperties: false\n required:\n - Amount\n - Currency\n description: \"Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. \\nUsage: This amount has to be transported unchanged through the transaction chain.\"\n properties:\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n DebtorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n description: Provides the details to identify the debtor account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"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. \\nNote, the account name is not the product name or the nickname of the account.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n Creditor:\n type: object\n additionalProperties: false\n description: Party to which an amount of money is due.\n properties:\n Name:\n description: Name by which a party is known and which is usually used to identify that party.\n type: string\n minLength: 1\n maxLength: 350\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAgent:\n type: object\n additionalProperties: false\n description: |-\n Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.\n This is the servicer of the beneficiary account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n description: Unique and unambiguous identification of the servicing institution.\n type: string\n minLength: 1\n maxLength: 35\n Name:\n $ref: '#\/components\/schemas\/Name'\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n type: object\n additionalProperties: false\n required:\n - SchemeName\n - Identification\n - Name\n description: Provides the details to identify the beneficiary account.\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n $ref: '#\/components\/schemas\/Identification_0'\n Name:\n description: \"The account name is the name or names of the account owner(s) represented at an account level. \\nNote, the account name is not the product name or the nickname of the account. \\nOB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.\"\n type: string\n minLength: 1\n maxLength: 350\n SecondaryIdentification:\n $ref: '#\/components\/schemas\/SecondaryIdentification'\n SupplementaryData:\n $ref: '#\/components\/schemas\/OBSupplementaryData1'\n MultiAuthorisation:\n type: object\n additionalProperties: false\n required:\n - Status\n description: The multiple authorisation flow response from the ASPSP.\n properties:\n Status:\n description: Specifies the status of the authorisation flow in code form.\n type: string\n enum:\n - Authorised\n - AwaitingFurtherAuthorisation\n - Rejected\n NumberRequired:\n description: Number of authorisations required for payment order (total required at the start of the multi authorisation journey).\n type: integer\n NumberReceived:\n description: Number of authorisations received.\n type: integer\n LastUpdateDateTime:\n description: \"Last date and time at the authorisation flow was updated.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n ExpirationDateTime:\n description: \"Date and time at which the requested authorisation flow must be completed.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n Debtor:\n $ref: '#\/components\/schemas\/OBDebtorIdentification1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n OBWritePaymentDetailsResponse1:\n type: object\n additionalProperties: false\n required:\n - Data\n properties:\n Data:\n type: object\n additionalProperties: false\n properties:\n PaymentStatus:\n type: array\n items:\n type: object\n additionalProperties: false\n description: Payment status details.\n required:\n - PaymentTransactionId\n - Status\n - StatusUpdateDateTime\n properties:\n PaymentTransactionId:\n description: Unique identifier for the transaction within an servicing institution. This identifier is both unique and immutable.\n type: string\n minLength: 1\n maxLength: 210\n Status:\n description: Status of a transfer, as assigned by the transaction administrator.\n type: string\n enum:\n - Accepted\n - AcceptedCancellationRequest\n - AcceptedCreditSettlementCompleted\n - AcceptedCustomerProfile\n - AcceptedFundsChecked\n - AcceptedSettlementCompleted\n - AcceptedSettlementInProcess\n - AcceptedTechnicalValidation\n - AcceptedWithChange\n - AcceptedWithoutPosting\n - Cancelled\n - NoCancellationProcess\n - PartiallyAcceptedCancellationRequest\n - PartiallyAcceptedTechnicalCorrect\n - PaymentCancelled\n - Pending\n - PendingCancellationRequest\n - Received\n - Rejected\n - RejectedCancellationRequest\n StatusUpdateDateTime:\n description: \"Date and time at which the status was assigned to the transfer.All dates in the JSON payloads are represented in ISO 8601 date-time format. \\nAll date-time fields in responses must include the timezone. An example is below: \\n2017-04-05T10:43:07+00:00\"\n type: string\n format: date-time\n StatusDetail:\n type: object\n additionalProperties: false\n required:\n - Status\n description: Payment status details as per underlying Payment Rail.\n properties:\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n Status:\n description: Status of a transfer, as assigned by the transaction administrator.\n type: string\n minLength: 1\n maxLength: 128\n StatusReason:\n description: Reason Code provided for the status of a transfer.\n type: string\n enum:\n - Cancelled\n - PendingFailingSettlement\n - PendingSettlement\n - Proprietary\n - ProprietaryRejection\n - Suspended\n - Unmatched\n StatusReasonDescription:\n description: Reason provided for the status of a transfer.\n type: string\n minLength: 1\n maxLength: 256\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/Meta'\n PostCode:\n description: |-\n Identifier consisting of a group of letters and\/or numbers that is added to a postal address to assist the sorting of mail.\n type: string\n minLength: 1\n maxLength: 16\n SecondaryIdentification:\n description: \"This is secondary identification of the account, as assigned by the account servicing institution. \\nThis can be used by building societies to additionally identify accounts with a roll number (in addition to a sort code and account number combination).\"\n type: string\n minLength: 1\n maxLength: 34\n StreetName:\n description: Name of a street or thoroughfare.\n type: string\n minLength: 1\n maxLength: 70\n SubDepartment:\n description: Identification of a sub-division of a large organisation or building.\n type: string\n minLength: 1\n maxLength: 70\n TownName:\n description: 'Name of a built-up area, with defined boundaries, and a local government.'\n type: string\n minLength: 1\n maxLength: 35\n OBDomesticVRPConsentResponse:\n type: object\n required:\n - Data\n - Risk\n - Links\n - Meta\n properties:\n Data:\n type: object\n required:\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - ControlParameters\n - Initiation\n properties:\n ReadRefundAccount:\n type: string\n enum:\n - 'Yes'\n - 'No'\n description: Indicates whether information about RefundAccount should be included in the payment response.\n ConsentId:\n type: string\n minLength: 1\n maxLength: 128\n description: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.\n CreationDateTime:\n type: string\n format: date-time\n description: Date and time at which the resource was created.\n Status:\n type: string\n description: Specifies the status of resource in code form.\n enum:\n - Authorised\n - AwaitingAuthorisation\n - Rejected\n - Expired\n StatusUpdateDateTime:\n type: string\n format: date-time\n description: Date and time at which the resource status was updated.\n ControlParameters:\n $ref: '#\/components\/schemas\/OBDomesticVRPControlParameters'\n Initiation:\n $ref: '#\/components\/schemas\/OBDomesticVRPInitiation'\n DebtorAccount:\n $ref: '#\/components\/schemas\/OBCashAccountDebtorWithName'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/VrpMeta'\n OBDomesticVRPConsentRequest:\n type: object\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n required:\n - ControlParameters\n - Initiation\n properties:\n ReadRefundAccount:\n type: string\n enum:\n - 'Yes'\n - 'No'\n description: Indicates whether information about RefundAccount should be included in the payment response.\n ControlParameters:\n $ref: '#\/components\/schemas\/OBDomesticVRPControlParameters'\n Initiation:\n $ref: '#\/components\/schemas\/OBDomesticVRPInitiation'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBDomesticVRPControlParameters:\n type: object\n required:\n - VRPType\n - PSUAuthenticationMethods\n - MaximumIndividualAmount\n - PeriodicLimits\n properties:\n ValidFromDateTime:\n type: string\n format: date-time\n description: Start date time for which the consent remains valid.\n ValidToDateTime:\n type: string\n format: date-time\n description: End date time for which the consent remains valid.\n MaximumIndividualAmount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n PeriodicLimits:\n type: array\n items:\n type: object\n required:\n - PeriodType\n - PeriodAlignment\n - Amount\n - Currency\n properties:\n PeriodType:\n type: string\n enum:\n - Day\n - Week\n - Fortnight\n - Month\n - Half-year\n - Year\n description: Period type for this period limit\n PeriodAlignment:\n type: string\n enum:\n - Consent\n - Calendar\n description: Specifies whether the period starts on the date of consent creation or lines up with a calendar\n Amount:\n $ref: '#\/components\/schemas\/OBActiveCurrencyAndAmount_SimpleType'\n Currency:\n $ref: '#\/components\/schemas\/ActiveOrHistoricCurrencyCode'\n VRPType:\n type: array\n items:\n $ref: '#\/components\/schemas\/OBVRPConsentType'\n minItems: 1\n description: The types of payments that can be made under this VRP consent. This can be used to indicate whether this include sweeping payment or other ecommerce payments.\n PSUAuthenticationMethods:\n type: array\n items:\n $ref: '#\/components\/schemas\/OBVRPAuthenticationMethods'\n minItems: 1\n description: Indicates that the PSU authentication methods supported.\n PSUInteractionTypes:\n type: array\n items:\n $ref: '#\/components\/schemas\/OBVRPInteractionTypes'\n description: Indicates interaction type, currently if customer is present or not present.\n SupplementaryData:\n type: object\n description: Additional information that can not be captured in the structured fields and\/or any other specific block\n OBDomesticVRPInitiation:\n type: object\n properties:\n DebtorAccount:\n $ref: '#\/components\/schemas\/OBCashAccountDebtorWithName'\n CreditorAgent:\n $ref: '#\/components\/schemas\/OBBranchAndFinancialInstitutionIdentification6'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n $ref: '#\/components\/schemas\/OBCashAccountCreditor3'\n RemittanceInformation:\n type: object\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n type: string\n minLength: 1\n maxLength: 140\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n Reference:\n type: string\n minLength: 1\n maxLength: 35\n description: \"Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. Usage - If available, the initiating party should provide this reference in the structured remittance information, to enable reconciliation by the creditor upon receipt of the amount of money. \\nIf the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification.\"\n OBCashAccountDebtorWithName:\n type: object\n description: Within the context of the Consents Refund object this is only included when `Data.ReadRefundAccount` is set to `Yes`\n required:\n - SchemeName\n - Identification\n - Name\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n type: string\n minLength: 1\n maxLength: 256\n description: Identification assigned by an institution to identify an account. This identification is known by the account owner.\n Name:\n type: string\n minLength: 1\n maxLength: 350\n description: Name of the account, as assigned by the account servicing institution. Usage The account name is the name or names of the account owner(s) represented at an account level. The account name is not the product name or the nickname of the account.\n SecondaryIdentification:\n type: string\n minLength: 1\n maxLength: 34\n description: This is secondary identification of the account, as assigned by theaccount servicing institution. This can be used by building societies to additionally identify accounts with a roll number (in addition to a sort code and account number combination)\n OBCashAccountCreditor3:\n type: object\n required:\n - SchemeName\n - Identification\n - Name\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalAccountIdentification4Code'\n Identification:\n type: string\n minLength: 1\n maxLength: 256\n description: Identification assigned by an institution to identify an account. This identification is known by the account owner.\n Name:\n type: string\n minLength: 1\n maxLength: 350\n description: \"Name of the account, as assigned by the account servicing institution. \\nUsage: the account name is the name or names of the account owner(s) represented at an account level. \\nThe account name is not the product name or the nickname of the account.\"\n SecondaryIdentification:\n type: string\n minLength: 1\n maxLength: 34\n description: \"This is secondary identification of the account, as assigned by the account servicing institution. \\nThis can be used by building societies to additionally identify accounts with a roll number (in addition to a sort code and account number combination)\"\n OBBranchAndFinancialInstitutionIdentification6:\n type: object\n properties:\n SchemeName:\n $ref: '#\/components\/schemas\/OBExternalFinancialInstitutionIdentification4Code'\n Identification:\n type: string\n minLength: 1\n maxLength: 35\n description: Unique and unambiguous identification of a financial institution or a branch of a financial institution.\n Name:\n type: string\n minLength: 1\n maxLength: 140\n description: Name by which an agent is known and which is usually used to identify that agent.\n PostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n OBDomesticVRPRequest:\n type: object\n required:\n - Data\n - Risk\n properties:\n Data:\n type: object\n required:\n - ConsentId\n - PSUAuthenticationMethod\n - Initiation\n - Instruction\n properties:\n ConsentId:\n type: string\n minLength: 1\n maxLength: 128\n description: Identifier for the Domestic VRP Consent that this payment is made under.\n PSUAuthenticationMethod:\n allOf:\n - $ref: '#\/components\/schemas\/OBVRPAuthenticationMethods'\n - description: The authentication method that was used to authenticate the PSU.\n Initiation:\n $ref: '#\/components\/schemas\/OBDomesticVRPInitiation'\n Instruction:\n $ref: '#\/components\/schemas\/OBDomesticVRPInstruction'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n OBDomesticVRPResponse:\n type: object\n required:\n - Data\n - Risk\n - Links\n - Meta\n properties:\n Data:\n type: object\n required:\n - DomesticVRPId\n - ConsentId\n - CreationDateTime\n - Status\n - StatusUpdateDateTime\n - Initiation\n - Instruction\n properties:\n DomesticVRPId:\n type: string\n minLength: 1\n maxLength: 40\n description: Unique identification as assigned by the ASPSP to uniquely identify the domestic payment resource.\n ConsentId:\n type: string\n minLength: 1\n maxLength: 128\n description: Identifier for the Domestic VRP Consent that this payment is madeunder.\n CreationDateTime:\n type: string\n format: date-time\n description: Date and time at which the resource was created.\n Status:\n type: string\n description: Specifies the status of the payment information group.\n enum:\n - AcceptedCreditSettlementCompleted\n - AcceptedWithoutPosting\n - AcceptedSettlementCompleted\n - AcceptedSettlementInProcess\n - Pending\n - Rejected\n StatusReason:\n $ref: '#\/components\/schemas\/OBVRPStatusReasonCode'\n StatusReasonDescription:\n type: string\n minLength: 1\n maxLength: 256\n description: 'Description related to provided Status\/StatusReason'\n StatusUpdateDateTime:\n type: string\n format: date-time\n description: Date and time at which the resource status was updated.\n ExpectedExecutionDateTime:\n type: string\n format: date-time\n description: Expected execution date and time for the payment resource.\n ExpectedSettlementDateTime:\n type: string\n format: date-time\n description: Expected settlement date and time for the payment resource.\n Refund:\n $ref: '#\/components\/schemas\/OBCashAccountDebtorWithName'\n Charges:\n type: array\n items:\n required:\n - Amount\n - ChargeBearer\n - Type\n type: object\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n description: Set of elements used to provide details of a charge for the payment initiation.\n Initiation:\n $ref: '#\/components\/schemas\/OBDomesticVRPInitiation'\n Instruction:\n $ref: '#\/components\/schemas\/OBDomesticVRPInstruction'\n DebtorAccount:\n $ref: '#\/components\/schemas\/OBCashAccountDebtorWithName'\n Risk:\n $ref: '#\/components\/schemas\/OBRisk1'\n Links:\n $ref: '#\/components\/schemas\/Links'\n Meta:\n $ref: '#\/components\/schemas\/VrpMeta'\n OBVRPFundsConfirmationRequest:\n type: object\n description: The OBVRPFundsConfirmationRequest object must be used to request funds availability for a specific amount in the Debtor Account included in the VRP consents.\n properties:\n Data:\n type: object\n required:\n - ConsentId\n - InstructedAmount\n properties:\n ConsentId:\n type: string\n minLength: 1\n maxLength: 128\n description: Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation consent resource.\n Reference:\n type: string\n minLength: 1\n maxLength: 35\n description: Unique reference, as assigned by the PISP, to unambiguously refer to the request related to the payment transaction.\n InstructedAmount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n OBVRPFundsConfirmationResponse:\n type: object\n description: The confirmation of funds response contains the result of a funds availability check.\n properties:\n Data:\n type: object\n required:\n - FundsConfirmationId\n - ConsentId\n - CreationDateTime\n - FundsAvailableResult\n - InstructedAmount\n properties:\n FundsConfirmationId:\n type: string\n minLength: 1\n maxLength: 40\n description: Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation resource.\n ConsentId:\n type: string\n minLength: 1\n maxLength: 128\n description: Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation consent resource.\n CreationDateTime:\n type: string\n format: date-time\n description: Date and time at which the resource was created.\n Reference:\n type: string\n minLength: 1\n maxLength: 35\n description: Unique reference, as assigned by the CBPII, to unambiguously refer to the request related to the payment transaction.\n FundsAvailableResult:\n $ref: '#\/components\/schemas\/OBPAFundsAvailableResult1'\n InstructedAmount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n OBPAFundsAvailableResult1:\n type: object\n description: Availability result, clearly indicating the availability of funds given the Amount in the request.\n required:\n - FundsAvailableDateTime\n - FundsAvailable\n properties:\n FundsAvailableDateTime:\n type: string\n format: date-time\n description: Date and time at which the funds availability check was generated.\n FundsAvailable:\n type: string\n description: Availability result, clearly indicating the availability of funds given the Amount in the request.\n enum:\n - Available\n - NotAvailable\n OBCharge2:\n type: object\n required:\n - ChargeBearer\n - Type\n - Amount\n properties:\n ChargeBearer:\n $ref: '#\/components\/schemas\/OBChargeBearerType1Code'\n Type:\n $ref: '#\/components\/schemas\/OBExternalPaymentChargeType1Code'\n Amount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n OBExternalStatus2Code:\n type: string\n enum:\n - Authorised\n - AwaitingFurtherAuthorisation\n - Rejected\n OBDomesticVRPInstruction:\n type: object\n required:\n - InstructionIdentification\n - EndToEndIdentification\n - InstructedAmount\n - CreditorAccount\n properties:\n InstructionIdentification:\n type: string\n minLength: 1\n maxLength: 35\n description: \"Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. \\nUsage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. \\nIt can be included in several messages related to the instruction.\"\n EndToEndIdentification:\n type: string\n minLength: 1\n maxLength: 35\n description: \"Unique identification assigned by the initiating party to unambiguously identify the transaction. \\nThis identification is passed on, unchanged, throughout the entire end-to-end chain. \\nUsage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. \\nIt can be included in several messages related to the transaction. \\nOB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field\"\n RemittanceInformation:\n $ref: '#\/components\/schemas\/OBVRPRemittanceInformation'\n LocalInstrument:\n $ref: '#\/components\/schemas\/OBExternalLocalInstrument1Code'\n InstructedAmount:\n $ref: '#\/components\/schemas\/OBActiveOrHistoricCurrencyAndAmount'\n CreditorAgent:\n $ref: '#\/components\/schemas\/OBBranchAndFinancialInstitutionIdentification6'\n CreditorPostalAddress:\n $ref: '#\/components\/schemas\/OBPostalAddress6'\n CreditorAccount:\n $ref: '#\/components\/schemas\/OBCashAccountCreditor3'\n SupplementaryData:\n type: object\n description: 'Additional information that can not be captured in the structured fields and\/or any other specific block.'\n OBVRPRemittanceInformation:\n type: object\n description: 'Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts'' receivable system.'\n properties:\n Unstructured:\n type: string\n minLength: 1\n maxLength: 140\n description: 'Information supplied to enable the matching\/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts'' receivable system, in an unstructured form.'\n Reference:\n type: string\n minLength: 1\n maxLength: 35\n description: |-\n Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. The PISP must populate this with the same value as specified in the\n `Data.Initiation.RemittanceInformation.Reference` of the consent.\n OBVRPStatusReasonCode:\n type: string\n x-namespaced-enum:\n - UK.OBIE.ExemptionNotApplied\n - UK.OBIE.OtherReason\n description: Reason Code provided for the status of a VRP. To be documented in the Developer Portal.\n OBVRPConsentType:\n type: string\n x-namespaced-enum:\n - UK.OBIE.VRPType.Sweeping\n - UK.OBIE.VRPType.Other\n OBVRPAuthenticationMethods:\n type: string\n x-namespaced-enum:\n - UK.OBIE.SCA\n - UK.OBIE.SCANotRequired\n OBVRPInteractionTypes:\n type: string\n enum:\n - InSession\n - OffSession\n"

{}