Krepling's cartridges go on your cartridge path like any other. Business Manager activates the code version, the SFRA checkout's payment stage runs on Krepling Pay, and every order is a Salesforce order: New, Paid, ready for export, on every site in the realm. Composable and headless storefronts take the same account through SCAPI hooks.
One set of cartridges, three switches in the Krepling portal. Each one reads the catalog Business Manager already holds and adds something without touching a base cartridge.
int_krepling_sfra adds one payment method to the Payment stage: card fields hosted by Krepling, sign-in by code, the Krepling Wallet's saved cards, Apple Pay and Google Pay. Shipping, promotions, tax and the order itself stay exactly as B2C Commerce builds them.
For a site that wants the whole thing: Checkout in the SFRA cart leads to aurelle.com/checkout, a Krepling page. Six fields, wallets first, Kora on hand, Autopilot testing it. The order is created through the Order API when the payment clears, with the promotions, shipping and tax Business Manager calculated.
The cartridge reads products, prices and inventory per site through the Admin API, read-only. Beacon tells you where the assistants name Aurelle and why not; AI Channel lets Gemini, Claude and Perplexity sell them, with the order landing in Business Manager like any other.
The same Aurelle order, four ways. SFRA takes the cartridge; Composable Storefront and headless builds take the same account through SCAPI hooks and a PWA Kit component; any site can hand its cart to a Krepling checkout instead. The route is a site preference in Business Manager.
Payments on B2C Commerce are a cartridge either way; Salesforce Payments is the native one, powered by Stripe. The four on the right take the card. Krepling Pay takes the card and brings the shopper, the agent, the test and the voice with it.
Agentforce Commerce brings agents to your own storefront and syndicates the catalog to ChatGPT and Google. Beacon scores how the open assistants already answer about you and lists the fixes in order; AI Channel publishes the feed Gemini, Claude and Perplexity can buy from, for $0. The agent's order is paid on Krepling and created in Business Manager, tagged by assistant.
Products, prices and inventory are read with the Admin API scopes you grant. Nothing is written except the fixes you approve, each with an undo.
Aurelle Europe is answered in euros from its own price book; Aurelle Japan in yen. Beacon scores each site on its own.
Inventory reserved, emails sent, exported to Order Management. Tagged by assistant in Business Manager and in Reports.
Krepling Pay is a cartridge among your cartridges. Whatever B2C Commerce calculates before the payment, and whatever your jobs and clouds do after it, carries on.
Promotions, coupon codes and source codes are applied by B2C Commerce; Krepling charges the result.
Methods and rates per site are read as they are; the shopper picks in the stage you kept.
Tax tables or your Avalara or Vertex cartridge calculate it; the total Krepling charges includes it.
Shoppers stay in the realm's customer lists, shared across sites. Krepling's sign-in by code sits alongside.
Recommendations, search dictionaries and predictive sort carry on. Kora reads the same catalog.
Pages, content slots and your components are untouched. The cartridge adds a payment method, not a layout.
Orders export as always, with the payment transaction. Capture and refund from OMS go through Krepling.
The order is a B2C Commerce order, so journeys and segments see it. Krepling Reports adds the payment side.
The cartridge for SFRA, SCAPI hooks and a PWA Kit component for Composable Storefront, the same hooks for any headless front end. No base cartridge is modified.
The cartridge reads what Business Manager knows before the payment and writes back what happened after it: the payment transaction, the order status, the capture, the refund. Jobs, exports and Order Management carry on, on every site.
Aurelle runs three sites in one realm: US, Europe and Japan, each with its locales, price books and tax rules. Krepling Pay is configured once and scoped per site in Business Manager; each site charges in its own currency and settles to its own entity. Pick a site to see its checkout.
Krepling's cartridges move with your code version: upload to a sandbox, test with sandbox keys, replicate to staging, then to production, where the live keys take over. Nothing about the release process changes; the keys are the only thing that differs per instance.
A pendant from the Bond Street vault and studs from the Madison workshop ship on different days. Krepling authorizes the whole order at checkout and captures each shipment as Order Management releases it; a return is refunded from the same screen. Payment status in Business Manager follows.
Claire at Bond Street builds the order for a client in Customer Service Center and sends a Krepling pay request instead of taking a card over the phone. The client pays on his phone, from his wallet, and the order is a normal order in Business Manager, placed by the agent.
Three cartridges on the path, hooks where Salesforce puts them, metadata you import once, a component for PWA Kit, webhooks for everything after the payment. Nothing in app_storefront_base is modified; upgrades stay upgrades.
int_krepling holds the hooks, services and models; int_krepling_sfra the templates and client script for the Payment stage; bm_krepling the Business Manager extension: captures, refunds, the log.
app.payment.processor.KREPLING for SFRA; dw.ocapi.shop.basket.payment_instrument.afterPOST for SCAPI and OCAPI. The same hooks serve Composable Storefront, headless builds and Customer Service Center.
System object extensions for the preferences, services.xml for krepling.http, payment-methods.xml for KREPLING. Imported with your site import or by the install job.
Sandbox and live keys at organization scope, overridable per site; webhooks signed with your secret; events replayable from the portal. A sandbox instance pairs with sandbox keys.
The cartridges upload like any release: Code Deployment or your pipeline. Nothing on a storefront changes until KREPLING is enabled as a payment method on that site, and no base cartridge is touched.
sfcc-ci code:deploy from your pipeline.Per successful charge, on B2C Commerce Growth, Plus and Premium, on every site in the realm. Salesforce charges no fee for the payment provider you choose; your licence is a share of GMV either way. No monthly fee, no setup fee, no subscriptions cartridge to add, no surcharge for agent orders. Beacon and AI Channel are included. Enterprise volumes and multi-entity settlement are priced on the Scale page.