Step 3 - Verification

Once you have finished testing in sandbox, you have to go through a small verification process, to ensure that your system is ready for production. We expect that you have tested all the features listed below, before you start the verification process. Then it can be completed in a day.

Once we have verified that the steps has been completed successfully, you are ready to start testing in production.

 
Verification Process - Sandbox

To complete the verification, you must go through the steps listed below. This is done to ensure good user experience from the customer side. It is mandatory to test Subscriptions Payments, OneOff and Agreements in sandbox, even if you do not intend on implementing all functions right away. The sandbox environment is designed to be close to the production environment, which makes the process from sandbox to production smother. 

When completing the steps, you must use a unique id as external_id. It must be unique in the sense that it is unique to your test, and therefore you cannot reuse an external_id from previous tests. Besides that, it can be whatever you like, with a maximum of 30 characters. You need to create three ids: one for agreements, one for a regular payment and one for a One-Off payment. Please send us an email with the three ids when you are ready to start the verification, and you can go ahead with the process. 

Example of external_id
"external_id": "CompanynameAgreement"

 

Agreement and subscriptions payment

1. Create a new agreement
2. Accept the agreement* 
3. Request a payment
4. Decline the pending payment
5. Request a new payment and wait until due date for this to execute
6. Cancel the agreement once the payment has been executed

Refund

7. Refund the subscriptions payment

OneOff payments

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
*Use the Subscription User Simulation API to complete this.

Internal Acceptance Testing

You should do smoke testing quick in the process to check the stability of the build received for software testing. You should verify that the software is stable enough for further testing. Afterwards, we recommend that you do Internal Acceptance Testing. The testing is performed by members of the organization that developed the software but who are not directly involved in the project (Development or Testing). Usually, it is the members of Product Management, Sales and/or Customer Support. User Acceptance Testing is performed by the end users of the software. They can be the customers themselves or the customers’ customers. 

Going from Sandbox to Production 
MobilePay Subscriptions

Sandbox

  1. Read documentation on Portal and on GitHub.
  2. Confirm user for Sandbox Developer Portal here.
  3. Create app here.
  4. Subscribe to Api's here.
  5. Get OpenId Credentials (Read More here)
  6. Make the first call to Sandbox API. 
  7. Test Subscriptions (Read more here).
  8. Set Payment Callback URL (Read more here).
  9. Set Callback Authentication Scheme (Read more here).
  10. Complete verification (Read more here).

Production 

  1. Confirm user for Production Developer Portal here.
  2. Create app here.
  3. Subscribe to API here.
  4. Get OpenID Connect Credentials. Read more here
  5. Set Payment Callback URL (Read more here).
  6. Set Callback Authentication Scheme (Read more here).
  7. Create agreement.
  8. Request a Subscription Payment.
  9. Document customers sign-up flow to developer@mobilepay.dk and ensure you've followed our UX guidelines
  10. When the Subscription Payment is executed, request for review from developer@mobilepay.dk
  11. Await approval from developer@mobilepay.dk
  12. Sign up for operational maillist. 
  13. Keep updated on MobilePay Subscriptions release notes on https://mobilepaydev.github.io/MobilePay-Subscriptions/release_notes
Step 3.1 - Test checkout flow

Once you have finished the technical verification in sandbox, the next step is to ensure that the UX is on point. You can ensure that, by testing it. Your ecommerce checkout flow is where the money is at. Think about it. Random visitors leave the site before ever entering the checkout funnel. Motivated buyers come here to finish their order.