Skip to content

Commit a56fa04

Browse files
authored
Update transition-to-one-platform.md
1 parent d1f1559 commit a56fa04

File tree

1 file changed

+3
-15
lines changed

1 file changed

+3
-15
lines changed

docs/subscriptions/transition-to-one-platform.md

Lines changed: 3 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -256,24 +256,23 @@ Parameter: `attachment_details`
256256

257257
### 7.1 Authorisation
258258

259+
259260
**For merchants**
260261

261-
* If you are using or are planning to start using Subscriptions on the MobilePay platform before transitioning to One Platform. All good, nothing to do for you, just make sure you complete the authorization setup before Nordic Wallet Launch.
262-
* If by any chance you will need to restart the consent flow, e.g. get a new refresh token after Nordic Wallet Launch, you will have to do that already though new Vipps MobilePay platform.
262+
* If you will need to restart the consent flow, e.g. get a new refresh token after Nordic Wallet Launch, you will have to do that already though new Vipps MobilePay platform.
263263
* If you are planning to start using Recurring on the New Vipps MobilePay platform, just integrate into the new setup from the beginning.
264264

265265
Read more about [Access token API guide](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/).
266266

267267
**For integrators/partners**
268268
* If you are planning to start using Recurring on New Vipps MobilePay platform, just integrate to the new setup from the beginning.
269-
* If you are an existing partner in Subscriptions on the MobilePay platform and you want to onboard new merchants, we will ask you to change your authorization setup. We are sorry, but from the Nordic Wallet Launch, we will not be able to support the existing flow where the merchant grants consent to you. Access and refresh tokens that were issued before the transition will remain valid and continue to work. To get providerId for new onboarded merchants, you can call `GET:/api/merchants/me` with the new authorization token and `Merchant-Serial-Number` header.
269+
* If you are an existing partner in Subscriptions on the MobilePay platform and you want to onboard new merchants, we will ask you to change your authorization setup. From the Nordic Wallet Launch, we will not be able to support the existing flow where the merchant grants consent to you. Access and refresh tokens that were issued before the transition will remain valid and continue to work. To get providerId for new onboarded merchants, you can call `GET:/api/merchants/me` with the new authorization token and `Merchant-Serial-Number` header.
270270

271271
- Read more about [Access token API guide](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/) and [Technical information for partners](https://developer.vippsmobilepay.com/docs/vipps-partner/#technical-information-for-partners).
272272

273273

274274
## **8. Settlements**
275275

276-
277276
### 8.1 From the Nordic Wallet Launch all sales units (payment points) will be switched to daily settlements
278277

279278
Currently you were able to select how to receive settlements: daily or instant. After NWL all sales units will be switched to receive daily settlements. Instant transfers will stay as a functionality, but it will be renamed to Single payment settlements, which represents the functionality in better way. Furthermore, functionality will be for an extra fee. With Single payment settlements every payment will be settled separately (not bundled up) and you will receive it in 1 days after payment was executed.
@@ -425,9 +424,6 @@ Some field names, like `mobile_phone_number`, will undergo changes; for instance
425424

426425
:star: **Recommendation:** Avoid relying on specific values in `error_description.message` and `error_description.error_type`. Update your error handling processes to ensure flexibility in these two fields.
427426

428-
### 9.6 From the Nordic Wallet Launch Merchant's server must be TLS 1.2
429-
430-
Please make sure that your servers hosting the token endpoint for callbacks supports TLS 1.2. If not, we will not be able to send callbacks back to you.
431427

432428
## **10. Test**
433429
The first version of the new test environment is ready for the Subscriptions facade. All features are available.
@@ -577,12 +573,4 @@ We will migrate 3 years of historical data (agreements, payment requests, refund
577573
3. Though [Merchant Portal](https://portal.vipps.no/register). Just for new transactions done after Nordic Wallet Launch.
578574
4. Integrate it into the [Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/). Read more [here](https://developer.vippsmobilepay.com/docs/mp-migration-guide/reporting/) about transition period.
579575

580-
### **4. What cool features are there ahead?**
581-
582-
For instance, there's profile sharing, allowing merchants to request users to share various information from the app, thereby streamlining the signup process. Additionally, we have upcoming campaigns, improved refund processes, enhanced capture capabilities, increased limits, expansion into three new markets, and various other flexibility improvements.
583-
584-
585-
## **Developer Support**
586576

587-
We're Here to Help!
588-
If you have any questions, our Developer support team ([email protected]) is available to provide guidance and support.

0 commit comments

Comments
 (0)