Magento · Adobe Commerce

One composer require. Your Magento checkout, finished.

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.

Magento Open Source 2.4Adobe Commerce, on-prem and CloudLuma, Hyvä and headlessComposer, no core overrides
Sales › Orders41,206created · Processing
deploy@northfield-prod ~/magentoMagento 2.4.8
bash · northfield-prod
northfield.com/checkout
Demo store on Magento Open Source 2.4.8. Each command lights one more piece; when the module is enabled, Krepling Pay is live in the payment step and every order is created in Sales › Orders.
Three ways in

A payment method, the whole checkout, or the assistants.

One extension, configured under Stores › Configuration › Sales › Payment Methods, with website and store-view scope like everything else in Magento.

A payment method in the checkout you run today

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.

What staysTheme, checkout, cart price rules, tax, shipping, order emails, Sales › Orders
What changesThe payment step, the processor, the rate
Price2.5% + 30¢ per successful charge
Luma, Hyvä and headless, live

Or let Krepling be the checkout

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.

What staysCart, catalog, price rules, tax, shipping, invoices, shipments, Sales › Orders
What changesThe checkout page itself
One ruleCarts with a subscription always use the full page
Drawer and full page, live

Beacon and AI Channel read the catalog over GraphQL

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.

AssistantsGemini, Claude, Perplexity today · ChatGPT and Copilot as ACP opens
What it adds$0. Agent orders cost what every order costs.
FixesWritten to the catalog only when you approve, with an undo
How it works on Magento
AI Feed1,240 products · 4 store views · synced 6 min ago
Ridgeline Shell JacketPrice per store view, stock, sizes, fabric: readable
Alpine Pack 32LNo volume attribute on the EU store view. Agents can't answer “how many litres?”
Agent order · via Gemini · $289.00Paid on Krepling · order #000041208 · Processing
$0 added
Every storefront Magento runs

Luma, Hyvä, headless. Embedded, drawer or full page.

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.

northfield.com/checkout/#paymentEmbedded · Luma
ConfigurationScope: Northfield US
Stores › Configuration › Sales › Payment Methods › Krepling Pay
Krepling Paykrepling/module-payment 2.3.1
EnabledYes[website]
Checkout displayEmbedded in the Magento checkout[store view]
StorefrontLuma · Knockout componentdetected
TitleCredit card[store view]
Payment actionAuthorize and capture[website]
Sort order1[website]
Carts with a subscription always use the full-page checkout.
Side by side

Krepling Pay next to the gateways Magento ships with.

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.

Payment Services
How it installsComposer, from the Marketplace. One module, Luma, Hyvä and GraphQL in the box.Marketplace extension; Cloud merchants get it preinstalledMarketplace extensionCore moduleCore moduleCore module
Where it runsIn the payment step, as a drawer over the cart, or as the whole checkout. One config value, per store view.In the payment stepIn the payment stepIn the payment step; the PayPal button opens PayPalIn the payment stepIn the payment step
Returning shoppersKrepling Wallet: recognised at any Krepling store, on any platform. A code to email or phone, no password, no Magento account.Vaulted cards for logged-in customersLink, at stores running StripeA PayPal accountVaulted cards for logged-in customersVaulted cards for logged-in customers
SubscriptionsBuilt in: plans, renewals, retries, card updates. No subscription extension to buy.Needs a subscription extensionNeeds a subscription extensionNeeds a subscription extensionNeeds a subscription extensionNeeds a subscription extension
B2B on Adobe CommerceCompany accounts pay a negotiable quote on Krepling, by card or net terms; the invoice and the dunning are Krepling's.Card on the quoteCard on the quotePayPal on the quoteCard on the quoteCard on the quote
Kora, the voice assistantOn cart and checkout: answers out loud, adds and removes products, checks shoppers out.Not part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gateway
AutopilotTests the live checkout per store view: display, field order, wallet order. Nothing changes until you approve it.Not part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gateway
Selling in AI assistantsAI Channel: Gemini, Claude, Perplexity; ChatGPT and Copilot as ACP opens. Orders land in Sales › Orders.Not part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gateway
US online card rate2.5% + 30¢Interchange plus a markup, quoted on your sales order2.9% + 30¢ · +1.5% international3.49% + 49¢ PayPal button · 2.99% + 49¢ card fields2.59% + 49¢2.9% + 30¢ · $25 a month
Published US rates and features as of November 2026, from each provider's pricing and documentation pages. Adobe Payment Services prices by interchange plus a negotiated markup, so it isn't in the calculator. Rates vary by product and change; check theirs before you decide.
Processing cost at your volumeUS card payments through each gateway, at your monthly volume and order size.
Monthly card volume$250,000
About 865 orders a monthKrepling Pay against Stripe: —
Krepling Pay—2.5% + 30¢ · the extension is free
—2.9% + 30¢ · +1.5% on international cards
—2.99% + 49¢ card fields · 3.49% + 49¢ with the button
—2.59% + 49¢ per card transaction
—2.9% + 30¢ plus $25 a month
Domestic US cards only; international, currency-conversion and dispute fees are extra on every gateway. Krepling Pay's published rate is 2.5% + 30¢ per successful charge; enterprise volumes are priced on the Scale page.
Beacon · AI Channel

Your catalog, read by the assistants. Per store view. Bought from, too.

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.

Visibility scorenorthfield.com · US store view · 5 assistants · 40 questions
Up 6 this week
0of 100
Named first for “waterproof shell jacket under $300”Skipped for “32 litre daypack in Europe”: no volume attribute on the EU view
From the catalog to the order$0 added by Krepling
Magento catalog1,240 products · 4 store views · GraphQL, read-only
AI FeedFixes drafted, approved by you, undoable
The assistantsNamed, then bought from where checkout is supported
Sales › Orders#000041208 · Processing · tagged krepling-ai
Fix drafted · Alpine Pack 32L · EU store viewVolume attribute “32 L” added to the feed; written to the catalog only if you press it
Agent order · via Gemini · Ridgeline Shell JacketPaid on Krepling Pay · order #000041208 · invoice created · your emails, your fulfilment
Processing
Read-only until you press a fix

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.

Per store view

The EU view is answered in euros with its own attributes; the US view in dollars. Beacon scores each view on its own.

A Magento order like any other

Stock reserved, invoice created, emails sent, your fulfilment extensions fired. Tagged by assistant in Sales › Orders and in Reports.

The rest of your store

Everything else keeps working.

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.

Cart price rules and coupons

Magento applies the rule; Krepling charges the result. Nothing is recomputed outside your server.

Shipping methods and table rates

Carriers, table rates and free-shipping thresholds are read as they are; the shopper picks the method in the checkout you chose.

Tax

Magento tax rules, Avalara or Vertex calculate it; the total Krepling charges includes it. Nothing to reconfigure.

Customer accounts and groups

Shoppers stay Magento customers in their groups, with group pricing intact. Krepling's sign-in by code sits alongside.

Invoices, shipments, credit memos

Authorize and capture or authorize only; invoices on capture, credit memos refund through Krepling. The order lifecycle is Magento's.

Websites, stores and currencies

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.

Page Builder, Live Search, ERP connectors

Content, search and the integrations around the order don't see a difference: it's a Magento order with a payment on it.

B2B on Adobe Commerce

Company accounts, shared catalogs, requisition lists and purchase orders carry on. Quotes can be paid on Krepling, by card or on terms.

Any storefront. Luma, Hyvä or headless.

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 write-back

Every order is a Magento order.

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.

Read from Magentonorthfield.com · 4 store views · todayWritten back by Krepling Pay
0.4 sfrom payment to the order in Sales › Orders
4store views, four currencies, one connection
0core files overridden
1module: Luma, Hyvä and GraphQL
Multi-store

One connection. Every store view, every currency.

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.

Stores › All Stores · Northfield1 Krepling connection · 4 store views
Krepling Pay · default scopeEnabled: Yes · Payment action: Authorize and capture · one merchant account, three settlement entities
Charged in the display currency

The shopper pays what the price shows; no conversion at checkout. Settlement follows the entity you map each view to.

Config scope like everything else

Enable at default, override the display or the title per website or store view. The same scope rules Magento uses for tax and shipping.

One grid, one report

Sales › Orders shows every view; Krepling Reports splits payments by store view, currency and entity.

B2B on Adobe Commerce

A company's quote, paid on Krepling. By card or on terms.

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.

Quote Q-2291 · Summit Guides Co.Negotiated by Priya Nair · shared catalog “Outfitters” · PO SG-2026-0417
Accepted
ItemQtyTier priceLine
Ridgeline Shell Jacket · assorted sizes40$239.00$9,560.00
Merino Base Layer40$78.00$3,120.00
Negotiated discount · 5% on the quote−$634.00
Freight · pallet to Jackson, WY$180.00
Quote total$12,226.00
How the company pays
Company account · Summit Guides Co.
AdminPriya Nair
Customer groupOutfitters · tier pricing
Payment on KreplingCard on file · net 30 approved
Credit limit$25,000 · $12,226 used
Krepling Wallet

Recognised in your checkout. No Magento account needed.

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.

  • Guest checkout stays guest checkout; no account to create, no password to set.
  • Card, address and delivery preference filled; he confirms and places the order.
  • Works the same on every store view and in every currency.
Hollin · a WooCommerce storeVisa •••• 6020Jonas A. · hollin.co · Aug 19
VeldtVisa •••• 6020Jonas A. · veldt.audio · Oct 3
Northfield · today · MagentoJonas Ahl1510 Pearl St · Visa •••• 6020Pay $499.07
Code sent to jonas@ahl.co · recognised from Veldt
Subscriptions

Plans without a subscription extension. Renewals as Magento orders.

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.

  • Keep, skip, swap or send now from the shopper's portal; every change is a comment on the order.
  • Card updates arrive from the network before the next renewal.
  • Carts with a plan use the full-page checkout.
Merino Base Layer × 2 · $196.00Every 6 months · Visa •••• 6020 · next May 12
Active
For developers

A proper Magento 2 module. Nothing clever.

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.

Magento Open Source2.4.4 to 2.4.8 · PHP 8.1 to 8.4
Adobe Commerce2.4.4 to 2.4.8 · on-prem and Cloud
StorefrontsLuma · Hyvä Checkout 1.1+ · PWA Studio · any GraphQL client
Standard gateway interfaces

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.

Three front ends from one module

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.

Keys and environments

Merchant ID and secret key per website scope; a sandbox pair for staging. Webhook signatures verified with the secret; replayable from the portal.

Upgrade-safe

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.

Install

Four steps. Two in the terminal, two in admin.

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.

  1. 1
    Require the packagecomposer require krepling/module-payment from repo.magento.com, or from the Marketplace zip on a server without Composer access.
  2. 2
    Enable and deploybin/magento module:enable Krepling_Payment, setup:upgrade, setup:di:compile, cache:flush. Static content deploys in production mode as usual.
  3. 3
    Connect and pick a displayStores › Configuration › Sales › Payment Methods › Krepling Pay: Merchant ID and secret key from your portal, Enabled: Yes, Embedded, Drawer or Full page. Scope per website or store view.
  4. 4
    Place a test orderIt lands in Sales › Orders as Processing with its invoice. Then switch on Beacon, AI Channel and Kora from the portal.
Pricing
2.5%+ 30¢

The extension is free. The rate is the same on every edition.

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.

IncludedThe extension for Luma, Hyvä and headless; embedded, drawer and full-page checkout; Krepling Wallet, sign-in by code, Kora, Autopilot, Subscriptions, B2B terms, Checkout Studio, Beacon, AI Channel, Reports, dispute responses prepared for every case.
Not includedYour Adobe Commerce licence and hosting, your other extensions, and any platform fee an assistant charges, which is listed before you switch that channel on.
LeavingSet Enabled to No, or disable the module, and your previous gateway is back on the next cache flush. Orders, customers and quotes stay in Magento.
FAQ

Questions, answered.

Still wondering? Speak to an expert.

Which editions and versions does it support?
Magento Open Source and Adobe Commerce, on-prem and on Cloud, 2.4.4 through the current 2.4.8 line, on PHP 8.1 to 8.4. The Marketplace listing shows the exact versions each release is tested against.
Does it work with Hyvä?
Yes. The module ships a Hyvä Checkout component alongside the Luma one; the right one loads for the theme you run. Hyvä's own Luma-fallback checkout works with the Luma component.
We're headless on PWA Studio. What do we get?
GraphQL: Krepling Pay is a payment method you set with 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.
Does the module store card details in Magento?
No. Card fields load from Krepling's hosted card-fields service and are tokenized in Krepling's PCI environment; Magento stores a token reference only. Your SAQ scope stays small.
How does multi-store work?
Enable once at the default scope and override per website or store view like any Magento config. Each view charges in its display currency; you map views to settlement entities in the portal. One Sales › Orders grid, one Krepling account.
Does it support Adobe Commerce B2B?
Company accounts, shared catalogs, negotiable quotes and purchase orders keep working. An accepted quote can be paid on Krepling by a company card on file or on net terms, with the invoice and reminders handled by Krepling and the order in Adobe Commerce.
Authorize only or authorize and capture?
Either, per website scope. With authorize only, capturing the invoice in admin captures the payment; credit memos refund through Krepling; voiding the order voids the authorization.
Will it slow the storefront down?
The components load on the checkout only, and Kora on the pages you give her. No JavaScript on catalog pages, nothing in the critical path of full-page cache.
Can I go back?
Set Enabled to No, or 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.

You've seen what Krepling Pay can do. Now let's wire it into your Magento store.