Merge pull request #139 from monzo/obie-v3.1.5

OBIE v3.1.5 Upgrade

Author: henryrowett

source/includes/_ais.md

@@ -22,6 +22,7 @@ Production | `https://api.monzo.com/open-banking/.well-known/openid-configuratio
 
 We've included the Base URLs for our Sandbox and Production environments below.
 
+
 ##### Base URLs
 
 <span class="hide">Environment</span> | <span class="hide">Base URL</span>
@@ -80,7 +81,7 @@ We only support the `tls_client_auth` authentication method.
 }
 ```
 
-We've implemented version 3.1.4 of the [Open Banking accounts specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/accounts.html).
+We've implemented version 3.1.5 of the [Open Banking accounts specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/Accounts.html).
 
 Once you have a consent for a customer, you'll be able to see their:
 
@@ -99,7 +100,7 @@ or `ReadAccountsDetail` permission. In the former case, we will omit the account
 
 ## Balances
 
-We've implemented version 3.1.4 of the [Open Banking balances specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/balances.html).
+We've implemented version 3.1.5 of the [Open Banking balances specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/Balances.html).
 
 When you query this endpoint, you'll see the customer's `InterimAvailable` balance. This is the same real-time balance 
 that our customers see in the Monzo app, and it includes pending and settled transactions.
@@ -133,7 +134,8 @@ that our customers see in the Monzo app, and it includes pending and settled tra
         "SupplementaryData": {
           "Declined": false,
           "RawTransactionDescription": "MR PAYROLL SERVICE"
-        }
+        },
+        "TransactionMutability": "Mutable"
       }
     ]
   },
@@ -144,7 +146,7 @@ that our customers see in the Monzo app, and it includes pending and settled tra
 }
 ```
 
-We've implemented version 3.1.4 of the [Open Banking transactions specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/transactions.html).
+We've implemented version 3.1.5 of the [Open Banking transactions specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/Transactions.html).
 
 For consistency with our internal systems and the rest of our API, you will need to provide the start and end times in 
 [**RFC3339 format**](https://www.ietf.org/rfc/rfc3339.txt).
@@ -162,9 +164,12 @@ identify transactions that are still pending.
 You'll only be allowed to fetch transactions that were made in the range defined by `TransactionFromDateTime` and 
 `TransactionToDateTime` in your consent. If you try to access transactions outside this range, it won't work.
 
+`TransactionMutability` was added in version 3.1.5 of the [Open Banking transactions specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/Transactions.html). 
+This field will always be set to `Mutable` because Merchant data and foreign exchange rate between authorisation and presentment for a card payment may vary between fetches.
+
 ## Parties
 
-We've implemented version 3.1.4. of the [Open Banking parties specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/parties.html)
+We've implemented version 3.1.5. of the [Open Banking parties specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/Parties.html)
 
 We have implemented the `GET /party` and `GET /accounts/{accountId}/party` endpoints for reading details of the consent authoriser and `GET /accounts/{accountId}/parties` for reading the details of all account holders/owners. These endpoints return the IDs, preferred names, and legal names of account holders/owners.
 
@@ -267,7 +272,7 @@ any more.
 
 ## Direct Debits
 
-We've implemented version 3.1.4 of the [Open Banking Direct Debits specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/direct-debits.html).
+We've implemented version 3.1.5 of the [Open Banking Direct Debits specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/direct-debits.html).
 
 We have only implemented `GET /accounts/{AccountId}/direct-debits` endpoint.
 
@@ -281,7 +286,7 @@ access Direct Debits that were collected within the last 90 days.
 
 ## Scheduled Payments
 
-We've implemented version 3.1.4 of the [Open Banking Scheduled Payments specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/scheduled-payments.html).
+We've implemented version 3.1.5 of the [Open Banking Scheduled Payments specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/scheduled-payments.html).
 
 We have only implemented `GET /accounts/{AccountId}/scheduled-payments` endpoint.
 
@@ -295,7 +300,7 @@ You can access all scheduled payments as long as the customer has completed Stro
 
 ## Standing Orders
 
-We've implemented version 3.1.4 of the [Open Banking Standing Orders specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/standing-orders.html).
+We've implemented version 3.1.5 of the [Open Banking Standing Orders specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/standing-orders.html).
 
 We have only implemented `GET /accounts/{AccountId}/standing-orders` endpoint.
 

source/includes/_cbpii.md

@@ -40,7 +40,7 @@ redirect flow, with authentication taking place in the customer's Monzo app.
 We only support the `tls_client_auth` authentication method.
 
 ## Confirmation of Funds
-We have implemented version 3.1.4 of the [Open Banking Confirmation of Funds Specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/profiles/confirmation-of-funds-api-profile.html).
+We have implemented version 3.1.5 of the [Open Banking Confirmation of Funds Specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/profiles/confirmation-of-funds-api-profile.html).
 
 We use the **redirection flow** for approving consents.
 

source/includes/_pis.md

@@ -46,7 +46,7 @@ have one hour.
 
 ## Domestic Payments
 
-We've implemented version 3.1.4 of the [Open Banking Domestic Payments specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/pisp/domestic-payments.html).
+We've implemented version 3.1.5 of the [Open Banking Domestic Payments specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/pisp/domestic-payments.html).
 
 When you request a consent for Domestic Payments, you should provide `UK.OBIE.FPS` as the `LocalInstrument`.
 
@@ -57,7 +57,7 @@ You can only make payments in `GBP`. We don't support other currencies.
 
 ## Scheduled Payments
 
-We've implemented version 3.1.4 of the [Open Banking Scheduled Payments specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/scheduled-payments.html).
+We've implemented version 3.1.5 of the [Open Banking Scheduled Payments specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/scheduled-payments.html).
 
 For consistency with our internal systems and the rest of our API, you will need to provide times in **RFC3339 format.**
 
@@ -76,7 +76,7 @@ All of our scheduled payments are sent in the early hours of the morning on the
 
 ## Standing Orders
 
-We have implemented version 3.1.4 of the [Open Banking Standing Order specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.4/resources-and-data-models/aisp/standing-orders.html).
+We have implemented version 3.1.5 of the [Open Banking Standing Order specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/resources-and-data-models/aisp/standing-orders.html).
 
 For consistency with our internal systems and the rest of our API, you will need to provide times in **RFC3339 format.**
 
@@ -142,6 +142,9 @@ The refund account data will be returned in the payment order creation response.
         "Identification": "12345612345678",
         "Name": "First Last"
       }
+    },
+    "Debtor": {
+      "Name": "First Last"
     }
   },
   "Links": {