Here is how it works:
- Jack is shopping for a new axe on your website. He finds a cherry red one and can’t help himself; he adds it to his shopping cart.
- He is ready to check out. He clicks checkout and is directed to a payment form where he enters all of his billing information.
- Once he submits the form, his information is sent to Beanstream through Secure Socket Layer and triggers an automatic creation of a new profile which is stored on Beanstream’s PCI-Level 1 servers.
- A token is created in conjunction with the profile. Beanstream sends the token back to you, the merchant. You won’t be able to unencrypt it, no one will. Which means if you have a data breach all of your customer’s data cannot be deciphered, keeping it safe and secure.
- Jack now decides that he needs some additional blades. He comes back to your website and fills up his shopping cart. Upon checkout, you pass the token associated with his profile to Beanstream.
- Beanstream then matches the token to the profile on our PCI-Level 1 servers and passes the billing information to the financial institution to process the payment. This all happens in real time.
Tokens are great because they mitigate risks associated with storing credit card numbers. If you have a data breach, they continue to protect your customer’s data.
Merchants who use recurring billing or batch processing can keep their customers data protected through tokenization. Merchants with a large customer base, repeat customers or those in need of significant security scope should all consider adding tokenization to their payment arsenal.
Keep your beans protected with tokenization.