Well-guarded and easily managed payment data

Businesses are using ecommerce technology to mimic that of a consumer online shopping experience. B2B ecommerce is being adopted as a new sales channel, augmenting traditional direct and channel sales strategies, including leveraging their web presence into a buyer-facing extension of their CRM or ERP.  And B2B sellers are increasingly using their web sites to handle more complex B2B product, contract management and pricing rules, pushing the final purchase online as well.  

To support these developments, our Secure Checkout (and API) provides a data tokenization solution for secure real-time payment processing.  Tokenization is valuable when payment data is needed for a specific business purpose like repeat customer purchases, one click ordering and recurring billing.  And a core strength of our solution is tokenization.  

Secure Checkout is a secure, hosted page, branded to look like your website or business invoice that collects, transmits, and stores cardholder data returning to your application a token value you can use to complete the order process.  With Secure Checkout you can allow your clients to manage their own customer profiles including payment data.  We will store this customer and payment information (card account or checking account) until you are ready to fulfill the order, supporting one-time, recurring and repeat buyers.

Case Study

Merchants and vendors alike say that one of their key criteria in a payment module is how it can securely store customer profile information and sensitive payment card data in the cloud.

Here is a common processing scenario.  During registration or check out, you capture your customer’s card details. This may potentially be the only time you would touch the card data.  Using a hosted SSL Secure Checkout process, sensitive data is encrypted, returning to your application a token of this customer profile.  This represents a best practice to reduce PCI Compliance Scope and employs tokenization for further card processing activity required by your application.  Once the customer profile is captured and stored, use the API to specify which customer profile (token) needs to be charged and how much it needs to be charged.  In this scenario, your system manages the timing and transaction value to initiate repeat and recurring transactions.