You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/app-payments/transition-to-one-platform.md
+14-4
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ There is no need to reintegrate into the new solution yet as the existing App Pa
20
20
-**2024** Plan and integrate new [ePayments API](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/)
21
21
-**2025Q1** Be ready with your API integration to the App Payments API. The facade will be switched off.
22
22
23
-
## Test options
23
+
## Test
24
24
The first version of the new test environment is ready for the App Payments facade. All features except Refund is available.
25
25
26
26
### Test credentials
@@ -30,9 +30,20 @@ The first version of the new test environment is ready for the App Payments faca
30
30
31
31
Please note: If you want to reuse your App Payments test data you will need to recreate your test data. Please note that all test data, including payments, refunds, and so on, created on the old platform will not be migrated from the sandbox to the merchant test environment.
32
32
33
-
**Authentication**
33
+
#### Authentication
34
+
34
35
You will have to integrate with the new and simplified Access Token API designed for the merchant test environment. The old MobilePay-issued API key for the sandbox will cease to function. [Access token API guide](https://developer.vippsmobilepay.com/docs/APIs/access-token-api/) Prod API keys will continue to work.
35
36
37
+
### Headers and endpoints
38
+
You must include these headers for all requests to the API
0 commit comments