Accepting online payments in Syria in 2026: a developer's guide
For Syrian checkouts in 2026, model the order before payment, match wallet transfers on the transaction ID (not amount alone), and use hosted Syriatel Cash ($2/number) or Sham Cash ($5/account) APIs when you do not want to run your own wallet reader. Covers WooCommerce, bots, and the edge cases to decide before launch.
If you are wiring a checkout for customers inside Syria in 2026, the hard part is rarely the product catalog. The hard part is what happens after the customer agrees to pay. Cards that work in Europe often fail here. A bank transfer can sit for days. Cash on delivery still covers a lot of orders, and mobile wallets do the rest. The job of your backend is to record the order clearly, tell the customer exactly how to pay, and mark the order paid only when you can prove the money arrived.
I build and run a hosted payment gateway for Syriatel Cash and Sham Cash, and I also build the sites, WooCommerce shops, and bots that sit in front of it. This guide is the picture I wish I could hand a developer on day one: which rails exist, how to model an unpaid order, how to match a transfer without guessing, and where a ready-made gateway saves you from running a wallet reader yourself.
The rails you actually have
Most Syrian checkouts I see use a mix of three methods, sometimes four.
Cash on delivery is still a first-class option for many shops, especially for food and for goods delivered inside the same city. Treat it as a real payment method with its own status. The order is confirmed, the amount is due on arrival, and the collected flag flips when the driver or the shop records it.
Mobile wallets are how a lot of prepaid orders actually move. The two I connect as a hosted API are Syriatel Cash, at $2 per number per month, and Sham Cash, at $5 per account per month. The customer transfers to a number or account the merchant owns, then types the transaction ID so your app can verify the amount.
Card gateways appear when the merchant already has access to one, or when part of the audience pays from abroad. I do card-gateway integrations as custom work. I am not going to name a processor here or pretend every Syrian shop can turn cards on this week. If you have a gateway, use its official SDK, keep raw card data off your server, and still keep a wallet option for customers who cannot complete a card charge.
Bank transfers remain useful for larger invoices. They are slow to confirm and awkward to match automatically. If you offer them, treat the order as an invoice with a long window, and confirm by hand unless you have a bank feed you actually trust. Offer the methods your customers already use, and keep the order record honest about which method was chosen.
Model the order before you touch a wallet
The bug I still step on, when I inherit a project, is a checkout that sends the customer to WhatsApp with a total and no row in the database. Someone later pastes a screenshot into the chat, and the admin is supposed to remember which conversation it belonged to.
Create the order first. At minimum I store:
- a stable order id
- the payable amount, in integer lira if you price in whole SYP
- the currency
- the payment method the customer picked
- the expected destination (a Syriatel Cash number, a Sham Cash account, cash on delivery, or a card session)
- created-at and the payment window
- a status field with room for more than paid or unpaid
- a place for the transaction ID and the sender number once a wallet transfer is confirmed
Statuses I actually use look like: awaiting payment, paid, needs review, expired, cancelled, refunded by policy, and collected (for cash on delivery). "Needs review" matters. Wrong amounts and reused IDs have to land somewhere a person can see, not in a generic failed flag that the shop ignores.
The payment window is shop policy. An hour is common for retail checkouts. Restaurants sometimes go shorter. Invoice-style orders may stay open until the end of the day. Put the rule in the database and on the confirmation screen.
Why wallet confirmation used to be a person with a phone
A typical wallet checkout still looks like this when nobody has automated it. The customer copies a number, pays in the wallet app, and sends a screenshot. An admin opens the merchant wallet, searches for an amount, and updates the order. That holds for a handful of orders a day. It slips when two customers pay around the same time, when a payment arrives while the admin is offline, or when someone forwards an old screenshot.
Syriatel Cash and Sham Cash transfers have no memo field for the payer. After they pay, the app or the SMS shows a transaction ID. That ID is the handle your system should use. I described the general flow in How to Automate Payment Confirmation for Syrian Wallets: the customer pays, they enter the transaction ID, your backend looks that ID up, you verify the amount, and you refuse to use the same ID twice.
Match on the transaction ID, then check the amount
I do not match open orders by amount. Two lunches at 25,000 SYP in the same quarter hour will collide, and a system that closes "the oldest unpaid order with this total" will ship the wrong one on the first busy day.
The sequence I ship is:
- The customer submits a transaction ID on the order they are looking at.
- If that ID is already stored against any order, reject it. Leave the current order unpaid.
- Ask the gateway to look up the ID on the wallet this order is waiting on. A Sham Cash ID must not be checked against a Syriatel Cash number.
- If the transfer is not found yet, leave the ID unused and ask the customer to retry in a minute. They may have mistyped it, or the transfer may still be settling.
- If the transfer is found, compare amounts as integers.
- If the amount is wrong, bind the ID to this order, flag it for review, and do not mark it paid.
- If the amount matches and the ID is new, mark the order paid and store the ID, the sender number, and the time the transfer arrived.
The sender number is always returned on the gateway I run. Store it. Do not require it to match the checkout phone. People pay from someone else's wallet all the time.
```js function toIntAmount(value) { return Math.round(Number(value)); }
async function confirmWalletPayment({ order, transactionId, wallet, usedTxIds, lookupTransfer, }) { const id = String(transactionId || "").trim(); if (!id) return { status: "bad_payload" }; if (order.expectedWallet !== wallet) { return { status: "wallet_mismatch" }; } if (await usedTxIds.has(id)) { return { status: "rejected", reason: "transaction_already_used" }; }
const transfer = await lookupTransfer({ wallet, transactionId: id }); // lookupTransfer talks to YOUR_GATEWAY_URL with YOUR_API_KEY. // Placeholder fields: found, amount, receivedAt, senderNumber
if (!transfer || !transfer.found) return { status: "not_found" };
const paid = toIntAmount(transfer.amount); const expected = toIntAmount(order.total); await usedTxIds.add(id);
if (paid !== expected) { return { status: "wrong_amount", transactionId: id, paid, expected, senderNumber: transfer.senderNumber, }; }
return { status: "paid", transactionId: id, paid, senderNumber: transfer.senderNumber, paidAt: transfer.receivedAt, }; } ```
In production, usedTxIds.add has to be a unique constraint inside the same database transaction that writes the paid status. An in-memory set disappears when the process restarts, and two parallel requests can both pass the has check.
Notify the customer after the status is saved. If the message fails, retry the message. Do not confirm the payment a second time as a way of "sending the SMS again."
Hosted APIs, WooCommerce, and bots
You can build your own reader that watches a wallet and pushes events into your app. That is a product of its own, with device or session problems, and it is usually more than a shop asked for. The other path is a hosted API that already sees incoming transfers on the merchant's number or account.
I offer that as a ready-made gateway, built and run by me, with same-day setup and no source-code handover. It works from outside Syria with no Syrian proxy or VPN, which matters when the site already lives on a VPS abroad. Sandbox access for Syriatel Cash, and a free trial for Sham Cash, are available on request. Details for each wallet are in Syriatel Cash API: Accept Payments on Your Site and Sham Cash API: Integrate Payments Into Your App. If you need both, subscribe to both; they are billed and managed separately. I compared them in Syriatel Cash API vs Sham Cash API.
If the shop is on WooCommerce, the same matcher sits behind a field on the thank-you page or the order view, then updates the WooCommerce status. I would still keep a manual confirm in wp-admin. I wrote the Syriatel Cash version of that hook in سيريتل كاش على ووكومرس: يدوي أم تلقائي؟.
If sales already happen in Telegram or WhatsApp, a payment bot can collect the transaction ID in the chat and confirm on top of the same gateways. That starts from $120 one-time. A bot does not remove the need for a unique ID constraint or a review queue. It only changes the surface the customer types into.
The store itself may be a hosted plan or a codebase the merchant owns. I laid out that choice, including the public prices, in Hosted vs Owned Online Store. Payment confirmation is a separate concern either way. Owning the theme does not, by itself, confirm a wallet transfer.
Edge cases you should write down before launch
Partial payments should not complete the order. Bind the ID, record the amount, and notify a person. If you later accept two transfers against one order, that is a written rule, not a silent sum in week one. Overpayments get the same hold unless the shop has a written surplus rule. Keep the extra visible.
The customer may pay after the order expired, or type the ID before the gateway can see the transfer. Leave a retry path for not_found. For a valid transfer after expiry, show it next to the expired order and let a person reopen it, convert it to store credit, or handle a refund by the shop's policy. Do not invent an automatic refund.
A Syriatel Cash payment will not appear on a Sham Cash lookup. Put the expected wallet on the confirmation screen. If the ID never shows, the manual path is how you audit it. If the customer pays and never returns, the order stays unpaid until they enter the ID or you paste it from a screenshot.
Receiving limits exist, they differ by account or number, and they change. Confirm the current limits with Syriatel or Sham Cash if you sell high-value items or expect a busy day. I am deliberately not publishing a number here. I also do not ship automatic matching without a dashboard button that can confirm or reject, and that records who did it.
A small backend you can actually run
The sketch below is the state machine I want around the matcher. It is not the gateway itself. Hook lookupTransfer to the hosted API when you have your URL and key.
```js const ALLOWED = { awaiting_payment: ["paid", "needs_review", "expired", "cancelled"], needs_review: ["paid", "cancelled", "awaiting_payment"], expired: ["paid", "cancelled"], cancelled: [], paid: ["refunded"], };
function transition(order, next, actor, reason) { const allowed = ALLOWED[order.status] || []; if (!allowed.includes(next)) { throw new Error(cannot move ${order.status} to ${next}); } return { ...order, status: next, history: [...order.history, { next, actor, reason, at: new Date().toISOString() }], }; } ```
That table is the whole point. A paid order should not fall back to awaiting payment because a webhook was replayed. An expired order can still be marked paid by a person if the transfer arrived late. A cancelled order should not be revived by a stray form submit.
What I would ship in the first week
Start with the wallets your customers already use. If they pay Sham Cash, connect Sham Cash first. Add Syriatel Cash when you have the matcher and the review queue working on one wallet. Cash on delivery can live beside them from day one; it just uses a different status.
Run four tests before you take real money through the new flow: an exact match, a reused ID, a wrong amount, and an ID that is not visible yet. If any of those four is missing, you are not ready, even if the happy path looks clean.
For a merchant-facing version of this same ground, in Arabic, see الدفع الإلكتروني في سوريا 2026: دليل أصحاب المتاجر.
Frequently asked questions
Can a shop in Syria take card payments and wallet payments on the same site?
Yes, if you actually have a card gateway, and if you store the method on the order so the confirmation path stays separate.
Do I need both Syriatel Cash and Sham Cash?
Only if your customers use both. Each API is a separate subscription. Many shops start with one wallet and add the second when the first flow is stable.
Does the customer type a note in the transfer?
No. Neither wallet gives the payer a memo field you can rely on. They enter the transaction ID on your site after they pay.
Will this work if the server is in Europe or the Gulf?
Yes for the hosted gateway I run. It is reachable from outside Syria with no Syrian proxy or VPN. Your app still needs HTTPS and a unique constraint on the transaction ID.
What does the payment bot include, and what does it cost?
The payment bot starts from $120 one-time. It collects the transaction ID in Telegram or WhatsApp and confirms through the same wallet APIs. The monthly API fees stay separate: $2 per Syriatel Cash number, $5 per Sham Cash account.
How do I start?
Write through the contact form on fayezalshami.com, or email fayezalshami.dev@gmail.com. Say which wallets you need, whether the checkout is a website, WooCommerce, or a bot, and how many numbers or accounts you have. Ask for sandbox or trial access if you want to test first.