Skip to content

Invoice Article Quantity decimal digits updated to 10 #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
stasys123 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Invoice Article Quantity decimal digits updated to 10 #104

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/api_reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. |
Expand Down Expand Up @@ -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. |
Expand Down
20 changes: 10 additions & 10 deletions docs/release_notes_1.4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,40 +3,40 @@ layout: default
---

## Invoice 1.4 Release Notes
### <a name="response_code"></a> 28 july 2020 - PaymentReference
### <a name="response_code"></a> 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.

### <a name="response_code"></a> 26 june 2020 - User consent for InvoiceDirect released in Sandbox
### <a name="response_code"></a> 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).

### <a name="response_code"></a> 23 april 2020 - ConsumerName and ConsumerAddressLines now optional
### <a name="response_code"></a> 23 April 2020 - ConsumerName and ConsumerAddressLines now optional
Removed **Required** validation for `ConsumerName` and `ConsumerAddressLines`

### <a name="response_code"></a> 17 february 2020 - Increased max number of invoices to one user
### <a name="response_code"></a> 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.

### <a name="response_code"></a> 17 february 2020 - Removed Merchant daily Invoice limit
### <a name="response_code"></a> 17 February 2020 - Removed Merchant daily Invoice limit
Daily invoice <code>Limit</code> for merchants was removed.

### <a name="response_code"></a> 16 january 2020 - Increased Invoice FI amount
### <a name="response_code"></a> 16 January 2020 - Increased Invoice FI amount
Invoice FI <code>Amount</code> validation was increased to 2000 EUR

### <a name="response_code"></a> 08 november 2019 - Removed consumer name validation
### <a name="response_code"></a> 08 November 2019 - Removed consumer name validation
<code>ConsumerName</code> validation (Levenshtein rule) was removed from InvoiceDirect validation rules.
However, it is still used for displaying <code>ConsumerName</code> when generating invoice PDF.


### <a name="response_code"></a> 06 august 2019 - Response Code
### <a name="response_code"></a> 06 August 2019 - Response Code
The response codes for invoices have been unified. Batch requests now return <code>202</code> , all others should now return <code>200</code>
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.

### <a name="decimals"></a> 01 april 2019 - decimals
### <a name="decimals"></a> 01 April 2019 - decimals
<code>TotalVATAmount</code> can not have more than two decimals.


### <a name="response_code"></a> 01 march 2019 - QR code
### <a name="response_code"></a> 01 March 2019 - QR code

New feature: Scanning QR code with InvoiceLink will open MobilePay Invoice

Expand Down
33 changes: 18 additions & 15 deletions docs/release_notes_1.5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,31 +4,34 @@ layout: default

## Invoice 1.5 Release Notes

### <a name="response_code"></a> 08 august 2022 - Callback intervals
### <a name="response_code"></a> 21 October 2022 - Invoice article <code>Quantity</code> decimal digits change
Invoice article <code>Quantity</code> field will now support up to 10 decimal digits, for example "0.0012345678".

### <a name="response_code"></a> 08 August 2022 - Callback intervals

We reduced intervals between callback batches from 30 to 5 seconds.

### <a name="response_code"></a> 17 may 2022 - Redirect url for accepting and paying invoice link
### <a name="response_code"></a> 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<span>://ProvidedUrl.com/</span>" in case of accepted payment user will be redirected to "https<span>://ProvidedUrl.com/?status=accepted</span>" and in case of instant payment user will be redirected to "https<span>://ProvidedUrl.com/?status=paid</span>". This feature supports both webUrls and deeplinks. If RedirectUrl property is not provided, everything will work as it did before.

### <a name="response_code"></a> 24 march 2022 - Quantity no longer required when creating invoice
### <a name="response_code"></a> 24 March 2022 - Quantity no longer required when creating invoice

Article quantity is not required when creating invoice direct or invoice link.

### <a name="response_code"></a> 08 march 2022 - Country code and Currency code are not required when creating invoice direct or invoice link
### <a name="response_code"></a> 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.

### <a name="response_code"></a> 05 january 2022 - Added PaymentReference field to GET invoice details response
### <a name="response_code"></a> 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.

### <a name="response_code"></a> 16 december 2021 - Added GrantedOn field to Invoice Direct user consent GET response
### <a name="response_code"></a> 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.

### <a name="response_code"></a> 10 november 2021 - Invoicing has become more flexible. These fields are optional:
### <a name="response_code"></a> 10 November 2021 - Invoicing has become more flexible. These fields are optional:

<ul>
<li><code>TotalVatAmount</code></li>
Expand All @@ -50,36 +53,36 @@ Also only either <code>InvoiceNumber</code> or <code>PaymentReference</code> mus

More information in [InvoiceDirect](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#direct) and [InvoiceLink](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#link).

### <a name="response_code"></a> 6 may 2021 - Added Sequence number to the callbacks
### <a name="response_code"></a> 6 May 2021 - Added Sequence number to the callbacks

[Sequence](callbacks#sequence_note) number can be used to determine the real order of the invoice events.

### <a name="response_code"></a> 1 april 2021 - Invoice link is deleted after expiration
### <a name="response_code"></a> 1 April 2021 - Invoice link is deleted after expiration

Invoice link data is deleted once it expires.

### <a name="response_code"></a> 26 january 2021 - Visual design of Invoice PDF changed.
### <a name="response_code"></a> 26 January 2021 - Visual design of Invoice PDF changed.

More information in [Visual examples](https://mobilepaydev.github.io/MobilePay-Invoice/visual_examples)

### <a name="response_code"></a> 20 january 2021 - Grant/Reject consent endpoint in UserSimulation API
### <a name="response_code"></a> 20 January 2021 - Grant/Reject consent endpoint in UserSimulation API

You can now test [InvoiceDirect user consent](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#direct-invoice-consent) functionality in [sandbox](https://sandbox-developer.mobilepay.dk/)

Endpoint was added that can be used to imitate user granting or rejecting consent.

### <a name="response_code"></a> 17 september 2020 - Sms notification time updates, for when future payment can't be processed
### <a name="response_code"></a> 17 September 2020 - Sms notification time updates, for when future payment can't be processed

[Sms notification](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#validations) time is updated from 10:00 UTC to 07:00 UTC (09:00 DK time or 10:00 FI time)

### <a name="response_code"></a> 03 september 2020 - Sms notification sending updates, for when future payment can't be processed
### <a name="response_code"></a> 03 September 2020 - Sms notification sending updates, for when future payment can't be processed

[Sms notification](https://mobilepaydev.github.io/MobilePay-Invoice/api_reference#validations) to user is sent at 10:00, after two attempts to make payment. If user completes payment manually after second attempt, but before he gets the notification, sms is not sent.

### <a name="response_code"></a> 10 august 2020 - User consent for InvoiceDirect released
### <a name="response_code"></a> 10 August 2020 - User consent for InvoiceDirect released

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

### <a name="response_code"></a> 10 august 2020 - Invoice 1.5 released
### <a name="response_code"></a> 10 August 2020 - Invoice 1.5 released