MENA Regional Payment Gateway Pack

The problem

Businesses across the Gulf and the Levant rarely collect through a single global card processor. A distributor in Riyadh takes domestic debit cards, a retailer in Kuwait routes through the national switch, a services firm in Amman or Beirut collects through a local acquirer with its own settlement calendar, and almost everyone is now accepting an installment or wallet product alongside cards. Each of those channels produces its own authorisation record, its own merchant statement, and its own fee structure.

SAP Business One does not know any of it. The typical result is an accountant exporting a portal report once a week, matching amounts by eye against a list of open A/R Invoices, keying Incoming Payments one at a time, and then posting a manual Journal Entry for the acquirer's commission and any FX difference. Refunds and chargebacks arrive days later and get handled as ad-hoc credit notes with no link back to the original transaction. Cash in the bank never quite equals cash in the ledger, and the month-end close absorbs the gap.

What ECOSIRE builds

ECOSIRE builds a per-tenant SAP Business One add-on that treats each regional acquirer as a configured payment channel and writes every money movement back into the ledger where it belongs.

Acquirer channel configuration

Each acquirer you use is defined as a channel record stored in User-Defined Tables, exposed through a User-Defined Object form inside the SAP Business One client. A channel holds its endpoint and credentials, the currency it settles in, the merchant identifier, the fee model (percentage, fixed, or tiered), the settlement cycle, and the House Bank Account and G/L accounts to be used for clearing, fees and FX differences. Credentials are stored encrypted and never written to the transaction rows.

Payment capture and posting

When a payment authorisation is confirmed, the add-on creates an Incoming Payment against the correct Business Partner and applies it to the open A/R Invoice or Sales Order down payment, using the Service Layer so that SAP Business One's own posting logic, exchange rates and internal reconciliation all apply. Where a channel settles net of commission, the add-on books the gross receipt to a clearing account and posts the acquirer fee to its configured expense account, so the amount landing on the House Bank Account matches the bank statement line rather than the invoice total.

Settlement-file reconciliation

Most regional acquirers publish a settlement or batch report rather than a real-time ledger. The add-on ingests those files on a schedule, matches each line to the transaction it created using the stored acquirer reference in a User-Defined Field, and produces a reconciliation run showing matched, unmatched and disputed lines. Matched batches post the corresponding Journal Entries for fees and rounding. Unmatched lines are held in a review queue with the reason recorded, so nothing is silently written off.

Refunds, chargebacks and cancellations

A refund raised against a captured transaction creates an Outgoing Payment or applies to an A/R Credit Memo, keeping the link to the original document through the stored reference. Chargebacks are recorded as a distinct state with their own G/L treatment and can be routed through a SAP Business One approval procedure before anything posts.

Multi-currency and multi-company handling

Channels settling in a currency other than the local currency post through the configured FX difference account using the exchange rate on the settlement date, not the invoice date, which is where most manual reconciliations drift. Where you run several company databases, each database receives its own channel configuration and its own accounts.

Operational visibility

The add-on ships with a transaction browser inside SAP Business One filtered by channel, status, date and Business Partner, plus Crystal Reports layouts for a settlement summary and an unreconciled-transaction listing that finance can run without leaving the client.

Who this is for

Wholesale and retail businesses in Saudi Arabia, the UAE, Kuwait, Qatar, Bahrain, Oman, Jordan, Egypt and Lebanon that collect through domestic switches or regional acquirers; e-commerce operations feeding orders into SAP Business One that need the money side to follow; and finance teams whose close is being delayed by manual payment matching.

Technical approach

The add-on is built against the SAP Business One Service Layer (OData/REST) for document creation and reading, with the DI API used where a specific object or posting behaviour is only exposed there. Extensibility is handled through User-Defined Fields on Business Partners, Incoming Payments, A/R Invoices and Journal Entries, User-Defined Tables for channel and settlement data, and User-Defined Objects for the configuration and reconciliation forms. It runs on SAP Business One 10.0 on either Microsoft SQL Server or SAP HANA, on-premise or on your hosted infrastructure. Outbound calls to acquirers go over TLS from a service component you control; no payment card data is stored in your company database.

How delivery works

Nothing here is a shelf product. The sequence is:

1. Scoping call. We confirm which acquirers you use, their integration documentation and settlement formats, your currencies, your chart of accounts mapping, your SAP Business One version and database platform, and who owns the merchant credentials. 2. Fixed quote. You receive a written scope and a fixed price and timeline before any code is written. The listed price is the starting point for a single-acquirer scope; additional acquirers or unusual settlement formats are quoted explicitly. 3. Build. Typical lead time is one working week depending on how many acquirers are in scope and how quickly their sandbox credentials are available. 4. Install in test. We install into your test company database first, configure the channels, and run transactions end to end against acquirer sandbox or low-value live credentials with your finance team watching the postings. 5. Production install. Once you sign off on the test postings, we install into the production company database, migrate the configuration, and stand by for the first live settlement cycle. 6. Support. A defined support window follows go-live for defect fixes and configuration adjustments, with the source code handed to you so you are never locked to us.