An integration is considered finished when all the elements of the relevant API’s checklist are done

Get started

1. Read API documentation. You’ll find it in the APIs menu. The API documentation provides insight into the structure of the API and will help you determine the best approach for integration as well as provide details on typical use cases.

2. Log-in Go to Sandbox developer portal and log in with your credentials.

3. Create app - My Apps > Create new App to register a new application. 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 x-ibm-client-id 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.

4. Subscribe to APIs. To implement MobilePay Subscriptions, go to APIs and subscribe to the following APIs:

   • Subscriptions
   • Subscriptions User Simulation

Step 2 - Authentication

Once you have

• 1. Have a whitelisted redirect_uri (Send an e-mail to developer@mobilepay.dk with your redirect_uri and we will revert back to you, once it has been whitelisted.
• 2. Received OIDC credentials via zip file. The zip file will be sent via e-mail. The zip file is locked with a password. DeveloperSupport will provide the password via text message, due to security reasons.
• 3. Received testmerchant

you can start implementing the OpenID Connect flow. Read more about OpenID Connect and the process here

If you have any questions, please write to developer@mobilepay.dk

Step 3 - Test

• 1. Create a new Agreement
• 2. Accept the Agreement*
• 3. Request a payment
• 4. Decline the pending Subscriptions payment
• 5. Request a new Subscriptions payment and wait until due date for this to execute
• 6. Cancel the Agreement once the Subscriptions payment has been executed
• 7. Refund the Subscriptions Payment
• 8. Request OneOff payment
• 9. Cancel the reserved/requested OneOff payment
• 10. Request a new OneOff payment
• 11. Accept the OneOff payment*
• 12. Capture the OneOff payment
• 13. You must also have a setup for handling cancelled orders, and cancel reserved payments

Step 3 - Avoid Integration pitfalls

• 14. The Merchant must not rely on user-redirect. All proper data comunication and logging and monitoring should be done thorugh callbacks and GET calls.
• 15. The MobilePay branding must be according to the MobilePay design guidelines
• 16. The Merchant must have a way for the user to manage and stop subscription if the merchant is using cancel-redirect. This should result in a timely update of the MobilePay Agreement.
• 17. Follow the external_id recommendations
• 18. Correctly handle callbacks from MobilePay, both for successful and unsuccessful payments.

Third Party integrators

In addition, all Integrators are required to complete the following:

• Technical documentation for Merchants
  • Documentation for merchants regarding how to apply for MobilePay products on the MobilePay Portal
  • Documentation for merchants regarding how to configure and use the Integrator module. This includes ensuring that the Merchant can customise the agreement parameters (amount, plan, frequency description, next_payment_date) and payment screens parameters (description, next_payment_date, external_id).
  • FAQ for merchants
• Provide one pilot customer to verify the integration in production environment

When the integration checklist is completed, notify the MobilePay Developer Support, who will verify the integration, and contact the Integrator.

MobilePay then adds the integrator to the MobilePay Website

Once you have followed the steps above, you are ready to do the self-certification. Click the “I’m ready” button here