Security

What protects every request, every key and every company's data, and what to do on your side.

Each company apart

  • Every company has its own database with its own login, which can open nothing else. A request is tied to one company before anything runs, and the data layer refuses to run without one.
  • A key names its company and is checked against that company’s own records only: no key can reach another company’s events, orders or guests.
  • Sandbox keys (eos_sk_test_) only work in the sandbox and live keys only in the live company.

Keys

  • A key’s secret part is shown once. EOS keeps only a keyed hash of it, checked in constant time, so a copy of EOS’s records would not reveal it.
  • Each key holds only the permissions it was given, and can expire, be rolled or be revoked at once.
  • Secret keys can be locked to your servers’ IP addresses; publishable keys only work from the web addresses listed on them.
  • The address a key is checked against is the one the request really came from. Headers a caller adds to claim another address are ignored.
  • A secret key sent from a web page is refused even when it is right, so a key pasted into front-end code fails at once.
  • Making, changing, rolling and revoking keys are written to the company’s audit trail, and each key’s requests are logged for 30 days.

Limits

  • Each key has its own limit of requests a minute.
  • An address whose requests keep failing the key check (30 in a minute) is held off for a minute, which makes guessing keys pointless.
  • With a publishable key, one visitor holds at most five checkout sessions at a time, so nobody can tie up an event’s tickets from a web page.
  • Bodies are JSON objects of at most 64 KB, and every value is checked before use.

Requests and answers

  • Call the API over HTTPS. Keys are read from headers, never from the address, so they stay out of logs and browser history.
  • Answers are never cached on the way (Cache-Control: no-store), never sniffed as anything but JSON, never framed, and send no referrer.
  • Every answer carries a request id, also in the key’s log, so any request can be traced.
  • Idempotency-Key makes retries safe: the same request never does a thing twice.

Webhooks

  • Every delivery is signed with the endpoint’s own secret (the Standard Webhooks scheme) and carries a timestamp, so your server can refuse forgeries and replays. How to check them.
  • Endpoints must be https addresses on the public internet. Each address is checked when the endpoint is added and again at the moment EOS connects, so a name cannot be switched to a private address in between.
  • Redirects are never followed. Signing secrets are kept sealed, shown once, and can be rolled at any time.

Card details

Card details never pass through EOS or your server: hosted checkout and Stripe’s Payment Element send them straight to Stripe, and payments are taken on the company’s own Stripe account.

On your side

  • Keep secret keys and webhook secrets in your server’s environment or a secrets manager, never in code, web pages or apps you give out.
  • One key per system, with only the permissions it needs, an expiry, and an IP lock where your servers’ addresses are fixed.
  • Check every webhook’s signature and timestamp before acting on it, and check livemode.
  • Store only the personal data you need, and protect it as you would your own customer records.
  • If a key or secret may have been seen, roll or revoke it in EOS straight away, then read its recent requests.