Integration Checklist

The comprehensive checklist to integrating with Number

Integrating payment processing into your system can be a daunting task. To help you on this journey, we've prepared a checklist which describes all the steps required from creating a Number account to going live, including the design, development, and testing.

1

Create a Number account and obtain credentials: 1-2 days

Sign up for a Number Sandbox account to gain access to the platform and its features. Ensure you have all necessary business information ready for registration.

Contact us to sign up for a Number Sandbox account: [e-mail] / [phone]

After account creation, retrieve the necessary credentials from the Number Client Admin Portal. This will be essential for encryption and authentication.

2

Choose your integration methods: 1-2 days

Read about the Integration Options and decide which one best suit your business needs. Options include:

• REST API and the PayForm: Utilize the Number API and a customizable pre-built payment form that can be integrated directly into your site.

• Verifone: Collect payments using Verifone card readers with our software.

• Mobile SDK: If you have a mobile application, use the Number SDK for in-app payments.

• Virtual Terminal: A web application for processing payments directly through a browser.

You can find guides that will help you learn how to navigate each integration method on the Integration Options page.

For example: PCI Level 1 clients can use a purely API integration, while others would need to implement a PayForm for collecting cardholder data directly through their website.

3

Develop a payment workflow: 1-2 days

Outline all interaction points in your current workflow where payments might be collected.

Define your requirements for various types of payment processes and equipment (card readers, web payments, card-present transactions, back-office processes, and reporting mechanisms).

4

Develop the frontend components: 1-2 weeks

If you are using the mobile SDKs or the Virtual Terminal, you can skip this step as you won't need to develop any additional frontend or UI components.

Create the frontend components necessary for user interaction.

5

Develop the EMV integration: 1 week

Unless you want to use Verifone card readers or other card readers, you can skip this step as you won't need the EMV integration.

Implement EMV functionality provided by our Windows service or SDK to support chip card transactions. Read the Verifone guide to learn how to use these services.

6

Develop the backend integration: 2-3 weeks

Depending on the scope of your integration, it might take less time. Also, you can skip this step if you only plan on only using the Virtual Terminal.

Write the server-side logic to handle payment processing, invoking our services. Develop data management, coupling your users with the payment activities by storing consent or transaction IDs, and optionally storing transaction amounts for reconciliation.

7

Develop the processes for logging, reporting, and reconciliation: 1 week

Set up basic logging where applicable. Consult us to set up reporting and reconciliation processes. They will allow you to track transactions and ensure financial accuracy.

8

Test your integration on a development environment: 1-2 weeks

Before going live, thoroughly test your integration in a sandbox environment. Ensure that all payment flows work as expected and that you can handle various transaction scenarios. You can read more about using the sandbox in the Testing section. Conduct unit testing to validate the integration functionality before going live, ensuring all components work as intended.

9

Number inspection: 1-2 meetings

The Number team always inspects the workflow that our clients develop prior to going live.

10

Go live: 1 day

Once testing is complete and you are satisfied with the implementation, switch to the production environment. Update your configuration as necessary.

11

Monitor and maintain: continuous

Once you go live, monitor your integration to make sure there are no problems. Work on improvements and fixes as required.