PayFort / Amazon Payment Services for Business Central

Key Features

Hosted-redirect and pay-by-link checkout via Amazon Payment Services (PayFort) so cardholder data never lands in your tenant (PCI scope reduction)

Card payments plus Mada, Apple Pay and merchant-configured installment plans, selectable per transaction

3DS2 / OTP authentication step-up enforced on the gateway with the result written back to the BC transaction record

Pay-by-link: a secure payment URL generated from a posted Sales Invoice and emailed to the customer, status auto-updated on settlement

Authorize, capture, void and refund actions in the Sales document ribbon, posting through standard BC routines to the Customer Ledger Entry

Tokenized recurring / subscription billing using saved card tokens, charged on a schedule via the BC job queue

Multi-currency MENA support (SAR, AED, EGP, JOD and others) aligned to your APS merchant accounts and BC currency setup

SHA request/response signature handling and webhook/return-URL verification to validate every gateway callback

Dedicated Payment Gateway Setup page: API key, access code, signature phrases, sandbox/live toggle, retry and timeout policy

Payment Transactions list with reconciliation against posted entries and drill-down to the originating document

Sandbox-first configuration with a guided test card flow before any live key is enabled

Optional Dataverse / Power Platform sync of paid transactions for unified Power BI reporting

Scoped permission set so only authorized finance roles can run captures, refunds and gateway setup

Event subscribers on sales posting events keep payment status and ledger entries consistent without core-object modification

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Amazon Payment Services (formerly PayFort) is the default acquirer for a large share of MENA mid-market merchants, yet Business Central ships with no native connector for it. This is a build-to-order AL extension that ECOSIRE designs, builds, installs as a per-tenant extension on your Business Central environment (cloud SaaS or on-premises), and supports — it is not an instant AppSource download.

The extension wires Amazon Payment Services into the documents your finance team already uses. It adds table and page extensions to Customer, Sales Invoice, Sales Order and Customer Ledger Entry, a dedicated Payment Gateway Setup page (API key, access code, SHA request/response phrases, sandbox vs. live), and a Payment Transactions list that reconciles against posted entries. Authorizations, captures, voids and refunds are initiated from the document ribbon and posted back through standard BC posting routines.

Customers pay through a hosted, PCI-DSS-scoped redirect or a pay-by-link URL emailed on the invoice, so cardholder data never touches your tenant. The integration covers cards, Mada, Apple Pay and installment plans, enforces 3DS2 / OTP step-up, supports multi-currency MENA settlement (SAR, AED, EGP, JOD and more), and tokenizes cards for recurring / subscription billing via the BC job queue.

ECOSIRE delivers the signed .app, a scoped permission set, a configuration package, UAT in your sandbox, and a recorded handover. Source is yours. Where you run Power Platform, paid transactions can flow to Dataverse for unified reporting.

What you get

Signed per-tenant Business Central extension (.app) built in AL, installed on your sandbox then production environment

Payment Gateway Setup configuration plus a RapidStart configuration package capturing your APS credentials and currency mapping

Scoped permission set and security role assignment for finance and gateway-admin users

Sandbox UAT cycle with documented test scripts covering cards, Mada, Apple Pay, installments, 3DS2 and refunds

Source AL code repository handed to your team with a short build/deploy README

Recorded handover session plus an admin runbook for key rotation, refunds and reconciliation

Who this is for

Finance Manager (MENA mid-market)

Owns AR and cash application. Wants invoices paid faster via pay-by-link and clean reconciliation of every APS settlement against the Customer Ledger Entry without manual re-keying.

Business Central Administrator

Manages the tenant, extensions and permission sets. Needs a per-tenant extension that installs cleanly, respects upgrade cycles, and isolates gateway credentials behind a scoped role.

E-commerce / Subscription Operations Lead

Runs recurring billing and online sales standardized on Amazon Payment Services. Needs tokenized cards, scheduled charges via the job queue, and Mada/Apple Pay coverage for regional buyers.

How PayFort / Amazon Payment Services for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Native Amazon Payment Services (PayFort) connector for Mada, Apple Pay and installments	Included	Partial support	Partial support
Pay-by-link generated from a posted Sales Invoice	Included	Partial support	Partial support
Tokenized recurring billing via the BC job queue	Included	Partial support	Partial support
Installed as a per-tenant extension and supported on your environment	Included	Partial support	Not included
Source AL code handed over to your team	Included	Included	Not included
3DS2 / OTP enforced with result written back to the BC record	Included	Partial support	Partial support
Multi-currency MENA settlement mapped to your APS merchant accounts	Included	Partial support	Partial support
Optional Dataverse / Power Platform sync of paid transactions	Included	Partial support	Not included

Frequently Asked Questions about PayFort / Amazon Payment Services for Business Central

Is this a download from Microsoft AppSource?

No. This is a build-to-order extension. ECOSIRE designs and builds it in AL for your specific APS merchant configuration, then installs it as a per-tenant extension directly on your Business Central sandbox and production environment. There is no instant AppSource listing — you receive the signed .app and the source code.

What is the delivery lead time?

Typical delivery is 2–4 weeks from kickoff: discovery and APS credential review, AL build, sandbox installation, then a UAT cycle covering cards, Mada, Apple Pay, installments, 3DS2 and refunds before go-live. Scope (multi-currency, recurring billing, Dataverse sync) and your APS onboarding status affect the exact timeline; we confirm dates after discovery.

How does ongoing support and updates work?

After go-live we provide a support window for defect fixes and assistance with reconciliation and key rotation. Because it is a per-tenant extension, we re-validate it against Business Central major releases (the twice-yearly waves) and adjust for any Amazon Payment Services API changes. Ongoing maintenance and SLA terms are agreed separately; the source is yours, so your own team can also extend it.

Do card details ever touch our Business Central tenant?

No. Payments go through the Amazon Payment Services hosted redirect or a pay-by-link page, so full card data is captured on the gateway, not in BC. We store only gateway tokens and transaction references, which keeps your PCI-DSS scope minimal. 3DS2/OTP is handled on the gateway and the result is written back to the BC transaction record.

Can it handle recurring subscription billing?

Yes. With customer consent, cards are tokenized by Amazon Payment Services and the token is stored against the customer. Scheduled charges run through the Business Central job queue, posting results back to the Customer Ledger Entry. Failed charges are flagged for retry per the policy configured on the Payment Gateway Setup page.

Cloud SaaS or on-premises Business Central — which is supported?

Both. The extension is built to AL per-tenant extension standards, so it installs on Business Central online (SaaS) and on supported on-premises deployments. We confirm your version and deployment model during discovery and target the matching runtime.