Skip to content

Commit 4f807bd

Browse files
Update detecting-mobilepay.md
1 parent 7b04897 commit 4f807bd

File tree

1 file changed

+4
-30
lines changed

1 file changed

+4
-30
lines changed

docs/pos/detecting-mobilepay.md

+4-30
Original file line numberDiff line numberDiff line change
@@ -2,35 +2,9 @@
22
sidebar_position: 3
33
---
44

5-
# Detecting MobilePay
5+
:::caution
66

7-
There are two ways in MobilePay PoS for a terminal/client to become aware that MobilePay has been chosen by the customer as the payment option: User activation and Notification service.
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/
89

9-
## User activation
10-
11-
This is the default way of detecting MobilePay presence. In a supermarket, this can be a button on the ECR (Electronic Cash Register) that sends the payment request to MobilePay. For example, the cashier will ask the customer or infer from the customer's actions which payment option the customer wants to choose and then push the MobilePay button. Another example of user activation is when the customer can choose MobilePay themselves on a keypad placed on a vending machine. Some vending machines only allow MobilePay to be used and therefore any request for the vending machine product would be inferred as a payment request to MobilePay.
12-
13-
[<img
14-
src={require('/img/pos-MobilepayButton.png').default}
15-
alt="MobilePay button"
16-
width="700"
17-
/>](/img/pos-MobilepayButton.png)
18-
19-
A last example of a user activation is in the case of a QR code being displayed in a terminal. Once the QR code is displayed,
20-
the terminal may start polling the endpoint `GET /v10/pointofsales/{posId}/checkin` to determine if a customer has checked in. The terminal may only poll for a check-in while the QR code is displayed on the terminal to ensure the check-in endpoint is not overloaded with requests.
21-
22-
[<img
23-
src={require('/img/pos-polling.png').default}
24-
alt="Polling"
25-
width="800"
26-
/>](/img/pos-polling.png)
27-
28-
## Notification service
29-
30-
Some interfaces do not include a possibility for user activation. In these cases an endpoint can be exposed by the MobilePay PoS integrator. This endpoint will be called with a check-in notification when a customer checks in. After receiving a notification the client can poll the `GET /v10/pointofsales/{posId}/checkin` endpoint for that PoS. For more details see [Notification Service](/docs/pos/notification-service).
31-
32-
[<img
33-
src={require('/img/pos-BeaconIDRead.png').default}
34-
alt="Beacon"
35-
width="700"
36-
/>](/img/pos-BeaconIDRead.png)
10+
:::

0 commit comments

Comments
 (0)