API keys & credentials 🛎️
Get onboarded with PAYSTRAX Operations to obtain your credentials.
Get onboarded 🧶
Before making any request, contact PAYSTRAX Operations at [EMAIL — placeholder, not yet confirmed] to get set up. Once your TEST account is ready, you'll receive:
| Item | Used as |
|---|---|
| API username and password | Obtain access tokens (see Getting an Access Token) |
| Token endpoint URL | POST to exchange credentials for a Bearer token |
| Integrator ID | X-Integrator-ID request header (case-sensitive) |
| Configuration ID | receiver.configuration_id in payment requests |
| Gateway base URL (TEST) | Prefix for all API paths — https://sandbox-api.paystrax.com |
| Gateway base URL (PRODUCTION) | Confirmed separately with your PAYSTRAX contact |
Required headers 🛎️
Every request needs these three headers:
| Header | Description |
|---|---|
Authorization | Bearer <token> — a JWT issued for your integration. Test tokens are typically 60-day JWTs. |
X-Integrator-ID | Your PAYSTRAX integrator identifier. |
Content-Type | application/json |
Getting an access token 🧶
Use the token endpoint URL from your PAYSTRAX welcome pack, and request a token via the OAuth2 password grant:
POST <token_endpoint_url>
Content-Type: application/x-www-form-urlencoded
client_id=<client_id_from_paystrax>&username=<api_username>&password=<api_password>&grant_type=password
Read access_token from the JSON response, and use it as Authorization: Bearer <access_token> until it expires — then repeat this step.
PAYSTRAX issues the client_id, username, password, and token URL directly; you don't configure or run your own identity server.
Token lifetime and refresh policy still needs confirming with PAYSTRAX — test tokens may be long-lived, but this isn't finalised.