# magebitcom/magento2-hyva-checkout-checkoutcom-payment

> This module enables to use CheckoutCom_Magento2 module with Hyva checkout

`composer require magebitcom/magento2-hyva-checkout-checkoutcom-payment`

Canonical URL: https://packagento.com/magebitcom/magento2-hyva-checkout-checkoutcom-payment

## At a glance

- **Vendor**: magebitcom (https://packagento.com/magebitcom.md)
- **Latest version**: 1.0.11 — released 2026-02-23
- **Pricing**: Free
- **Package type**: Magento 2 module
- **Status**: active, accepting new buyers

## Installation

Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them.

1. **Sign in or create an account** at https://packagento.com/customer/account/.

2. **Add the package to your account.** Open https://packagento.com/magebitcom/magento2-hyva-checkout-checkoutcom-payment and complete the free checkout. A licence is minted automatically.

3. **Create or pick a project, then activate the licence on it.**
   - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/.
   - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project.

4. **Add the project credentials to your Magento codebase.**

   Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`:

   ```json
   {
     "http-basic": {
       "packagento.com": {
         "username": "ppk_live_...",
         "password": "psk_live_..."
       }
     }
   }
   ```

   Add the Packagento Composer repository to `composer.json`:

   ```json
   {
     "repositories": [
       { "type": "composer", "url": "https://packagento.com" }
     ]
   }
   ```

5. **Install and apply.**

   ```bash
   composer require magebitcom/magento2-hyva-checkout-checkoutcom-payment:*
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```

## What it does

This module enables to use CheckoutCom_Magento2 module with Hyva checkout

## README

### Installation

1. Install [CheckoutCom_Magento2](https://www.checkout.com/docs/payments/accept-payments/connect-to-an-ecommerce-platform/magento-2)
2. Install Compatability Module by running
```bash
composer require magebitcom/magento2-hyva-checkout-checkoutcom-payment
```
3. Enable Module
```bash
bin/magento module:enable Magebit_CheckoutComPayment && bin/magento setup:upgrade
```

### Feature Coverage

- [x] Card Payments (Multiple iframes)
    - [X] Vault
- [x] Google Pay
    - [x] Checkout Page
    - [ ] Cart
    - [ ] Minicart
- [x] Apple Pay
    - [x] Checkout Page
    - [X] Cart
    - [X] Minicart
- [x] Alternative payment methods
    - [X] MB WAY

#### Functionality that is currently not supported:
* Adding a new Stored Card from My Account -> Stored Payment Methods

#### Configurations that currently are not supported:
* Configuration -> Global Settings -> Default Active Method
* Card Payments -> Display Card Icons

#### Payment methods the currently are not supported:
* Klarna (NAS)
* Paypal Payments (NAS)
* MOTO Payments

#### Google Pay Payments: New Configuration Options

* Button corner radius

This option sets the `border-radius` property of the button and is measured in pixels. There is no need to specify the
CSS `px` unit in this option input field.

#### Apple Pay Payments: New Configuration Options

* Button corner radius

This option sets the `border-radius` property of the button and is measured in pixels. There is no need to specify the
CSS `px` unit in this option input field.

* Button height

This option sets the `height` property of the button and is measured in pixels. There is no need to specify the
CSS `px` unit in this option input field.


#### Alternative payments: New Configuration Options

* Enable MB WAY Phone Validation

This option sets strict phone validation for MB WAY phone numbers (must be 9 digits and start with 9).

#### Webhook Configuration for MB WAY Payments

MB WAY payments require webhook configuration to properly handle payment status updates.

The extension use default endpoint URL: https://your-domain.com/checkout_com/webhook/callback which is the same for 
CheckoutCom_Magento2 module.

* MB WAY Status Page Text

Text on waiting page while waiting on webhook events is customizable.

* MB WAY Status Polling Interval

Option to adjust interval at which customer waiting page will look for webhook updates. Recommended value is 3-5 seconds.

* Additional success states

By default, the waiting page will result in success page only if webhook with response code '10000' is received. This
config makes it possible to also select "Payment Pending" and "Payment Capture Pending" as a signal to redirect customer to success page
although after this redirect the order still might get automatically cancelled for example because of "Transaction has expired" error.

---
![magebit (1)](https://github.com/user-attachments/assets/cdc904ce-e839-40a0-a86f-792f7ab7961f)

*Developed by Magebit. Have questions or need help? Contact us at info@magebit.com or on our [website](https://magebit.com/contact).*

## Recent Versions

| Version | Released |
|---|---|
| 1.0.11 | 2026-02-23 |
| 1.0.10 | 2026-02-15 |
| 1.0.9 | 2025-11-24 |
| 1.0.8 | 2025-10-25 |
| 1.0.7 | 2025-10-08 |
| 1.0.6 | 2025-09-30 |
| 1.0.5 | 2025-09-22 |
| 1.0.4 | 2025-05-23 |
| 1.0.3 | 2025-04-07 |
| 1.0.2 | 2025-03-31 |

Showing 10 of 12 versions. Full release history on https://packagento.com/magebitcom/magento2-hyva-checkout-checkoutcom-payment.

## Dependencies

### Require

| Package | Constraint |
|---|---|
| checkoutcom/magento2 | ^7.0.0 |
| hyva-themes/magento2-compat-module-fallback | * |
| hyva-themes/magento2-hyva-checkout | * |
| magento/framework | * |

## Quality

Latest release (1.0.11) passes the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers.


### Compatibility

Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | not tested | not tested | – | – |
| 2.4.8 | – | not tested | not tested | – |
| 2.4.9 | – | – | not tested | not tested |


### Code Quality

Advisory checks against the module's source. Never affect the Compatibility verdict — a phpcs finding can't make a module incompatible.

#### Static Analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Warning | 49 | 49 warnings (ruleset: Magento2) — 4 auto-fixable with phpcbf |
| PHPMD | Warning | 9 | 9 rule violations (UnusedFormalParameter:4, UnusedPrivateField:1, ExcessiveParameterList:1, CyclomaticComplexity:1, NPathComplexity:1) |
| Cpd | Pass | 0 |  |
| Composer validate | Info | 4 | valid; 4 advisory notes (composer validate --strict) |

#### PHPStan

Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | Error | Error | – | – |
| 2.4.8 | – | Error | Error | – |
| 2.4.9 | – | – | Error | Error |


### Tests

Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately.

#### Unit Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |

#### Integration Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |


### Security

Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| Composer audit | N/A | 0 | no resolvable dependency tree to audit — Your requirements could not be resolved to an installable set of packages. Problem 1 |
| Malware scan | Pass | 0 |  |

## Licence and pricing

Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step.

Refundable within 14 days of first purchase via https://packagento.com/account/refunds/.

## Install via Claude Code or any MCP client

The Packagento MCP server can run the licence + project + Composer steps above in one tool call:

```
purchase_and_install_packages(
  composer_names=["magebitcom/magento2-hyva-checkout-checkoutcom-payment"],
  project_id="proj_xxx"
)
```

This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup.

## Vendor

magebitcom is a Magento 2 vendor on Packagento. See https://packagento.com/magebitcom.md for their full catalogue.