Beispielhafte VorschauA custom-built Tamara payment method for Magento 2 / Adobe Commerce
— Pay in 3, Pay Later and Pay Now with on-site widget messaging, installed and supported on your store by ECOSIRE.
Was ist Tamara BNPL for Magento 2?
A custom-built Tamara payment method for Magento 2 / Adobe Commerce — Pay in 3, Pay Later and Pay Now with on-site widget messaging, installed and supported on your store by ECOSIRE. Built to order by ECOSIRE for Magento 2 / Adobe Commerce (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
Hauptfunktionen
Auf Bestellung gebaut, komplett für Sie erledigt
Keine Selbsteinrichtung — eine funktionierende App, die von ECOSIRE erstellt, installiert und betreut wird.
- 1
Sie bestellen
Starten Sie mit einem einmaligen Entwicklungspreis. Den Umfang legen wir beim Kickoff gemeinsam fest.
- 2
Wir bauen & installieren
ECOSIRE erstellt, konfiguriert und installiert sie auf Ihrem Magento 2.
- 3
Go-live + Support
Sie gehen in etwa einer Arbeitswoche live, mit zwei Wochen Go-live-Support. Fehler im von uns gelieferten Code beheben wir kostenlos.
Über dieses Produkt
Tamara BNPL for Magento 2 is a build-to-order payment integration that adds Saudi-born Tamara — Pay in 3, Pay Later and Pay Now — as a native payment method on your Magento 2 (Open Source) or Adobe Commerce store. This is not an instant Adobe Commerce Marketplace download. ECOSIRE builds the module to your environment, installs it on your Magento install, configures the Tamara merchant credentials, and supports it after go-live.
Under the hood it ships as a proper module under app/code/Ecosire/TamaraBnpl, wired through di.xml and etc/payment.xml, implementing Magento's payment service contracts (Magento\Payment\Gateway command pool: authorize, capture, refund, void). Checkout uses a Magento_Checkout / Magento_Payment UI component (Knockout.js renderer) so the Tamara option renders cleanly in the one-page and Hyvä/PWA checkouts. The Tamara Checkout API session is created server-side via a virtual-typed HTTP client; the shopper is redirected to Tamara to complete approval, then returned through a controller that finalizes the order.
On-site widget messaging (the "or 4 interest-free payments of…" snippet) is injected on PDP, cart and checkout via layout XML blocks and the Tamara JS SDK, with the instalment plan keyed to the product/cart total and store currency (SAR, AED, KWD).
Order lifecycle stays in sync: a webhook controller plus Magento observers/events (sales_order_save_after, order_cancel_after) reconcile authorized → captured → refunded states, so an admin credit memo in Magento triggers a real Tamara refund and partial refunds map line-by-line. Status reconciliation runs on cron. Admin configuration lives under Stores → Configuration → Payment Methods, gated by an ACL resource, with sandbox/production toggle and per-website scope. Every build includes a sandbox walkthrough, documentation, and a support window. Sharia-compliant, interest-free instalments are handled entirely by Tamara — ECOSIRE delivers the clean Magento integration around them.
Was Sie bekommen
- A custom Magento 2 module (Ecosire_TamaraBnpl) under app/code, built and tested against your exact Magento/Adobe Commerce version
- Installation and configuration on your Magento environment, including composer/setup:upgrade, DI compilation and static content deploy
- Tamara merchant account wiring: API key, notification/webhook token and merchant URL configuration in sandbox then production
- On-site widget placement tuned to your theme (Luma, Hyvä or custom) on PDP, cart and checkout
- End-to-end sandbox test walkthrough covering approval, capture, full refund and partial refund
- Admin and developer documentation, plus a post-launch support window for fixes and Magento-version compatibility questions
Für wen das ist
Saudi & GCC online retailer
A merchant on Magento 2 selling into KSA, UAE or Kuwait who wants Tamara's locally trusted, Sharia-compliant BNPL brand at checkout to lift conversion and average order value without building the integration in-house.
Magento agency / system integrator
A development partner delivering a GCC store who needs a clean, service-contract-based Tamara module they can hand to a client, rather than spending sprint time reverse-engineering the Tamara Checkout API and webhook flow.
Headless / Hyvä storefront owner
A team running PWA Studio, Hyvä or a custom GraphQL frontend that needs Tamara to work through API-driven checkout and on-site messaging, not just the legacy Luma one-page checkout.
Wie Tamara BNPL for Magento 2 im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Magento 2 nativ |
|---|---|---|---|---|
| Tamara Pay in 3 / Pay Later / Pay Now at checkout | Im Lieferumfang enthalten | Teilweise Unterstützung | Im Lieferumfang enthalten | Nicht im Lieferumfang enthalten |
| Built and tested against your exact Magento/Adobe Commerce version | Im Lieferumfang enthalten | Im Lieferumfang enthalten | Nicht im Lieferumfang enthalten | Nicht im Lieferumfang enthalten |
| Installed and configured on your store (not a self-install zip) | Im Lieferumfang enthalten | Teilweise Unterstützung | Nicht im Lieferumfang enthalten | Nicht im Lieferumfang enthalten |
| On-site widget messaging on PDP, cart and checkout | Im Lieferumfang enthalten | Teilweise Unterstützung | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
| Webhook + cron order/refund reconciliation out of the box | Im Lieferumfang enthalten | Teilweise Unterstützung | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
| Headless / Hyvä / GraphQL checkout support | Im Lieferumfang enthalten | Teilweise Unterstützung | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
| Post-launch support and Magento-version compatibility maintenance | Im Lieferumfang enthalten | Nicht im Lieferumfang enthalten | Teilweise Unterstützung | Nicht im Lieferumfang enthalten |
| No per-seat license fee or annual extension subscription | Im Lieferumfang enthalten | Im Lieferumfang enthalten | Nicht im Lieferumfang enthalten | Im Lieferumfang enthalten |
Häufig gestellte Fragen zu Tamara BNPL
Is this an instant download from the Adobe Commerce Marketplace?
No. This is a build-to-order integration. ECOSIRE builds the Tamara module specifically for your Magento 2 / Adobe Commerce version, installs it on your environment, configures your Tamara merchant credentials, and supports it afterward. You are not buying a generic Marketplace zip — you are buying a delivered, working integration on your store.
How long does delivery take after I order?
Typical delivery is about 5 to 10 business days from the point we have access to your Magento environment (staging or production) and your Tamara sandbox/production credentials. Timelines can shift with theme complexity (heavily customized or Hyvä checkouts), custom currency rules, or if Tamara merchant onboarding is still pending on your side. We confirm a firm date once we review your setup.
What do you need from me to get started?
Your Magento version and access (SSH/admin to a staging environment, or a deploy path), your Tamara merchant account with sandbox and production API keys, and the storefronts/currencies where Tamara should appear. If your Tamara account isn't approved yet, we can build and test against the sandbox in parallel.
Do you provide ongoing support and updates?
Yes. Every build includes a post-launch support window for bug fixes and configuration help. After that, ECOSIRE offers ongoing support and compatibility maintenance — for example adjusting the module for Magento 2.4.x patch upgrades or changes in the Tamara API. We scope continued support separately so you only pay for what you need.
Will refunds and order cancellations sync correctly with Tamara?
Yes. Issuing a credit memo in the Magento admin triggers a real refund through Tamara's refund API, including partial, line-level refunds. Order state is kept in sync through Tamara webhooks plus Magento observers, and a cron reconciliation job recovers any webhook that was missed, so Magento and Tamara never drift out of agreement.
Does it work with Adobe Commerce and headless/Hyvä storefronts?
Yes. The module is built on Magento payment service contracts and the gateway command pool, so it runs on both Magento Open Source and Adobe Commerce. Because checkout is API-driven, it also works with GraphQL/REST headless setups, PWA Studio and Hyvä — we tune the on-site widget placement to your specific theme.
Verwandte Module
Stripe Payments Gateway for Magento 2
A full Stripe payment connector built to order for your Magento 2 / Adobe Commerce store — cards, wallets, Link, BNPL and SCA-compliant 3DS2 — installed and supported by ECOSIRE on your own install.
Tabby BNPL for Magento 2
A custom-built Tabby buy-now-pay-later payment method for Magento 2 / Adobe Commerce, with on-site split-in-4 messaging — built, installed and supported on your store by ECOSIRE.
Tax Compliance & Rates Engine (GCC/EU/US)
A custom-built Magento 2 / Adobe Commerce extension that automates multi-region tax calculation (GCC VAT, EU VAT, US sales tax, India GST) with clean region-isolated rules, address-based rate determination, and return-ready reporting. Built, installed and supported by ECOSIRE on your store.
TaxJar Sales Tax Automation for Magento 2
A build-to-order Magento 2 / Adobe Commerce extension that connects your store to the TaxJar API for rooftop-accurate US sales-tax calculation, economic nexus tracking, and filing preparation. ECOSIRE builds, installs, and supports it on your install.
Tamara BNPL
A custom-built Tamara payment method for Magento 2 / Adobe Commerce — Pay in 3, Pay Later and Pay Now with on-site widget messaging, installed and supported on your store by ECOSIRE.
- Native Tamara payment method supporting Pay in 3, Pay Later (single deferred payment) and Pay Now, selectable at Magento checkout
- On-site widget messaging on PDP, cart and checkout, with instalment amounts derived from the live product/cart total and store currency (SAR, AED, KWD)
- Server-side Tamara Checkout API session creation with redirect-and-return flow handled by a dedicated Magento controller
- Full gateway command pool via service contracts: authorize, capture, refund, void — no direct DB writes