Security, in full.

Everything that protects the details, explained in plain terms. Each one is something the system cannot do, not just something we promise not to do.

Security, built in.

Six things the system cannot do, even if someone wanted it to.

Point by point.

  • Encryption on the client's device

    The details are scrambled on the client's phone with 256-bit encryption, the same standard banks use. The key that unscrambles them is never sent anywhere.

  • A fresh key pair per link

    Every link gets its own brand-new key, made on the agent's computer. That key is created in a form that cannot be copied, exported or emailed off that computer.

  • A relay that cannot read

    Our service holds only the scrambled version and has no key to it. Anyone who runs the service, or breaks into it, would see nothing readable.

  • Details tied to their own link

    The scrambled details only open for the link they were made for. If anyone changes a single character, they will not open at all.

  • One use, one pickup

    A link takes one submission. Picking it up and deleting it happen in the same step, so it can never be collected twice.

  • Expiry and purge

    A link nobody uses expires 30 minutes after it was made, and expired records are cleared out shortly after. Nothing piles up.

  • Masking on both screens

    Numbers show as dots while the client types, and the agent's screen shows only the last four digits unless the agent chooses to see more.

  • Encrypted on the way, too

    Everything travels over a secure HTTPS connection, so the scrambled details are wrapped in a second layer of encryption while in transit.

  • No outside code on the form

    The page the client sees loads no trackers, no ad pixels and no code from other companies, and it is only allowed to talk to our own service.

  • An address that shows nothing

    Any address other than a live link shows a plain not-found page. There is no home page for the service, no sign-in page and no list of anything.

  • Confirmations travel with the details

    The client's two confirmations, authorizing the payment and vouching for the details, are scrambled together with the details and time-stamped, so the record and the data cannot be separated.

  • No names, no identifiers

    Links and pages show no agent name, client name or company name. If a link is forwarded or leaks, it says nothing about who it was for.

  • No retention

    There is no database of payment details, no list of past submissions and nothing to export. Once the details are in the application, the system has no copy.

  • Each organization kept apart

    Each organization gets its own separate setup, with its own keys and its own web address if it wants one. Nothing is shared between organizations.

Questions from your security people?

We will walk your security or compliance staff through every point above on a call, with the system in front of them.