Configuration

Ottu empowers the merchant to make his own configuration easily.

Merchant Name or title Required

Merchant’s name to be displayed on the dashboard.

Merchant subheader Optional

A merchant's most important information is briefly highlighted in this field.

Logo Optional

Merchant trade market logo

Favicon Optional

An icon displayed beside URL in the browser tab or next to the site name in a user's list of bookmarks.

Merchant Website URL

URL address of the merchant website.

Email Required

This email address gets the request for authorizing the permission. Should be only one email address. Normally, it is the email of the installation owner.

Merchant phone Optional

Merchant contact phone number.

Fixer access key Optional

Is paused Optional

Enabling it, will lead to freeze all the transaction process related to payment request link till it gets disabled.

Enable 2FA on Required

Enabling it, will send OTP to the dedicated email address for every dashboard logging in action.

Version Required

Current installation version.

Live update Optional

It is the date of the first live transaction.

Last update Required

The date of the last update on the merchant installation.

Renewal update Required

Installation renewal date, It is determined by the signed contract between Ottu and the merchant.

Expire payment transaction? Required

Enable disclosure_url Error Notification Required

Enabling it, will trigger a notification error when the merchant disclosure server can not be accessible.

Disclosure_url Error Emails Optional

Email address where merchant wants to receive disclosure notification error.

Notes Optional

Where the merchant can write a note for any additional configuration other than default configuration.

Enable webhook notifications?

Enabling it, will lead to post any triggered transaction operation (Void, capture, or refund) through webhook on the dedicated webhook URL.

Enable webhook notifications

if transaction initiated from API Enabling it, will lead to disclose the response data of any transaction operation (Void, capture, or refund) initiated by API on the dedicated webhook URL.

Webhook URL

Where to post the disclosed data.

SSL expiry date

Security socket layer, it is used to secure a merchant’s server and should be updated according to the SSL expiry date which is populated automatically based on the date of the installation.

Reference Prefix

It is for Ottu operations team, If a merchant is having two Ottu installations and one PG then one of the installation should have the reference prefix configured to avoid duplicate track ID for the PG.

Last updated