Authentication
The Strictly platform uses two separate credential systems depending on where in your integration you are. Understanding which one to use where is the most important thing to get right before writing any code.
| API credentials | Tokenization key | |
|---|---|---|
| Objective | Authenticate and validate API requests | Enable the tokenization form / library on your web page |
| Used by | Your server | Browser / ZeroGateway.js |
| Sent as | Authorization + key-hash headers | Query param in script URL |
| Safe to expose? | No — keep secret | Yes — client-side safe |
| Where to find | Settings → Security Keys → API Key | Settings → Security Keys → Tokenization Source |
Server-side: API credentials
These two headers are required on every call your server makes to the Strictly API.
A missing or invalid credential returns 401 Unauthorized.
Authorization header
Encode your merchant email:password as Base64 and prefix it with Basic :
Terminal
JavaScript
Then set the header:
Code
key-hash header
A static API key issued to your integration, passed as a plain header value:
Code
Complete example
cURL
JavaScript (fetch)
Your Authorization credentials and key-hash are server-side secrets. Never include them
in client-side JavaScript, mobile apps, or public repositories. Use environment variables —
never hardcode them.
Client-side: Tokenization key
The tokenization key is used exclusively with ZeroGateway.js in the browser to collect card data. It is safe to expose in client-side code because it can only be used to tokenize cards — it cannot make API calls or access your account.
Code
To get your tokenization key: Settings → Security Keys → Tokenization Source.
See Tokenization for the full ZeroGateway.js setup guide.
Getting your credentials
Both credentials live in the Strictly dashboard:
- Log in and go to Settings → Security Keys
- Copy your API key → used as the
key-hashheader - Copy your Tokenization Source key → used with ZeroGateway.js in the browser
- Your
Authorizationheader uses your merchant account email and password
If you don't have an account yet, contact your account manager or reach out to us to request sandbox access.