Step 1:  Get Started

The 1st step is to familiarize yourself with the process, so you know the next actions, when you are adding MobilePay Invoice or MobilePay Subscriptions payments to your Third Party platform. 

Process 
  1. Integrator Onboarding
    1. Sign up as an integrator here and choose the API product 
    2. Sign certification agreement and send it to MobilePay Partner  
  2. Technical onboarding
    1. We will send an invitation to you to our Sandbox environment 
    2. Integrate Invoice (read more here)
    3. Integrate Subscriptions (read more here)
  3. Adhere to branding guideline 
    1. Use the Integrator Badge
    2. Use the correct buttons (you'll find them on this site)
    3. Provide a landing page that will be used on www.mobilepay.dk to promote you as an integrator 
  4. Demonstrate integration to developer@mobilepay.dk
    1. You are not certified unless you've had a demo session via MS teams. After the session, the DeveloperSupport team will evaluate the merchant onboarding, ease of integration and reconciliation handling, and revert back to you within 24 hours with an answer, whether you have been certified or not. 
Integrator & Merchant's responsibility

The Merchant can choose to

  1. integrate to our api directly
  2. they can choose to make use of the certified integrators.

If the Merchant decides to have the solution established via an integrator, the responsibility is as follows:

The Merchant

  1. The Merchant orders the MobilePay solution on the MobilePay Portal and enters an agreement with MobilePay.
  2. The Merchant chooses the integrator.
  3. The Merchant can always revoke consent to their existing integrator. 
  4. The Merchant has access to the MobilePay Portal

MobilePay

  1. MobilePay sends the callbacks.
  2. MobilePay helps the Integrator with their certification.

The Third Party integrator

  1. The Third Party integrator signs the Certification Agreement 
  2. The Third Party integrator administers the data for the merchant.
  3. The Third Party integrator configures the payment_status_callback url so callbacks for all subscriptions agreements and payments are received.
  4. The Third Party integrator receives Release Notes.
  5. The Third Party integrator implement features that the merchant wishes to have implemented.
  6. The Third Party integrator does normally not have access to the MobilePay Portal. It is possible to have a multiple user assigned to the MobilePay Portal. However, it is up to the Merchant. 
  7. The Third Party integrator has access to the Developer Portal 
  8. The Third Party integrator is able to help the Merchant with reconciliation using the Transaction Reporting Api

 Right now, an API product can only be managed by 1 integrator. Multiple integrators cannot manage the same API product.

Migrating from one integrator to another

If a Merchant needs to remove their existing integrator and connect to the new integrator, and the Merchant has existing payment details stored with another Integrator, note that all parties need to reserve some lead time. 

An example: If one company Carwash  is overtaking another company, named Housewash, and thereby also overtaking company Housewash CVR number, MobilePay can assist in moving the agreements, payments from the "old" company Housewash to the new one.

 

However, if the company is not overtaking the CVR number, it is not possible for MobilePay to move the already created agreements due to legal reasons. In that case, the company needs to inform all existing customers on the existing solution, so the customers can create a new agreement on the new CVR number. 

 

Merchant process 

  1. Merchant logs in to MobilePay Portal with merchant credentials
  2. Merchant clicks 'indstililnger' in the menu on the left
  3. Merchant clicks 'integration'
  4. Merchant clicks 'x' to remove the existing integrator

The access_token expires after 5 minutes. Therefore, there is a delay, where the previous integrator still can use the access_token until it expires. However, the refresh_token will not be able to be used, and then the previous integrator will not be able to get a new access_token. This is why we want to have short lived access_token, as refresh_token have a longer lifespan of 1 year, until they can be revoked.

Change Third Party Integrator process

  1. Merchant initiates the flow from integrator environment or link 
  2. Merchant is redirected by the new integrator and logs-into MobilePay Portal
  3. Merchant grants the new integrator consent
  4. Merchant gets redirected back to integrators environment.  

Once step 4 has been executed, the new integrator can get access to the existing debits that have been sent by the previous integrator. We have API GET calls that help you with that.

Because Third Party integrators often need some time on migrations, MobilePay advises getting in touch with the existing Third Party integrator as soon as possible

 

Useful migration Subscriptions API calls

  • Get the list of Subscriptions agreements
  • Get agreement details.
  • Get a list of one-off payments by agreement ID.
  • Get a list of agreement's payments.
  • Get single one-off payment details by ID.
  • Get single payment details by ID.

Checklist

  • Configure the /payment_status_callback_url 
    •  /payment_status_callback_url is configured on Payment Point level.  As of now, a previous integrator can still have their old /payment_status_callback_url  registered. Therefore, it is important that the new integrator patches the /payment_status_callback_url so the previous integrator does not get spammed with callbacks for payments that they are no longer managing. 
  • Coordinate the usage of all mandatory and obligatory parameters for agreements, payments and one-off payments with the merchant, so you as their new integrator ensure, that the Merchant needs are fulfilled. 
    • Important: Ensure that usage of external_id matches the new integrator needs. If it doesn't match, you can patch the external_id 
  • Coordinate regarding the last debits from the previous integrator and the upcoming debits
  • Do not e-mail or otherwise send sensitive customer information directly to MobilePay. If you are in need of data, please get in touch, so we can securely transfer your data. 

Step 2 - Efficient consent

MobilePay uses OpenID Connect (OIDC) as the integration protocol. OIDC is a secure solution to Merchants, who require user consent when Third Party accesses data through an MobilePay API. The purpose of Step to is that Third Party Integrators establish an efficient consent process with the Merchants. 

Step 2