Authentication
A quickstart guide to authenticating with Number services
Last updated
Was this helpful?
A quickstart guide to authenticating with Number services
Last updated
Was this helpful?
To authenticate to our services, depending on your integration of choice, you might need the following:
Here's a basic step-by-step guide on how to authenticate with our APIs:
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.
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.
For SOAP API, include a SessKey
parameter in the request body.
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
, contact Number.
The format for the key is as follows: ___. Include this key in the same way as you would include the SessKey
(see case above).
If you want to read more about authentication, see the Authentication guide
Authenticating with the mobile SDKs is very simple. Contact Number 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.
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, Contact Number. 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.
REST API: SOAP API:
If you have your own PCI compliant program and want to handle cardholder data using our REST API, you'll need to supplement the authentication header with the HMAC secret and you'll need to use our RSA certificate to encrypt cardholder data.
The methods below are for PCI Level 1 compliant merchants only. These operations involve sensitive credit card data. Additionally, they require . If you are not PCI compliant, use our instead.
Configure EasyPay
class. You can do that in your Payment Module or in AppDelegate
(didFinishLaunchingWithOptions
). Set isProduction = true
to enable jailbroken device detection.
Configure the EasyPay
class at the very beginning of the application lifecycle, e.g. in the main Application class (in the onCreate()
method).