FAQ

1️ What forms of payments are supported by the SDK?

The SDK supports the following payment forms: applePay, tokenPay, ottuPG, redirect, googlePay, and stcPay. Merchants can display specific methods according to their needs. For example, if you want to only show the Apple Pay button, you can do so using formsOfPayment = [applePay], and only the Apple Pay button will be displayed. The same applies for stcPay, googlePay, and other methods.

2️ How do I migrate from an older version of the SDK to the new version?

To migrate from an older version to the latest version, please refer to the Installation section of the Ottu SDK docs. There you can find the SDK script with the latest version.

3️ How can I customize the appearance of the checkout page using themes?

The SDK offers various predefined themes that merchants can use to easily change the checkout page’s appearance. Themes such as dark theme, minimal theme, hide headers, and hide amount are available. Each theme is predefined by specific css classes with unique properties.

4️ Can I customize the appearance beyond the provided themes?

Yes, after familiarizing yourself with the supported css classes, you can use the theme object to customize the appearance of any component you want. Example: If you want to change Pay Button color to blue, you can use below class in theme

theme: {
    "pay-button": {
        "background": "blue"
    }
}

5️ Are there any known compatibility issues with browsers or platforms?

Yes, there are some compatibility nuances to be aware of:

• For the Apple Pay button, it is mainly displayed on Apple devices and the Safari browser. For Chrome, it will only be displayed on the latest iOS 16.

• For and Google Pay, stc pay & other payments methods, always refer to their official documentation for the most recent information about compatibility issues.

6️ How do I customize the payment request for Apple Pay and Google Pay?

You can tailor the payment request for both Apple Pay and Google Pay using their respective initialization methods. These methods allow you to set various properties like API version, supported cards, networks, countries, and merchant capabilities etc.You can check the list of properties supported by ApplePay & GooglePay.

7️ Why am I seeing a tooltip related to Apple Pay’s unavailability on the Apple Pay button?

The tooltip indicates certain prerequisites for Apple Pay are not met. Reasons could include a pending iOS update, cards not added to the Wallet, invalid merchant configurations, domain not verified by Apple, or the device being unsupported or old. Ensure all Apple Pay requirements are met for a smooth payment experience.

8️ What if a merchant wants to perform specific actions before the payment process?

Merchants can utilize the beforePayment hook. This allows for specific actions or checks to be performed prior to payment/redirection. Once your actions or checks are complete, resolve the promise to proceed with the redirection/payment.

In conclusion, this documentation serves as your comprehensive guide to our Web SDK. Here's a quick recap of the key points covered: Information about the fundamental Checkout SDK, the backbone of seamless web-based transactions. Practical demonstrations have provided valuable insights into effective SDK integration. Detailed descriptions of functions and methods have equipped you to harness the SDK's full potential. Explaining the essential role of callbacks in event handling. A rich array of examples has guided you through real-world SDK feature implementations. Exploring Apple Pay, Google Pay, and even KNET-Apple Pay for efficient, secure payments.

As you conclude your journey through this documentation, consider exploring the next section: Checkout SDK - iOS.