Step 2:  Finish consent flow 

When the Merchant is logged in, the MobilePay Portal presents the Merchant with a consent screen. When the Merchant clicks yes and thereby gives consent, then the Merchant is redirected back to the integrators website/environment. The authentication experience includes a consent screen that describes the information that the user is releasing and the terms that apply. The consent screen also presents information such as your Third Party name, logo, and a homepage URL.  

Step 1 - Register as an integrator 


  1. Sign up as an integrator  on the MobilePay website here . You will be contacted by our Business unit, and they will send you a Certification Agreement, that needs to be signed.
  2. Take a look at the API documentation on the Developer Portal You'll find it in the APIs menu.
  3. You should already have received an e-mail from developer@mobilepay.dk with an invitation to our Sandbox environment. That e-mail elaborates the next technical steps.  That e-mail contains a testmerchant and OIDC credentials. 
  4. Go to sandbox-developer.mobilepay.dk and log in with your credentials. You log-in using your e-mail and self-chosen password. 

Step 2 - Authentication


Once you have obtained credentials via zip file, sent the redirect URI to developer@mobilepay.dk and received a test merchant (step 4 from above), you can start implementing the OpenID Connect flow.  

Currently, our network utilizes the global IP range 212.93.32.0/19. As an external party, you might need to modify your firewall rules to allow traffic from us from 212.93.32.0/19 and 185.218.228.0/22 instead. Otherwise our traffic may be blocked, and our services stop working.

Step 3 - Create an App  


  1. Next you select your account > My Apps Create new App to register a new application.
    1. IMPORTANT: Please make a note of your Client Secret as you will only see this once! You need to supply the x-ibm-client-id and x-ibm-client-secret when calling the api. 


You should always store the Client Secret in a secure location, and never reveal it publicly. If you suspect that the secret key has been compromised, you may reset it immediately by clicking the link on the application details page.

Step 4 -  Subscribe to APIs


To implement MobilePay Subscriptions or MobilePay Invoice, go to APIs and subscribe to the following APIs:

  • Subscriptions
  • Subscriptions User Simulation
  • Invoice
  • Invoice User Simulation

And now you can call the api :)

Third Party  - Consent flow 

 

  1. The user (Merchant) wants to grant the Integrator permission to handle their solution.
  2. The Merchant initiates the flow on the Integrator website, or by contacting the integrator for instructions.
  3. The Merchant is redirected by the Integrator and thereby logs-into https://admin.mobilepay.dk.
  4. The Merchant grants the Integrator consent.
  5. The Merchant gets redirected back to Integrators environment.

The integrator can now manage the MobilePay solution on behalf of the Merchant.

It is not possible to have two different integrators managing the same product 
Integrator Environment 

You need to adhere to MobilePay branding requirements, as the merchant experience is relied heavily on the visual system for look and feel. The following is a short checklist. When you are providing MobilePay Invoice, we need to see 

  • Logo
    • The MobilePay logo should be clearly displayed
    • The logo should not be altered   
    • Ensure you use our logo, that you can download here
  • Redirect
    • When the consent process is completed, the Third Party Integrator should direct the enduser to a suitable landing page 
  • MobilePay button 
    • Leverage our brand guidelines, and display our assets 
    • Ensure you use our assets, that you can download here.
  • Invoice creation
    • Do you communicate that the customer should order Invoice first on https://admin.mobilepay.dk ?
    • How easy is it for the customer to send an invoice? 
    • Do you have a pop up to promote Invoice for your existing customers, that do not have MobilePay Invoice?

Note: we need to verify your flow, as your graphical interface is also a part of our verification. We need to have a demo from you that showcases that an MobilePay Invoice can be successfully sent through your system. This can be done by providing us with test credentials to your environment, so we can test it ourselves, and/or if we have a Skype demo screensharing session. 

Integrator Buttons
As an integrator, your focus is that the merchant quickly establishes the MobilePay product through your environment. Using our MobilePay buttons will add quick context for the merchant.
We provide the button in blue, dark blue and white, for use on dark/coloured backgrounds.

Brug MobilePay

For use on white or light-colored backgrounds that provide sufficient contrast. Do not place a black button on a black or very dark background; instead, select the white button option shown below.

MobilePay Blue


White

The white button is for use on colored and dark backgrounds, where the blue is ill fitting.

White with stroke


White on colour


Dark blue

Can be used for websites with an already heavy use of blue.

Dark blue


Start her

We provide the button in blue, dark blue and white, for use on dark/coloured backgrounds. 

Start her

For use on white or light-colored backgrounds that provide sufficient contrast. Do not place a black button on a black or very dark background; instead, select the white button option shown below.

MobilePay Blue


White

The white button is for use on colored and dark backgrounds, where the blue is ill fitting.

White with stroke


Dark blue

Can be used for websites with an already heavy use of blue.

Dark blue


 
Integrator Badges

Please note you cannot use the badges below, if the MobilePay Developer Support team hasn't reviewed your integration. If necessary, our team will provide feedback to ensure that your integration meets the MobilePay Integrator requirements and follows our best practices. 

Step 3 - Landing Page  

Now that the merchant has granted consent via OIDC, we can now move on to illustrate for new and other merchants the Subscriptions and Invoice product value proposition from your context.

Previous step Step 3