Checks before the order
Allow, flag or block, with a score and a reason you can read.
Product / TrustOrder
FreeAt checkout the system already checks the buyer's earlier order history, and for a problem buyer it turns off cash on delivery automatically.
Free, no monthly fee. Once it is on, you can create an API key right away.
Checks across Europe
AllowFlag or block
In plain words
TrustOrder works like a shared memory. Connected webshops report back when a buyer did not pick up their parcel. The next time that buyer orders with cash on delivery, even in another shop, the shop sees what to expect before the order goes through.
It is like a neighbouring shopkeeper telling you: this customer ordered from me too, and never came for the parcel. Only here nobody sees who the customer is. Instead of name, email and address, a fingerprint goes out, and the person cannot be read back from it.
One simple call before the order. Plugs into any webshop, CRM or system of your own.
Paste the key into the plugin, and it checks cash-on-delivery orders on its own.
A fingerprint instead of email, phone and address. TrustOrder never stores raw personal data.
Answer, before the order
Reason: did not pick up parcels at several shops.
The shop decides what to do, for example hide cash on delivery and offer prepayment.
Allow, flag or block, with a score and a reason you can read.
Only hashed identifiers go out. TrustOrder neither stores nor logs raw personal data.
One bad experience does not block anyone for good. A block needs reports from several different shops.
Allow and block lists per shop: let your regulars through even if they had trouble elsewhere.
Live and test keys, deleted in one click, a separate key per shop.
Checks, blocks and feedback for the last 30 days, split into live and test.
One account, every product
You switch TrustOrder on in the Console.
The same sign-in reaches our other products too. Billing, team members and tickets in one place.
Security and privacy
Raw personal data of the buyer never leaves your shop. The plugin turns it into a one-way code (a hash) inside the shop and sends only that. The original data cannot be read back from the code. This is everything that goes out about the buyer:
| Data in the order | What TrustOrder receives | Why |
|---|---|---|
| Name | Nothing | The decision does not need it. |
| Email address | A one-way code | So the same buyer can be recognised across shops without knowing the address. It is normalised first, so upper and lower case or a plus-sign alias do not matter. |
| Phone number | A one-way code | For the same reason. Local and international formats give the same code. |
| Shipping address | A one-way code, without floor and door | So an order to the same address under another name is recognised too. |
| Email domain | A one-way code, and a yes/no flag on whether it can receive mail | To filter out disposable and non-existent addresses. The plugin runs this check inside the shop. |
| Country and postcode | As plain text, but not linked to the order: only the shop and the hour sit next to it. You can turn it off in the settings. | For anonymous statistics. No order number, amount, product or IP address goes with it. |
| Amount, products, IP address | Nothing | The decision does not need it. |
The server seals each incoming code once more with a secret key kept only on the server, and stores only that. Even if the database ever leaked, the data could not be worked back from the codes.
Individual checks are not stored, only a daily count per shop. No code goes into logs or metrics either.
The weight of old cases halves every year, and they are deleted after 3 years.
How can we help? We reply within one business day.