Skip to content

Commit 5d021c5

Browse files
Update test.mdx
1 parent d25e91b commit 5d021c5

File tree

1 file changed

+1
-49
lines changed
  • docs/app-payments/development-guide

1 file changed

+1
-49
lines changed

docs/app-payments/development-guide/test.mdx

+1-49
Original file line numberDiff line numberDiff line change
@@ -5,52 +5,4 @@ import TestApp from '/docs/shared-blocks/_test-app.mdx';
55

66
# Testing
77

8-
This page includes information to make sure your integration works as planned. Testing activities will be done in a sandbox environment and it won't create any real payments.
9-
10-
## MobilePay sandbox environment
11-
12-
The sandbox environment is dedicated for integration purposes. It is the same as production with some limitations (not a full list):
13-
14-
- No actual payments and reservations are made.
15-
16-
## Test merchants
17-
18-
You will receive details for a test merchant to use in a sandbox environment during your onboarding. It will allow you to login to [Sandbox MobilePay portal](https://sandprod-portal.mobilepay.dk/) to [generate API keys](/docs/app-payments/authentication), and/or to [set up Payment Points](/docs/app-payments/payment-points) for your testing purposes. It is a valuable experience since you will need to do the same activities when moving to production.
19-
20-
## Test users
21-
22-
You will receive information about test users during your onboarding. You will have a dedicated test user which you will be able to use to login into [MobilePay Test App](#test-app)
23-
24-
## Test app
25-
26-
In order to complete a payment flow in the sandbox environment, a test version of the MobilePay app is available. This version of the MobilePay app is similar to the live version, but only supports payments in the sandbox environment. You can only use the test users that we provide to you.
27-
28-
:::note
29-
30-
Do not use the test phone number in the production environment, as it might be a real user there.
31-
32-
:::
33-
34-
<TestApp />
35-
36-
:::caution
37-
**MobilePay Sandbox** app supports not only it's own schema `mobilepay-test://` but also the production schema `mobilepay://`. This means that some of you may experience issues in iOS when trying to make a real production payment, sandbox app would open.
38-
To circumvent this you could try closing MobilePay Sandbox app and opening MobilePay so that it's running in the background while doing the production payment. Read more on how to close an app: https://support.apple.com/en-us/HT201330.
39-
:::
40-
41-
## Integration tests
42-
43-
We also have a Payments Testing API in sandbox environment, which has only one endpoint for simulating user's swipe in MobilePay app. You can use that to setup integration tests or in any other way where it fits you.
44-
45-
```bash title="Simulate user swiping and confirming the payment in MobilePay app."
46-
curl https://api.sandbox.mobilepay.dk/v1/integration-test/payments/{PAYMENT_ID}/reserve \
47-
-X POST \
48-
-H 'Authorization: Bearer {API_KEY}' \
49-
-H 'Content-Type: application/json' \
50-
-d '{
51-
"paymentSourceId": {UUID},
52-
"userId": {UUID}
53-
}'
54-
```
55-
56-
`paymentSourceId` and `userId` are unique for your test users. You will receive these values during onboarding.
8+
Please read [here](https://developer.mobilepay.dk/docs/app-payments/transition-to-one-platform#test-options)

0 commit comments

Comments
 (0)