Frequently asked questions
What are the MobilePay IP addresses?
Note that MobilePay does not require merchants to whitelist specific IP addresses to access REST APIs. We utilize different ranges for the APIs and callbacks as well as for the different environments. We cannot supply specific IPs because we may change IPs within the listed ranges and therefore recommend to whitelist the entire range.
Production: 18.104.22.168/28 and 22.214.171.124/28
Production and sandbox: 126.96.36.199/19 and 188.8.131.52/22
What is the difference between Sandbox and Production
Sandboxes are isolated from your production organisation, so operations that you perform in the MobilePay sandbox don’t affect your production organisation. The production version of the API provides access to the real customer data, i.e. you will be able to initiate real payments. Once you go to test in production, you will use another basepath, the live MobilePay app and a real MobilePay user.
|User||We have test users available. Visit the product sites to find information about test users||A real MobilePay user, that has downloaded the MobilePay app on their smartphone. We do not have test user that you can use in production.|
|Payment limit||Same as in production. Read here: DK - FI|
|Functionality||Sandbox processes API calls in exactly the same manner as the production environment, except you are not dealing with real money and transactions.||Only real transaction can be completed|
How do I, as an Integrator test in production?
Once you have finished testing in sandbox and the verification, you can verify that the set-up is also working in production. This is especially important with regards to using the right redirect URI's in production, and using the right credentials for OpenID Connect in production. You need to update all URLs and credentials to production values.
Once you've done so, there are two possibilities, and you can choose the option, that fits you the best.
Test with your own customer
You can use one of your existing customers as pilot merchant. In order to do so they need to have an active MobilePay agreement and chosen the decired MobilePay product.
Test with your own account
If you do not want to test with your customer, you have the possibility to order the API product yourself, so you have a registration in production. In this case, you'll be marked as an integrator, and will only pay for the transactions, and not the monthly fee.
Payment limit in Sandbox
The behavior of the API when you are in sandbox mode is the same as when your app is live, but comes with the following restrictions. The users in the Sandbox have a daily limit at 3.000 DK. It is recommended to send Payment Requests below 10 DKK or 2 EUR. Be sure to test with reasonable amounts and only run a limited number of transactions.
What is correlationId?
CorrelationId is a unique identifier value that is set as header for each API request
header 'correlationid: REPLACE_THIS_VALUE'
The id serves as reference for the particular API request and makes API support more efficient. If you are having issue with an API request, please include the correlationId. We recommend to use a random GUID as the correlationId.
What is payment reference
If you have one of our MobilePay products, then you can expect to see a Payment Reference in your bank account. Payment reference is a reference that is assigned to payment and is visible in bank account statement when payment is completed and received by your bank. It is usually used for tracking and verifying which payments were received to the bank account (e.g. transfers).
MobilePay specific reference: PCRRRRRRRRJJJDDMMYYX
PC Product code - Products need to identify the product, code is then put when generating the reference.
- 01 = POS
- 02 = MyShop
- 03 = Subscriptions
- 04 = Invoice
- 05 = AppSwitch
- 06 = Online
RRRRRRRR External Payment Point ID (length 8). Myshop number, Pos LocationID etc. External Payment PointID will be sent in the payload from the product.The external payment point ID must be unique within the Merchant for the payment point. For Subscription and Invoice this will consist of 8 zeros (00000000).
JJJ Running number (length 3)
DDMMYY Date (lenght 6)
X Check digit (length 1)
Example: 03000000000011602193 - which indicates Subscriptions payments received 16.02.2019