Paymentology and Huru prepare a Jaywan card launch in the UAE

The announced development

Paymentology and Huru announced on 12 October 2026 that they are expanding their partnership to support a Huru card on Jaywan, the UAE's domestic card scheme. Paymentology says the launch is scheduled for the fourth quarter of 2026, with its processing technology supporting the program. The announcement therefore describes a planned launch, rather than confirming that the card is already available to every customer.

Huru's proposition centres on an individual account that can remain with a customer when employment changes. The release places the planned card within that wider financial services offering. It does not publish a merchant acceptance schedule, acquiring tariff or exhaustive description of supported transaction types. Those details require confirmation from the relevant providers.

Merchant analysis: issuance and acceptance are separate

A new card program can expand how customers access their money, but merchants experience the development through their own acceptance arrangements. A business should ask its acquirer whether its terminals and online checkout support the relevant domestic scheme. The answer may depend on configuration, channel and the specific transaction. A card launch announcement is useful intelligence, not a substitute for that confirmation.

For a neighbourhood shop, the first practical question is whether customers are likely to present the new card. Existing customer enquiries and transaction patterns can inform that assessment without requiring intrusive questions about employment or income. A merchant should respond to demonstrated demand and maintain several appropriate payment choices rather than assuming every customer will move to one new instrument.

Physical and online acceptance should be considered independently. A successful terminal transaction does not prove that a website can recognise and process the same card. Conversely, an online integration does not confirm readiness across a merchant's stores. Record the channels covered by the provider's confirmation and name an internal owner for checking that each promised capability actually works.

A salary account can influence shopping routines

The connection between incoming income and everyday spending is commercially relevant, although the announcement does not establish how customers will behave. Merchants can consider scenarios in which customers use a salary linked account more frequently for routine purchases. Those scenarios should guide observation and small experiments, not claims about guaranteed sales growth or a customer's financial position.

A grocery merchant, for example, might look at whether payment failures concentrate around certain trading periods and whether customers request alternative methods. The appropriate response is a convenient checkout and respectful customer service. It is not to infer a person's available balance from the brand of card they present. Staff should avoid assumptions about a customer's occupation, salary or circumstances.

Businesses with repeat purchases should also distinguish convenience from a recurring payment mandate. The availability of a card does not automatically establish support for subscriptions, stored credentials or subsequent merchant initiated charges. Those functions require explicit provider confirmation and appropriate customer consent. Merchants should not promise recurring billing until they understand the supported flow and have tested changes, cancellations and expired credentials.

Prepare support before advertising acceptance

When a new payment product enters a market, customers may ask basic questions at the point of sale. Merchants should give staff a short, verified explanation of what the business accepts and how to handle a failed attempt. Avoid presenting frontline employees as experts on the customer's account. Questions about card activation, limits or account access belong with the customer's provider.

A useful support script separates three situations: the merchant does not support the method, an attempted transaction received a clear decline, or the outcome remains uncertain. Those cases call for different responses. A customer should not be encouraged to keep retrying while staff are unable to determine whether an earlier attempt completed. Reliable transaction lookup is more valuable than a reassuring but inaccurate answer.

If acceptance is introduced in phases, signage and online information should match the actual rollout. A chain should avoid promoting universal support while some locations remain unconfigured. Store managers need a simple escalation route when a card that should work repeatedly fails. Capturing a transaction reference and time is usually more useful for investigation than asking the customer to disclose unnecessary payment credentials.

Settlement and refunds make the business case real

The merchant's evaluation should include where funds settle, how transaction records appear and how fees are calculated. A domestic scheme's role in national infrastructure does not by itself establish a particular price or settlement timetable for an individual business. Obtain the applicable commercial terms in writing and compare them with the merchant's actual mix of transactions.

Refunds are an essential test. Staff should know whether they can locate the original payment and return the correct amount through the supported process. A partial refund, cancelled order and transaction reversal may be treated differently. Testing these cases before a broad launch helps prevent customer service teams from improvising with cash or unrelated transfers when the original payment needs correction.

Reconciliation should be checked across the entire chain from sale to bank deposit. The same transaction needs a dependable reference in the checkout system, provider report and accounting workflow. Where information differs, document the mapping. A merchant may accept a payment successfully yet spend excessive time matching deposits. That labour belongs in the cost calculation alongside visible processing charges.

Run a bounded launch readiness exercise

Merchants interested in the planned card can prepare without assuming a firm availability date. Begin by asking the acquirer for its current support position and any required updates. Keep the enquiry specific to the merchant's business, channels and equipment. Record which statements are confirmed and which remain plans. This makes later rollout decisions easier to review when circumstances change.

The first live trial should use a limited set of authorised transactions and trained staff. Test ordinary purchases, an interruption, a refund and end of day reconciliation. Protect customer information and avoid retaining sensitive data merely because the payment method is unfamiliar. Any additional logging should have a defined operational purpose and fit the merchant's existing security practices.

After introduction, monitor actual usage and service quality. A low initial share need not mean failure if the product is still becoming available, but it should limit claims about commercial impact. Decide whether further investment is justified by customer demand, manageable support requirements and acceptable costs. The purpose is reliable acceptance of useful customer payment choices, rather than adding another logo to a checkout page.

Small merchants should also ask how acceptance updates reach their installed equipment. An unattended software change during a busy trading period can create confusion if screens or receipt details change unexpectedly. Agree a suitable update window, identify who confirms readiness and retain the provider's support reference. For a business with several branches, a simple location register can record equipment, configuration status and staff training. That register makes phased introduction easier to manage and gives head office a reliable basis for customer facing claims. It should reflect verified operational status, with unresolved issues assigned to a clearly named owner.