Business Central · Payments

Modern checkout,settlement, andledger in sync.

Payment Integration connects Microsoft Dynamics 365 Business Central to the Saudi payment and loyalty ecosystem your customers already use — from bank points and BNPL to specialised gateways — so sales documents, settlements, and customer balances stay coherent without parallel payment spreadsheets.

Delivered integrations · BC-native posting · Partner-led implementation

Delivery footprint
10Provider programmesRajhi Point through Redeemly
BCSingle ledgerposting in Business Central
1Implementation partnerPro Max Gulf delivery
KSALocal contextSaudi programmes & BNPL norms
The problem

Checkout innovation moved faster than the back office — and finance is left stitching gateways, BNPL, and loyalty back into the ERP by hand.

  • 01Sales channels activate Tamara, Tabby, or bank-point programmes faster than BC is configured to recognise their settlements.
  • 02Settlement files and gateway fees arrive in formats that do not map cleanly to VAT lines, dimensions, or customer ledger entries.
  • 03Customer service sees payment status in the storefront while AR sees something different in email exports.
  • 04Each new provider becomes a one-off project unless integrations share patterns, error handling, and monitoring.
Siloed payments vs. BC-integrated payments

What changes when payment providers are implemented as part of Business Central.

Fragmented payments

  • Gateway dashboards are the system of record; BC is updated late or partially.
  • BNPL and point redemptions reconciled with spreadsheets and pivot tables.
  • Hard to explain which BC invoice matches which clearing batch.
  • IT maintains brittle scripts per provider, per store.
  • New brands (e.g. another BNPL) restart the cycle from zero.

Payment Integration

  • BC remains authoritative for documents, VAT, and customer balances.
  • Provider-specific flows normalised into posting and matching patterns your team can operate.
  • Clear linkage from payment capture to posted sales documents.
  • Extension-style delivery that fits Microsoft partner upgrade practices.
  • Reuse of architecture as you add or swap providers where the rail allows.
How we implement

A consistent delivery model across gateways, BNPL, and loyalty rails.

Engagements combine your BC chart of accounts, VAT setup, document types, and channel mix with each provider’s technical requirements. The list below is representative of rails Pro Max Gulf has integrated for customers; exact APIs and certification steps are confirmed during discovery.

Checkout orchestration

Map storefront or POS checkout to BC sales documents so authorisations and captures have a home in the ERP.

BNPL & instalments

Model Tamara, Tabby, and similar flows so instalment schedules and refunds do not break AR hygiene.

Bank points & loyalty

Connect Rajhi Point, ANB Point, Redeemly, and related programmes to redemption and earn logic your finance team can audit.

Settlement & fees

Align clearing batches, fees, and adjustments with BC bank and GL accounts to speed bank reconciliation.

Controls & roles

Segregate who can void, refund, or resync using BC security and approval patterns.

Secrets & environments

Keep credentials out of spreadsheets; use sandbox to production promotion paths your IT team expects.

Providers delivered

Rails we have integrated for Business Central customers.

The following providers reflect real delivery work — naming follows how each programme is marketed in the Saudi market. Capabilities depend on your BC version, channel architecture, and each provider’s current API programme.

Rajhi Point

Al Rajhi Point

Loyalty and bank-point redemption flows connected to sales and settlement in Business Central.

Tamara

Tamara

Buy-now-pay-later checkout and order sync so finance sees BNPL orders alongside card and cash.

Tabby

Tabby

Split-pay and instalment journeys integrated with invoicing and customer ledger visibility.

Inma

Inma

Payment experiences aligned with Inma rails where your commerce or POS stack requires it.

Madfu

Madfu

Madfu payment paths wired into posting and reconciliation so AR teams work from one system.

WalaOne

WalaOne

WalaOne connectivity for the scenarios your storefront or field channels depend on.

Walaplus

Walaplus

Walaplus integration patterns mapped to BC documents and dimensions.

MSI

MSI

MSI payment integration for the merchant flows you run on top of Business Central.

ANB Point

ANB Point

Arab National Bank point programmes linked to sales and loyalty redemption in BC.

Redeemly

Redeemly

Redeemly redemption and campaign logic surfaced through governed BC transactions.

How we deliver

From provider selection to stable reconciliation in BC.

01

Discovery

Inventory channels, currencies, VAT treatment, and which providers (Tamara, Tabby, bank points, etc.) must coexist on day one.

02

Design & mapping

Define document types, posting profiles, dimensions, and exception queues so finance and IT agree on the golden path.

03

Build & sandbox

Implement and test against provider sandboxes with realistic orders, partial captures, refunds, and point redemptions.

04

Pilot go-live

Roll out to a limited store or company with hypercare monitoring of settlement files and BC postings.

05

Operate & extend

Tune matching rules, add providers, and schedule regression tests around BC cumulative updates.

Inside Business Central

Controllers reconcile when payment status lives next to the invoice.

Representative views of how finance teams trace a BNPL or card capture back to the BC document that customers and auditors expect.

ERP AI Assistant
Payments · TabbyLive · Tabby
Is the Tabby capture for SI-2025-08912 fully settled?
Captured. Settlement batch ST-240918-07 matched to SI-2025-08912 with no variance.
Tabby · SI-2025-08912BC · Live
AuthorisedSAR 3,240.00
CapturedSAR 3,240.00
SettlementMatched
Fee (est.)SAR 48.60

Ask for status against the sales invoice already in BC.

erp.company.com / ai-ops
Modules AI Ops Control Center
Payment operations board
Business Central · Multi-rail
Settlements · Live
Captured today
SAR 184K
all rails
Pending match
6
2 BNPL
Refunds in flight
3
awaiting provider
Fee accrual
OK
posted to GL
Settlement pipeline · todayWorkflow automation · live
Authorised312
Captured298
Cleared276
Matched to BC270
Recent payment eventsAudit trail
  • 11:04Tamara order TMR-8831 linked to SI-2025-08904OK
  • 10:58Rajhi Point redemption RP-2219 applied to SI-2025-08890OK
  • 10:41Batch ST-240918-06 variance SAR 12.40 — fee line reviewWARN

Clearing batches, fees, and exceptions in one operational pane.

Multi
BNPL, cards, points
BC
Posted where finance works
Partner
Pro Max Gulf delivery
Common questions

What commerce and finance leaders ask before integrating payments on BC.

We implement and configure integrations as your Microsoft partner. Each provider retains its own merchant onboarding, compliance, and certification rules; we align BC to the technical interfaces they expose once your merchant agreements are in place.

Next step

Connect the payment brands your customers expect — without losing BC as the source of truth.

Contact Pro Max Gulf to review your channels, provider mix, and BC footprint. We will outline discovery, integration scope, and a pragmatic go-live plan for finance and IT.

Microsoft partner · Saudi payment context · Straightforward delivery

ProMax TechPro Max Gulf

Premier technology partner delivering enterprise-grade ERP, AI, software, and hardware solutions across Saudi Arabia.

Quick Links

Services

© 2026 Pro Max Gulf. All Rights Reserved.info@promaxgulf.com