Fincheck

Environments

How UAT and Production differ, and what to confirm before going live.

FincheckEngine has two environments. Each has its own API origin and its own keys.

EnvironmentUse it forData
UATBuilding your integration, validating payloads, and acceptance testingFictional applicants only
ProductionSending real applicants after Fincheck approves your integrationLive applicant data

The key decides the environment. A UAT key is rejected by Production, and a Production key is rejected by UAT. Leads, offers, and batches never move between environments.

Base URL

Fincheck sends each key with its API origin. Every endpoint is under /api/v2:

Text
https://your-api-origin/api/v2

The Connection details section of the Overview shows the base URL for the environment these docs are connected to.

Before you go live

Confirm that your integration:

  • calls the Production origin with the Production key;
  • sends the Authorization header on every request;
  • keeps the key on your server and calls the API over HTTPS;
  • corrects 422 validation errors instead of dropping the lead;
  • stores the returned lead id for follow-up and support; and
  • handles every response your integration can receive, as described in Errors and, for Comparisons, Accepting an Offer.

Never send a real applicant to UAT or a fictional one to Production.