Token Lifetime & Reuse
The access token returned by this endpoint is valid for a limited period. Clients should cache and reuse the token for subsequent API requests until it expires. If an API call fails due to token expiration, your integration should request a new token and retry the original request with the refreshed credentials. Expired or invalidated tokens are expected to occur and should only be reported if you are no longer able to successfully get a valid new token.
Token Expiration & Error Handling
Expired or invalidated tokens are expected in normal operation. Your client should handle these cases gracefully by obtaining a new token and retrying the request. Only raise an error or alert if your integration is unable to successfully acquire a valid replacement token.
Token Contents
JWTs may contain embedded claims or metadata. These values are not guaranteed to remain stable and should not be parsed, interpreted, or relied upon for business logic. Integrations must treat the token as an opaque credential and use it solely for authentication.
Request
| Field Parameter | Value | Required | Field Values or Constraints |
|---|---|---|---|
merchantID | 123456 | Required | 6 All Numeric |
integratorID | xYzAbC123 | Required | 4 / 30 Alphanumeric, space and dash |
trxID | 123456 | Required | 4 / 20 Alphanumeric, a-z, A-Z, 0-9 - (dash) (Must be Unique for 2 years) |
GET https://cce.cashline.certegy.com/v1/user/login?integratorID={integratorID}&merchantID={merchantID}&trxID={trxID}
Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=
Response – Success
| Field Parameter | Field Values or Constraints |
|---|---|
status | enabled |
role | some role |
jwt | eyJ0eXAiOiJKV1QiLCJh[...]85db6kx-nLOwWqZE4Dg |
{
"status": "enabled",
"role": "some role",
"jwt": "eyJ0eXAiOiJKV1QiLCJh[...]85db6kx-nLOwWqZE4Dg"
}