A per-tenant AL extension that connects Dynamics 365 Business Central to Amazon Payment Services (PayFort), enabling cards, Mada, Apple Pay, installments, pay-by-link invoices, 3DS2 and tokenized recurring billing across MENA. Built, installed and supported by ECOSIRE. One-time license from $299.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A per-tenant AL extension that connects Dynamics 365 Business Central to Amazon Payment Services (PayFort), enabling cards, Mada, Apple Pay, installments, pay-by-link invoices, 3DS2 and tokenized recurring billing across MENA. Built, installed and supported by ECOSIRE.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
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.
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
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.
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.
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.
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.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des PayFort / Amazon Payment Services for Business Central-Moduls von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „PayFort / Amazon Payment Services for Business Central“ und klicken Sie auf „Installieren“.
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Native Amazon Payment Services (PayFort) connector for Mada, Apple Pay and installments | ||||
| Pay-by-link generated from a posted Sales Invoice | ||||
| Tokenized recurring billing via the BC job queue | ||||
| Installed as a per-tenant extension and supported on your environment | ||||
| Source AL code handed over to your team | ||||
| 3DS2 / OTP enforced with result written back to the BC record | ||||
| Multi-currency MENA settlement mapped to your APS merchant accounts | ||||
| Optional Dataverse / Power Platform sync of paid transactions |
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.
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.
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.
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.
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.
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.
A per-tenant AL extension that connects Dynamics 365 Business Central to Amazon Payment Services (PayFort), enabling cards, Mada, Apple Pay, installments, pay-by-link invoices, 3DS2 and tokenized recurring billing across MENA. Built, installed and supported by ECOSIRE.