Security and trust
How Flint handles card data and customer data.
What reaches Flint's servers, how data is encrypted, who processes it for Flint, and where to send a security question.
Card data
When a buyer pays, the card number goes from the browser to Stripe. Flint's servers receive a token, never the number.
SOC 2
Flint does not have a SOC 2 report yet.
Security contact
01Card data
Stripe's fields collect cards.
Flint's hosted checkout, buyer account, and dashboard take card details through Stripe Elements. The buyer types into fields that Stripe serves in its own frames, and Stripe turns the entry into a ConfirmationToken or a PaymentMethod ID. Flint's servers receive that ID. In every payment flow they never receive the card number or the security code. The Help community is separate: Flint screens its posts for pasted card numbers and keeps a post that contains one private, so don't post a card number there.
For a saved card, Flint keeps Stripe's PaymentMethod ID with the card's brand, last four digits, expiry month and year, and fingerprint. The card itself stays with Stripe.
Flint does not publish a PCI DSS Attestation of Compliance. Which self-assessment questionnaire a merchant files depends on its whole integration and its acquirer. Flint can describe the data flow, which the checkout security guide does, and a merchant takes that flow to its acquirer or a Qualified Security Assessor. To ask about Flint's PCI status or request documents, email security@withflintpay.com.
02Encryption
What is encrypted.
In transit. The load balancer in front of the API, dashboard, checkout, developer docs, and this site accepts TLS 1.2 and 1.3 only, and redirects plain HTTP to HTTPS. The API sends an HTTP Strict Transport Security header with a two-year lifetime that covers subdomains. Flint's connection to its Postgres database requires a verified TLS certificate, and the server refuses to connect to a remote database without one. The cache that holds rate limits and webhook coordination data is reached over TLS.
At rest. Flint encrypts several kinds of sensitive values itself, with AES-256-GCM, before it stores them: the credentials that connect a merchant's tax provider, the saved results of sensitive requests that are retried with an idempotency key, and private fulfillment quote and selection data. The private keys that sign ID tokens and webhooks stay in a managed key management service, and only the backend can use them to sign.
Encryption of the database, file storage, and cache volumes is a setting on the providers that host them. Flint's infrastructure code does not manage it, so Flint makes no claim about it beyond Section 9 of the privacy policy. To ask about it, email security@withflintpay.com.
03Data roles
Controller and processor.
Flint is a data controller for merchant account data: registration, onboarding, and billing. When a merchant submits its customers' data through Flint's APIs, such as customer names, email addresses, and payment information tied to orders, Flint is a data processor on the merchant's behalf. Merchants are responsible for giving their own customers the right privacy notices and collecting any consent the law requires. The roles come from Section 7 of the privacy policy.
Flint publishes no standalone data processing agreement. For questions about data processing terms, email privacy@withflintpay.com.
04Service providers
Subprocessors.
Flint uses a small number of service providers (subprocessors) to run the service, under contracts that require appropriate security and confidentiality. For the current list, email security@withflintpay.com or privacy@withflintpay.com.
05SOC 2
No SOC 2 report yet.
Flint does not have a SOC 2 report yet. If a SOC 2 report is a requirement for your purchase, email security@withflintpay.com so Flint knows.
06Contact
Reports and questionnaires.
Send vulnerability reports and security questionnaires to security@withflintpay.com. Don't post a vulnerability in a public Help thread. Send privacy requests to privacy@withflintpay.com.
07Questions
Short answers.
Is Flint PCI compliant?
When a buyer pays, card numbers are entered into fields that Stripe serves and go to Stripe, so Flint's servers receive a token or payment method ID and never a card number. Flint does not publish a PCI DSS Attestation of Compliance. For Flint's PCI status or documents, email security@withflintpay.com.
Does Flint have a SOC 2 report?
No. Flint does not have a SOC 2 report yet.
Is Flint a data controller or a data processor?
Both. Flint is a data controller for merchant account data (registration, onboarding, and billing). When a merchant submits its customers' data through Flint's APIs, Flint is a data processor on the merchant's behalf.
Does Flint use subprocessors?
Yes. Flint uses a small number of service providers (subprocessors) to run the service, under contracts that require appropriate security and confidentiality. For the current list, email security@withflintpay.com or privacy@withflintpay.com.
How do I report a vulnerability or send a security questionnaire?
Email security@withflintpay.com. Don't post a vulnerability in a public Help thread.
Try the API with a sandbox key before you send any customer data.