Step 4: Implementation

When your merchant is implementing MobilePay Invoice or Subscriptions using a third-party platform, you - the third party - should have and provide more information on how to approach the implementation.

New Features and current certification

The Subscriptions and the Invoice API is continuously getting new features, and as an integrator, you are expected to keep your integration up to date and read the recent updates. 

Release Notes and changelogs

For details about the newest releases, you can find the release notes on

  • GitHub Subscriptions here
  • GitHub Invoice here 

If you have subscribed to our newsletter here, you will also receive the release notes by e-mail. 

Be sure to check out all the new features and known issues.  New features can involve new calls, new capabilities and/or new fields added to existing calls. We greatly appreciate your bug reports and feature requests, which help us make MobilePay API's better. If you encounter a problem, let us know by reporting a bug


Use the checklists to help track your progress through the integration phase. Depending on your integration, you might have other items to track that aren't listed.

Remember to write to if you have any further technical questions.

Transaction Reporting Api 
  • It is a standard practice for Merchants of all shapes and sizes to utilise various financial practices and keep operations running smoothly. One of the most important of these is reconciliation, which is why certified integrators should be able to help Merchants with reconciliation for MobilePay Invoice and MobilePay Subscriptions.
  • The Merchant can export simple excel files from the MobilePay Portal, but that is rarely enough for larger organizations. The process of reconciliation has historically been a manual one. Many Merchants have now embraced auto-reconciliation to streamline the process and create efficiencies, and this is where the MobilePay Transaction Reporting Api comes to play.
Third Party Integrator - API Checklist  

The goals of the integration plan are to: Confirm the functionality of the integration and create a plan for fine-tuning where required.

Phase Tasks of a Third Party integration Responsible  Time

 0 Onboarding 

Third Party Integrator Onboarding 
  • 0.1 The Third Party integrator signs up in a few simple steps here 
  • 0.2 Sign certification agreement  
Business  1h 

1 Scoping

  • Learn about key onboarding components and start to make integration decisions and architect your application’s subscription or billing flow.  Map out the flow that your customers will take through your application (or site) when they adopt and manage subscriptions or recurring billing. Key questions to address are:
    • How do customer cancel their subscription?
    • What is your refunding behaviour when/if ccustomers cancel?
    • what happens if a payment fails?
    • What happens in your application (front-end and back-end) when the customer subscribes?
    • Read GitHub docs for Subscriptions API here 
    • Read GitHub docs for Invoice API here 
 Business + Developers 1h 




Get started  






  • 2.3 Test the API in sandbox
    • Make first call to Sandbox API.
    • Test subscriptions (read more here) For details, see MobilePay Subscriptions Testing documentation.
      • Set payment callback url (read more here)
      • Set callback authentication scheme (read more here)
  • 2.4 Conduct Sandbox verification (read more here


  • 2.5 Configure a Developer Account on
    • Create an app here
    • Subscribe to API's here
  • 2.6 Set up OpenID Connect to production values.
  • 2.7 Test the final actions in the API in Production
    • Create agreement (Read more here)
    • Request Subscriptions Payment (Read more here)
    • We recommend that you test internally within the organisation. Ensure that you have downloaded the newest version of the MobilePay app from the AppStore.

Merchant Engineering organization completes this phase, which MobilePay estimates to typically take about a week.

 1 week

Phase 3

Quality Assessment 

3.0 Assess technical integration 

  • The developer Support team at will review your integration prior going live and answer you within 24 hours.
  • Please include all steps in phase 4 to ensure a quick assessment. 
  • Once the technical verification is finished, we will add you to our operational mailbox.  24 hours

Phase 4 


  • Use the MobilePay Portal to change Subscription payment point 
  • Manage refunds
  • Read Product FAQ

The Finance and Customer Service organizations typically own this phase, which MobilePay estimates to typically take about a week.


1 week 

Phase 5

Go To Market

5.0 checklist 

  • Integrator 
    • Ensure you have a Landing page dedicated for registrating for MobilePay. Read more here 
  • Merchant side 
    • Ensure merchant has informed their employees and customer service about MobilePay Subscriptions.
    • Ensure merchant has FAQ about MobilePay Subscriptions on website. 
    • Ensure you have visible MobilePay buttons (You can do it on your website, newsletters and self-service environment).
    • Ensure you adhere to our Brand Guideline.
  • Ensure you use the right MobilePay logo.
  • Ensure you use the correct Subscriptions assets.

Document final signup flow (forward screenshots of  customer registration/payment flow to or present the flow in a Skype call) 

Tip: Read our inspirational page for Subscriptions here





Remember to write to if you have any further technical questions

Merchant UX 

As an integrator, you need to ensure that the merchant uses the correct MobilePay Logo and buttons. MobilePay buttons give merchants a standard that helps their customers to quickly recognise the MobilePay brand, so the customers can pay instantly using the button.  

Onboarding process

  1. Scoping: Learn about key onboarding components and start to make integration decisions. (1 week)
  2. Integration: Start implementing based on the decisions you made in the scoping phase. Engineering and UX teams complete a lot of the work in this phase, but product managers and other nondeveloper teams are involved in making integration decisions. (3-4 weeks)
  3. TestingAs work is completed in the integration phase, you can start the testing phase. The workload in this phase is often split among several teams. Engineering teams can test charge flows, product managers can test verification flows, finance teams can verify reports and dashboard information, and so on. (1 week)
  4. Training: The training phase is mostly for nondevelopers. Customer service, finance, business, and product management teams are usually involved. Much of the training focuses on using the MobilePay Portal, understanding funds flows and using the Transaction Reporting API, and managing refunds and disputes. (1 week)
  5. Go-to-market: Work on strategies for user adoption and transitioning users to MobilePay from other payment methods. Even though this phase is last, there’s a lot you can work on in the beginning of the onboarding process. Having a strong GTM strategy gives you and your customers a smoother transition to MobilePay.


Ongoing Support & Communication 

Maillist and updates 

We have two mailing lists that are relevant to you :

  • Operational mailing list. We use this to inform external stakeholders about any operational problems. Here we receive one or more email addresses for this list.  
  • Developer newsletter.  Updates to our API are made on a regular basis. When this happens, we send release notes to those who may be interested in it. Please inform us, which e-mail should be the recipient.
  • Release Notes: They can be found on GitHub 


MobilePay DeveloperSupport sometimes get cases handed over from our own support team, where your customers can be involved. In these cases, we would like an integrator email from you, that we can contact for further information about the case, so a solution can be found. 

3. Contact emails at MobilePay:


Onboarding docs
  • When your merchant is implementing MobilePay Invoice or Subscriptions using a third-party platform, you - the third party - should have and provide more information on how to approach the implementation. 
  • The onboarding documentation
    • aims to help new MobilePay merchants make informed decisions to build an integration that’s best for their business and use case.
    • identify considerations such as merchants scope, integrate, test, train cross-functional teams, and bring their product to market. 
  • The onboarding content doesn’t replace MobilePay's product documentation but should be used as an additional resource to aid in building a unique and scalable MobilePay integration.
What's next?

Now that you've gone through the ThirdParty Integrator set-up, why not read our latest news on our page here

Previous step