Versions Compared

Key

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

Contents

Table of Contents
outlinetrue

Version Control


Version
Date
Author
Comments
1.0.001 March 2019Payments NZ API Working Group
Transactions specifications
Baseline specification for Scheduled Payments Resource


Endpoints

Endpoints for the resource - and available methods.


ResourceHTTP OperationEndpointMandatory?ScopeGrant TypeIdempotentParametersRequest ObjectResponse Object
1scheduled-paymentsGETGET /accounts/{AccountId}/scheduled-paymentsOptionalaccountsAuthorization Code



OBReadScheduledPayment1
2scheduled-paymentsGETGET /scheduled-paymentsOptionalaccountsAuthorization Code

Pagination


OBReadScheduledPayment1

GET /accounts/{AccountId}/scheduled-payments

An API Provider may provide this endpoint for Third Parties to retrieve the scheduled-payments for a specific AccountId (which is retrieved in the call to GET /accounts).

GET /scheduled-payments

If an API Provider has implemented the bulk retrieval endpoints - a Third Party may optionally retrieve the scheduled-payments resources in bulk.

This will retrieve the scheduled-payments resources for all authorised accounts linked to the account-request.

Data Model

Resource Definition

A resource that contains a set of elements that describes the scheduled payments that have been set up on a specific account (AccountId). A scheduled payment is a single one-off payment scheduled for a future date.

An account (AccountId) may have no scheduled payments set up, or may have multiple scheduled payments set up.

UML Diagram

Notes:

  • The Account and CreditorAccount blocks replicate what is used consistently throughout the Account Information APIs to identify an account. 
  • For the /accounts/{AccountId}/scheduled-payments endpoint - the Account and CreditorAccount blocks represent the account that is receiving funds (so has been named the CreditorAccount - for consistency with the PISP use case).
  • A DateTime element has been used - so that there is consistency across all API endpoints using dates. Where time elements do not exist in API Provider systems - the time portion of the DateTime element will be defaulted to 00:00:00+00:00
  • The Amount elements all have embedded Currency elements - for consistency is ISO 20022, and across the other API endpoints

Permission Codes

The resource differs depending on the permissions (ReadScheduledPaymentsBasic and ReadScheduledPaymentsDetail) used to access resource. In the event the resource is accessed with both ReadScheduledPaymentsBasic and ReadScheduledPaymentsDetail, the most detailed level (ReadScheduledPaymentsDetail) must be used.

  • These objects must not be returned without the ReadScheduledPaymentsDetail permission:
    • OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAgent
    • OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAccount
  • If the ReadScheduledPaymentsDetail is granted by the PSU:
    • OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAgent may be returned if applicable to the account and API Provider (0..1)
    • OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAccount must be returned (1..1)

Data Dictionary

NameOccurrenceXPathEnhancedDefinitionClassCodesPattern
OBReadScheduledPayment1
OBReadScheduledPayment1
OBReadScheduledPayment1

Data1..1OBReadScheduledPayment1/Data
OBReadDataScheduledPayment1

ScheduledPayment0..nOBReadScheduledPayment1/Data/ScheduledPayment
OBScheduledPayment1

AccountId1..1OBReadScheduledPayment1/Data/ScheduledPayment/AccountIdA unique and immutable identifier used to identify the account resource. This identifier has no meaning to the account owner.Max40Text

ScheduledPaymentId0..1OBReadScheduledPayment1/Data/ScheduledPayment/ScheduledPaymentIdA unique and immutable identifier used to identify the scheduled payment resource. This identifier has no meaning to the account owner.Max40Text

ScheduledPaymentDateTime1..1OBReadScheduledPayment1/Data/ScheduledPayment/ScheduledPaymentDateTimeThe date on which the scheduled payment will be made.ISODateTime

ScheduledType1..1OBReadScheduledPayment1/Data/ScheduledPayment/ScheduledTypeSpecifies the scheduled payment date type requestedOBExternalScheduleType1CodeArrival
Execution

InstructedAmount1..1OBReadScheduledPayment1/Data/ScheduledPayment/InstructedAmountAmount 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.
OBActiveOrHistoricCurrencyAndAmount

Amount1..1OBReadScheduledPayment1/Data/ScheduledPayment/InstructedAmount/AmountA number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217.ActiveCurrencyAndAmount_SimpleType
^\d{1,13}\.\d{1,5}$
Currency1..1OBReadScheduledPayment1/Data/ScheduledPayment/InstructedAmount/CurrencyA 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".ActiveOrHistoricCurrencyCode
^[A-Z]{3,3}$
Reference0..1OBReadScheduledPayment1/Data/ScheduledPayment/ReferenceRemittance information for use with BECSElectronicCredit payment scheme.NZBECSRemittance1

CreditorName1..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/CreditorNameThe Creditor's Name.Max20Text

DebtorName0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/DebtorNameThe Debtor's Name.Max20Text

CreditorReference0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/CreditorReferenceInformation supplied to enable the reconciling of the payment with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system.NZBECSReference1

Particulars0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/CreditorReference/ParticularsReference information, as assigned by the debtor, which when combined with Code and Reference, unambiguously refer to the payment transaction.Max12Text

Code0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/CreditorReference/CodeReference information, as assigned by the debtor, which when combined with Particulars and Reference, unambiguously refer to the payment transaction.Max12Text

Reference0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/CreditorReference/ReferenceReference information, as assigned by the debtor, which when combined with Particulars and Code, unambiguously refer to the payment transaction.Max12Text

DebtorReference0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/DebtorReferenceInformation supplied to enable the reconciling of the payment with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system.NZBECSReference1

Particulars0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/DebtorReference/ParticularsReference information, as assigned by the debtor, which when combined with Code and Reference, unambiguously refer to the payment transaction.Max12Text

Code0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/DebtorReference/CodeReference information, as assigned by the debtor, which when combined with Particulars and Reference, unambiguously refer to the payment transaction.Max12Text

Reference0..1OBReadScheduledPayment1/Data/ScheduledPayment/Reference/DebtorReference/ReferenceReference information, as assigned by the debtor, which when combined with Particulars and Code, unambiguously refer to the payment transaction.Max12Text

CreditorAgent0..1OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAgentParty 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.
This is the servicer of the beneficiary account.
OBBranchAndFinancialInstitutionIdentification2

SchemeName1..1OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAgent/SchemeNameName of the identification scheme, in a coded form as published in an external list.OBExternalFinancialInstitutionIdentification2CodeBICFI
Identification1..1OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAgent/IdentificationUnique and unambiguous identification of the servicing institution.Max35Text

CreditorAccount0..1OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAccountProvides the details to identify the beneficiary account.OBCashAccount1

SchemeName1..1OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAccount/SchemeNameName of the identification scheme, in a coded form as published in an external list.OBExternalAccountIdentification2CodeBECSElectronicCredit
Identification1..1OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAccount/IdentificationBeneficiary account identification.Max34Text

Name0..1OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAccount/NameName of the account, as assigned by the account servicing institution, in agreement with the account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in certain user communities to provide a means of identifying the account, in addition to the account owner's identity and the account number.
Max70Text

SecondaryIdentification0..1OBReadScheduledPayment1/Data/ScheduledPayment/CreditorAccount/SecondaryIdentificationThis 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).
Max34Text

Enumerations

This section gives the definitions for enumerations used.

Code ClassName Definition 
OBExternalAccountIdentification2CodeBECSElectronicCreditBECS Electronic Credit - identifier scheme used in  NZ by financial institutions to identify the account of a customer. The identifier is bank-branch-account-suffix.
The regular expression for this identifier is: ^[0-9]{2}-[0-9]{4}-[0-9]{7}-[0-9]{2}$
OBExternalFinancialInstitutionIdentification2CodeBICFIValid BICs for financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory, and consist of eight (8) or eleven (11) contiguous characters.
OBExternalScheduleType1CodeExecutionScheduled payment date is specified as the execution date.
OBExternalScheduleType1CodeArrivalScheduled payment date is specified as the arrival date for the recipient.

Usage Examples

Specific Account

Request 

Code Block
languagejs
themeMidnight
titleGet Account Specific Scheduled Payments Request
linenumberstrue
GET /accounts/22289/scheduled-payments HTTP/1.1
Authorization: Bearer Az90SAOJklae
x-fapi-financial-id: OB/2017/001
x-fapi-customer-last-logged-time:  Sun, 10 Sep 2017 19:43:31 UTC
x-fapi-customer-ip-address: 104.25.212.99
x-fapi-interaction-id: 93bac548-d2de-4546-b106-880a5018460d
Accept: application/json



Response

Code Block
languagejs
themeMidnight
titleGet Accounts Specific Scheduled Payments Response
linenumberstrue
HTTP/1.1 200 OK
x-fapi-interaction-id: 93bac548-d2de-4546-b106-880a5018460d
Content-Type: application/json

{
  "Data": {
    "ScheduledPayment": [
      {
        "AccountId": "22289",
        "ScheduledPaymentId": "SP03",
        "ScheduledPaymentDateTime": "2017-05-05T00:00:00+00:00",
        "ScheduledType": "Execution",
        "InstructedAmount": {
          "Amount": "10.00",
          "Currency": "NZD"
        },
        "CreditorAccount": {
          "SchemeName": "BECSElectronicCredit",
          "Identification": "01-0101-0123456-00",
          "Name": "Mr Tee"
        }
      }
    ]
  },
  "Links": {
    "Self": "https://api.examplebank.co.nz/open-banking-nz/v1.0/accounts/22289/scheduled-payments/"
  },
  "Meta": {
    "TotalPages": 1
  }
}


Bulk

Request

Code Block
languagejs
themeMidnight
titleGet Bulk Scheduled Payments Request
linenumberstrue
GET /scheduled-payments HTTP/1.1
Authorization: Bearer Az90SAOJklae
x-fapi-financial-id: OB/2017/001
x-fapi-customer-last-logged-time:  Sun, 10 Sep 2017 19:43:31 UTC
x-fapi-customer-ip-address: 104.25.212.99
x-fapi-interaction-id: 93bac548-d2de-4546-b106-880a5018460d
Accept: application/json


Response

Code Block
languagejs
themeMidnight
titleGet Bulk Scheduled Payments Response
linenumberstrue
HTTP/1.1 200 OK
x-fapi-interaction-id: 93bac548-d2de-4546-b106-880a5018460d
Content-Type: application/json

{
  "Data": {
    "ScheduledPayment": [
      { 
		"AccountId": "22289",
        "ScheduledPaymentId": "SP03",
        "ScheduledPaymentDateTime": "2017-05-05T00:00:00+00:00",
        "ScheduledType": "Execution",
        "InstructedAmount": {
          "Amount": "10.00",
          "Currency": "NZD"
        },
        "CreditorAccount": {
          "SchemeName": "BECSElectronicCredit",
          "Identification": "01-0101-0123456-00",
          "Name": "Mr Tee"
        }
      },
      {
        "AccountId": "39570",
        "ScheduledPaymentId": "SP77",
        "ScheduledPaymentDateTime": "2017-04-05T00:00:00+00:00",
        "ScheduledType": "Execution",
        "InstructedAmount": {
          "Amount": "12.00",
          "Currency": "NZD"
        },
        "CreditorAccount": {
          "SchemeName": "BECSElectronicCredit",
          "Identification": "01-0101-0123456-00",
          "Name": "Mr Tee"
        }
      }
    ]
  },
  "Links": {
    "Self": "https://api.examplebank.co.nz/open-banking-nz/v1.0/scheduled-payments/"
  },
  "Meta": {
    "TotalPages": 1
  }
}