|
2 | 2 | sidebar_position: 3 |
3 | 3 | --- |
4 | 4 |
|
5 | | -# Self-certification |
| 5 | +:::caution |
6 | 6 |
|
7 | | -After your test is complete you must complete a self-certification in order to get access to the production API and go live with your integration. MobilePay provides an automatic certification process where it is possible for most integrators to create a fully automated self-certification. The certification concludes with an automated report on how the certification went. For the PoS API all Major and Minor versions of clients must be certified. |
| 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/ |
8 | 9 |
|
9 | | -## Access to self-certification |
10 | | - |
11 | | -Before you can start self-certification you must have a signed agreement with MobilePay and receive a production clientId. |
12 | | -When your test is completed and you wish to start self-certification please [contact Developer support ](mailto:[email protected]) to request production security credentials that will include the production clientId needed for the certification. |
13 | | - |
14 | | -:::info Note |
15 | | -Production security credentials are not to be used for self-certification because this is performed in sandbox. Therefore you must use your security credentials from sandbox. The production security credentials should be used for production after self-certification. |
16 | | -::: |
17 | | - |
18 | | -## Self-certification process |
19 | | - |
20 | | -The Self Certification process has four steps: Identification, Selection, Certification and Approval. |
21 | | - |
22 | | -:::note |
23 | | -The bottom of this page contains configuration details for your client. You will need to use our self certification store, merchant and URL instead of your test credentials. |
24 | 10 | ::: |
25 | | - |
26 | | -### Identification Step |
27 | | - |
28 | | -In the first step the Integrator identifies themselves in the tool. The following information is needed: |
29 | | - |
30 | | -* Client IDs for Sandproduction and Production - ID created on the MobilePay Developer Portal which identifies the client to be certified. Each Integrator is allowed to create multiple Client IDs, however it is also acceptable to have just one Client ID. |
31 | | -* Version numbering - The three dimensional number that defines the version of the Client that needs to be certified. See [Client Identification](/docs/pos/api-principles#client-versioning) |
32 | | -* Client system name - the name of the software being certified. |
33 | | - |
34 | | -[](/img/pos-identificationstep.png) |
35 | | - |
36 | | -### Selection Step |
37 | | - |
38 | | -In the second step the Integrator selects which major features to certify. There are the following major features in MobilePay PoS API v10: |
39 | | - |
40 | | -* Onboarding - The mandatory proces of creating a Point-of-Sale on the MobilePay backend. |
41 | | -* Payments - Certification in sections of the API necessary for doing a simple payment. |
42 | | -* Prepared payments - Certification in sections of the API necessary for doing a prepared payment. |
43 | | -* Payments with restrictions - Certification in sections of the API necessary for handling restrictions to payments. |
44 | | -* Prepared payments with restrictions - Certification in sections of the API necessary for handling restrictions to prepared payments. |
45 | | -* Refunds - Certification in sections of the API necessary for handling refunds. |
46 | | - |
47 | | -[](/img/pos-categories_step.png) |
48 | | - |
49 | | -### Certification Step |
50 | | - |
51 | | -In the third step the integrator goes through all the different certification cases necessary using their client. In this step it might be necessary to operate the client to go through the different steps of a certification case. |
52 | | - |
53 | | -[](/img/pos-onboarding-cases.png) |
54 | | - |
55 | | -### Approval step |
56 | | - |
57 | | -In the fourth and final step the Integrator gets a certificate proving that the client is certified. It is now possible for the client to access production. |
58 | | - |
59 | | -In general, we urge all integrators to use this tool to do continuous testing. It is a requirement to re-certify when upgrading major or minor versions. We also recommended to use the tool when making new build versions. The tool will never retract a certification from a client version that has already been certified. Retraction of a certification will only be done after an individual evaluation by MobilePay based on input from production. |
60 | | - |
61 | | -[](/img/pos-approvalstep.PNG) |
62 | | - |
63 | | -### Configuration details |
64 | | - |
65 | | -Please use the following data for configuring your client before commencing self certification. |
66 | | - |
67 | | -| Self Certification info | | |
68 | | -|---|---| |
69 | | -| Website link | [https://pos-certification.mobilepay.dk/mobilepay-pos-selfcertification-website/index.html](https://pos-certification.mobilepay.dk/mobilepay-pos-selfcertification-website/index.html) | |
70 | | -| PoS self-certification API base URL | [https://api.sandbox.mobilepay.dk/pos-self-certification-api/pos/v10](https://api.sandbox.mobilepay.dk/pos-self-certification-api/pos/v10) | |
71 | | -| Integrator Authentication API base URL | [https://api.sandbox.mobilepay.dk/integrator-authentication](https://api.sandbox.mobilepay.dk/integrator-authentication) |
72 | | -| merchantLocationId | 00001 | |
73 | | -| merchantBrandId | MPPOSCERT1 | |
74 | | -| VAT number DK | 90000028 | |
75 | | -| VAT number FI | 90000040 | |
0 commit comments