1. Home
  2. CashLine
  3. Check Cashing and Deposit

Check Cashing and Deposit

Decisioning designed to meet the unique challenges of cashing checks and providing immediate funds from payroll and government checks; bringing more money to the casino floor.

Listed are the endpoints for Check Cashing and Deposit:

Check Cashing and Deposit

Supported Customer Environments

Testing and production environments are available for customers 24×7:

Certification Server, used when a customer is validating their application just before moving their code to production
Production Server, shared between all CashLine customers

To begin a request, the user will need a user name and password, which is considered a Basic Authentication. We will respond with the Bearer Key, also known as the Java Web Token (JWT). This JWT has an expiration. The time limit starts at the request for the Bearer Key, not the last transaction submitted. If the Java Web Token has expired, you would begin again with the Basic Authentication to obtain another Java Web Token at which time the expiration clock starts again.


Certegy CashLine supports two forms of authentication:

  1. Basic Authentication (basicAuth)
  2. Bearer Key Authentication (bearerAuth)

Basic Authentication is used for “/user/login” and “/user/{merchantID}/login” transactions, validating the user’s credentials and allowing a Java Web Token (JWT) “bearer” token to be returned and used in subsequent requests.

Bearer Key Authentication uses bearer authentication (also called token authentication) which is an HTTP authentication scheme that involves security tokens called bearer tokens. The bearer token is a cryptic string, usually generated by the server in response to a logon request. It has an expiration time of 60 minutes, if the token expires, a new token will need to be generated and presented (do another logon).


Back to Top

Was this article helpful to you? Yes No

How can we help?