The CliQ Payment Revolution -- Why Jordanian Businesses Still Can't Accept It Online

In December 2020, the Central Bank of Jordan launched CliQ through the Jordan Payments and Clearing Company (JoPACC). The idea was straightforward: let any Jordanian with a bank account send money to any other Jordanian instantly, using nothing more than a phone number, national ID, or custom alias. No waiting periods. No intermediary fees eating into small transactions. No need to know someone's IBAN.

Five years later, CliQ has exceeded every adoption projection. In 2025, the system processed over 18 million transactions with a total value exceeding 12 billion JD. Year-over-year transaction volume grew by 130%. Among Jordanians aged 18-35, CliQ is now the default way to send money -- more common than cash handoffs for rent, split bills, and peer-to-peer payments.

Jordan's payment infrastructure is, by regional standards, exceptional. CliQ for instant transfers. JoMoPay for mobile wallet interoperability. eFAWATEERcom for bill payments and invoicing. The Central Bank has done its job. The rails are built, they are fast, they are reliable, and they are accessible to virtually every banked adult in the country.

And yet: try to pay for a shawarma order online using CliQ. Try to check out on a Jordanian restaurant's website with your Zain Cash wallet via JoMoPay. Try to receive an eFAWATEERcom invoice from a local business you just ordered delivery from.

You can't. Not because the payment infrastructure doesn't support it, but because the software that businesses use doesn't connect to it.

The Integration Gap

Here is the fundamental disconnect: Jordan has world-class payment rails, but the business software ecosystem -- point-of-sale systems, ordering platforms, invoicing tools, e-commerce solutions -- was almost entirely built by companies that target global or Western markets. These platforms integrate with Stripe, Square, PayPal, and Apple Pay. They do not integrate with CliQ, JoMoPay, or eFAWATEERcom.

This is not a minor feature gap. It means that the payment methods most Jordanians actually use -- the methods the Central Bank spent years building and promoting -- are disconnected from the digital commerce tools most businesses would use to accept them.

Consider the implications. A restaurant that sets up online ordering using a global platform can accept Visa and Mastercard. But only 8% of Jordanian adults have credit cards. The remaining 92% -- including the majority of the restaurant's potential online customers -- would need to pay cash on delivery or not order at all. The restaurant has a digital ordering system that, by design, excludes the vast majority of its market from the most convenient payment method.

Meanwhile, those same customers are using CliQ to split dinner bills, pay their gym membership, and send rent to their landlords. The money is digital. The willingness to pay digitally exists. The infrastructure works. What's missing is the bridge between "I want to order food online" and "I want to pay with CliQ."

Why Integration Is Technically Hard

Building CliQ integration into a business platform is not as simple as adding a "Pay with CliQ" button. The challenges are real and worth understanding:

CliQ Is a Bank-to-Bank System

Unlike Stripe, which provides a unified API for accepting payments, CliQ operates through individual banks. There is no single CliQ API that a software developer can call to initiate a payment. Instead, each bank exposes its own CliQ capabilities through its own APIs (when it has APIs at all). A platform integrating CliQ needs to either:

• Partner with a specific bank and use that bank's CliQ API, which means customers of other banks need to initiate the transfer manually
• Build integrations with multiple banks, multiplying the development and maintenance effort
• Use a payment aggregator that sits on top of CliQ -- but few exist, and those that do are young and limited

Verification Is Asynchronous

When a customer pays with Stripe, the platform receives an instant webhook confirming the payment. With CliQ, the payment is instant at the bank level, but verifying receipt in a business application requires either manual confirmation ("I sent it, check your account") or API-based account monitoring. The latter requires bank-level API access that most software companies do not have.

This creates a user experience problem. The customer pays instantly, but the business platform might not know the payment has been received for minutes -- or until someone manually checks. For an online ordering system, that delay is unacceptable.

Request-to-Pay Is Emerging But Not Universal

The most elegant solution for CliQ commerce is "Request to Pay" (RTP) -- the merchant's system sends a payment request to the customer's banking app, the customer approves it, and the payment completes instantly with automatic confirmation to both sides. JoPACC has been developing this capability, and some banks now support it. But it is not yet universally available across all banks, and the technical specification is still evolving.

The JoMoPay Parallel

JoMoPay, Jordan's mobile wallet interoperability platform, faces a similar gap but from a different angle. Launched by JoPACC, JoMoPay allows users of different mobile wallets -- Zain Cash, Orange Money, Umniah Pay, Dinarak -- to transact with each other. A Zain Cash user can scan an Orange Money merchant's QR code and pay.

For physical merchants, this works reasonably well. The QR code is printed and posted at the counter. But for online commerce -- ordering from a website, paying through an app -- JoMoPay integration requires the same kind of software development that most platforms have not undertaken. The QR code needs to be generated dynamically, the payment needs to be verified automatically, and the order needs to be updated in real-time.

With 5.2 million registered mobile wallet accounts in a country of 11 million, mobile wallets represent a massive payment channel that online commerce platforms are leaving untouched.

What Businesses Are Doing Instead

Faced with the integration gap, Jordanian businesses have adopted workarounds that are functional but crude:

The WhatsApp Screenshot Method

The most common workaround: the customer places an order (by phone, WhatsApp, or a basic website), transfers payment via CliQ to the business's alias, takes a screenshot of the transfer confirmation, and sends it via WhatsApp. A staff member manually verifies the screenshot against the bank account and confirms the order.

This "works" in the same way that writing orders on napkins "works." It is manual, error-prone, time-consuming, and impossible to scale. It also creates fraud opportunities -- screenshot manipulation is trivial. Several restaurant owners in Amman report losing 500-2,000 JD annually to fake CliQ screenshots.

Cash on Delivery Dominance

The default fallback. If online payment is too complicated, just collect cash when the order arrives. This works but carries significant costs: drivers need float, cash handling creates security risks, and cash-on-delivery orders have a 15-20% higher cancellation rate than prepaid orders according to regional delivery data. The customer has no financial commitment until the food arrives at their door.

Card-Only Payment

Some restaurants accept card payments through gateways like Myfatoorah or HyperPay. This works for the 8% with credit cards and some debit card holders, but excludes the majority of potential customers. Conversion rates for card-only payment flows in Jordan are significantly lower than in markets with higher card penetration -- typically 30-40% lower than comparable flows in the UAE.

Who Is Building the Bridge

The gap between Jordan's payment infrastructure and business software is being addressed by several players, each approaching it differently:

Payment aggregators like Myfatoorah and Tap Payments are expanding their Jordanian offerings to include CliQ-adjacent options, though full CliQ integration with instant verification remains limited.

Local fintech startups are building CliQ payment APIs that abstract away the complexity of bank-by-bank integration. Companies like Liwwa and Mawdoo3 Pay are developing middleware layers that could eventually make CliQ integration as simple as adding Stripe -- though they are still in early stages.

Business platforms with a Jordan-first focus are integrating CliQ verification into their ordering flows. Nexara, for example, has built CliQ payment verification directly into its restaurant ordering system, allowing customers to pay via CliQ with automatic order confirmation. iMenu and some custom-built platforms are pursuing similar approaches.

Banks themselves are offering merchant solutions -- but these tend to be standalone products (a bank's own POS terminal, a bank's own payment page) rather than APIs that third-party platforms can integrate.

What Needs to Happen

Solving the CliQ commerce gap requires action at three levels:

1. Standardized Merchant API

JoPACC should prioritize a unified CliQ merchant API -- a single integration point that any software platform can use to accept CliQ payments, regardless of which bank the merchant or customer uses. This is the single most impactful thing that could happen for digital commerce in Jordan. Stripe's success was not because it invented payment processing, but because it made integration simple. CliQ needs its Stripe moment.

2. Request-to-Pay Universality

The RTP mechanism needs to be available at every bank in Jordan, with a standardized protocol. When a customer checks out online, they should receive a push notification in their banking app, approve the payment with biometrics, and have the transaction confirmed in the merchant's system -- all within 10 seconds. The technology exists. Several banks support it. It needs to be universal and mandatory.

3. Platform-Level Integration

Business software companies serving the Jordanian market need to prioritize CliQ and JoMoPay integration as core features, not afterthoughts. This means allocating real engineering resources to building robust payment flows that handle edge cases -- partial payments, refunds, timeouts, failed transfers -- not just the happy path.

The Opportunity in Numbers

The business case for solving this gap is substantial:

Restaurants that have implemented CliQ payment verification report 25-40% higher online order conversion rates compared to card-only flows. The average online order value with prepayment (CliQ or card) is 18% higher than cash-on-delivery orders, because customers who have already paid are less likely to reduce their order or cancel.

For a restaurant doing 200 delivery orders per month with an average value of 8 JD, switching from cash-on-delivery to CliQ prepayment could mean: 15-20% fewer cancellations (saving ~240 JD/month in wasted preparation), 18% higher average order value (adding ~290 JD/month in revenue), and reduced cash handling costs (~100 JD/month in float and reconciliation). The total impact: roughly 600 JD/month in improved economics.

The Clock Is Ticking

Jordan's digital payment infrastructure is among the best in the MENA region. The adoption curve has been faster than expected. The population -- especially the under-35 majority -- is ready and willing to pay digitally for everything, including food.

The missing piece is not the payment infrastructure. It is the software that connects that infrastructure to everyday business transactions. Every month that this gap persists, billions of fils in potential digital transactions flow through the analog workaround channels of WhatsApp screenshots and cash-on-delivery.

The banks have built the highway. Someone needs to build the on-ramps.

---