# Getting Started ## [Ottu API](#ottu-api) Welcome to Ottu’s API documentation! We have designed our platform to offer a unified API experience across all our endpoints. No matter which [payment gateway](/ottu-team-sandbox-doc/user-guide/payment-gateway.md) you choose, you’ll find the same intuitive interface, allowing you to integrate just once and leave the heavy lifting to us. Before diving into the technical details, you should familiarize yourself with a few key concepts that will recur throughout our documentation. ## [Key Concepts](#key-concepts) #### [1. Payment Gateway](#1.-payment-gateway) In the context of Ottu, the payment gateway holds the MID (Merchant ID) credentials provided by your bank. For more details on this, check the [Payment Gateway section](/ottu-team-sandbox-doc/user-guide/payment-gateway.md). Currently, our staff handle this configuration and will provide you with the [pg\_codes](/ottu-team-sandbox-doc/developer/checkout-api.md#pg_codes-array-required) needed for the API. Alternatively, you can fetch these codes using our Payment Methods API. #### [2. Currency Configuration](#2.-currency-configuration) Currency configuration involves setting up the currencies you want to charge your customers. Ottu supports multi-currency transactions. If your MID is set up for KWD, but you want to display the charge amount to your customers in USD, we’ve got you covered. Your customers will see the amount in USD, but the actual funds will arrive in your bank account in KWD. Find more details in our [Currency Configuration section](/ottu-team-sandbox-doc/user-guide/currencies.md#currency-configuration). #### [3. Payment Transaction](#3.-payment-transaction) Every payment or API operation starts with or involves a payment transaction. Essentially, this is the metadata for the payment. It includes information like amount, currency, customer data (email, phone number, address), and more. A payment transaction’s state can change based on the flow `created`, `paid`, `expired`, `canceled`, etc.). Learn more in the [Payment Transaction section](/ottu-team-sandbox-doc/user-guide/payment-tracking.md#payment-transaction). #### [4. REST API](#4.-rest-api) To get started with Ottu’s REST API, first understand our authentication methods in the [Authentication section](/ottu-team-sandbox-doc/developer/authentication.md). Then proceed to the [Checkout API section](/ottu-team-sandbox-doc/developer/checkout-api.md) to learn how to create payments and charge customers. Following this, you might want to explore the [Payment Notification Webhook](/ottu-team-sandbox-doc/developer/webhooks/payment-notification.md). This feature is crucial if you want to integrate Ottu with a system and get notified about payment status updates. After creating a payment transaction, you can specify a [webhook URL](/ottu-team-sandbox-doc/developer/checkout-api.md#webhook_url-string-optional) where Ottu will send updates about the payment status. This will keep your systems up to date in real-time with payment events. See [Webhook](/ottu-team-sandbox-doc/developer/webhooks.md). ## [API Selection Guide](#api-selection-guide) Based on your specific needs, you can proceed to the sections that apply to your business: * #### [CRM or Other Internal Systems](#crm-or-other-internal-systems) You don’t need to perform any additional steps. Just use the [Checkout API](/ottu-team-sandbox-doc/developer/checkout-api.md) to create payment links and share them with your customers. They’ll land on Ottu’s checkout page, where we handle everything. * #### [Ecommerce or Similar APPs](#ecommerce-or-similar-apps) Our [Checkout SDK](/ottu-team-sandbox-doc/developer/checkout-sdk.md) is perfect for you. Available for both web and mobile apps, it integrates seamlessly with the [Checkout API](/ottu-team-sandbox-doc/developer/checkout-api.md). Simply load the library and install it on your page, and it will manage the entire payment process. * #### [Apple Pay, Google Pay, and Other Payment Services](#apple-pay-google-pay-and-other-payment-services) These services work only with the [Checkout SDK](/ottu-team-sandbox-doc/developer/checkout-sdk.md). The SDK automatically enables these services on your website or app without any further configuration. * #### [Refund, Capture, or Void Operations](#refund-capture-or-void-operations) After familiarizing yourself with the [Checkout API](/ottu-team-sandbox-doc/developer/checkout-api.md), check the [Operations section](/ottu-team-sandbox-doc/developer/operations.md) to understand how they work. If you wish to use these operations, the next step is to check the [Webhook Operation Notification section](/ottu-team-sandbox-doc/developer/webhooks/operation-notification.md). * #### [Subscription, Recurring Payments, and Offline Payments](#subscription-recurring-payments-and-offline-payments) Check the [User Cards](/ottu-team-sandbox-doc/developer/user-cards.md) and [Auto-Debit](/ottu-team-sandbox-doc/developer/auto-debit.md) Docs. * #### [Concerned about Security?](#concerned-about-security) Our sensitive API calls are signed for added security. Check out the [Signing Mechanism section](/ottu-team-sandbox-doc/developer/webhooks/signing-mechanism.md). For any other questions, please feel free to contact your local Ottu representative.\ Happy integration! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://sandbox-doc.gitbook.io/ottu-team-sandbox-doc/developer/getting-started.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.