PHPackages                             digitalhydra/clipclap-magento-gateway - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. digitalhydra/clipclap-magento-gateway

ActiveMagento2-module

digitalhydra/clipclap-magento-gateway
=====================================

Extencion para agregar la Billetera ClipClap como metodo de pago

001PHP

Since Apr 20Pushed 10y ago1 watchersCompare

[ Source](https://github.com/digitalhydra/clipclap-magento-gateway)[ Packagist](https://packagist.org/packages/digitalhydra/clipclap-magento-gateway)[ RSS](/packages/digitalhydra-clipclap-magento-gateway/feed)WikiDiscussions master Synced 2mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

Modulo para Magento CE 2.0.x
----------------------------

[](#modulo-para-magento-ce-20x)

Extencion para agregar la Billetera ClipClap como metodo de pago

Technical feature
-----------------

[](#technical-feature)

### Configuracion del modulo

[](#configuracion-del-modulo)

1. El modulo se instala atraves de composer
2. Se debe modificar el archivo composer.json

### Gateway configuration

[](#gateway-configuration)

##### Let's look into configuration attributes:

[](#lets-look-into-configuration-attributes)

- `debug` enables debug mode by default, e.g log for request/response
- `active` is payment active by default
- `model` `Payment Method Facade` used for integration with `Sales` and `Checkout` modules
- `merchant_gateway_key` encrypted merchant credential
- `order_status` default order status
- `payment_action` default action of payment
- `title` default title for a payment method
- `currency` supported currency
- `can_authorize` whether payment method supports authorization
- `can_capture` whether payment method supports capture
- `can_void` whether payment method supports void
- `can_use_checkout` checkout availability
- `is_gateway` is an integration with gateway
- `sort_order` payment method order position on checkout/system configuration pages
- `debugReplaceKeys` request/response fields, which will be masked in log
- `paymentInfoKeys` transaction request/response fields displayed on payment information block
- `privateInfoKeys` paymentInfoKeys fields which should not be displayed in customer payment information block

### Dependency Injection configuration

[](#dependency-injection-configuration)

> To get more details about dependency injection configuration in Magento 2, please see [DI docs](http://devdocs.magento.com/guides/v2.0/extension-dev-guide/depend-inj.html).

In a case of Payment Gateway, DI configuration is used to define pools of `Gateway Commands` with related infrastructure and to configure `Payment Method Facade` (used by `Sales` and `Checkout` modules to perform commands)

Payment Method Facade configuration:

```

        \Magento\ClipClapGateway\Model\Ui\ConfigProvider::CODE
        Magento\Payment\Block\Form
        Magento\ClipClapGateway\Block\Info
        ClipClapGatewayValueHandlerPool
        ClipClapGatewayCommandPool

```

- `code` Payment Method code
- `formBlockType` Block class name, responsible for Payment Gateway Form rendering on a checkout. Since Opepage Checkout uses knockout.js for rendering, this renderer is used only during Checkout process from Admin panel.
- `infoBlockType` Block class name, responsible for Transaction/Payment Information details rendering in Order block.
- `valueHandlerPool` Value handler pool used for queries to configuration
- `commandPool` Pool of Payment Gateway commands

#### Pools

[](#pools)

> ! All `Payment\Gateway` provided pools implementations use lazy loading for components, i.e configured with component type name instead of component object

##### Value Handlers

[](#value-handlers)

There should be at least one Value Handler with `default` key provided for ValueHandlerPool.

```
!-- Value handlers infrastructure -->

            ClipClapGatewayConfigValueHandler

        ClipClapGatewayConfig

```

##### Commands

[](#commands)

All gateway commands should be added to CommandPool instance

```

            ClipClapGatewayAuthorizeCommand
            ClipClapGatewayCaptureCommand
            ClipClapGatewayVoidCommand

```

Example of Authorization command configuration:

```

        ClipClapGatewayAuthorizationRequest
        ClipClapGatewayResponseHandlerComposite
        Magento\ClipClapGateway\Gateway\Http\TransferFactory
        Magento\ClipClapGateway\Gateway\Http\Client\ClientMock

            Magento\ClipClapGateway\Gateway\Request\AuthorizationRequest
            Magento\ClipClapGateway\Gateway\Request\MockDataRequest

        ClipClapGatewayConfig

            Magento\ClipClapGateway\Gateway\Response\TxnIdHandler
            Magento\ClipClapGateway\Gateway\Response\FraudHandler

```

- `ClipClapGatewayAuthorizeCommand` - instance of GatewayCommand provided by `Payment\Gateway` configured with request builders, response handlers and transfer client
- `ClipClapGatewayAuthorizationRequest` - Composite of request parts used for Authorization
- `ClipClapGatewayResponseHandlerComposite` - Composite\\List of response handlers.

Installation
------------

[](#installation)

This module is intended to be installed using composer. After including this component and enabling it, you can verify it is installed by going the backend at: STORES -> Configuration -> ADVANCED/Advanced -> Disable Modules Output Once there check that the module name shows up in the list to confirm that it was installed correctly.

Tests
-----

[](#tests)

Unit tests could be found in the [Test/Unit](Test/Unit) directory.

Contributors
------------

[](#contributors)

Magento Core team

License
-------

[](#license)

[Open Source License](LICENSE.txt)

###  Health Score

18

—

LowBetter than 8% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity1

Limited adoption so far

Community5

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/83e93ea0ca06a34dfdbe2a2aa84458c53110aee9e8c9562b88fe46f27725f7af?d=identicon)[digitalhydra](/maintainers/digitalhydra)

### Embed Badge

![Health badge](/badges/digitalhydra-clipclap-magento-gateway/health.svg)

```
[![Health](https://phpackages.com/badges/digitalhydra-clipclap-magento-gateway/health.svg)](https://phpackages.com/packages/digitalhydra-clipclap-magento-gateway)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)