We understand this is a concern. The Food Corridor, LLC technically does not store any payment information on our servers. This is all done through a trusted 3rd Party payment processor, Stripe. TFC chose Stripe due to their stringent security considerations. Two of those considerations relevant to the concerns are:
Stripe has been audited by a PCI-certified auditor and is certified to PCI Service Provider Level 1. This is the most stringent level of certification available in the payments industry.
All card numbers are encrypted on disk with AES-256. Decryption keys are stored on separate machines. None of Stripe’s internal servers and daemons are able to obtain plaintext card numbers; instead, they can just request that cards be sent to a service provider on a static whitelist. Stripe’s infrastructure for storing, decrypting, and transmitting card numbers runs in separate hosting infrastructure, and doesn’t share any credentials with Stripe’s primary services (API, website, etc.).
If a kitchen allows a client to pay by check, and not use the payment processing through The Food Corridor, the kitchen is responsible for manually tracking the client’s payment and reconciliation. This is because TFC won't be able to tell if a client has paid or not.
To do this, the Kitchen Administrator selects “Manual payment processing” in from Clients tab > Edit for the Client that is wanting to pay manually. The Administrator must mark the invoices as "paid" on or after the invoice due date, once payment is collected for that invoice. Note that the platform fee of 2% will still be charged for the billing. Here's more on manual payment processing.