diff --git a/docs/api_reference.md b/docs/api_reference.md index 3ca1905..4b5f894 100644 --- a/docs/api_reference.md +++ b/docs/api_reference.md @@ -49,7 +49,7 @@ POST api/v1/merchants/{merchantId}/invoices | |`TotalVATAmount` |`decimal` |Total VAT amount of article. Decimals separated with a dot. | | |`TotalPriceIncludingVat` |`decimal` |Total price of article including VAT. | | |`Unit` |`string` |Unit, e.g. Pcs, Coli. | -| |`Quantity` |`decimal` |Quantity of article. Allowed to have more than two decimal digits. | +| |`Quantity` |`decimal` |Quantity of article. Allowed to have up to ten decimal digits. | |   |`PricePerUnit`            |`decimal` |Price per unit. Allowed to have more than two decimal digits. | | |`PriceReduction` |`decimal` |Price reduction. | | |`PriceDiscount` |`decimal` |Price discount. | @@ -237,7 +237,7 @@ POST api/v1/merchants/{merchantId}/invoices/link | |`TotalVATAmount` |`decimal` |Total VAT amount of article. Decimals separated with a dot. | | |`TotalPriceIncludingVat` |`decimal` |Total price of article including VAT. | | |`Unit` |`string` |Unit, e.g. Pcs, Coli. | -| |`Quantity` |`decimal` |Quantity of article. Allowed to have more than two decimal digits. | +| |`Quantity` |`decimal` |Quantity of article. Allowed to have up to ten decimal digits. | |   |`PricePerUnit`            |`decimal` |Price per unit. Allowed to have more than two decimal digits. | | |`PriceReduction` |`decimal` |Price reduction. | | |`PriceDiscount` |`decimal` |Price discount. | diff --git a/docs/release_notes_1.4.md b/docs/release_notes_1.4.md index b271ea2..eb2f85b 100644 --- a/docs/release_notes_1.4.md +++ b/docs/release_notes_1.4.md @@ -3,40 +3,40 @@ layout: default --- ## Invoice 1.4 Release Notes -### 28 july 2020 - PaymentReference +### 28 July 2020 - PaymentReference Due to restrictions in external systems we added recommendation to keep `PaymentReference` up to 30 symbols for [direct invoice](api_reference#single-invoice-request) and [invoice link](api_reference#invoice-link-request) requests. -### 26 june 2020 - User consent for InvoiceDirect released in Sandbox +### 26 June 2020 - User consent for InvoiceDirect released in Sandbox New feature: User consent for InvoiceDirect. Read more about user consent for InvoiceDirect [here](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#direct-invoice-consent) Goal of this functionality is for invoice issuer to ask users phone number and consent to receive Invoices directly to MobilePay (InvoiceDirect). Current release is just in Sandbox. Release in Production is planned for beginning of August. App version from which functionality can work for users - 4.24.0 (July). -### 23 april 2020 - ConsumerName and ConsumerAddressLines now optional +### 23 April 2020 - ConsumerName and ConsumerAddressLines now optional Removed **Required** validation for `ConsumerName` and `ConsumerAddressLines` -### 17 february 2020 - Increased max number of invoices to one user +### 17 February 2020 - Increased max number of invoices to one user Increased the max number of invoices per day merchants can send to one user. Now merchants can send up to 10 invoices to one user. -### 17 february 2020 - Removed Merchant daily Invoice limit +### 17 February 2020 - Removed Merchant daily Invoice limit Daily invoice Limit for merchants was removed. -### 16 january 2020 - Increased Invoice FI amount +### 16 January 2020 - Increased Invoice FI amount Invoice FI Amount validation was increased to 2000 EUR -### 08 november 2019 - Removed consumer name validation +### 08 November 2019 - Removed consumer name validation ConsumerName validation (Levenshtein rule) was removed from InvoiceDirect validation rules. However, it is still used for displaying ConsumerName when generating invoice PDF. -### 06 august 2019 - Response Code +### 06 August 2019 - Response Code The response codes for invoices have been unified. Batch requests now return 202 , all others should now return 200 If your system logic examines the concrete response code and checks strict the status code, you may have to change the logic in order to cope with the change in response code. We do not consider this a breaking chance, as most merchants only check if the call was a success such as 2xx, and do not depend on a concrete status code. However, having the right HTTP status codes mapped also enables you to get more insight around the response received. -### 01 april 2019 - decimals +### 01 April 2019 - decimals TotalVATAmount can not have more than two decimals. -### 01 march 2019 - QR code +### 01 March 2019 - QR code New feature: Scanning QR code with InvoiceLink will open MobilePay Invoice diff --git a/docs/release_notes_1.5.md b/docs/release_notes_1.5.md index 328beab..5d95efd 100644 --- a/docs/release_notes_1.5.md +++ b/docs/release_notes_1.5.md @@ -4,31 +4,34 @@ layout: default ## Invoice 1.5 Release Notes -### 08 august 2022 - Callback intervals +### 21 October 2022 - Invoice article Quantity decimal digits change +Invoice article Quantity field will now support up to 10 decimal digits, for example "0.0012345678". + +### 08 August 2022 - Callback intervals We reduced intervals between callback batches from 30 to 5 seconds. -### 17 may 2022 - Redirect url for accepting and paying invoice link +### 17 May 2022 - Redirect url for accepting and paying invoice link [Invoice link](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#link) now has an optional "RedirectUrl" property. It can be set when creating single or multiple Invoice links. User will be redirected to provided url after accepting invoice link payment for the future, or paying for it instantly. Redirect will happen with appropriate query parameters, i.e. if provided RedirectUrl value is "https://ProvidedUrl.com/" in case of accepted payment user will be redirected to "https://ProvidedUrl.com/?status=accepted" and in case of instant payment user will be redirected to "https://ProvidedUrl.com/?status=paid". This feature supports both webUrls and deeplinks. If RedirectUrl property is not provided, everything will work as it did before. -### 24 march 2022 - Quantity no longer required when creating invoice +### 24 March 2022 - Quantity no longer required when creating invoice Article quantity is not required when creating invoice direct or invoice link. -### 08 march 2022 - Country code and Currency code are not required when creating invoice direct or invoice link +### 08 March 2022 - Country code and Currency code are not required when creating invoice direct or invoice link If these parameters are passed with requrest, they will be ignored. Right now we automatically assign merchant's country and currency codes to invoice or invoice link. -### 05 january 2022 - Added PaymentReference field to GET invoice details response +### 05 January 2022 - Added PaymentReference field to GET invoice details response [Invoice details](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#get-details) GET response now has PaymentReference field. -### 16 december 2021 - Added GrantedOn field to Invoice Direct user consent GET response +### 16 December 2021 - Added GrantedOn field to Invoice Direct user consent GET response [InvoiceDirect user consent](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#direct-invoice-consent) GET response now has GrantedOn field that shows exact time when the consent was granted. -### 10 november 2021 - Invoicing has become more flexible. These fields are optional: +### 10 November 2021 - Invoicing has become more flexible. These fields are optional: