In this section, we delve into the intricacies of Ottu's online payment management system, shedding light on how each element on the checkout page is meticulously controlled to enhance user experience and streamline the payment process. Explore Ottu's Checkout Page, where every element is strategically controlled for a seamless and secure payment experience.
The and sections managed by:
Both the and plugins offer the ability to customize the Contact Information and Order Description sections. Adding Custom or Builtin fields can be done effortlessly by the following three steps:
Step 1: Go to Ottu Dashboard > Administration Panel > Payment Request or ECommerce> Fields
Step 2: Click on Add another Field
Step 3: Complete the information below and proceed to save.
The type of the added field can be categorized as either Custom or Builtin.
If checked, the new added field will be shown in the “schedule table” or “planning table” (itinerary table) within the receipt PDF.
It determines the placement of the newly added field on the checkout page. Available options include , .
When neither the Order Description nor the From sections are selected, the default placement for newly added fields will be the To section. This applies to the following built-in fields: first_name, last_name, phone, email, and the Custom field full_name. For more details, see .
It allows for the control and management of the newly added field on a site or platform, providing the ability to enable or disable its usage and visibility.
It determines whether a newly added field is mandatory or optional.
It imposes constraints or rules on the new field's value. It ensures that the provided value meet certain requirements or conditions specified by the validator.
It determines the display positioning of the fields within the same section.
It provides guidance or an example of the expected input, helping users understand what information is required or the format it should take. (Should be In English).
It provides guidance or an example of the expected input, helping users understand what information is required or the format it should take. (Should be In Arabic).
HTML field name utilized solely for backend validation. It will not be visible anywhere.
Custom field's label in English.
Custom field's label in Arabic.
Through Unit Configuration, merchants gain control over the information presented to customers, including details about the site, contact information, social media accounts, and other crucial details.
Consider the following steps when adding a new unit.
Step 1: Go to Ottu Dashboard > Administration Panel > Unit> Units
Step 2: Click on Add Unit
Step 3: Complete the information below and proceed to save.
Indicates whether this object is active, usable, and visible on the site.
It refers to a code assigned to the unit for the purpose of identification within URLs, bulk operations, and similar contexts.
It adds a secondary heading below the main header, providing additional context or categorization within a specific section.
If checked, the unit title will appear.
Merchant's Website URL.
Where the merchant can upload their chosen business logo.
Where the merchant can upload his “favorite icon”, which is a small icon associated with a website that is typically displayed in the browser's address bar, tabs, bookmarks, and other areas.
It refers to the web address associated with the merchant's Facebook page.
It denotes the web address linked to the merchant's Twitter page.
It indicates the web address associated with the merchant's Instagram page.
It is the designated email where responses or replies to communications are directed.
It refers to the customizable color setting for the header section of a webpage, document, or application interface.
Option 1: By incorporating two new Builtin fields, namely First Name and Last Name.
Option 2: By introducing a Custom field labeled as Name with the HTML name defined as full_name.
In cases where both Builtin and Custom field have the same location on the checkout page, priority is given to the Builtin fields.
The Order Description section cannot include the following fields:
Builtin fields: First Name, Last Name, and Phone.
A drop-down list of predefined fields. It is presented when the Builtin type is selected in the parameter.
If the is marked as Custom, the parameter will disappear, and the following fields will be displayed for filling:
Unit Configuration empowers you to articulate precise parameters that intricately mold not only the section on the checkout page but also conveying detailed and illustrative information about the merchant to the user.
The name to appear in the status bar, emails, templates, etc. (Displayed on section)
Similar function as the parameter, but to be completed in Arabic. (Displayed on section)
To select the method to shorten the generated URL. Please check .
Merchant's Email Address. (Displayed on section)
Merchant's Phone Number. (Displayed on section)
It entails the inclusion of the physical location details of the merchant's business. This information typically comprises the street address, city, state or region, postal code, and country.
section can be managed through either the or. Additionally, configuring the ENV variable (Environment Variable) can lead to the removal of the entire section. For more information about Environment Variable, check .
takes precedence over . That means when adding a new field, whether Custom or Builtin, to the From section using Plugin Fields Configuration, the configuration from the plugin fields will be considered.
Only Custom field with Label [en] as Full Name and the HTML defined as full_name can not be displayed on From section.
When the affects the From section, only the following parameters will be displayed: Name, Email, and Phone.
section is controlled through . Only three elements can be displayed:
section is managed through .
Custom field: Field with as Full Name and the HTML defined as full_namecan not be displayed on Order Description section.
