A custom-built Magento 2 / Adobe Commerce payment gateway for Amazon Payment Services (PayFort) covering UAE, KSA, Egypt, Jordan, Lebanon and Qatar — with tokenized cards, Apple Pay, installments and 3D Secure. Built, installed and supported by ECOSIRE on your store. Built to order by ECOSIRE for Magento 2 / Adobe Commerce (build-to-order) — indicative price from $249.00 USD; request a quote for a scoped proposal.
Illustrative previewA custom-built Magento 2 / Adobe Commerce payment gateway for Amazon Payment Services (PayFort) covering UAE, KSA, Egypt, Jordan, Lebanon and Qatar — with tokenized cards, Apple Pay, installments and 3D Secure. Built, installed and supported by ECOSIRE on your store.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Magento 2.
You go live in about 2–4 weeks, with a post-launch support window.
PayFort / Amazon Payment Services for Magento 2 is a build-to-order payment integration that connects your Magento Open Source or Adobe Commerce checkout to Amazon Payment Services (APS / PayFort) — the Amazon-owned MENA gateway serving the UAE, KSA, Egypt, Jordan, Lebanon and Qatar.
This is not an instant Marketplace download. ECOSIRE builds the module against your store's exact Magento version, theme and checkout, then installs and supports it on your environment. You receive a clean, namespaced module under app/code/Ecosire/AmazonPaymentServices that registers a proper payment method through Magento's gateway command framework (Magento\Payment\Gateway) — authorize, capture, sale, void and refund commands wired via di.xml, not a hard-coded controller.
What gets built: card processing across all supported APS countries and currencies; SAQ A-EPP-aligned tokenization so card data never touches your servers (tokens stored against the customer and reused for one-click and recurring scenarios); Apple Pay and installment plans where the merchant account supports them; both Merchant Page (iframe/hosted fields) and Redirect integration modes; and full 3D Secure 2 authentication with signature (SHA) request/response validation on every transaction.
Server-to-server notifications are handled by a dedicated, ACL-protected controller that verifies the APS signature before touching an order, with idempotent status transitions through Magento's order/invoice service contracts. Admin configuration lives under Stores → Configuration → Sales → Payment Methods, with merchant identifier, access code and SHA phrases stored as encrypted core_config_data and gated by an Ecosire_AmazonPaymentServices::config ACL resource.
You get the source, the install, and a real engineer behind it — sandbox-tested against the APS test environment before go-live.
A retailer in the UAE, KSA, Egypt or Jordan already holding (or onboarding) an Amazon Payment Services merchant account who needs local card acceptance, Apple Pay and installments inside their Magento store without sending card data through their own servers.
A development agency delivering a Magento Open Source or Adobe Commerce build for a Gulf client who needs a correctly architected APS gateway (gateway commands, signature validation, ACL) without burning sprint capacity reverse-engineering the APS API.
A payments or finance lead consolidating onto Amazon Payment Services who needs reliable 3DS authentication, accurate refund reconciliation through credit memos, and PCI scope kept to SAQ A-EPP via tokenization.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Native Amazon Payment Services (PayFort) integration for MENA | Included | Partial support | Partial support | |
| SAQ A-EPP tokenized card storage (no card data on your server) | Included | Partial support | Included | |
| Apple Pay and installment plans at checkout | Included | Partial support | Partial support | |
| 3D Secure 2 with full SHA signature request/response validation | Included | Partial support | Included | |
| Built, installed and version-matched to your exact store by an engineer | Included | Included | Not included | |
| Gateway-command architecture (di.xml, service contracts, ACL) vs hard-coded controller | Included | Partial support | Partial support | |
| Ongoing support and updates tied to your specific build | Included | Partial support | Partial support | |
| Instant self-service download and one-click install | Not included | Not included | Included |
Typical delivery is 2 to 4 weeks from the point we have your Magento version details and APS sandbox credentials. A straightforward redirect-mode integration on a clean store lands faster; Merchant Page mode plus Apple Pay, installments and multi-store credential scoping takes longer. We confirm a firm timeline after a short scoping call and keep you updated through sandbox testing and go-live. This is built and installed by ECOSIRE — it is not an instant Adobe Commerce Marketplace download.
The integration is designed so cardholder data is captured directly by Amazon Payment Services (hosted Merchant Page or redirect) and never stored or processed on your Magento server — APS returns a token your store reuses. This keeps you aligned with SAQ A-EPP scope rather than the far heavier SAQ D. We implement it to that model, but final PCI compliance always depends on your overall hosting, configuration and an assessment by your QSA or acquirer; we do not issue PCI certification.
Every build includes a post-launch support window for bug fixes and configuration help. Because the module is built for your specific store, updates are handled as scoped work — for example adapting to a Magento or Adobe Commerce upgrade, an APS API change, or adding a new country/currency later. We offer ongoing support and retainer arrangements so the gateway stays current as your platform and the APS API evolve.
Yes. The module uses standard Magento 2 framework APIs — gateway commands, di.xml, service contracts and core_config_data — that exist in both editions, so it runs on Magento Open Source and Adobe Commerce (on-prem or cloud). On Adobe Commerce Cloud we follow the cloud deployment model (composer-based install, build/deploy phases) rather than committing module code directly into app/code on the live node.
Yes. The base build covers card processing and 3D Secure across the APS countries you operate in. Apple Pay and installment plans depend on your APS merchant account having them enabled — once they are, we wire them into checkout. Adding further countries or currencies later, or enabling installments for new issuers, is a scoped change on top of the existing module rather than a rebuild.
A build-to-order 2Checkout / Verifone payment gateway for Magento 2 and Adobe Commerce: localized checkout in 12 languages, iDEAL, Giropay and regional methods, multi-currency global selling, subscription billing and tax/invoicing automation — engineered, installed and supported by ECOSIRE.
A build-to-order Magento 2 extension that forces PSD2-compliant 3D Secure 2 authentication at checkout, with smart frictionless-versus-challenge routing, per-payment-method SCA enforcement, exemption handling (low-value/TRA) and liability-shift tracking. Gateway-agnostic, built and installed by ECOSIRE.
A custom-built Magento 2 / Adobe Commerce extension that automatically recovers lost carts with scheduled multi-step reminder emails, auto-generated coupons, one-click restore links and recovery analytics — engineered, installed and supported by ECOSIRE on your own store.
A custom-built Magento 2 / Adobe Commerce extension that detects abandoned carts and recovers revenue through scheduled, personalized email and SMS sequences. Built, installed, and supported on your store by ECOSIRE.
A custom-built Magento 2 / Adobe Commerce payment gateway for Amazon Payment Services (PayFort) covering UAE, KSA, Egypt, Jordan, Lebanon and Qatar — with tokenized cards, Apple Pay, installments and 3D Secure. Built, installed and supported by ECOSIRE on your store.