Project

General

Profile

Edit Copy Actions
Copy link

Feature #9754

open

we have one high priority pending task is there related to dejavoo at present we maintain dejavoo keys on .env but its not a good practice so we need to change that keys into company DB and give changing access to user so if user need to change device key

Added by Teja Sriram Sangani 25 days ago. Updated 25 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Teja Sriram Sangani
Target version:
-
Start date:
07/10/2026
Due date:
% Done:

90%

Estimated time:
Spent time:
7:00 h
Add

Subtasks

Add

Related issues

QuoteActions
Copy link
 #1

Updated by Teja Sriram Sangani 25 days ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 90
  • Moved Dejavoo (CPP) configuration from `.env` to the company database with secure encryption for sensitive credentials.
  • Added support for managing multiple Dejavoo devices per company, including default device selection.
  • Updated Dejavoo payment APIs to use company-specific device credentials instead of environment variables.
  • Created a Dejavoo configuration section in the Company Profile → Integrations screen for tenant admins.
  • Implemented functionality to add, edit, remove, and manage Dejavoo terminal credentials from the UI.
  • Added a device selection dropdown in the POS payment screen, with the default device automatically selected.
  • Fixed integration validation so Dejavoo settings can be saved without being blocked by unrelated Stripe, SMTP, or Twilio validation.
  • Improved secret handling by preserving existing encrypted credentials when masked values are submitted.
  • Resolved the default device persistence issue caused by UUID and MongoDB ObjectId mapping differences.
  • Verified that multiple devices, default device selection, and Company Profile integration are working as expected.
Edit Copy Actions
Copy link

Also available in: Atom PDF