Krepling Pay installs as a Magento 2 extension from the Adobe Commerce Marketplace. It becomes a payment method in your Luma or Hyvä checkout, or takes the whole checkout over, on every store view and in every currency, with saved cards, subscriptions, B2B terms and Kora built in. Orders land in Sales › Orders as they always have.
One extension, configured under Stores › Configuration › Sales › Payment Methods, with website and store-view scope like everything else in Magento.
Luma, Hyvä Checkout or your own theme. Krepling Pay appears in the payment step with sign-in by code, saved cards and subscription plans inside it. Shipping, tax, cart rules and the order are Magento's; the payment step is Krepling's. Hosted card fields, so no card data touches your server.
Set the display to Drawer or Full page and Krepling's checkout takes over from the cart: six fields, wallets first, Kora on hand, Autopilot testing it. Magento still owns the quote, the order, invoices, shipments and credit memos.
The extension gives Krepling a read-only view of products, prices and stock per store view. Beacon tells you where the assistants name you and why not; AI Channel lets Gemini, Claude and Perplexity sell them, with the order created in Sales › Orders like any other.
The same Northfield order, every way. The extension renders a Knockout component for Luma, a Magewire component for Hyvä Checkout, and exposes GraphQL mutations for PWA Studio or any headless front end. The display is one config value, scoped per website or store view.
PayPal, Braintree and Authorize.net come in the box; Adobe Payment Services and Stripe come from the Marketplace. All five take the card. Krepling Pay takes the card and brings the shopper, the plan, the quote, the assistant and the test with it.
Magento has no built-in way into Gemini, Claude or Perplexity. The extension exposes your products, prices and stock over GraphQL, read-only and scoped per store view, so the US and EU views are answered in their own currency. Beacon scores how the assistants answer about you; AI Channel publishes the feed they can buy from. An agent's order is paid on Krepling and created in Sales › Orders, tagged by assistant.
Products, prices and stock are read over GraphQL with an integration token you scope. Nothing is written except the fixes you approve, each with an undo.
The EU view is answered in euros with its own attributes; the US view in dollars. Beacon scores each view on its own.
Stock reserved, invoice created, emails sent, your fulfilment extensions fired. Tagged by assistant in Sales › Orders and in Reports.
Krepling Pay is a module among your modules. Whatever Magento calculates before the payment step, and whatever your other extensions do after it, carries on.
Magento applies the rule; Krepling charges the result. Nothing is recomputed outside your server.
Carriers, table rates and free-shipping thresholds are read as they are; the shopper picks the method in the checkout you chose.
Magento tax rules, Avalara or Vertex calculate it; the total Krepling charges includes it. Nothing to reconfigure.
Shoppers stay Magento customers in their groups, with group pricing intact. Krepling's sign-in by code sits alongside.
Authorize and capture or authorize only; invoices on capture, credit memos refund through Krepling. The order lifecycle is Magento's.
Scope the config per website or store view; the charge is made in the store view's display currency, settled to the entity you choose.
Content, search and the integrations around the order don't see a difference: it's a Magento order with a payment on it.
Company accounts, shared catalogs, requisition lists and purchase orders carry on. Quotes can be paid on Krepling, by card or on terms.
One module ships the Knockout component, the Hyvä Checkout component and the GraphQL schema. No core overrides, so 2.4.x upgrades don't break it.
The module reads what Magento knows before the payment and writes back what happened after it: the order, its state and status, the invoice, the stock, the renewal. Your observers and plugins fire as they always have, on every store view.
Northfield runs four store views on one Magento. Krepling Pay is enabled once at the default scope; each view charges in its own display currency, settles to the entity you map it to, and writes its orders to the one Sales › Orders grid. Pick a view to see its checkout.
The shopper pays what the price shows; no conversion at checkout. Settlement follows the entity you map each view to.
Enable at default, override the display or the title per website or store view. The same scope rules Magento uses for tax and shipping.
Sales › Orders shows every view; Krepling Reports splits payments by store view, currency and entity.
Summit Guides Co. has a company account, a shared catalog and a negotiable quote for forty shells. When the quote is accepted, Krepling Pay collects it: a card on file, or net 30 with the invoice, the reminders and the receipt handled by Krepling. The purchase order and the order itself stay in Adobe Commerce.
Magento's vault remembers cards for customers who registered. The Krepling Wallet remembers anyone who has paid at any Krepling store, on any platform. Jonas bought headphones at Veldt last month; at Northfield he types his email, gets a code, and his Visa and address are there.
Magento has no subscriptions of its own. Krepling's plans live in the extension: Jonas's base layers renew every six months on the card he saved, and each renewal is a new order in Sales › Orders with its invoice. When a card declines, the order is marked Payment review and the plan paused; Autopilot retries at the hour that card usually clears.
Composer package, standard payment gateway interfaces, config in system.xml with full scope, GraphQL mutations for headless, webhooks for everything that happens after the payment. No core overrides, no setup scripts that touch your schema beyond its own tables.
Built on Magento\Payment\Gateway: command pool, request builders, response handlers. Authorize, capture, refund, void and vault all go through the usual commands, so your own plugins and observers see them.
A Knockout component for Luma, a Magewire component for Hyvä Checkout, and setPaymentMethodOnCart plus placeOrder over GraphQL for headless. Hosted card fields in all three; card data never reaches your origin.
Merchant ID and secret key per website scope; a sandbox pair for staging. Webhook signatures verified with the secret; replayable from the portal.
No preferences on core classes, no layout overrides outside the payment step, declarative schema for its two tables. setup:upgrade and setup:di:compile, as with any module.
The extension comes from the Adobe Commerce Marketplace like any other. Require it, enable it, paste your keys, pick a display. Nothing on the storefront changes until Enabled is set to Yes and the config is saved.
composer require krepling/module-payment from repo.magento.com, or from the Marketplace zip on a server without Composer access.bin/magento module:enable Krepling_Payment, setup:upgrade, setup:di:compile, cache:flush. Static content deploys in production mode as usual.Per successful charge, on Magento Open Source, Adobe Commerce and Adobe Commerce on Cloud, on every store view. No monthly fee, no setup fee, no subscription extension to buy, no surcharge for agent orders. Beacon and AI Channel are included; the checkout display is your choice. Enterprise volumes and multi-entity settlement are priced on the Scale page.
setPaymentMethodOnCart and complete with placeOrder, with a client token mutation for the hosted card fields. The drawer and full page also work as a route in any front end via checkout.js.module:disable, and your previous gateway is back after a cache flush. Orders, invoices, customers and quotes stay in Magento; your Krepling history stays in the portal.