Ajman Bank and AFS Make Merchant Acquiring a Platform Bet

Merchant acquiring used to be easy to describe: give the merchant a terminal, settle the money, handle disputes, and price the service.

That description is now too small.

On 6 July 2026, Ajman Bank announced that it had signed a Memorandum of Understanding with Arab Financial Services. A ZAWYA-distributed press release carried the same collaboration scope: merchant acquiring, payment issuing, processing services, and corporate banking solutions.

That is the useful part. The announcement is not evidence that every merchant product is already live. It is an operating-model signal: in the Gulf, acquiring is becoming a bank platform bet, not a standalone acceptance product.

The Short Answer

Ajman Bank and AFS are framing merchant acquiring as a connected bank-and-processor capability. The hard work is not signing the MoU. The hard work is turning merchant onboarding, acceptance, issuing, processing, settlement, reconciliation, support, and corporate banking into one reliable service experience for businesses.

If that work is done well, the merchant does not experience a pile of payment products. The merchant experiences one business operating layer.

A Merchant Does Not Buy "Acquiring"

Most merchants do not wake up wanting acquiring. They want a business problem solved.

They want to accept cards in-store and online. They want payment links, SoftPOS, recurring billing, refunds, chargeback handling, settlement visibility, statements, cash-flow predictability, and support when something breaks. A larger merchant may also want working-capital products, payroll, supplier payments, expense cards, and treasury services.

The bank sees those as product lines. The merchant sees one operating burden.

This is why the Ajman Bank and AFS scope matters. The public language crosses merchant acquiring, issuing, processing, and corporate banking. That combination creates a broader design question: can the bank use payments as the front door to a deeper business relationship?

That is similar to the logic in UAE acceptance expansion. Coverage is the beginning. Productive merchant activity is the result.

The Bank Brings Trust, The Processor Brings Operating Depth

In a bank-led acquiring model, the bank usually owns the customer relationship, balance sheet context, compliance posture, and broader business-services proposition. The processor brings transaction infrastructure, scheme connectivity, terminals, gateways, tokenization, fraud tools, settlement files, dispute workflows, and platform operations.

Neither side is enough on its own.

A bank-only proposition can become slow, fragmented, and product-led by internal silos. A processor-only proposition can struggle to attach payments to financing, deposits, relationship management, and corporate banking. The opportunity is in the handoff.

The MoU language is early and intentionally broad. That makes execution discipline more important. The first deliverable should not be a slide deck with all possible products. It should be a responsibility map.

For each merchant capability, name:

• who owns onboarding and KYB;
• who configures terminals, gateway, and acceptance methods;
• who sets pricing, MDR, reserves, and exception rules;
• who produces settlement and reconciliation evidence;
• who owns fraud monitoring, disputes, and chargeback operations;
• who answers the merchant when a transaction fails;
• who decides the roadmap when bank products and payment products collide.

That map is the difference between partnership announcement and operating platform.

The Merchant Funnel Is The Real Scorecard

The right metric is not the number of merchants offered a service. It is how many merchants become active, profitable, and supportable.

I would run the programme through seven states:

1. Targeted: the merchant segment is eligible and commercially attractive.
2. Approved: KYB, risk tier, pricing, and contract are complete.
3. Configured: POS, gateway, payment links, settlement account, and reporting are ready.
4. Activated: a live sale, refund, and settlement cycle are proven.
5. Productive: repeat volume appears across the intended channels.
6. Expanded: the merchant adopts another banking or payment product because the first one works.
7. Retained: dispute, support, and settlement performance remain within tolerance.

That funnel should be segmented by merchant size, sector, channel, emirate, risk tier, and product bundle.

If the first product is acquiring, expansion might mean corporate cards, payroll, supplier payouts, trade finance, or cash-management services. If the first product is business banking, expansion might mean in-store acceptance, e-commerce acceptance, or embedded payment links.

The operator question is not "can Ajman Bank and AFS offer more services?" It is "can they reduce the merchant's total operating burden?"

Settlement And Reconciliation Decide Trust

Acquiring credibility is often won after the payment, not during checkout.

A merchant can tolerate a slightly ordinary terminal if cash arrives predictably and exceptions are explainable. It cannot tolerate unclear settlement, mismatched statements, unexplained reserves, slow chargeback evidence, or support teams that bounce issues between the bank and processor.

That is why local settlement control has become a strategic acquiring topic. In the Gulf, where businesses often operate across entities, channels, and markets, the finance team needs clean evidence: transaction, fee, tax, refund, dispute, payout, and bank credit tied together.

Any Ajman Bank and AFS build should treat settlement and reconciliation as product requirements, not back-office cleanup.

The same applies to support. A merchant should not need to know whether an issue sits with the bank, AFS, a terminal provider, a gateway, a scheme, or a fraud rule. The service model must hide that complexity without hiding accountability.

Do Not Confuse Breadth With Integration

The announcement lists several collaboration areas. That breadth is useful only if the merchant journey becomes simpler.

The failure mode is common: every product team ships its own portal, onboarding checklist, pricing sheet, service queue, and reporting format. The merchant gets more capability and more work at the same time.

The stronger model is one merchant operating console: applications, acceptance channels, settlement, disputes, service tickets, business banking, and expansion offers tied to a shared merchant identity and risk profile.

That does not require one monolithic system. It requires a shared merchant record, clear event model, unified support ownership, and consistent evidence. Merchant onboarding is where this usually succeeds or fails first.

Actionable Takeaway

Treat the Ajman Bank and AFS MoU as an acquiring-platform test.

The next proof points should be practical: merchant activation rate, time to first live transaction, settlement predictability, reconciliation quality, support resolution time, dispute handling, and cross-sell into relevant business-banking products.

The debate for Gulf payment leaders is not whether banks should partner with processors. They have to. The debate is whether those partnerships create one merchant operating experience, or just a larger bundle of products with a bank logo on the front.

If you are building a merchant-acquiring or payments platform, work with Rizwan to turn acceptance, settlement, risk, support, and business banking into one operating model.

FAQ

What did Ajman Bank and AFS announce?

They announced a Memorandum of Understanding to collaborate across merchant acquiring, payment issuing, processing services, and corporate banking solutions.

Is this already a launched merchant product?

The public material describes an MoU and a framework for collaboration. It should be treated as a strategic operating-model signal unless specific products are later announced.

What should operators watch next?

Watch merchant activation, settlement quality, reconciliation, support ownership, dispute handling, and whether payments attach to a broader business-banking relationship.