OSOSS Help Center
العربيةOpen Dashboard

Payment Methods

Payment Methods defines every way money can reach you - cash, cash on delivery, bank transfer, KNET, cards, wallets - and, just as importantly, where each one lands in your books and what it does to the order when it succeeds or fails. Get this page right once and reconciliation stops being detective work.

Menu path: Settings > Payment Methods

URL: https://my.ososs.com/dashboard/general-settings/payment-management

Two kinds of method

The page is split into two tabs, and the difference is not cosmetic.

Offline methodsOnline methods
Where they come fromYou create them hereInstalled as gateways from the Marketplace
Source columncustomsystem
Money movementRecorded by your staffCaptured by the gateway
Typical examplesCash, cash on delivery, bank transfer, chequeKNET, card gateways, wallets

Offline methods are the ones you own: OSOSS records that the customer paid this way, and a person is responsible for the cash or the transfer actually arriving. Online methods are payment gateways; the provider is subscribed from the Marketplace (paid add-on) and appears on this tab once installed, credentials and all. The Add button is available on the Offline tab only - you cannot invent a gateway here.

Whatever the type, the list shows the logo, the name, the Source, the Account and an on/off switch. The switch is the control your team uses day to day: on means the method is offered at checkout, off means it disappears from the POS payment screen and the storefront payment step without affecting anything already paid through it.

Add a payment method

  1. Open the Offline methods tab and click Add.
  2. Enter the name in both English and Arabic using the language switcher. This is the wording the cashier and the customer read, so use the words your staff already say.
  3. Upload a logo. On the storefront the logo does more work than the name.
  4. Save, then use the switch to turn the method on when you are ready to accept it.

Map it to accounting and to order status

A new method is not finished until it is configured. Settings on the row sets the account each channel's payments post to; Configure goes further and, per channel - e-commerce website, mobile app, POS, invoicing and API - pairs an account with the order status to apply when a payment initialises, succeeds and fails. The General and Custom switch decides whether one account and one set of statuses covers every channel or each channel is mapped separately, which is what you want when POS cash goes to a till account and online card payments go to a bank clearing account. The same drawer holds Require reference number, which forces the person taking the payment to enter a transfer or authorisation number, and the condition rules that limit a method to certain countries.

Delete a payment method

Unused methods can be deleted from the list. Deleting removes the method from checkout screens; it does not alter payments already recorded through it - those keep their history and accounting.

Warning: Delete only methods that were never used, or that you have stopped accepting entirely. If a method may return seasonally, switch it off instead so its reporting history stays intact.
Note: Each method's account mapping is what routes money to the right ledger - cash to the till account, KNET to the bank clearing account. Get the mapping right and reconciliation stays sane.
Tip: Configure the account before the first live order. Payments taken while a method points at the wrong account have to be corrected with journal entries afterwards.

Full reference

Every option and control on this page, at a glance.

List columns

Shown by default: Logo, Name, Source, Account, Active

Filters (3)

Form fields (3)

Active, Logo, Name

Standard list tools

Every list page in OSOSS shares these controls:

Related pages

What you can do on this page

Every action on this page, step by step. What you see depends on your role, so a control your account is not set up for simply does not appear.

Add a record

  1. Click Add above the table - some pages label it New or show a + icon.
  2. Complete the form. Required fields carry a red asterisk and the form will not submit until they are filled.
  3. Click Save. Validation runs on submit; any field that fails shows its message directly beneath itself, and the form scrolls to the first problem.
  4. You land back on the list with the new record in place.

Fields on this form: Active, Logo, Name

Searchable dropdowns (customer, product, account, branch...) read live data - start typing to filter rather than scrolling. Most also let you create the missing record inline so you don't lose the form you are in.

Edit a record

  1. Open the row's actions menu at the end of the row and choose Edit, or open the record and use Edit there.
  2. The form loads with current values. Change only what you need.
  3. Click Save.
Documents that are already posted to accounting, paid, or fulfilled lock the fields that would change history. That is deliberate - issue a refund, a credit note, or an adjustment instead of rewriting the original.

Delete a record

  1. Open the row's actions menu and choose Delete.
  2. Confirm in the dialog. There is no undo from the interface.
  3. If the record is referenced elsewhere - used on a document, tied to a transaction - the delete is refused and the reason shown.
When a record is refused, or when it may come back into use later, deactivate it instead of deleting. It disappears from selection lists while every document that already used it keeps reading correctly.

Export the list

  1. Filter and choose your columns first - the export mirrors exactly what is on screen, not the whole table.
  2. Click Export All.
  3. The file downloads as a spreadsheet: one row per record, your visible columns in your order.