No. This is a build-to-order integration. ECOSIRE engineers the Ecosire_BnplGcc module against your specific Magento version, theme, and GCC currencies, then installs and validates it on your store. You are buying a built-and-installed solution with support, not a self-service Marketplace ZIP.

After purchase we confirm your Magento version (Open Source or Adobe Commerce), storefront type (Luma or headless), and target currencies, then schedule the build. Typical delivery is roughly one working week depending on theme complexity and how quickly your Tabby and Tamara merchant accounts and API credentials are available. We give you a firm date during scoping before any build starts.

Yes. Tabby and Tamara each onboard, underwrite, and settle merchants directly. You hold the merchant contracts and receive settlement; we integrate the gateways using the API keys and webhook secrets from your provider dashboards. We can guide you through obtaining and configuring credentials during the build.

Delivery includes a warranty window for defect fixes after go-live. Because Tabby, Tamara, and Magento all ship updates, we offer an optional ongoing support and maintenance plan covering API/webhook changes, Magento minor-version compatibility, and enhancements. Without a plan, post-warranty changes are quoted per request.

Yes. The module is built on Magento service contracts and the gateway command framework, so it runs on both Magento Open Source and Adobe Commerce. For headless storefronts we expose the BNPL methods and promo data through GraphQL/REST so your PWA checkout can render and complete Tabby and Tamara flows. Confirm your stack during scoping so we target it precisely.

Refunds are wired to Magento's native credit memo workflow. Issuing a full or partial credit memo in admin triggers a refund gateway command to the correct provider (Tabby or Tamara), and a cron reconciliation job keeps Magento order state aligned with provider settlement status so your finance reporting stays accurate.