Skip to main content

Sensitive data encryption

Context​

Identity theft & fraudulous payments​

The payment industry is the favorite target of fraudsters, who try to obtain card numbers or identity documents and use it to pay without the real owner's knowledge. Hackers have creative tricks to reach their goal, and so must the payment industry continuously work to fight back.

Our technology is here to help you fight this situation, and give your end-customer the peace of mind your business requires. To enable this, Xpollens uses encrypted payloads, and a specific SDK called Secure Interface.

Customer experience -vs- security PCI-DSS​

Your end-customer will want to access some of his very sensitive data directly on his selfcare :

  • his card PIN
  • his card number, expiry date, CVV2 code
  • his account IBAN

These data are subject to a specific regulation, PCI-DSS.

You do not need to become PCI-DSS compliant. Our solution is compliant and packaged inside our Secure Interface : you will never manipulate unencrypted sensitive data.

icons
Screen mirroring, screenshots, malware, spyware, jailbreak, code change : our Secure Interface is there to ensure these types of hack will not occur on your end-customer's device.

SDK Secure Interface​

To ensure end-to-end encryption, some payloads will be fully encrypted. You will not have the keys to decrypt such payloads, and you will have to use our SDK to encrypt the payload directly on your end-user's device.

Note that you will not have access to your end-user's data ; only her/him will have the possibility to see the data.

issuerClientId is the SDK parameter that must receive the publicUserCode given by the callback type 34.

icons
Our Secure Interface SDK documentation is subject to Non-Disclosure Agreement, please talk to your Sales Representative.