One of the key features of Ottu is the ability to streamline the checkout process via tokenization. This feature is currently compatible with MasterCard, Visa, and STC Pay, with further options planned for future inclusion.
Consider tokenization as a powerful security vault where all sensitive data is replaced with a secure code, or ‘token’. Just like a vault secures precious jewels by keeping them out of sight and replacing them with a secure code, tokenization replaces sensitive card data with unique identifiers, protecting it from prying eyes. This process is paramount for securing payments, offering merchants the luxury of securely processing transactions without having to be PCI DSS compliant.
Tokenization Enhances Security: Tokenization significantly reduces the risk associated with handling sensitive customer card data. Instead of storing the actual card details, a unique token is generated and used for future transactions, thus enhancing the security of your payment processes.
To kick off the process, use the Checkout API to create a payment session (session_id) with a customer ID (customer_id) associated with a Merchant Identification Number (MID) that supports and has tokenization enabled. The presence of the customer ID is critical, as it’s the primary way to associate saved cards with a specific customer. The payment you’ve just initiated can then be rendered using the Checkout SDK. Remember, the Card Verification Value (CVV) may be required based on your Payment Gateway configuration – this can be set by contacting our technical team.
When the merchant utilizes the Checkout SDK and fulfills all the necessary requirements, the “Save Card” button will become available. This will enable the customers with the choice to securely save their payment card information for potential future transactions. After a customer decides to save their card and successfully completes a payment, the card details are converted into a tokenized form for added security. For upcoming transactions, if the merchant includes the same customer_id as in the preceding transaction within the request payload, all cards linked to that
customer_idare presented to the customer. This streamlines the process of choosing and utilizing any of the stored cards for payment. Only the last four digits of each card are revealed. Subsequently, customers can employ any of these saved cards for payment, with the CVV being optional based on the acquiring bank's policies. Our Checkout SDK seamlessly handles challenges like 3D Secure or One-Time Password (OTP) codes, relieving you of the complexities of payment processing.
Simplifying your checkout process with tokenization is easy with Ottu. Here’s a step-by-step guide on how to get started:
"pg_codes": ["mpgs", "credit-card", "stc-pay"],
Once you’ve created the payment link, the next step is to access the checkout_url from the Checkout API response. This action will open the Ottu checkout page where the Checkout SDK will render all available payment methods. To save a card, select a hosted payment method that has the save card input enabled, or the Ottu pg hosted page, based on the pg_code you input in the API. If the customer chooses to save the card and performs a successful payment, the card details will be saved, and a token will be associated with the customer_id.
Successful Payment is a Prerequisite: A saved card, represented by a unique token, can only be created after the customer completes a successful payment transaction. This process ensures the validity of the card and enables tokenization.
By following these steps, you can easily streamline your payment process, ensuring that customers have a seamless checkout experience. As mentioned, we’ll be providing visual aids between each step to further guide you in implementing this feature. Remember, at Ottu, we are always here to assist you in navigating the complexities of online transactions, so don’t hesitate to reach out if you need any help.
The ‘Save Card’ option is entirely voluntary. If a customer chooses not to save their card, the standard checkout process will proceed without tokenization.
Absolutely. Tokenization is a security measure that replaces sensitive card details with a unique token, thus ensuring that the actual card information isn’t exposed.
Yes! That’s the whole point. Ottu does all the heavy lifting for you, so you can simply use tokenization even if you’re not PCI DSS compliant.
Absolutely. You can safely store tokens in your database even without PCI DSS compliance. It’s important to remember that these tokens are not actual card numbers but are unique identifiers created through the tokenization process. They don’t carry the same security risks as storing raw card details.
Yes, you certainly can. Ottu uses tokenization to ensure that your customer’s Primary Account Number (PAN) is never exposed. What you receive and can safely store is a token, not an actual card number. It’s structured like a card number but doesn’t carry the same security risks. If you’re curious about how tokenization works, you can check out this Wikipedia article for a deeper dive.
The optimal time to save the card token in your database is immediately after the first payment against the subscription that you plan to auto-debit. While it’s not strictly necessary—you can always fetch this information through the User Cards API and Payment Methods APIs—it does streamline your processes and reduce development complexity.
Currently, the only way to save a new card is by having the customer successfully complete a payment with it. At the moment, it’s not possible to just save new card details directly.
No, it’s not mandatory to use the Checkout SDK. You can control the payment process using the responses from the Checkout API. However, it’s worth noting that the Checkout SDK simplifies the UI implementation and is necessary for certain payment methods such as Apple Pay, Google Pay, STC Pay, and others. While it’s recommended to use the Checkout SDK for its simplicity and comprehensive features, the choice ultimately lies in your hands based on your specific needs.
To explore the full potential of tokenization, check out the Checkout SDK, User Cards Section and the Auto Debit section of our documentation. These sections provide a deep dive into managing saved cards and automating recurring payments respectively, helping you leverage the best of Ottu’s payment solutions. Whether you’re a merchant looking to provide your customers with a seamless checkout experience or a developer eager to integrate state-of-the-art payment solutions, Ottu’s tokenization feature is your go-to choice for secure, hassle-free transactions.
Efficiency and Customer Convenience: By enabling tokenization, you simplify the checkout process for returning customers, as they won’t need to re-enter their card details for every transaction. This not only speeds up the payment process but also improves the customer experience.