|
2 | 2 | sidebar_position: 2 |
3 | 3 | --- |
4 | 4 |
|
5 | | -import Tabs from "@theme/Tabs" |
6 | | -import TabItem from "@theme/TabItem" |
7 | | -import TestApp from '/docs/shared-blocks/_test-app.mdx'; |
| 5 | +:::caution |
8 | 6 |
|
9 | | -# Test |
| 7 | +Please notice that as part of the merger between MobilePay and Norwegian Vipps, we will consolidate products on one joint platform. |
| 8 | +This product is now closed. Please visit our new developer documentation to see the new APIs we offer https://developer.vippsmobilepay.com/ |
10 | 9 |
|
11 | | -In this section, you can find information on testing, and our test ressources. To ensure a good user experience, we recommend you to test your solution thoroughly before certification and launch. |
12 | | - |
13 | | -## MobilePay PoS Sandbox Environment |
14 | | - |
15 | | -We have provisioned a sandbox environment for integration purposes The environment is the same bits and bytes as the production environment, with a few exceptions: |
16 | | - |
17 | | -* No actual payments and reservations are made. The payment backend have been mocked, and the transactions are kept in sandbox storage. This means that transactions won’t be visible in the test app activity list, and no app notifications are sent. |
18 | | -* Loyalty card system is also mocked, and static loyalty card information is returned when applicable |
19 | | - |
20 | | -**Audience**: The test environment is meant for PoS integrators to be able to test integrations against the MobilePay PoS platform. It is an isolated environment that behaves as in live production, thus enabling PoS integrators to fully test the PoS API and business logic. |
21 | | - |
22 | | -**Background**: The environment is strictly meant for carrying out tests and development tasks towards certification. |
23 | | - |
24 | | -**The API**: The Merchant API in the sandprod environment is identical to the live production API. |
25 | | - |
26 | | -To complete a payment flow in the sandprod environment you will need to make user actions. To do so you have to options: |
27 | | - |
28 | | -* User simulation API: The API mimick the actions of a user and allows you to check in on a beaconId, accept and cancel a payment. |
29 | | -* Test app: This version of the MobilePay app is similar to the live version, but only supports payments in the sandprod environment. |
30 | | - |
31 | | -## Test app |
32 | | - |
33 | | -<TestApp /> |
34 | | - |
35 | | -## User simulation API |
36 | | - |
37 | | -To complete a payment flow in the sandprod environment you will need to make user actions. We have made an API that can mimick the actions of a user. You find it in the [API documentation](/api/pos#tag/User-Simulation). |
38 | | - |
39 | | -With the API you can do the following: |
40 | | - |
41 | | -* Perform a check in on a beaconId |
42 | | -* Accept a payment |
43 | | -* Cancel a payment |
44 | | - |
45 | | -You must subscribe to the User simulation API, before you can use it. When calling the API, you must supply: |
46 | | - |
47 | | -|Input| Source| |
48 | | -|--|--| |
49 | | -|**BeaconId**|Created through the PoS API| |
50 | | -|**Phonenumber**|See below list of test users| |
51 | | - |
52 | | -### How to use the User simulation API |
53 | | - |
54 | | -1. Perform a check in on a beaconId: `POST /app/usersimulation/checkin` |
55 | | -2. Initiate a payment through the PoS API: `POST /api/v10/payments` |
56 | | - * Accept the payment: `POST /app/usersimulation/acceptpayment` |
57 | | - * Cancel payment: `POST /app/usersimulation/cancelpaymentbyuser` |
58 | | - |
59 | | -To perform a check in and payment accept, you must supply a phone number for a test user. Below you find a list of test users with different features. |
60 | | - |
61 | | -## Test user |
62 | | - |
63 | | -When using the test app or user simulation API, you must use a test user. Below you can find a list of user ids for Denmark and Finland. If there is an issue with a test user please contact us. These test users are only to be used for for MobilePay PoS test. If you need a test user for a different product please visit the relevant product pages for more information or contact us at [email protected] |
64 | | - |
65 | | -:::caution |
66 | | -Below users are shared amongst all PoS integrators and receipts for all test transactions are visible in the activity list. Please note that the PoS name (defined in CreatePosRequest) is visible on the receipt. Therefore do not include any sensitive or confidential data in the PoS name. |
67 | 10 | ::: |
68 | | - |
69 | | -<Tabs |
70 | | -defaultValue="dk" |
71 | | -values={[ |
72 | | -{label: 'DK test user', value: 'dk'}, |
73 | | -{label: 'FI test users', value: 'fi'}, |
74 | | -]}> |
75 | | - |
76 | | -<TabItem value="dk"> |
77 | | - |
78 | | -|Phone number|PaymentSource|Feature| |
79 | | -|--|--|--| |
80 | | -|+45 20031801|Credit|Credit card| |
81 | | -|+45 20031802|Debit|Debit card| |
82 | | -|+45 20031803|Credit|Credit card| |
83 | | -|+45 20031804|Credit|Loyalty| |
84 | | -|+45 20031805|Credit|Partial capture| |
85 | | - |
86 | | -</TabItem> |
87 | | - |
88 | | -<TabItem value="fi"> |
89 | | - |
90 | | -|Phone number| PaymentSource|Feature| |
91 | | -|--|--|--| |
92 | | -|+358 200318001|Credit|Credit card| |
93 | | -|+358 200318002|Debit|Debit card| |
94 | | -|+358 200318003|Credit|Credit card| |
95 | | -|+358 200318004|Credit|Loyalty| |
96 | | -|+358 200318005|Credit|Partial capture| |
97 | | - |
98 | | -</TabItem> |
99 | | -</Tabs> |
0 commit comments