PaymentInitiationAPI

OBExternalAccountIdentification4Code

`OBCashAccountCreditor3` - Up

Provides the details to identify the beneficiary account.

SchemeName

Identification

String Identification assigned by an institution to identify an account. This identification is known by the account owner.

Name

String 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. OB: ASPSPs may carry out name validation for Confirmation of Payee, but it is not mandatory.

SecondaryIdentification (optional)

String This is secondary identification of the account, as assigned by the account 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).

`OBCashAccountDebtor4` - Up

Provides the details to identify the debtor account.

SchemeName

OBExternalAccountIdentification4Code

Identification

String Identification assigned by an institution to identify an account. This identification is known by the account owner.

Name (optional)

SecondaryIdentification (optional)

`OBCharge2` - Up

Set of elements used to provide details of a charge for the payment initiation.

ChargeBearer

OBExternalPaymentChargeType1Code

Type

Amount

OBCharge2_Amount

`OBCharge2_Amount` - Up

Amount of money associated with the charge type.

Amount

OBActiveCurrencyAndAmount_SimpleType

Currency

String

`OBChargeBearerType1Code` - Up

Specifies which party/parties will bear the charges associated with the processing of the payment transaction.

`OBCountrySubDiv` - Up

`OBDeliverAddress` - Up

Information that locates and identifies a specific address, as defined by postal services or in free format text.

AddressLine (optional)

OBAddressLine

StreetName (optional)

String Name of a street or thoroughfare.

BuildingNumber (optional)

String Number that identifies the position of a building on a street.

PostCode (optional)

String Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.

TownName

String Name of a built-up area, with defined boundaries, and a local government.

CountrySubDivision (optional)

OBCountrySubDiv

Country

String Nation with its own government, occupying a particular territory.

`OBDomestic2` - Up

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.

InstructionIdentification

String Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. 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.

EndToEndIdentification

String 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. Usage: 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. OB: The Faster Payments Scheme can only access 31 characters for the EndToEndIdentification field.

LocalInstrument (optional)

InstructedAmount

OBActiveCurrencyAndAmount_SimpleType 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. Usage: This amount has to be transported unchanged through the transaction chain.

DebtorAccount (optional)

CreditorAccount

CreditorPostalAddress (optional)

RemittanceInformation (optional)

SupplementaryData (optional)

`OBDomesticScheduled2` - Up

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.

InstructionIdentification

EndToEndIdentification (optional)

LocalInstrument (optional)

RequestedExecutionDateTime

Date Date at which the initiating party requests the clearing agent to process the payment. Usage: 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: 2017-04-05T10:43:07+00:00 format: date-time

InstructedAmount

DebtorAccount (optional)

CreditorAccount

CreditorPostalAddress (optional)

RemittanceInformation (optional)

SupplementaryData (optional)

`OBDomesticStandingOrder2` - Up

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.

Frequency

String Individual Definitions: EvryDay - Every day EvryWorkgDay - Every working day IntrvlDay - An interval specified in number of calendar days (02 to 31) IntrvlWkDay - An interval specified in weeks (01 to 09), and the day within the week (01 to 07) WkInMnthDay - A monthly interval, specifying the week of the month (01 to 05) and day within the week (01 to 07) IntrvlMnthDay - An interval specified in months (between 01 to 06, 12, 24), specifying the day within the month (-5 to -1, 1 to 31) QtrDay - Quarterly (either ENGLISH, SCOTTISH, or RECEIVED). ENGLISH = Paid on the 25th March, 24th June, 29th September and 25th December. SCOTTISH = Paid on the 2nd February, 15th May, 1st August and 11th November. RECEIVED = Paid on the 20th March, 19th June, 24th September and 20th December. Individual Patterns: EvryDay (ScheduleCode) EvryWorkgDay (ScheduleCode) IntrvlDay:NoOfDay (ScheduleCode + NoOfDay) IntrvlWkDay:IntervalInWeeks:DayInWeek (ScheduleCode + IntervalInWeeks + DayInWeek) WkInMnthDay:WeekInMonth:DayInWeek (ScheduleCode + WeekInMonth + DayInWeek) IntrvlMnthDay:IntervalInMonths:DayInMonth (ScheduleCode + IntervalInMonths + DayInMonth) QtrDay: + either (ENGLISH, SCOTTISH or RECEIVED) ScheduleCode + QuarterDay The regular expression for this element combines five smaller versions for each permitted pattern. To aid legibility - the components are presented individually here: 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) Full Regular Expression: ^(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))$

Reference (optional)

String 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. 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.

NumberOfPayments (optional)

String Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.

FirstPaymentDateTime

Date 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. All date-time fields in responses must include the timezone. An example is below: 2017-04-05T10:43:07+00:00 format: date-time

RecurringPaymentDateTime (optional)

Date The date on which the first recurring payment for a Standing Order schedule will be made. Usage: 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. All date-time fields in responses must include the timezone. An example is below: 2017-04-05T10:43:07+00:00 format: date-time

FinalPaymentDateTime (optional)

Date 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. All date-time fields in responses must include the timezone. An example is below: 2017-04-05T10:43:07+00:00 format: date-time

FirstPaymentAmount

OBActiveCurrencyAndAmount_SimpleType The amount of the first Standing Order

RecurringPaymentAmount (optional)

OBActiveCurrencyAndAmount_SimpleType The amount of the recurring Standing Order

FinalPaymentAmount (optional)

OBActiveCurrencyAndAmount_SimpleType The amount of the final Standing Order

DebtorAccount (optional)

CreditorAccount

SupplementaryData (optional)

`OBError1` - Up

ErrorCode

String Low level textual error code, e.g., UK.OBIE.Field.Missing

Message

String A description of the error that occurred. e.g., 'A mandatory field isn't supplied' or 'RequestedExecutionDateTime must be in future' OBIE doesn't standardise this field

Path (optional)

String Recommended but optional reference to the JSON Path of the field with error, e.g., Data.Initiation.InstructedAmount.Currency

Url (optional)

String URL to help remediate the problem, or provide more information, or to API Reference, or help etc

`OBErrorResponse1` - Up

An array of detail error codes, and messages, and URLs to documentation to help remediation.

Code

String High level textual error code, to help categorize the errors.

Id (optional)

String A unique reference for the error instance, for audit purposes, in case of unknown/unclassified errors.

Message

String Brief Error message, e.g., 'There is something wrong with the request parameters provided'

Errors

array[OBError1]

`OBExchangeRate1` - Up

Provides details on the currency exchange rate and contract.

UnitCurrency

String Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.

ExchangeRate (optional)

BigDecimal 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.

RateType

OBExchangeRateType2Code

ContractIdentification (optional)

String Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party/creditor and the debtor agent.

`OBExchangeRate2` - Up

Further detailed information on the exchange rate that has been used in the payment transaction.

UnitCurrency

String Currency in which the rate of exchange is expressed in a currency exchange. In the example 1GBP = xxxCUR, the unit currency is GBP.

ExchangeRate

BigDecimal 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.

RateType

OBExchangeRateType2Code

ContractIdentification (optional)

String Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party/creditor and the debtor agent.

ExpirationDateTime (optional)

Date Specified date and time the exchange rate agreement will expire. 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: 2017-04-05T10:43:07+00:00 format: date-time

`OBExchangeRateType2Code` - Up

Specifies the type used to complete the currency exchange.

`OBExternalAccountIdentification4Code` - Up

Name of the identification scheme, in a coded form as published in an external list.

`OBExternalAuthorisation1Code` - Up

Type of authorisation flow requested.

`OBExternalConsentStatus1Code` - Up

Specifies the status of resource in code form.

`OBExternalConsentStatus2Code` - Up

Specifies the status of consent resource in code form.

`OBExternalFileType1Code` - Up

Specifies the payment file type.

`OBExternalFinancialInstitutionIdentification4Code` - Up

Name of the identification scheme, in a coded form as published in an external list.

`OBExternalLocalInstrument1Code` - Up

User community specific instrument. Usage: This element is used to specify a local instrument, local clearing option and/or further qualify the service or service level.

`OBExternalPaymentChargeType1Code` - Up

Charge type, in a coded form.

`OBExternalPaymentContext1Code` - Up

Specifies the payment context

`OBExternalPermissions2Code` - Up

Specifies the Open Banking service request types.

`OBExternalPurpose1Code1` - Up

Specifies the external purpose code in the format of character string with a maximum length of 4 characters. The list of valid codes is an external code list published separately. External code sets can be downloaded from www.iso20022.org.

`OBExternalStatus1Code` - Up

Specifies the status of resource in code form.

`OBExternalStatus2Code` - Up

Specifies the status of the authorisation flow in code form.

`OBFile2` - Up

The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds using a payment file.

FileType

OBExternalFileType1Code

FileHash

String A base64 encoding of a SHA256 hash of the file to be uploaded.

FileReference (optional)

String Reference for the file.

NumberOfTransactions (optional)

String Number of individual transactions contained in the payment information group.

ControlSum (optional)

BigDecimal Total of all individual amounts included in the group, irrespective of currencies.

RequestedExecutionDateTime (optional)

LocalInstrument (optional)

DebtorAccount (optional)

RemittanceInformation (optional)

SupplementaryData (optional)

`OBFundsAvailableResult1` - Up

Result of a funds availability check.

FundsAvailableDateTime

Date 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. All date-time fields in responses must include the timezone. An example is below: 2017-04-05T10:43:07+00:00 format: date-time

FundsAvailable

Boolean Flag to indicate the availability of funds given the Amount in the consent request.

`OBInternational2` - Up

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.

InstructionIdentification

EndToEndIdentification

LocalInstrument (optional)

InstructionPriority (optional)

OBPriority2Code

Purpose (optional)

OBExternalPurpose1Code1

ChargeBearer (optional)

CurrencyOfTransfer

String Specifies the currency of the to be transferred amount, which is different from the currency of the debtor's account.

InstructedAmount

ExchangeRateInformation (optional)

OBExchangeRate1

DebtorAccount (optional)

OBBranchAndFinancialInstitutionIdentification6

Creditor (optional)

OBPartyIdentification43

CreditorAgent (optional)

CreditorAccount

RemittanceInformation (optional)

SupplementaryData (optional)

`OBInternationalScheduled2` - Up

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.

InstructionIdentification

EndToEndIdentification (optional)

LocalInstrument (optional)

InstructionPriority (optional)

OBPriority2Code

Purpose (optional)

OBExternalPurpose1Code1

ChargeBearer (optional)

RequestedExecutionDateTime

CurrencyOfTransfer

String Specifies the currency of the to be transferred amount, which is different from the currency of the debtor's account.

InstructedAmount

ExchangeRateInformation (optional)

OBExchangeRate1

DebtorAccount (optional)

OBBranchAndFinancialInstitutionIdentification6

Creditor (optional)

OBPartyIdentification43

CreditorAgent (optional)

CreditorAccount

RemittanceInformation (optional)

SupplementaryData (optional)

`OBInternationalStandingOrder2` - Up

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.

Frequency

Reference (optional)

NumberOfPayments (optional)

String Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.

FirstPaymentDateTime

FinalPaymentDateTime (optional)

Purpose (optional)

OBExternalPurpose1Code1

ChargeBearer (optional)

CurrencyOfTransfer

String Specifies the currency of the to be transferred amount, which is different from the currency of the debtor's account.

InstructedAmount

DebtorAccount (optional)

OBBranchAndFinancialInstitutionIdentification6

Creditor (optional)

OBPartyIdentification43

CreditorAgent (optional)

CreditorAccount

SupplementaryData (optional)

`OBMultiAuthorisation1` - Up

The multiple authorisation flow response from the ASPSP.

Status

OBExternalStatus2Code

NumberRequired (optional)

Integer Number of authorisations required for payment order (total required at the start of the multi authorisation journey). format: int32

NumberReceived (optional)

Integer Number of authorisations required for payment order (total required at the start of the multi authorisation journey). format: int32

LastUpdateDateTime (optional)

Date Last date and time at the authorisation flow was updated. 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: 2017-04-05T10:43:07+00:00 format: date-time

ExpirationDateTime (optional)

`OBPartyIdentification43` - Up

Party to which an amount of money is due.

Name (optional)

String Name by which a party is known and which is usually used to identify that party.

PostalAddress (optional)

OBExternalPaymentContext1Code

`OBPostalAddress6` - Up

Information that locates and identifies a specific address, as defined by postal services.

AddressType (optional)

OBAddressTypeCode

Department (optional)

String Identification of a division of a large organisation or building.

SubDepartment (optional)

String Identification of a sub-division of a large organisation or building.

StreetName (optional)

String Name of a street or thoroughfare.

BuildingNumber (optional)

String Number that identifies the position of a building on a street.

PostCode (optional)

String Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.

TownName (optional)

String Name of a built-up area, with defined boundaries, and a local government.

CountrySubDivision (optional)

String Identifies a subdivision of a country such as state, region, county.

Country (optional)

String Nation with its own government.

AddressLine (optional)

OBPostalAddressLine

`OBPostalAddressLine` - Up

Information that locates and identifies a specific address, as defined postal services, presented in free format text.

`OBPriority2Code` - Up

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.

`OBRemittanceInformation1` - Up

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.

Unstructured (optional)

String 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.

Reference (optional)

`OBRisk1` - Up

The Risk section is sent by the initiating party to the ASPSP. It is used to specify additional details for risk scoring for Payments.

PaymentContextCode (optional)

MerchantCategoryCode (optional)

String Category code conform to ISO 18245, related to the type of services or goods the merchant provides for the transaction.

MerchantCustomerIdentification (optional)

String The unique customer identifier of the PSU with the merchant.

DeliveryAddress (optional)

OBDeliverAddress

`OBSupplementaryData1` - Up

Additional information that can not be captured in the structured fields and/or any other specific block.

`OBTransactionIndividualStatus1Code` - Up

Specifies the status of the payment information group.

`OBWriteDataDomestic2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

Initiation

`OBWriteDataDomesticConsent2` - Up

Initiation

Authorisation (optional)

`OBWriteDataDomesticConsentResponse2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Date Date and time at which the resource was created. 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: 2017-04-05T10:43:07+00:00 format: date-time

Status

StatusUpdateDateTime

Date Date and time at which the resource status was updated. 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: 2017-04-05T10:43:07+00:00 format: date-time

CutOffDateTime (optional)

Date Specified cut-off date and time for the payment consent. 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: 2017-04-05T10:43:07+00:00 format: date-time

ExpectedExecutionDateTime (optional)

Date Expected execution date and time for the payment resource. 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: 2017-04-05T10:43:07+00:00 format: date-time

ExpectedSettlementDateTime (optional)

Date Expected settlement date and time for the payment resource. 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: 2017-04-05T10:43:07+00:00 format: date-time

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

Authorisation (optional)

OBTransactionIndividualStatus1Code

`OBWriteDataDomesticResponse2` - Up

DomesticPaymentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the domestic payment resource.

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Date Date and time at which the message was created. 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: 2017-04-05T10:43:07+00:00 format: date-time

Status

StatusUpdateDateTime

ExpectedExecutionDateTime (optional)

ExpectedSettlementDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

MultiAuthorisation (optional)

`OBWriteDataDomesticScheduled2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

Initiation

`OBWriteDataDomesticScheduledConsent2` - Up

Permission

Initiation

Authorisation (optional)

`OBWriteDataDomesticScheduledConsentResponse2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

Date 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. All date-time fields in responses must include the timezone. An example is below: 2017-04-05T10:43:07+00:00 format: date-time

Permission

CutOffDateTime (optional)

ExpectedExecutionDateTime (optional)

ExpectedSettlementDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

Authorisation (optional)

`OBWriteDataDomesticScheduledResponse2` - Up

DomesticScheduledPaymentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the domestic schedule payment resource.

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

ExpectedExecutionDateTime (optional)

ExpectedSettlementDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

MultiAuthorisation (optional)

`OBWriteDataDomesticStandingOrder2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

Initiation

`OBWriteDataDomesticStandingOrderConsent2` - Up

Permission

Initiation

Authorisation (optional)

`OBWriteDataDomesticStandingOrderConsentResponse2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

Permission

CutOffDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

Authorisation (optional)

`OBWriteDataDomesticStandingOrderResponse2` - Up

DomesticStandingOrderId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the domestic standing order resource.

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

MultiAuthorisation (optional)

`OBWriteDataFile2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

Initiation

`OBWriteDataFileConsent2` - Up

Initiation

Authorisation (optional)

OBExternalConsentStatus2Code

`OBWriteDataFileConsentResponse2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

CutOffDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

Authorisation (optional)

`OBWriteDataFileResponse2` - Up

FilePaymentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the file payment resource.

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

MultiAuthorisation (optional)

`OBWriteDataFundsConfirmationResponse1` - Up

FundsAvailableResult (optional)

OBFundsAvailableResult1

SupplementaryData (optional)

`OBWriteDataInternational2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

Initiation

`OBWriteDataInternationalConsent2` - Up

Initiation

Authorisation (optional)

`OBWriteDataInternationalConsentResponse2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

CutOffDateTime (optional)

ExpectedExecutionDateTime (optional)

ExpectedSettlementDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

ExchangeRateInformation (optional)

Initiation

Authorisation (optional)

OBTransactionIndividualStatus1Code

`OBWriteDataInternationalResponse2` - Up

InternationalPaymentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the international payment resource.

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

ExpectedExecutionDateTime (optional)

ExpectedSettlementDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

ExchangeRateInformation (optional)

Initiation

MultiAuthorisation (optional)

`OBWriteDataInternationalScheduled2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

Initiation

`OBWriteDataInternationalScheduledConsent2` - Up

Permission

Initiation

Authorisation (optional)

`OBWriteDataInternationalScheduledConsentResponse2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

Permission

CutOffDateTime (optional)

ExpectedExecutionDateTime (optional)

ExpectedSettlementDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

ExchangeRateInformation (optional)

Initiation

Authorisation (optional)

`OBWriteDataInternationalScheduledResponse2` - Up

InternationalScheduledPaymentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the international scheduled payment resource.

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

ExpectedExecutionDateTime (optional)

ExpectedSettlementDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

ExchangeRateInformation (optional)

Initiation

MultiAuthorisation (optional)

`OBWriteDataInternationalStandingOrder2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

Initiation

`OBWriteDataInternationalStandingOrderConsent2` - Up

Permission

Initiation

Authorisation (optional)

`OBWriteDataInternationalStandingOrderConsentResponse2` - Up

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

Permission

CutOffDateTime (optional)

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

Authorisation (optional)

`OBWriteDataInternationalStandingOrderResponse2` - Up

InternationalStandingOrderId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the international standing order resource.

ConsentId

String OB: Unique identification as assigned by the ASPSP to uniquely identify the consent resource.

CreationDateTime

Status

StatusUpdateDateTime

Charges (optional)

array[OBCharge2] Set of elements used to provide details of a charge for the payment initiation.

Initiation

MultiAuthorisation (optional)

`OBWriteDomestic2` - Up

Data

OBWriteDataDomestic2

Risk

OBWriteDataDomesticConsent2

`OBWriteDomesticConsent2` - Up

Data

Risk

OBWriteDataDomesticConsentResponse2

`OBWriteDomesticConsentResponse2` - Up

Data

Risk

OBWriteDataDomesticResponse2

Links

Meta

`OBWriteDomesticResponse2` - Up

Data

Links

Meta

`OBWriteDomesticScheduled2` - Up

Data

OBWriteDataDomesticScheduled2

Risk

OBWriteDataDomesticScheduledConsent2

`OBWriteDomesticScheduledConsent2` - Up

Data

Risk

OBWriteDataDomesticScheduledConsentResponse2

`OBWriteDomesticScheduledConsentResponse2` - Up

Data

Risk

OBWriteDataDomesticScheduledResponse2

Links

Meta

`OBWriteDomesticScheduledResponse2` - Up

Data

Links

Meta

`OBWriteDomesticStandingOrder2` - Up

Data

OBWriteDataDomesticStandingOrder2

Risk

OBWriteDataDomesticStandingOrderConsent2

`OBWriteDomesticStandingOrderConsent2` - Up

Data

Risk

OBWriteDataDomesticStandingOrderConsentResponse2

`OBWriteDomesticStandingOrderConsentResponse2` - Up

Data

Risk

OBWriteDataDomesticStandingOrderResponse2

Links

Meta

`OBWriteDomesticStandingOrderResponse2` - Up

Data

Links

Meta

Links

Meta

`OBWriteFileResponse2` - Up

Data

OBWriteDataFileResponse2

Links

Meta

`OBWriteFundsConfirmationResponse1` - Up

Data

OBWriteDataFundsConfirmationResponse1

Links

Meta

`OBWriteInternational2` - Up

Data

OBWriteDataInternational2

Risk

OBWriteDataInternationalConsent2

`OBWriteInternationalConsent2` - Up

Data

Risk

OBWriteDataInternationalConsentResponse2

`OBWriteInternationalConsentResponse2` - Up

Data

Risk

OBWriteDataInternationalResponse2

Links

Meta

`OBWriteInternationalResponse2` - Up

Data

Links

Meta

`OBWriteInternationalScheduled2` - Up

Data

OBWriteDataInternationalScheduled2

Risk

OBWriteDataInternationalScheduledConsent2

`OBWriteInternationalScheduledConsent2` - Up

Data

Risk

OBWriteDataInternationalScheduledConsentResponse2

`OBWriteInternationalScheduledConsentResponse2` - Up

Data

Risk

OBWriteDataInternationalScheduledResponse2

Links

Meta

`OBWriteInternationalScheduledResponse2` - Up

Data

Links

Meta

`OBWriteInternationalStandingOrder2` - Up

Data

OBWriteDataInternationalStandingOrder2

Risk

OBWriteDataInternationalStandingOrderConsent2

`OBWriteInternationalStandingOrderConsent2` - Up

Data

Risk

OBWriteDataInternationalStandingOrderConsentResponse2

`OBWriteInternationalStandingOrderConsentResponse2` - Up

Data

Risk