* B2C Commerce *

🤖 Build real expertise for the Agentic AI era. 

Trailhead Journeys are now available across 10 Salesforce products empowering you to move from fundamentals to advanced expertise with a progressive, step-by-step curriculum. 

Newly added journeys:

• ⚡ Headless 360 platform
• 📈 Agentforce Marketing
• 👥 Agentforce Service 
• 🛒 Agentforce Commerce
• 🔌 Omnistudio

Skip the search. Start the journey 👉 trailhead.com/trailhead-journeys

I have created an API Client under Account Manager

In Business Manager for my user under  Manage Access Keys I created "Agent User Login and OCAPI"

When I test making a call to https://[sandbox domain]/dw/oauth2/access_token?client_id={API Client ID}

with header info:

basic_auth_token = b64encode(

            bytes(f"{business_manager_username}:{business_manager_password}:{api_client_password}",

                  "utf-8")

        ).decode("ascii")

headers = {}

authorization = f"Basic {basic_auth_token}"

headers["Authorization"] = authorization

headers["Content-type"] = "application/x-www-form-urlencoded"

headers["Cache-Control"] = "no-cache" 

and

data = {

"grant_type": "urn:demandware:params:oauth:grant-type:client-id:dwsid:dwsecuretoken"

}

I keep getting HTTP 400 with error message:

"Client id 'client id' has invalid credentials to use grant type 'urn:demandware:params:oauth:grant-type:client-id:dwsid:dwsecuretoken'."

anyone can pinpoint what I am doing wrong?

@* B2C Commerce * 

We're building out Headless 360 learning on Trailhead and want your input. 💙  

We're running a short survey to understand what you want to learn, how you like to learn, and which use cases matter most to your work. 

👉 Take the Headless 360 survey now through July 28.

Thank you for taking the time to provide this valuable feedback! 🙌  

Hii Salesforce Community,. 

1. I need a complete, step-by-step guide for integrating Salesforce Payments with Salesforce Order Management (OMS). 

Please explain the entire implementation process, including: 

• How to configure and integrate Salesforce Payments with Salesforce OMS from scratch.
• The prerequisites, required licenses, and Salesforce features that must be enabled.
• How to connect Salesforce Payments to OMS, including the objects, settings, and relationships involved.
• The complete payment lifecycle, including Authorization, Capture, Void, and Refund.
• How payment transactions are associated with Orders and Fulfillment Orders in OMS.
• Whether payment capture is handled automatically by Salesforce OMS when an order is fulfilled, or whether custom automation (such as Flows, Apex, Platform Events, or APIs) is required.
• The standard APIs, payment gateway adapters, and integration points involved in the process.
• A complete end-to-end implementation example, from checkout through order creation, fulfillment, payment capture, cancellation, and refund.
• Salesforce best practices, common implementation challenges, and recommended architecture for a production environment.

2. How does payment capture work in Salesforce Order Management (OMS) when an order reaches the Fulfilled status? 

• I would like a complete, step-by-step explanation of the end-to-end payment capture process, including:

• Whether Salesforce OMS automatically captures an authorized payment when an order is fulfilled, or if custom automation is required.

• The complete implementation flow from payment authorization through order fulfillment to payment capture.

• Which standard Salesforce OMS components, payment gateway integrations, and APIs are involved in the capture process.

• If automation is required, please explain how to implement it using Flows, Apex, Platform Events, or other recommended approaches.

• Include a practical example with the order lifecycle, payment transaction states, and best practices for production implementations.