diff --git a/.yarn/install-state.gz b/.yarn/install-state.gz index 4db0692d0..50aeba0c7 100644 Binary files a/.yarn/install-state.gz and b/.yarn/install-state.gz differ diff --git a/docs/app-payments/_category_.json b/docs/app-payments/_category_.json index 6d2cce330..c2adc0c1a 100644 --- a/docs/app-payments/_category_.json +++ b/docs/app-payments/_category_.json @@ -1 +1 @@ -{ "label": "App Payments", "position": 1 } +{ "label": "App Payments Facade", "position": 1 } diff --git a/docs/app-payments/development-guide/getting-started.md b/docs/app-payments/development-guide/getting-started.md index 6a89ca946..d5de35030 100644 --- a/docs/app-payments/development-guide/getting-started.md +++ b/docs/app-payments/development-guide/getting-started.md @@ -2,6 +2,8 @@ sidebar_position: 1 --- +# Getting Started + :::caution Closed It is no longer possible to onboard MobilePay App Payments. The product have been replaced with [ePayments API](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/) diff --git a/docs/online/_category_.json b/docs/online/_category_.json index 1ce7df395..014f2b5c4 100644 --- a/docs/online/_category_.json +++ b/docs/online/_category_.json @@ -1 +1 @@ -{ "label": "Online", "position": 3 } +{ "label": "Online PSP", "position": 5 } diff --git a/docs/online/basics/allowed-card-types.md b/docs/online/basics/allowed-card-types.md index b84f9fdfd..94720bdcb 100644 --- a/docs/online/basics/allowed-card-types.md +++ b/docs/online/basics/allowed-card-types.md @@ -5,3 +5,6 @@ sidebar_position: 9 # Allowed card types The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#allowed-card-types) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/allowed-currencies.md b/docs/online/basics/allowed-currencies.md index 400be9554..f3d043216 100644 --- a/docs/online/basics/allowed-currencies.md +++ b/docs/online/basics/allowed-currencies.md @@ -5,3 +5,6 @@ sidebar_position: 8 # Allowed currencies The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#allowed-currencies) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/basics.md b/docs/online/basics/basics.md index 34d7775ee..7a9cf01c4 100644 --- a/docs/online/basics/basics.md +++ b/docs/online/basics/basics.md @@ -1,3 +1,6 @@ # Basics The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/callbacks.md b/docs/online/basics/callbacks.md index 1214a745c..6b1ff0d47 100644 --- a/docs/online/basics/callbacks.md +++ b/docs/online/basics/callbacks.md @@ -4,3 +4,6 @@ sidebar_position: 5 # Callbacks The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#callbacks) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/embedded-flow.md b/docs/online/basics/embedded-flow.md index 927bf7167..2fcc1e0da 100644 --- a/docs/online/basics/embedded-flow.md +++ b/docs/online/basics/embedded-flow.md @@ -5,3 +5,6 @@ sidebar_position: 10 # Embedded Flow (IFrame) The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#embedded-flow-iframe) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/error-codes.md b/docs/online/basics/error-codes.md index 4b1a8bb24..fdf027361 100644 --- a/docs/online/basics/error-codes.md +++ b/docs/online/basics/error-codes.md @@ -4,3 +4,6 @@ sidebar_position: 7 # Error codes The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#error-codes) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/flow.md b/docs/online/basics/flow.md index a02ad95fe..2dfd9fa72 100644 --- a/docs/online/basics/flow.md +++ b/docs/online/basics/flow.md @@ -4,3 +4,6 @@ sidebar_position: 3 # Dual device and single device flow The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#dual-device-and-single-device-flow) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/merchants.md b/docs/online/basics/merchants.md index 5a4459484..c29c26d7e 100644 --- a/docs/online/basics/merchants.md +++ b/docs/online/basics/merchants.md @@ -4,3 +4,6 @@ sidebar_position: 1 # Merchants The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#merchants) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/payments.md b/docs/online/basics/payments.md index 1960d726b..afc071c92 100644 --- a/docs/online/basics/payments.md +++ b/docs/online/basics/payments.md @@ -4,3 +4,5 @@ sidebar_position: 2 # Payments The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#payments) + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/request-fishing.md b/docs/online/basics/request-fishing.md index d4a241db3..e7ff75523 100644 --- a/docs/online/basics/request-fishing.md +++ b/docs/online/basics/request-fishing.md @@ -5,3 +5,6 @@ sidebar_position: 6 # Request Fishing Scenario The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#request-fishing-scenario) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/basics/retry-policy.md b/docs/online/basics/retry-policy.md index df78779a4..de7690e8e 100644 --- a/docs/online/basics/retry-policy.md +++ b/docs/online/basics/retry-policy.md @@ -5,3 +5,5 @@ sidebar_position: 4 # Retry policy The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#retry-policy) + +![docs](/img/icon_checkout.png) diff --git a/docs/online/development-guide/development-guide.md b/docs/online/development-guide/development-guide.md index 0a2574100..29b202eed 100644 --- a/docs/online/development-guide/development-guide.md +++ b/docs/online/development-guide/development-guide.md @@ -1,3 +1,6 @@ # Development Guide The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/development-guide/getting-started.md b/docs/online/development-guide/getting-started.md index a14e9dbc5..8b45f4921 100644 --- a/docs/online/development-guide/getting-started.md +++ b/docs/online/development-guide/getting-started.md @@ -5,3 +5,6 @@ sidebar_position: 1 # Getting started The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-getting-started/) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/development-guide/production.md b/docs/online/development-guide/production.md index 29ef7c58d..aac956376 100644 --- a/docs/online/development-guide/production.md +++ b/docs/online/development-guide/production.md @@ -4,3 +4,6 @@ sidebar_position: 4 # Production The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-checklist/) + +![docs](/img/icon_checkout.png) + diff --git a/docs/online/development-guide/test.mdx b/docs/online/development-guide/test.mdx index c21352d7a..ad1eecbab 100644 --- a/docs/online/development-guide/test.mdx +++ b/docs/online/development-guide/test.mdx @@ -5,3 +5,6 @@ sidebar_position: 2 # Test The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-getting-started/#test) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/development-guide/verification.md b/docs/online/development-guide/verification.md index 896536ba0..d4fba6f62 100644 --- a/docs/online/development-guide/verification.md +++ b/docs/online/development-guide/verification.md @@ -5,3 +5,6 @@ pagination_label: verification # Verification The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-checklist/) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/online.md b/docs/online/online.md index 2b25554c2..5ea97de67 100644 --- a/docs/online/online.md +++ b/docs/online/online.md @@ -7,3 +7,6 @@ pagination_next: null # MobilePay Online The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/resources.md b/docs/online/resources.md deleted file mode 100644 index 17e647e57..000000000 --- a/docs/online/resources.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -layout: forward -target: https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/ ---- - -# Resources - -The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/) diff --git a/docs/online/sca.md b/docs/online/sca.md index ad13b3f88..1a00b6c81 100644 --- a/docs/online/sca.md +++ b/docs/online/sca.md @@ -4,3 +4,6 @@ sidebar_position: 3 # Strong Customer Authentication The documentation have been moved to the [Vipps MobilePay documentation](https://developer.vippsmobilepay.com/docs/APIs/psp-mp-api/mp-psp-api-api/#strong-customer-authentication) + + +![docs](/img/icon_checkout.png) diff --git a/docs/online/transition-to-one-platform.md b/docs/online/transition-to-one-platform.md index 28f454ae4..b00b324ae 100644 --- a/docs/online/transition-to-one-platform.md +++ b/docs/online/transition-to-one-platform.md @@ -30,7 +30,7 @@ If you do not update the VAT number of your existing merchants you will not be a For sole props. not having a VAT no. you can use an alternative number for example your own unique merchant id. ## Callback servers -On our new platform we will use different callback servers than currently used. If you have whitelisted our IP ranges for callbacks please ensure to include our new servers. You can find our server guidelines [here](https://developer.vippsmobilepay.com/docs/developer-resources/servers/). Note that this is only for callbacks. During the transition period to our new platform you may receive callbacks from our old setup and new servers. Therefore you must allow both the [old](/docs/support/faq) and [new servers](https://developer.vippsmobilepay.com/docs/developer-resources/servers/) for a period of time until we have completely transitioned to one platform. We encourage you to enable this as soon as possible as this will come into effect in January 2024. +On our new platform we will use different callback servers than currently used. If you have whitelisted our IP ranges for callbacks please ensure to include our new servers. You can find our server guidelines [here](https://developer.vippsmobilepay.com/docs/developer-resources/servers/). Note that this is only for callbacks. During the transition period to our new platform you may receive callbacks from our old setup and new servers. Therefore you must allow both the old and [new servers](https://developer.vippsmobilepay.com/docs/developer-resources/servers/) for a period of time until we have completely transitioned to one platform. We encourage you to enable this as soon as possible as this will come into effect in January 2024. ## Feature changes During Q1 2024 - once we fully consolidate our platforms – the following endpoints/features will stop working for MobilePay Online. diff --git a/docs/subscriptions/_category_.json b/docs/subscriptions/_category_.json index 9fa628290..76a3c5256 100644 --- a/docs/subscriptions/_category_.json +++ b/docs/subscriptions/_category_.json @@ -1 +1 @@ -{ "label": "Subscriptions", "position": 5 } +{ "label": "Subscriptions Facade", "position": 3 } diff --git a/docs/subscriptions/development-guide/production.md b/docs/subscriptions/development-guide/production.md index b4b338920..0d298d5fb 100644 --- a/docs/subscriptions/development-guide/production.md +++ b/docs/subscriptions/development-guide/production.md @@ -73,7 +73,7 @@ It is important to know which transfer type are possible to use as a merchant. T | | Instant Transfer | Daily Transfer | |--|--|--| |**WHEN TRANSFER IS DONE**|MobilePay transfers **instantly** after the payment is completed. Transfer might reach Merchant account later than MobilePay executes transfers. It depends on Merchant bank transfer times.|MobilePay transfers **once per day**, at night. Payments paid on day X will be transferred on day X+1. Transfer might reach Merchant account later than MobilePay executes transfers. It depends on Merchant bank transfer times.| -|**REFERENCE NUMBER**|Field **external_id** for recurring payments and one_off_payment. `external_id` for one-off payments is used as Reference number.|Reference number is generated by MobilePay. External Rules [here](/docs/support/faq#what-is-payment-reference).| +|**REFERENCE NUMBER**|Field **external_id** for recurring payments and one_off_payment. `external_id` for one-off payments is used as Reference number.|Reference number is generated by MobilePay..| |**HOW TO SET IT**| Merchant can set **Instant transfers** for each Subscription provider in MobilePay portal.|Merchant can set **Daily transfers** for each Subscription provider in MobilePay portal.| |**BANK STATEMENT**|**`external_id`** for recurring payments and one_off_payment.`external_id` for one-off payments will be used in bank statement in fields. DK: Text field. FI: Text field and Reference no. field.| MobilePay generated reference number will be used in bank statement in fields. DK: Text field. FI: Text field and Reference no. field.| |**Refund**|Currently it is not possible to refund when the merchant has chosen 'instant transfer' method.|You can only refund your customers if you have received payments with MobilePay on the day to cover the refund| diff --git a/docs/subscriptions/transition-to-one-platform.md b/docs/subscriptions/transition-to-one-platform.md index 613d40246..66d6b3043 100644 --- a/docs/subscriptions/transition-to-one-platform.md +++ b/docs/subscriptions/transition-to-one-platform.md @@ -61,7 +61,7 @@ You'll receive an email with the required information, even if you're an existin - **API Endpoint:** `POST /api/providers/{providerId}/agreements` or `PATCH /api/providers/{providerId}/agreements/{agreementId}` - **Parameter:** `amount` -![WMP Amount](path/to/img/vmpamount.png) +![WMP Amount](/img/vmpamount.png) [WMP Amount -::: - -## What are the MobilePay IP addresses? - -Note that MobilePay does not require merchants to whitelist specific IP addresses to access REST APIs. -We utilize different ranges for the APIs and callbacks as well as for the different environments. We cannot supply specific IPs because we may change IPs within the listed ranges and therefore recommend to whitelist the entire range. - -**API requests**
-Production: 20.238.5.64/28 and 4.245.40.224/28
-Sandbox: 4.175.250.192/28 - -**Callbacks**
-Production and sandbox: -212.93.32.0/19 and 185.218.228.0/22 - -:::danger Important info -We are in the process of consolidating our platform with Vipps to create a new shared platform. For the products that are using facades ([Subscriptions](/docs/subscriptions/transition-to-one-platform), [App Payments](/docs/app-payments/transition-to-one-platform) and [Online](/docs/online/transition-to-one-platform) ) please note that we will use new servers for all callbacks. Therefore you must adhere to our new [server guidelines](https://developer.vippsmobilepay.com/docs/developer-resources/servers/). -::: - -**Port**: 443 - -
- What is the difference between Sandbox and Production -
- -
-
- -
- How do I, as an Integrator test in production? -
- -
-
- -
- Payment limit in Sandbox -
- -
-
- -
- What is correlationId? -
- -
-
- -
- What is payment reference -
- -
-
diff --git a/docs/support/faq/_correlationId.mdx b/docs/support/faq/_correlationId.mdx deleted file mode 100644 index 663270503..000000000 --- a/docs/support/faq/_correlationId.mdx +++ /dev/null @@ -1,6 +0,0 @@ -CorrelationId is a unique identifier value that is set as header for each API request -``` -header 'correlationid: REPLACE_THIS_VALUE' -``` - -The id serves as reference for the particular API request and makes API support more efficient. If you are having issue with an API request, please include the correlationId. We recommend to use a random GUID as the correlationId. \ No newline at end of file diff --git a/docs/support/faq/_difference.mdx b/docs/support/faq/_difference.mdx deleted file mode 100644 index 375ebcb19..000000000 --- a/docs/support/faq/_difference.mdx +++ /dev/null @@ -1,9 +0,0 @@ -Sandboxes are isolated from your production organisation, so operations that you perform in the MobilePay sandbox don’t affect your production organisation. The production version of the API provides access to the real customer data, i.e. you will be able to initiate real payments. Once you go to test in production, you will use another basepath, the live MobilePay app and a real MobilePay user. - -| | Sandbox | Production | -|-|---------|------------| -|User|We have test users available. Visit the product sites to find information about test users|A real MobilePay user, that has downloaded the MobilePay app on their smartphone. We **do not** have test user that you can use in production.| -|Payment limit|Same as in production. Read here: [DK](https://www.mobilepay.dk/hjaelp/mobilepay-til-private/fakta/hvor-meget-kan-jeg-overfoere-med-mobilepay) - [FI](https://www.mobilepay.fi/asiakastuki/mobilepay-kayttajille/tietoa-mobilepaysta/kuinka-paljon-voin-siirtaa-mobilepaylla#scroll)| -|Functionality|Sandbox processes API calls in exactly the same manner as the production environment, except you are not dealing with real money and transactions.|Only real transaction can be completed| -|Endpoint|https://api.sandbox.mobilepay.dk|https://api.mobilepay.dk| -|Mobilepay Portal|https://sandprod-admin.mobilepay.dk|https://admin.mobilepay.dk| \ No newline at end of file diff --git a/docs/support/faq/_ip-addresses.mdx b/docs/support/faq/_ip-addresses.mdx deleted file mode 100644 index 154853c5c..000000000 --- a/docs/support/faq/_ip-addresses.mdx +++ /dev/null @@ -1,4 +0,0 @@ - -* MobilePay does not require merchants to whitelist specific IP addresses to access REST APIs. -* We utilize IPs in these ranges: 212.93.32.0/19 and 185.218.228.0/22 -* MobilePay uses port 443 diff --git a/docs/support/faq/_payment-limit.mdx b/docs/support/faq/_payment-limit.mdx deleted file mode 100644 index 500b9aeb8..000000000 --- a/docs/support/faq/_payment-limit.mdx +++ /dev/null @@ -1 +0,0 @@ -The behavior of the API when you are in sandbox mode is the same as when your app is live, but comes with the following restrictions. The users in the Sandbox have a daily limit at 3.000 DK. It is recommended to send Payment Requests below 10 DKK or 2 EUR. Be sure to test with reasonable amounts and only run a limited number of transactions. \ No newline at end of file diff --git a/docs/support/faq/_payment-reference.mdx b/docs/support/faq/_payment-reference.mdx deleted file mode 100644 index fdbcef22d..000000000 --- a/docs/support/faq/_payment-reference.mdx +++ /dev/null @@ -1,27 +0,0 @@ -If you have one of our MobilePay products, then you can expect to see a Payment Reference in your bank account. Payment reference is a reference that is assigned to payment and is visible in bank account statement when payment is completed and received by your bank. It is usually used for tracking and verifying which payments were received to the bank account (e.g. transfers). - -MobilePay specific reference: -PCRRRRRRRRJJJDDMMYYX - -**PC** -Product code - Products need to identify the product, code is then put when generating the reference. -* 01 = POS -* 02 = MyShop -* 03 = Subscriptions -* 04 = Invoice -* 05 = AppSwitch -* 06 = Online - -**RRRRRRRR** -External Payment Point ID (length 8). Myshop number, Pos LocationID etc. External Payment PointID will be sent in the payload from the product.The external payment point ID must be unique within the Merchant for the payment point. For Subscription and Invoice this will consist of 8 zeros (00000000). - -**JJJ** -Running number (length 3) - -**DDMMYY** -Date (lenght 6) - -**X** -Check digit (length 1) - -*Example: 03000000000011602193 - which indicates Subscriptions payments received 16.02.2019* \ No newline at end of file diff --git a/docs/support/faq/_production-test.mdx b/docs/support/faq/_production-test.mdx deleted file mode 100644 index 194cef9a9..000000000 --- a/docs/support/faq/_production-test.mdx +++ /dev/null @@ -1,11 +0,0 @@ -Once you have finished testing in sandbox and the verification, you can verify that the set-up is also working in production. This is especially important with regards to using the right redirect URI's in production, and using the right credentials for OpenID Connect in production. You need to update all URLs and credentials to production values. - -Once you've done so, there are two possibilities, and you can choose the option, that fits you the best. - -**Test with your own customer** - -You can use one of your existing customers as pilot merchant. In order to do so they need to have an active MobilePay agreement and chosen the decired MobilePay product. - -**Test with your own account** - -If you do not want to test with your customer, you have the possibility to order the API product yourself, so you have a registration in production. In this case, you'll be marked as an integrator, and will only pay for the transactions, and not the monthly fee. diff --git a/docs/support/support.md b/docs/support/support.md deleted file mode 100644 index aebc2de87..000000000 --- a/docs/support/support.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -displayed_sidebar: supportSidebar ---- - -# Developer Support - -MobilePay Developer Support provide **technical support in regards to integration and maintenance** for the following products: - -* MobilePay Subscriptions -* MobilePay App Payments -* PSP support for MobilePay Online - -For merchant support of your MobilePay Online solution please contact your PSP. You can find a list of PSPs providing MobilePay Online here: [DK](https://mobilepay.dk/erhverv/payment-service-providers-liste) and [FI](https://mobilepay.fi/yrityksille/maksupalveluntarjoajat) - - -## We help with technical issues - -MobilePay Developer support provides support in Danish and English. You can contact us either by using the contact form below or write us an email at developer@vippsmobilepay.com We will respond as soon as possible, within one business day. - -### What to include in the email - -* **Please: Always include a detailed description of the problem** -* Company details - * Organization number (find yours at Virk) - * Merchant_ID -* Environment: Sandbox or the Production -* Date and time -* Any relevant id such as: orderId, transactionId, merchant_id, payment_id, agreement_id etc. -* For API issues: Complete request and response details (plain HTTP from Postman) -* For app issues: Specify iOS or Android, and the MobilePay app version -* How to reproduce the error -* Screenshots, if possible. -* Please provide your contact information (if not in your email signature): - * Name - * Email -* Please include any other information that may be relevant or possibly helpful. - -*Can I call you?* -Nope. We do not have a phone number for Developer Support, and we do not have the capacity to help 1:1 on phone, sorry, since most cases involve information that needs to be in written form, such as ids, API requests/responses, etc. We can set up a MS teams call in urgent cases. diff --git a/docusaurus.config.js b/docusaurus.config.js index c506996fa..9152df08b 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -34,17 +34,12 @@ module.exports = { }, items: [ { - label: 'App Payments', + label: 'App Payments Facade', position: 'left', to: '/docs/app-payments/', }, { - label: 'Online', - position: 'left', - to: '/docs/online', - }, - { - label: 'Subscriptions', + label: 'Subscriptions Facade', position: 'left', to: '/docs/subscriptions', }, @@ -53,31 +48,18 @@ module.exports = { position: 'left', items: [ { - label: 'App payments', + label: 'App payments Facade', to: '/api/app-payments', }, { - label: 'Webhooks', - to: '/api/wehooks', - }, - { - label: 'Online', - to: '/api/online', - }, - { - label: 'Subscriptions', + label: 'Subscriptions Facade', to: '/api/subscriptions', }, ], }, { - label: "Support", - to: '/docs/support', - position: "right", - }, - { - href: "https://github.com/MobilePayDev/MobilePayDev.github.io", - label: "GitHub", + href: "https://developer.vippsmobilepay.com/", + label: "Vipps MobilePay Documentation", position: "right", }, ], diff --git a/sidebars.js b/sidebars.js index 5a8ae7451..19a1e2058 100644 --- a/sidebars.js +++ b/sidebars.js @@ -11,6 +11,5 @@ module.exports = { // By default, Docusaurus generates a sidebar from the docs folder structure - docsSidebar: [{ type: 'autogenerated', dirName: '.' }], - supportSidebar: ['support/support','support/faq'] + docsSidebar: [{ type: 'autogenerated', dirName: '.' }] } diff --git a/src/pages/checkout-best-practice.md b/src/pages/checkout-best-practice.md deleted file mode 100644 index b1153c066..000000000 --- a/src/pages/checkout-best-practice.md +++ /dev/null @@ -1,134 +0,0 @@ -# MobilePay Checkout best practice - -MobilePay Checkout lets webshops offer their customers a faster and easier purchase flow by linking payment and delivery details. - -[![checkout main flow](/img/online-Checkoutmainflow.png)](/img/online-Checkoutmainflow.png) - -The customer can easily approve the order in his/her MobilePay –and the webshop receives the information to be used to process the order. - -## What is MobilePay Checkout - -* An add-on for MobilePay Online –which does not cost extra -* Is available via the PSPs which support the solution. See the PSPs [here](https://mobilepaygroup.com/partner/payment-service-providers) -* Requires a special technical integration to the webshop's PSP –contact your PSP for further information -* Available for selected shop systems –contact your PSP for further information - -If you build your own webshop (or if someone else does it for you) –you will need to integrate MobilePay Checkout into your webshop yourself. You may do so in a way that is optimal for your webshop–including the placement of the MobilePay Checkout button as well as handling of delivery. - -The following documentation show examples of best practice and examples –for your inspiration –of how a given webshop can build MobilePay Checkout into the webshop. - -## Best practice - -### MobilePay Checkout button - -Place the MobilePay Checkout button in the webshop where it makes sense. - -It is entirely up to you where you place the button in your user flow – but please make sure that it is easy for your customers to find the button and pay. Consider where you want to place the button, e.g. at the end of the user flow, as an alternative to the normal checkout flow or close to the product to create a ‘buy now’ experience. - -Only use approved MobilePay buttons: [Find buttons](https://cdn.mobilepay.dk/res-website/img/assets.html) - -### End-user choices - -You may use overlay or pop-up for additional end-user choices, e.g. for acceptance of terms and conditions. - -Follow best practice and provide the user with an overview of the order before he/she accepts it. - -:::danger Mandatory! -Always insert the mandatory text where you place the MobilePay Checkout button. The mandatory text must always appear before the user accepts the order. -Note: the final text depends on the choice of delivery method. Find mandatory texts on the next slides. -::: - -Use e.g. overlay or pop-up windows in the webshop to display additional options for the end user. This may be approval of the shop’s terms and conditions or choice of delivery method. -The MobilePay Checkout button directs the end user to the MobilePay app, where delivery information and payment are approved. - -[![overlay](/img/online-OverlaySmall.png)](/img/online-Overlay2.png) - -:::info Please note -Checkout without use of overlay is also possible but you must ensure to add the mandatory text close to the Checkout button. -::: - -## Delivery options - -You must decide how delivery is to be handled. This is to be defined and constructed in the webshop - -**The simple solution** -*Short user flow / fewer choices* -(See [Delivery option 1](#delivery-option-1---simple-solution)) - -* The webshop constructs the solution so that the delivery method is selected on behalf of the customer -* This means a minimum of user interaction and the fewest possible checkout steps -* The checkout flow is short and the user can complete his/her purchase quickly and - easily - -**The flexible solution** -*Longer user flow / more end-user choices* -(See [Delivery option 3](#delivery-option-3---flexible-solution)) - -* The webshop constructs the solution so that the customer is given a choice between several delivery methods in the webshop -* The solution provides several options for the customer, e.g. choice of post office/parcel shop or different suppliers with different prices -* The checkout flow will be a little longer, with a few more user choices, which may be relevant for some webshops and their customers - -### Delivery option 1 - Simple solution - -[PoS confirmation screen](/img/online-Deliveryoption1big.png) - -MobilePay Checkout is integrated in the webshop with delivery to an address (e.g. home address or workplace) - -* In MobilePay the customer must select a delivery address (Specify the correct configuration for MobilePay Checkout. See more in the PSP documentation). -* After the customer has approved his or her delivery details in MobilePay the order confirmation can be generated by the webshop. -* Insert the mandatory text close to the MobilePay Checkout button in the user flow in the webshop. - -:::info Mandatory text -ENG: When you pay with MobilePay Checkout you choose your delivery address in MobilePay - -DK: Når du betaler med MobilePay Checkout, vælger du din leveringsadresse i MobilePay -::: - -### Delivery option 2 - Simple solution - -[PoS confirmation screen](/img/online-Deliveryoption2big.png) - -MobilePay Checkout is integrated in the webshop with automatic delivery to the nearest parcel shop - -* The pickup location closest to the customer’s address in MobilePay is automatically selected by the webshop. -* NB! Depends on the carrier’s options and setup in the webshop (Specify the correct configuration for MobilePay Checkout. See more in the PSP documentation). -* Insert the mandatory text close to the MobilePay Checkout button in the user flow. - -:::info Mandatory text -ENG: When you pay with MobilePay Checkout your purchase is sent to the nearest post office/parcel shop - -DK: Når du betaler med MobilePay Checkout, sendes dit køb til nærmeste posthus/pakkeshop -::: - -### Delivery option 3 - Flexible solution - -[PoS confirmation screen](/img/online-Deliveryoption3big.png) - -MobilePay Checkout is integrated in the webshop with delivery to a parcel shop selected by the customer - -* Allow the customer to choose a pickup location (including pick-up in a store) before MobilePay Checkout is activated – e.g. in an additional overlay or pop-up window in the webshop (depends on the webshop's setup and the options provided by the carrier chosen by the webshop). -* In MobilePay, the customer is therefore not to choose a delivery address (Specify the correct configuration for MobilePay Checkout. See more in the PSP documentation) -* Insert the mandatory text close to the MobilePay Checkout button in the user flow. - -:::info Mandatory text -ENG: When you pay with MobilePay Checkout, your purchase will be sent to the pickup location you selected in the shop - -DK: Når du betaler med MobilePay Checkout, sendes dit køb til den afhentningssted du har valgt i butikken -::: - -[Return to documentation](/checkout) diff --git a/src/pages/checkout.md b/src/pages/checkout.md deleted file mode 100644 index b19c93b7a..000000000 --- a/src/pages/checkout.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -sidebar_position: 1 ---- - -# Checkout - -With MobilePay Checkout webshops can offer their customers to complete purchases even faster by linking payment and delivery details. When using Checkout MobilePay will supply you with the billing address and optionally the delivery address of the customer. When initiating a Checkout payment the user will then be prompted to choose address before accepting the payment in the MobilePay app. - -Please visit our [best practice guide](/checkout-best-practice) for guidelines and recommendations on how to use MobilePay Checkout in a webshop. - -## How to initiate a Checkout payment - -Checkout can be used on any MobilePay Online payment and is initiated as any other payment using: -`POST /payments` - -Four parameters are required when initiating a Checkout payment: - -```json title="Request body example" - "isCheckout":true, - "addressCallbackUrl":"http://example.com", - "deliveryAddressAllowed":true, - "deliveryAddressDisallowedReasonCode":4, //Only required if "deliveryAddressAllowed":false. -``` - -* isCheckout: This will define the payment as a Checkout payment when set to true -* addressCallbackUrl: The url where we will deliver the checkout callback with the address details. The Checkout callback will always be delivered before the card/token callback. -* deliveryAddressAllowed: Will define whether the user is allowed to choose delivery address. If set to false the user can only choose a billing address. Can be used for instance if the user has chosen 'Pick up at store' in the webshop. -* deliveryAddressDisallowedReasonCode: if deliveryAddressAllowed is set to false a reason must be given: -1: Reason not given, 2: Goods don't require physical delivery, 3: 'Pick up at store' already selected in the Webshop, 4:'Parcel Shop' already selected in the Webshop, 5: Shop will select a parcel shop close to your home. - -[![checkout sequence diagram](/img/online-checkout-sequence-diagram.svg)](/img/online-checkout-sequence-diagram.svg) - -## Checkout callback - -The callback will have a JSON body like this: - -```json title="Checkout callback example" - { - "PaymentId": "9369ea35-4b5b-428a-bdf8-c29c29a4b264", - "AuthorizationAttemptId": "a8c99cbf-3468-4eb9-9c0e-ddd110e8ed33", - "Addresses": [{ - "FirstName": "John", - "Surname": "Doe", - "Attention": "", - "CompanyName": "", - "AddressLine1": "Flower Street 23", - "AddressLine2": "", - "PostalCode": "3434", - "City": "Great city", - "CountryCode": "DK", - "IsCustomerOfficialAddress": true, - "IsBillingAddress": true, - "IsDeliveryAddress": true, - "AddressValidationMethod": "DaWa", - "AddressValidationStatus": "NotValidated" - }], - "EmailAddress": "johndoe@gmail.com", - "EmailAddressValidationMethod": "EmailEnteredTwice", - "EmailAddressValidationStatus": "Validated", - "PhoneNumber": "+4512345678", - "PhoneNumberValidationMethod": "SMSChallenge", - "PhoneNumberValidationStatus": "Validated" - } -``` - -The address array may contain two items. One for billing address and one for delivery address. If billing and delivery address is the same the array will only contain one item where IsBillingAddress and IsDeliveryAddress is set to true. - -If deliveryAddressAllowed is set to false on payment initiation the array will only contain one item where IsBillingAddress is set to true and IsDeliveryAddress is set to false. diff --git a/src/pages/index.md b/src/pages/index.md index dcff80667..a001c8719 100644 --- a/src/pages/index.md +++ b/src/pages/index.md @@ -1,13 +1,10 @@ --- hide_table_of_contents: true +title: We moved! --- -Banner +# drawing We moved! But not very far :star: -We're thrilled to embark on the journey of creating the ultimate payment wallet experience for our wonderful customers, partners, and users in the Nordics. We are launching a single, unified platform: MobilePay in Denmark and Finland, and Vipps in Norway. Together this will be [**Vipps MobilePay**](https://developer.vippsmobilepay.com/). +We have packed up most of our documentation and moved to: https://developer.vippsmobilepay.com/ -The old MobilePay platform have now been closed and it is no longer possible to make new integrations for these. Please visit our new developer documentation to see our new products: https://developer.vippsmobilepay.com/ +[![docs](/img/front_docs.png)](https://developer.vippsmobilepay.com/) \ No newline at end of file diff --git a/src/pages/invalidation.md b/src/pages/invalidation.md deleted file mode 100644 index 9e420a154..000000000 --- a/src/pages/invalidation.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -sidebar_position: 4 ---- - -# Invalidation of a payment - -In some cases the user goes back to the merchant webshop and adds something to the shopping basket after the payment has been initiated. The user could end up with several requests with different amounts and there would be a possibility, that the user accepts the wrong one in MobilePay. In this case payment invalidation endpoint can be useful. When the invalidation is completed, it means that the user cannot create a request for the payment or accept the payment. Active requests will also expired immediately. - -## Invalidation before callback - -If the invalidation request is received by MobilePay before the callback to the PSP is made, no callback will be performed and the invalidation will complete. - -[![Payment invalidation before callback](/img/online-invalidation-before-callback.svg)](/img/online-invalidation-before-callback.svg) - -## Invalidation after callback - -If the invalidation request is received by MobilePay after the callback to the PSP is performed, the PSP must also PATCH the authorizationAttempt with succeeded=false and the ReasonCode 1010 - RejectedForInvalidatePayment. - -In this case the invalidation request will be processed in the MobilePay backend according to these rules: - -1. If a successful authorization already exists on the payment, the invalidation endpoint will return the error code 2100. -2. If a callback has been sent but the authorization attempt has not yet been patched or 3DS is ongoing, the invalidation endpoint will return the error code 2101. The authorization attempt must be patched with reasoncode 1010 before invalidation. -3. A failed authorization will result in a successful invalidation. - -[![Payment invalidation after callback](/img/online-invalidation-after-callback.svg)](/img/online-invalidation-after-callback.svg) diff --git a/src/theme/NotFound.js b/src/theme/NotFound.js index f2ceb6866..d17ce8711 100644 --- a/src/theme/NotFound.js +++ b/src/theme/NotFound.js @@ -19,25 +19,30 @@ export default function NotFound() { - Whoops + We moved!

- We tried really hard but we could not find whatever you were looking for. But we are sure it is here somewhere. We have been rearranging a lot lately so it may have been lost in the moving process. Although fear not as we are here to help! + So that is probably why you didn't find what you looked for + - If you know what product it concerns you could try the menu right at the very top. If you look to the right there is also a search option which we think might be really helpfull in times of need. + Italian Trulli

- If everything else fails you are very welcome to contact us at developer@vippsmobilepay.com. We will gladly help you find what you are looking for or answer any questions you might have. + But don't stress, try to go to our new page and see if you can find it there: + + + https://developer.vippsmobilepay.com/

+ diff --git a/static/img/front_docs.png b/static/img/front_docs.png new file mode 100644 index 000000000..ed800f97a Binary files /dev/null and b/static/img/front_docs.png differ diff --git a/static/img/icon_checkout.png b/static/img/icon_checkout.png new file mode 100644 index 000000000..8a43d2a14 Binary files /dev/null and b/static/img/icon_checkout.png differ