All pages
Powered by GitBook
1 of 1

Loading...

Authentication

A quickstart guide to authenticating with Number services

Basics

To authenticate to our services, depending on your integration of choice, you might need the following:

1

An account code and token

Using your unique key representing the Number account and the token generated from the Client Admin Portal, you'll be able to authenticate to the REST API.

2

API key

When initializing either of the mobile SDKs, you'll need an API key provided by Number.

3

HMAC secret

If you are PCI Compliant and want to use our REST API to collect cardholder data, some endpoints will require you to append additional data to the session header. You'll be able to generate this header using an HMAC secret provided by us.

4

Username and password

When logging into the Virtual Terminal you'll need a username and password. When logging into the Client Admin Portal this will also require two-factor authentication using a text message to your mobile phone.


REST API

Here's a basic step-by-step guide on how to authenticate with our APIs:

1

Find your account code

This will be provided by Number when you create an account with us.

2

If you want to read more about authentication, see the guide


Android and iOS SDK

Authenticating with the mobile SDKs is very simple. to get an API key, HMAC secret, and an optional Sentry DSN.

After installing the SDK of your choice, you can configure and initialize the EasyPay class.

Android

iOS


Virtual Terminal

To log in and use the features of Virtual Terminal, you'll first need to create accounts for your users through the Client Admin Portal.

To access the portal, . You will be asked to provide the full name, e-mail address, and cell phone number for every individual you wish to have access to the portal. Those individuals will then be able to enter the portal and create new Virtual Terminal users through the portal by entering Manage Accounts > Users through the navigation on the left.

Now, those users will be able to access the Virtual Terminal using the link below.

Create a new token

Use the Client Admin Portal to create a token. If you don't have access to the Client Admin Portal, contact the Number support team.

3

Send a request to authenticate and store the session key

You'll need to provide your account code as AcctCode and token as Token.

REST API:

Handle the response and store the SessKey value.

4

Include the session key in your requests

If you don't encounter a PCI Level 1 compliance warning in API reference page:

For REST API, include a SessKey header with the stored value.

In case you encounter the compliance warning in API reference page, as seen below:

You'll need to prepare a secured header and use its value in place of the original SessKey.

If the HMAC secret was not provided to you previously or you don't know how to find the value of UserID or DeviceID, .

The format for the key is as follows: SessKey_Epoch_DeviceID_Hash. Include this key in the same way as you would include the SessKey (see case above).

Authentication
Contact Number
Contact Number
contact Number
Authentication Old