Skip to content

Security

Card numbers never reach our servers. This page explains, in plain words, how we protect payments and personal data, and how to tell us about a security issue.

Card data and PCI DSS

Card details stay with the processor

Card numbers are typed into payment fields hosted by our payment processor, which is validated as a PCI DSS Level 1 service provider. They never pass through our servers and never appear in our database, logs, support tickets or analytics. We keep the processor's attestation of compliance on file.

Our PCI DSS assessment

Because card data never reaches us, we complete the PCI DSS Self-Assessment Questionnaire A and sign its attestation of compliance before taking live payments, and every year after. Payment partners can ask us for it.

A locked-down checkout page

The checkout page loads no third-party scripts other than the processor's payment fields, and it cannot be framed by sites the seller has not authorized.

Data protection

Encryption

Data is encrypted in transit with TLS 1.2 or higher. Tax IDs, bank account numbers and two-factor secrets are encrypted in our database, and our backups are encrypted.

Backups

Backups are kept off-site, and we test restoring them.

Records that can't be rewritten

Our application can add to the payment ledger and the audit log but cannot change or delete their entries.

Only the data we need

We collect what a sale, its tax and its evidence in a dispute require. The privacy policy lists it, and the sub-processors page lists who processes it for us.

Access to our systems

Our team

Every staff member has their own account, protected by two-factor authentication. Approvals, verification decisions and other sensitive actions are recorded in an audit log, with the person and the reason.

Seller accounts

Passwords are stored as salted hashes. Sellers can turn on two-factor authentication. Sensitive changes ask for the password again, logins are rate-limited, and a new payout bank account is used only after we approve it.

Fraud controls

3-D Secure

We request 3-D Secure authentication from the buyer's bank on the first payment with each card. Renewals of a subscription the buyer already authorized are not asked again.

Card testing

Payment attempts are rate-limited per IP address, per minute and per hour. Further attempts are refused until the limit resets.

Screening

Every payment goes through our payment processor's fraud screening.

Sellers

Every seller is verified before going live and reviewed while it sells. How we verify sellers.

Report a vulnerability

If you find a security problem in our site, checkout or API, please tell us before anyone else.

Email security@merquay.com with what you found, the steps to reproduce it and the impact you expect.

We confirm we received your report, and keep you informed while we fix it.

While you research, please

  • Use only your own accounts and the sandbox, never real cards
  • Don't access, change or keep other people's data
  • Don't degrade the service for others
  • Give us reasonable time to fix the issue before you disclose it