Retrieves the payment configuration for the organization.
Parameters:*
siteId: Required. The site identifier for context-specific configurationcurrency: Required. Three-letter currency code (ISO 4217) for payment method configurationcountryCode: Required. Two-letter country code (ISO 3166-1 alpha-2) for country-specific payment configurationResponse Behavior:*
If you would like to get a raw Response object use the other getPaymentConfiguration function.
An object containing the options for this method.
A promise of type PaymentConfiguration.
Retrieves the payment configuration for the organization.
Parameters:*
siteId: Required. The site identifier for context-specific configurationcurrency: Required. Three-letter currency code (ISO 4217) for payment method configurationcountryCode: Required. Two-letter country code (ISO 3166-1 alpha-2) for country-specific payment configurationResponse Behavior:*
An object containing the options for this method.
Set to true to return entire Response object instead of DTO.
A promise of type Response if rawResponse is true, a promise of type PaymentConfiguration otherwise.
Generated using TypeDoc
Shopper Payments
*Download API specification
API Overview
Use the Shopper Payments API to retrieve payment configuration information for organizations in the B2C Commerce system.
The Shopper Payments API provides access to comprehensive payment configuration data, including payment processor settings, gateway configurations, and payment method details.
Authentication & Authorization
The client requesting payment configuration information must have access to the
/payment-configurationresource. The Shopper Payments API requires a shopper access token from the Shopper Login and API Access Service (SLAS).For details on how to request a shopper access token from SLAS, see the guest user flows for public clients and private clients in the SLAS guides.
You must include
sfcc.shopper-baskets-ordersorsfcc.shopper-baskets-orders.rwin the client ID used to generate the token. For a full list of permissions, see the Authorization Scopes Catalog.Use Cases
Payment Method Discovery
Retrieve available payment methods and their capabilities for dynamic payment form generation.
Gateway Status Monitoring
Check the status and configuration of payment gateways and processors.
Payment Flow Configuration
Determine supported payment modes (multi-step vs express) for different payment methods.
SDK Version Management
Ensure compatibility by checking the current SDK version requirements.
Simple example:
API Version: 0.0.33import { ShopperPayments } from "commerce-sdk-isomorphic"; const clientConfig = { parameters: { clientId: "XXXXXX", organizationId: "XXXX", shortCode: "XXX", siteId: "XX" } }; const shopperPaymentsClient = new ShopperPayments(clientConfig);Last Updated: