Salesforce Commerce Cloud

Activate one code version. Every site gets Krepling Pay.

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.

B2C Commerce Growth, Plus and PremiumSFRA, Composable Storefront and headlessEvery site, locale and currencyNo base cartridge modified
Orders18,341Merchant Tools › Ordering · New · Paid
business manager · aurelleCode Deployment
aurelle.com/checkoutKrepling Pay · cartridge
Demo on Salesforce B2C Commerce (Commerce Cloud, now Agentforce Commerce). Activating the code version that carries Krepling's cartridges puts Krepling Pay in the SFRA checkout; each order is created in Business Manager as New · Paid and exported to Order Management.
Three ways in

In your checkout, as the checkout, or in the assistants.

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.

Krepling Pay as the payment method in your SFRA checkout

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.

What staysYour storefront, Business Manager, promotions, shipping, tax, Order Management
What changesThe payment method and the processor
Price2.5% + 30¢ per successful charge · the cartridges are free
Every storefront, live

Or hand the cart to a Krepling checkout on your domain

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.

What staysStorefront, basket, promotions, shipping methods, tax, customer lists
What changesThe checkout pages, the processor, the rate
Per siteAurelle Japan can hand off while Aurelle US keeps the SFRA checkout
The handoff, live

Beacon and AI Channel read the catalog Business Manager already publishes

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.

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 Commerce Cloud
AI Feed1,140 products · 3 sites · synced 4 min ago
Oval Solitaire 1.20 ctPrice, carat, colour, clarity, GIA number, lead time: readable
Aurelle PendantEngraving is a checkout option, not a product attribute. Agents can't answer “can it be engraved?”
Agent order · via Gemini · $3,400.00Paid on Krepling · order 00018343 · New · Paid
$0 added
Every storefront on B2C Commerce

SFRA, Composable Storefront, headless, or the handoff. One cartridge set.

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.

aurelle.com/checkoutSFRA cartridge
KreplingSite Preferences › Custom Preferences

Site: Aurelle US

Route
Payment method in the SFRA checkout
Payment in Composable Storefront · PWA Kit
Headless · SCAPI hooks
Hosted handoff from the cart
Payment method
KREPLING · enabled · processor KREPLING
Mode
Live · production keys
Side by side

Krepling Pay next to Salesforce Payments, Adyen, Braintree and Checkout.com.

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.

Salesforce Payments
Where it runsA payment method in SFRA, a component in Composable Storefront, hooks for headless, or the whole checkout on your domain. A site preference.Overlay cartridge for SFRA; Composable StorefrontCartridge for SFRA; headless through Adyen's APICartridge for SFRACartridge for SFRA; headless through Frames
Returning shoppersKrepling Wallet: recognised at any Krepling store, on any platform. A code to email or phone, no account.Link and saved cards for registered shoppersStored card for registered shoppersStored card for registered shoppersStored card for registered shoppers
SubscriptionsBuilt in: plans, renewals, retries, card updates. No subscriptions cartridge to add.Needs a subscriptions cartridgeNeeds a subscriptions cartridgeNeeds a subscriptions cartridgeNeeds a subscriptions cartridge
Capture on shipAuthorize at order, capture per shipment from Order Management or Business Manager; refunds the same way.Through Salesforce Order ManagementBusiness Manager extension or an OMS adapterBusiness Manager extensionBusiness Manager extension
Kora, the voice assistantOn the storefront, basket and checkout: answers out loud, adds products, checks shoppers out.Not part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gateway
AutopilotTests the live checkout per site: wallet order, field order, the handoff itself. Nothing changes until you approve it.Not 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 in Business Manager.Agentforce Commerce syndicates the catalog to ChatGPT and Google; see belowNot part of the gatewayNot part of the gatewayNot part of the gateway
US online card rate2.5% + 30¢, every editionQuoted: blended, or interchange+ with a Salesforce markupInterchange++ · $0.13 + 0.6% + interchange2.59% + 49¢ cards · 3.49% + 49¢ PayPalQuoted: interchange++
Salesforce's fee for using itNoneNoneNoneNoneNone
Published US rates and features as of November 2026, from each provider's pricing and documentation pages. Salesforce Payments is powered by Stripe and priced by quote; Adyen and Checkout.com price interchange++. Your B2C Commerce licence is a share of GMV whichever gateway you run. Rates change; check theirs before you decide.
Processing cost at your volumeKrepling Pay's published rate against the blended rate you pay today. Enterprise gateways on B2C Commerce are quoted, so set yours.
Monthly card volume$900,000
Your rate today2.60%
Plus, per charge30¢
About 265 orders a month—
Krepling Pay—2.5% + 30¢ · the cartridges are free · no Salesforce fee
Your current gateway—2.60% + 30¢ · as set above
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 · Agentforce

Your catalog, read by the assistants. Bought from, too.

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.

Visibility scoreaurelle.com · Aurelle US · 5 assistants · 40 questions
Up 6 this week
0of 100
Named first for “oval diamond solitaire under $10,000 with a GIA report”Skipped for “yellow gold pendant that can be engraved”: engraving isn't a product attribute
From the catalog to the order$0 added by Krepling
Business Manager catalog1,140 products · 3 sites · Admin API, read-only
AI FeedFixes drafted, approved by you, undoable
The assistantsNamed, then bought from where checkout is supported
Orders00018343 · New · Paid · tagged krepling-ai
Fix drafted · Aurelle PendantEngraving added as a product attribute in the feed; written to the catalog only if you press it
Agent order · via Gemini · Aurelle PendantPaid on Krepling Pay · order 00018343 · your emails, your Order Management
New · Paid
Agentforce CommerceSalesforce's agents and channelsBeacon · AI Channel · Kora
Where it livesAgents configured in Salesforce, on your storefront and in Business Manager; channel syndication set up with Salesforce.Three switches in the Krepling portal; the cartridge reads the catalog per site, read-only.
On your storefrontA shopper agent: a chat concierge that recommends products and helps with orders.Kora: a voice assistant that answers out loud, adds to the basket and checks out. Beacon shows what shoppers are asking.
AssistantsChatGPT and Google, through the Agentic Commerce Protocol and Google's protocol; your own Agentforce agents elsewhere.
Gemini, Claude and Perplexity today; ChatGPT and Copilot as ACP opens. Beacon scores all five.
Checkout and paymentCheckout inside the assistant through Stripe and Salesforce Payments, where the channel supports it.Paid on Krepling Pay; the order is created in Business Manager like any other, tagged by assistant.
What it adds to the billPriced with your Salesforce contract; agent usage is metered.$0. Agent orders cost what every order costs.
Status · November 2026Agents shipping across the Agentforce Commerce releases; ChatGPT and Google syndication announced and rolling out.Live for Gemini, Claude and Perplexity; ChatGPT and Copilot wait on each assistant's checkout opening.
As published by Salesforce and the assistants in November 2026; both change often. Running both is fine: Agentforce for your storefront's agents, Beacon and AI Channel for the open assistants.
Read-only until you press a fix

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.

Per site

Aurelle Europe is answered in euros from its own price book; Aurelle Japan in yen. Beacon scores each site on its own.

A Salesforce order like any other

Inventory reserved, emails sent, exported to Order Management. Tagged by assistant in Business Manager and in Reports.

The rest of your realm

Everything else keeps working.

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.

Campaigns and promotions

Promotions, coupon codes and source codes are applied by B2C Commerce; Krepling charges the result.

Shipping methods

Methods and rates per site are read as they are; the shopper picks in the stage you kept.

Tax

Tax tables or your Avalara or Vertex cartridge calculate it; the total Krepling charges includes it.

Customer lists

Shoppers stay in the realm's customer lists, shared across sites. Krepling's sign-in by code sits alongside.

Einstein

Recommendations, search dictionaries and predictive sort carry on. Kora reads the same catalog.

Page Designer

Pages, content slots and your components are untouched. The cartridge adds a payment method, not a layout.

Order Management

Orders export as always, with the payment transaction. Capture and refund from OMS go through Krepling.

Marketing Cloud and Data Cloud

The order is a B2C Commerce order, so journeys and segments see it. Krepling Reports adds the payment side.

Any storefront. SFRA, Composable or headless.

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

Every order is a Salesforce order.

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.

Read from Business Manageraurelle · 3 sites · todayWritten back by Krepling Pay
0.4 sfrom payment to the order in Business Manager
3sites, three currencies, one connection
2key sets, sandbox and live, across four instances
0base cartridges modified
Multi-site

One realm. Every site, locale and currency.

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.

Administration › Sites › Manage Sites1 Krepling connection · 3 sites
Krepling Pay · the cartridgesConfigured once at organization scope · overridden per site · settlement per entity · Beacon per site
The instance path

Sandbox to production, the way your releases already travel.

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.

Realm · aurelle
Sandboxdev01-aurelleDeveloper sandboxv26_11_kreplingKrepling keys · sandboxCartridges uploaded here first. Test cards, no money moves.
Developmentdevelopment-aurelleDevelopmentv26_11_kreplingKrepling keys · sandboxIntegration testing with the SI's QA; the same sandbox keys.
Stagingstaging-aurelleStagingv26_11_kreplingKrepling keys · sandboxCode and data staged; the replication source for production.
Productionproduction-aurelleProductionv26_10_releaseKrepling keys · liveShoppers and Order Management. Live keys at organization scope.
Krepling keys per instance
sandbox
pk_test_aurelle_7f3a…Sandbox, development and staging · test cards only
live
pk_live_aurelle_c91e…Production only · Custom Preferences at organization scope
Order Management

Authorize at order. Capture when it ships.

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.

Order 00018342 · Elena Moreauaurelle.com · Aurelle US · $11,105.25 · Amex •••• 1007
Paid
Aurelle Pendant 0.50 ct · yellow goldFO-0001 · Bond Street vault · ships Tuesday
$3,701.75
Diamond studs 1.00 ctFO-0002 · Madison workshop · prong check · ships Thursday
$7,403.50
What happens
Order Summary · 00018342Order Management
FO-0001 · Bond Street vaultAurelle Pendant · ship to 40 Bond St
Shipped
FO-0002 · Madison workshopDiamond studs · prong check
Allocated
Payment SummaryKREPLING · Amex •••• 1007
Authorized$11,105.25
Captured$0.00
Refunded$0.00
Balance to capture$11,105.25
Customer Service Center

A phone order, paid by the client. No card read aloud.

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.

Customer Service CenterNew orderOrdersCustomersAgent · Claire D. · Bond Street
RK
Rohan K.rohan.k@example.com · Aurelle customer list · 2 orders · paid on Krepling before
Registered

Basket

Diamond line bracelet18k white gold · 17 cm · complimentary resize
$6,200.00
Shipping
Insured courier · 40 Bond St pickup · complimentary
Total
$6,750.25 · incl. $550.25 tax

Payment

Send a Krepling pay request to the client's phone
Enter card details by phone · disabled by Aurelle's policy
Nothing is charged until the client confirms.
9:41Messages
Rohan's phone
For developers

Built the way B2C Commerce expects.

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.

PlatformB2C Commerce 24.x to 26.x · SFRA 6 and 7 · SiteGenesis on request
StorefrontsSFRA · Composable Storefront (PWA Kit, Managed Runtime) · headless on SCAPI or OCAPI · hybrid
Business ManagerCode Deployment · Custom Preferences at site scope · Services framework · Jobs
Three cartridges

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.

Hooks, not overrides

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.

Metadata, once

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.

Keys and instances

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.

Install

Four steps. All of them in Business Manager.

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.

  1. 1
    Upload the cartridgesAdministration › Site Development › Code Deployment: int_krepling, int_krepling_sfra and bm_krepling into the active code version, or sfcc-ci code:deploy from your pipeline.
  2. 2
    Add them to the cartridge pathAdministration › Sites › Manage Sites › Aurelle US › Settings: int_krepling_sfra:int_krepling in front of your custom cartridges; bm_krepling on the Business Manager site.
  3. 3
    Import the metadata and connectSite import of the metadata, then Custom Preferences › Krepling: merchant ID, keys, mode. Enable KREPLING under Ordering › Payment Methods.
  4. 4
    Place a test orderIt lands in Ordering › Orders as New · Paid. Then switch on Beacon, AI Channel and Kora from the portal.
Business ManagerMerchant ToolsAdministrationSite: Aurelle US
Pricing
2.5%+ 30¢

The cartridges are free. Salesforce adds nothing on top.

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.

IncludedThe three cartridges, the hosted checkout on your domain, the PWA Kit component and the SCAPI hooks, Krepling Wallet, sign-in by code, Kora, Autopilot, Subscriptions, capture on ship, Checkout Studio, Beacon, AI Channel, Reports, dispute responses prepared for every case.
Not includedYour B2C Commerce licence, your SI's hours, and any platform fee an assistant charges, which is listed before you switch that channel on.
LeavingDisable KREPLING as a payment method and your previous methods are back on the next page load. Orders, customers and exports stay in Salesforce.
FAQ

Questions, answered.

Still wondering? Speak to an expert.

Is this a LINK cartridge? Where do we get it?
LINK is retired; Salesforce lists B2C Commerce cartridges on AppExchange after its security review. Krepling's cartridges are live today and the listing follows. Until then, Krepling sends you the cartridges, the metadata and the install guide, and sets up the sandbox keys with your team.
Does it work with Composable Storefront?
Yes. The payment runs through the same SCAPI hooks the cartridge installs, and a PWA Kit component renders Krepling's step in your checkout on Managed Runtime. Hybrid sites, PWA Kit pages with an SFRA checkout, work too.
We're still on SiteGenesis.
The controller version of int_krepling runs on SiteGenesis storefronts on request; the templates differ, the hooks don't. Tell us before you plan the release and we'll scope it with your SI.
Can we keep Salesforce Payments for a while?
Yes. KREPLING is one payment method among those enabled on a site, so two providers can run side by side during a migration, or per site. Autopilot can test the order of methods and wallets within Krepling's step.
Do orders still export to Order Management?
Yes. The order carries a payment transaction with processor KREPLING and the authorization, and exports as always. Order Management captures each shipment and refunds returns through Krepling; payment status in Business Manager follows.
How do instances and keys work?
Sandbox keys on sandbox, development and staging; live keys on production. Both live in Custom Preferences at organization scope, overridable per site, and replicate with your data like any preference.
What about Salesforce B2B Commerce?
B2B Commerce runs on the Salesforce core platform, a different product from B2C Commerce. Krepling takes payments there through a Lightning component on request, with net terms and invoices handled by Krepling. Speak to an expert and we'll scope it.
Does the cartridge store card details in B2C Commerce?
No. Card fields are hosted by Krepling and tokenized in Krepling's PCI environment; the payment instrument on the order carries a token. Saved cards live in the Krepling Wallet, not in your realm.
Can we go back?
Any time. Disable KREPLING under Payment Methods and your previous methods are back on the next page load; remove the cartridges from the path with your next release. Orders stay in Salesforce and your history in the portal.

You've seen what Krepling Pay can do. Now let's deploy it to your Salesforce storefronts.