Currencies

Discover Ottu, the groundbreaking multi-currency Online Payment Management System (OPMS) developed to revolutionize your online business. Ottu empowers merchants with unprecedented flexibility, allowing them to effortlessly accept payments in multiple currencies. With our advanced currency exchange options, businesses can seamlessly manage online payments with a wide array of currency options across borders, ensuring a smooth and user-friendly experience for customers worldwide, with the ability to customize the markup fees according to their preferences. Say goodbye to limitations and unlock a world of endless payment possibilities with Ottu, your ultimate solution to currency restrictions.

Currency Configurations

Ottu offers a convenient payment gateway with preconfigured currency settings. For instance, the default currency for KNET Payment Gateway is the Kuwaiti Dinar (KWD). This feature guarantees smooth transactions and enhances user experience, simplifying the management of online payments.

Currency Configuration Page

Once you access the Ottu Dashboard, click on the three dots positioned in the right corner of the page. This action will lead you to the Administration Panel, where you'll find a range of exciting options. Within the Administration Panel, you'll discover the Currency Tab awaiting your attention.

There are three types of currency configuration:

Currencies (adding and managing different currencies)
Currency exchanges (setting up currency exchange)
Exchanges config (defining currency rules for the payment gateway)

Each type serves a distinct purpose and aspect in enabling smooth and efficient transactions. These configurations empower merchants to navigate the complexities of multiple currencies, facilitate currency exchanges, and define specific currency rules for payment gateways.

Currencies

In Ottu dashboard, you can find a wide range of currencies to choose from. If you wish to add a new currency, just follow these simple steps:

Step 1:

Click on the Add Currency button to include a new currency.

Step 2:

Mark the active option and then click on Save to finalize the process.

Currency Exchanges

Sometimes, merchants may prefer receiving payments in their local currency, even when the customer resides in a different country. To facilitate this payment process, Ottu offers a convenient currency exchange service that benefits merchants and customers, enhancing seamless payment processes. Occasionally, when the bank acts as an intermediary between the merchant and the customer, they may impose a markup fee to cover the currency exchange fees. To configure the currency exchange feature, simply follow these three steps:

Step 1

Click on Add Currency Exchange.

Step 2

Enter the necessary parameters as required.

Step 3

Finally, click on Save.

Exchange Configuration

The configuration of the payment gateway is closely tied to the configuration of the exchange. This configuration determines the currency rules that should be applied to any payments made through that gateway. Adding an exchange configuration is a straightforward process consisting of just two steps:

Step 1

Click on the Add Exchange Config button.

Step 2

Provide the necessary information and click on the Save button.

Field Descriptions

Field	Description
Name	This field is used to identify the exchange configuration.
Default currency	The default currency of the payment gateway.
Currencies	These are the payment currencies that the merchant wants to deal with.
Fee type	There are two types of fees, Fixed fees and Percent fees. Fix fee: A predetermined amount that is added to the payment. Percent fee: An additional amount calculated based on a percentage of the payment.
Fees Description	Identification of the fee according to the merchant’s purposes
Work as	The exchange rate can be determined in two ways: Online or Local. Online: Utilizing online services to define the exchange rate. Local: Allows the merchant to manually define the exchange rate.
Fix fee	Fixed amount
Percentage fee	Dynamic amount
Charge default currency	When this event is activated, a fee will be added to the original amount, even if the payment transaction is conducted in the default currency of the payment gateway.

Field

Description

Name

This field is used to identify the exchange configuration.

Default currency

The default currency of the payment gateway.

Currencies

These are the payment currencies that the merchant wants to deal with.

Fee type

There are two types of fees, Fixed fees and Percent fees.

Fix fee: A predetermined amount that is added to the payment.

Percent fee: An additional amount calculated based on a percentage of the payment.

Fees Description

Identification of the fee according to the merchant’s purposes

Work as

The exchange rate can be determined in two ways: Online or Local.

Online: Utilizing online services to define the exchange rate.

Local: Allows the merchant to manually define the exchange rate.

Fix fee

Fixed amount

Percentage fee

Dynamic amount

Charge default currency

When this event is activated, a fee will be added to the original amount, even if the payment transaction is conducted in the default currency of the payment gateway.

Foreign currencies are not functioning properly in operations.

Tracking-Key Header

Overview

The Tracking-Key, in the context of the Operation API, is a unique identifier embedded in the header of each operation request initiated by the merchant. This key plays a pivotal role in maintaining the distinctiveness of every operation transaction, ensuring precise tracking and efficient retrieval of the latest status information.

Purpose of Tracking Key

It enables merchants to obtain the most recent status of an operation without the possibility of triggering duplicate operations in subsequent requests using the same key.

Utilizing Tracking-Key Process

Explore how to efficiently inquire about operations by leveraging the Tracking-Key header.

Initiating an Operation Request:
The merchant begins by adding the Tracking-Key to the header of the operation API when sending a request. This key acts as a unique identifier, distinguishing each operation from others initiated by the merchant.
Storing Details in the Database:
As the operation request is processed, the Tracking-Key is stored alongside other operation transaction details in the Ottu database. This inclusion allows for the efficient association of the Tracking-Key with the specific operation, facilitating future queries.
Retrieval of Operation Status: When the merchant wishes to inquire about the status of a previously performed operation, another operation request should be initiated.

Considering the points below:

The merchant should include a new header parameter, Tracking-Key, with the same value as in the previous operation transaction.
Alongside the Tracking-Key, the session_id / order_no of the specified operation transaction should be provided in the operation request.
Merchant specifies the Extrenal Operation associated with the provided Tracking-Key and session_id / order_no of targeted operation transaction

Exploring Operation Status: Ottu's system, recognizing the Tracking-Key and the associated session_id / order_no, retrieves the relevant transaction details from the database. The response to the operation request includes the latest status information for the specified operation transaction.

Guide: Step by Step

After explaining the process of utilizing the Tracking-Key, this section will delve into an example illustrating how a merchant can employ the Tracking-Key.

1. Perform Operation Request

The merchant initiates a POST Refund request by submitting the session_id of the previous paid transaction and specifying the refund amount.

Additionally, a new header parameter, Tracking-Key, is included, with "trackingtest" used as an example value for demonstration purposes.

Header Parameter:

Tracking-Key: "trackingtest"

Body Parameters:

{
    "operation": "refund",
    "session_id": "2a956e4c9294c2c0e9253c21b1a592ceb4018c68",
    "amount": "1"
}

2. Retrieve the Latest Operation Status

The merchant initiates another operation request, utilizing the same Tracking-Key as in the previous transaction, and specifies the previous operation.

Header Parameter:

Tracking-Key: "trackingtest"

Body Parameters:

{
    "operation": "refund",
    "session_id": "2a956e4c9294c2c0e9253c21b1a592ceb4018c68"
}

Response:

{
   "amount":"1.00",
   "amount_details":{
      "currency_code":"SAR",
      "amount":"1.0",
      "total":"1.0",
      "fee":"0"
   },
   "currency_code":"SAR",
   "customer_id":"Example_id",
   "customer_phone":"12345678",
   "extra":{},
   "gateway_account":"Credite-Card",
   "gateway_name":"mpgs",
   "gateway_response":{
      It will contain the raw pg response sent by the pg to Ottu
   },
   "initiator":{},
   "is_sandbox":true,
   "payment_type":"one_off",
   "reference_number":"SMAUGGGLERDK",
   "remaining_amount":"1.000",
   "result":"success",
   "session_id":"cb4b9e4cde8f2ac9664eba743497657d13e3c9b6",
   "signature":"3f312d13**************",
   "state":"refunded",
   "timestamp_utc":"2023-11-23 11:20:50"
}