A server-installed Magento payment module
MagicPay redirects Magento customers to a hosted payment page for card entry and handles POS routing. A developer with server access installs the module. Request the package through the demo or contact channel and preserve your current configuration before starting.
The documented Magento releases for this package are 2.4.7 and 2.4.8, with PHP 8.2 or 8.3. The Magento framework dependency is constrained to ~103.0.7. Check these requirements against actual server dependencies; a higher version number alone does not establish suitability. Begin in a test environment.
Place the files and follow Magento's setup sequence
Check the extracted directory structure first. An extra enclosing folder can leave the module outside the expected location. Run setup steps from the Magento root, taking the store's operating mode into account.
- Extract the package into app/code/MagicPay/Checkout and confirm registration.php is directly inside that directory.
- Apply bin/magento module:enable MagicPay_Checkout, bin/magento setup:upgrade and bin/magento setup:di:compile in order.
- In production mode, complete the installation guide's static-content deployment step before bin/magento cache:flush.
- Open Stores > Configuration > Sales > Payment Methods. Enter MagicPay's API key and Secret key, set Enabled to Yes, leave Test mode on and select Save Config.
Match website scope and callback results
Obtain credentials from Ayarlar > API Yetki Yönetimi in MagicPay and keep the secret private. Credentials can be entered at website level. In Stores > Settings > Virtual POS, select the corresponding website. Manage banks in the payment settings opens the same POS management area. Your account needs an active POS.
Place a test order on the website you configured. Pay with a test card on MagicPay and compare the Magento order with the panel transaction. Public HTTPS access is required for notifications; the module supplies the callback address. One website's successful test does not validate the others.
Launch and update by website scope
Keep full or partial refund tests within the remaining refundable balance. Check successful and declined payments, customer returns and order results. Disable test mode in the intended website scope, enter live keys and select Save Config.
For updates, extract the new package into the same directory and repeat the guide's enable, upgrade, compile and cache steps, including static-content deployment in production mode. Repeat order checks for the affected website after changes.