creditkey / b2bgateway

creditkey/b2bgateway

Credit Key integration with payment gateway

magento2-module Compatibility: 2.4.7-2.4.8 Code Quality: Fail Tests: N/A Security: Pass

Are you the maintainer of creditkey?

Packagento pulls creditkey's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

Credit Key Magento 2 Module

Installation

From your root Magento directory, run the following command:

% composer require creditkey/b2bgateway

Then enable the module with the following commands:

% php bin/magento module:enable CreditKey_B2BGateway
% php bin/magento setup:upgrade

Configuration

From the Magento admin, navigate to Stores > Configuration > Sales > Payment Methods and scroll down to the Credit Key (Gateway) section.

The Marketing Content on Product Pages section allows you to enable the Credit Key marketing content to be displayed on the selected product detail pages. You can enable/disable this feature globally, select the specific categories to allow the content to be displayed on the products belonging to said categories, and select the style of the displayed content.

Payment Action can be set to Authorize or Authorize and Capture. Authorize and Capture will create an invoice when an order is created. Authorize will not create an invoice when an order is created.

Customization

To move the location of the marketing display on the product details page you will need to modify the file catalog_product_view.xml from your active theme. This will most likely be located at {magento_root}/app/design/frontend/{YourCompany}/{theme-name}/Magento_Catalog/layout/catalog_product_view.xml.

In this file you would simply use the <move> element to move our block, named product.info.creditkey.marketing, to the new location. For example, if you wanted it to be just below the "Add to Cart" button it would look something like the following where element is the name of our block, destination is the name of the container you are moving it into, and after is the name of the block or container it will go after. This could instead be before if you want to place it before a specific block/container.

<?xml version="1.0"?>
<page layout="1column" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
    <body>
        <move element="product.info.creditkey.marketing" 
                destination="product.info.form.content" 
                after="product.info.addtocart"/>
    </body>
</page>

To see the available containers you can use reference Magento's primary catalog_product_view.xml file, located at vendor/magento/module-catalog/view/frontend/layout/catalog_product_view.xml.

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
1.0.72 stable Fail Magento 2.4.7-2.4.8 Details 2026-05-21 19:42:22
1.0.71 stable Not tested Not yet tested Details 2025-09-17 18:40:09
1.0.69 stable Not tested Not yet tested Details 2025-06-06 17:37:49
1.0.68 stable Not tested Not yet tested Details 2025-05-16 14:38:06
1.0.66 stable Not tested Not yet tested Details 2025-04-08 19:57:35
1.0.65 stable Not tested Not yet tested Details 2024-08-20 14:53:46
1.0.64 stable Not tested Not yet tested Details 2023-12-26 15:07:16
1.0.63 stable Not tested Not yet tested Details 2023-01-10 16:54:51
1.0.62 stable Not tested Not yet tested Details 2022-09-30 16:16:49
1.0.61 stable Not tested Not yet tested Details 2022-09-12 16:44:11
1.0.60 stable Not tested Not yet tested Details 2022-07-19 21:11:11
1.0.59 stable Not tested Not yet tested Details 2022-05-04 13:23:40
1.0.58 stable Not tested Not yet tested Details 2022-02-14 14:57:57
1.0.56 stable Not tested Not yet tested Details 2021-10-06 20:43:38
1.0.55 stable Not tested Not yet tested Details 2021-08-17 13:38:41
1.0.54 stable Not tested Not yet tested Details 2020-12-23 20:18:04
1.0.52 stable Not tested Not yet tested Details 2020-10-22 18:40:16
1.0.51 stable Not tested Not yet tested Details 2020-03-10 14:19:23
1.0.50 stable Not tested Not yet tested Details 2019-10-16 16:21:01
1.0.49 stable Not tested Not yet tested Details 2019-10-04 00:12:06
1.0.48 stable Not tested Not yet tested Details 2019-09-27 14:37:30
1.0.47 stable Not tested Not yet tested Details 2019-09-16 14:17:44
1.0.46 stable Not tested Not yet tested Details 2019-08-21 13:28:34
1.0.45 stable Not tested Not yet tested Details 2019-08-16 20:41:35
1.0.44 stable Not tested Not yet tested Details 2019-08-05 20:35:47
1.0.43 stable Not tested Not yet tested Details 2019-07-26 20:37:37
1.0.42 stable Not tested Not yet tested Details 2019-06-17 19:53:37
1.0.41 stable Not tested Not yet tested Details 2019-06-12 19:37:59
1.0.40 stable Not tested Not yet tested Details 2019-06-10 17:28:14
1.0.39 stable Not tested Not yet tested Details 2019-06-05 14:20:05
1.0.38 stable Not tested Not yet tested Details 2019-05-21 00:58:04
1.0.37 stable Not tested Not yet tested Details 2019-05-14 18:36:55
1.0.36 stable Not tested Not yet tested Details 2019-05-13 17:04:32
1.0.35 stable Not tested Not yet tested Details 2019-05-10 06:06:24
1.0.34 stable Not tested Not yet tested Details 2019-05-09 14:26:22
1.0.33 stable Not tested Not yet tested Details 2019-05-08 01:46:02
1.0.32 stable Not tested Not yet tested Details 2019-05-07 23:53:28
1.0.30 stable Not tested Not yet tested Details 2019-05-06 19:12:00
1.0.29 stable Not tested Not yet tested Details 2019-05-04 20:45:51
1.0.28 stable Not tested Not yet tested Details 2019-05-02 17:25:14
1.0.27 stable Not tested Not yet tested Details 2019-05-02 00:39:41
1.0.26 stable Not tested Not yet tested Details 2019-05-01 19:53:41
1.0.25 stable Not tested Not yet tested Details 2019-04-26 19:41:19
1.0.24 stable Not tested Not yet tested Details 2019-04-11 17:50:09
1.0.23 stable Not tested Not yet tested Details 2019-04-05 20:19:37
1.0.22 stable Not tested Not yet tested Details 2019-03-29 21:53:51
1.0.21 stable Not tested Not yet tested Details 2019-03-29 19:31:53
1.0.20 stable Not tested Not yet tested Details 2019-03-29 14:16:17
1.0.19 stable Not tested Not yet tested Details 2019-03-28 15:49:26
1.0.18 stable Not tested Not yet tested Details 2019-03-27 20:36:31
1.0.17 stable Not tested Not yet tested Details 2019-03-26 16:19:41
1.0.15 stable Not tested Not yet tested Details 2019-02-07 14:46:03
1.0.13 stable Not tested Not yet tested Details 2019-01-29 21:17:09
1.0.12 stable Not tested Not yet tested Details 2019-01-24 17:24:43
1.0.11 stable Not tested Not yet tested Details 2019-01-24 17:13:44
1.0.10 stable Not tested Not yet tested Details 2019-01-24 17:03:24
1.0.9 stable Not tested Not yet tested Details 2019-01-24 15:56:13
1.0.8 stable Not tested Not yet tested Details 2019-01-08 20:59:10
1.0.7 stable Not tested Not yet tested Details 2019-01-08 20:36:37
1.0.6 stable Not tested Not yet tested Details 2019-01-02 01:30:29
1.0.5 stable Not tested Not yet tested Details 2018-12-09 21:03:33
1.0.4 stable Not tested Not yet tested Details 2018-12-04 22:30:01
1.0.2 stable Not tested Not yet tested Details 2018-09-05 19:28:40
1.0.1 stable Not tested Not yet tested Details 2018-09-05 18:56:51
1.0.0 stable Not tested Not yet tested Details 2018-09-04 16:39:03
0.9.1 stable Not tested Not yet tested Details 2018-08-30 22:33:12
0.9.0 stable Not tested Not yet tested Details 2018-08-30 21:40:55

Requires 5

Package Constraint
creditkey/creditkey-php >=1.0.7
magento/framework >=101.0.0
magento/module-checkout >=100.2.0
magento/module-payment >=100.2.0
magento/module-sales >=101.0.0

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Fail di error

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. 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.

Static analysis results
Tool Status Findings Summary
PHPCS Warning 28 28 warnings (ruleset: Magento2)
PHPMD Warning 15 15 rule violations (UnusedLocalVariable:5, MissingImport:4, NPathComplexity:2, ExcessiveMethodLength:2, ExcessiveParameterList:1)
Cpd Warning 1 1 duplicated chunk spanning 68 total lines (min-lines=5, min-tokens=70)
Composer validate Info 7 valid; 7 advisory notes (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 33 33
2.4.8 33 33
2.4.9 33 34

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
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

Integration tests results by Magento and PHP version
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

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0

No license declared

This package's composer.json doesn't declare a license, homepage, or authors. Check the source repository for terms of use.

Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.