Payments are one of the first questions in any app or e-commerce conversation in Lebanon, and one of the most misunderstood. Business owners often assume an app must take card payments online from day one, or that it cannot work without them. Neither is true. Many successful local apps start by recording payments made through the methods customers already use, and add online card payments later if customers ask for them.
This post covers the practical options and, more importantly, how to build the app so payments are tracked reliably whatever the method. I will not quote provider fees or claim specific integrations, because those change and depend on your agreement with each provider. Always confirm current terms directly with them.
Start from how your customers already pay
Before choosing technology, look at your current customers:
- Do they pay cash on delivery or at the end of a visit?
- Do business clients pay by bank transfer against an invoice?
- Do people send money through Whish or OMT?
- Do they ask to pay by card?
Your app should first support what they already do, smoothly. Forcing a payment method customers do not use is a quick way to lose orders.
Option 1: Pay on delivery or on site, recorded in the app
The simplest model: the customer books or orders in the app, pays in person, and the staff member marks the payment in the app. For many service and delivery businesses this is the right first version.
What the app needs:
- A payment status on each order or booking: unpaid, paid, partially paid.
- The method used and the amount received, including currency.
- Who recorded it and when.
- A daily summary so the owner can reconcile cash with what the app says.
That last point is what makes this model work. Without reconciliation, cash payments become a source of disputes and losses.
Option 2: Bank transfer against an invoice
Common for business customers and larger amounts. The app or web platform issues an invoice with a reference, the customer transfers, and someone marks the invoice paid when the transfer arrives.
Make it easy:
- Generate invoices automatically with a unique reference the customer includes in the transfer.
- Show bank details clearly on the invoice and in the app.
- Let the finance person mark payments received in bulk.
- Send automatic reminders for overdue invoices.
Receivables tracking like this is a core part of field-service and B2B platforms. In NeonTask, for example, work orders are tracked through to invoice and payment, with receivables and reports in the web app.
Option 3: Whish and OMT
Many customers in Lebanon are comfortable sending money through Whish or OMT. The workflow in the app usually looks like bank transfer: the customer sends the payment, includes a reference or sends a confirmation, and the business confirms receipt in the admin.
Some providers offer merchant or online payment services beyond person-to-person transfers. Whether an automated integration is available for your business, and on what terms, is something to ask the provider directly. Design the app so that adding an automated method later does not change the rest of the order flow.
Option 4: Card payments online
Online card payments give the smoothest experience when they work: the customer pays inside the checkout, and the order is confirmed instantly. For a Lebanese business, the practical questions are:
- Which payment gateways can your business actually use, given where your company and bank accounts are registered? Ask your bank and gateway providers directly.
- Which currencies can you charge in and settle to?
- What are the fees and payout schedules?
- What are the requirements for your website: terms, refund policy, privacy policy?
Never store card numbers yourself. Use the gateway's hosted payment page or its secure components, so card data goes directly to the provider. This keeps you out of the heavy security obligations that come with handling card data.
A note on app store rules
If you sell physical goods or real-world services, like a meal, a delivery or a cleaning visit, in a mobile app, you can use your own payment methods. If you sell digital goods or content consumed inside the app, Apple and Google generally require their in-app purchase systems. Know which category your product is in before you design checkout. I covered other review rules in publishing your app on the App Store and Google Play.
Design the payment model, not just the button
Whatever methods you use, the backend should model payments properly:
- Orders and payments are separate records. One order can have several payments (a deposit, then the balance), and a payment can be refunded.
- Every payment has a status: pending, confirmed, failed, refunded.
- Currency is explicit on every amount. Many Lebanese businesses deal in US dollars and Lebanese pounds. Store the currency with each amount, and if you convert, store the rate used and when.
- Nothing is deleted. Corrections are new entries, so the history stays auditable.
- Online payments are confirmed by the server, through the gateway's server-to-server notifications, not by the app saying "it worked". Apps lose connection mid-payment; the server must be the source of truth.
Getting this model right is what lets you add or change payment methods later without rewriting the app.
What to show the customer
- The total, the currency and what is included, before confirming.
- Accepted payment methods, clearly.
- Instructions for transfer methods, with the reference to use.
- The current payment status on the order.
- A receipt or invoice they can find later.
What to give the business
- A list of unpaid and overdue orders.
- Daily totals per method and currency.
- Export for the accountant.
- Permissions: not every staff member should mark payments or issue refunds.
Refunds and disputes
Plan how refunds work before the first one happens. For cash and transfer methods, a refund is a new outgoing payment that someone must actually send, so the app should record it as pending until it is confirmed. For card payments, refunds go through the gateway and the server should update the status when the gateway confirms. Either way, keep the reason and who approved it.
A sensible path
- Launch with the methods customers already use, recorded in the app with clear statuses.
- Add invoices and reminders for transfers.
- Add online card payments when demand and your banking setup support it.
If you are planning an app or website that takes orders or bookings, see my work and get in touch. I can help you design the payment flow so it fits how your customers pay today and can grow later.