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: Optional. Two-letter country code (ISO 3166-1 alpha-2) for country-specific payment configurationamount: Optional. Transaction amount for payment method configurationzoneId: Optional. Payment zone identifier to retrieve zone-specific 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: Optional. Two-letter country code (ISO 3166-1 alpha-2) for country-specific payment configurationamount: Optional. Transaction amount for payment method configurationzoneId: Optional. Payment zone identifier to retrieve zone-specific 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:
The API returns the available payment methods, merchant account details, and payment gateway configurations for a specific payment zone site assignment.
The response includes:
Authentication & Authorization
The client requesting payment configuration 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-orders,sfcc.shopper-baskets-orders.rw, orsfcc.shopper-standardin the client ID used to generate the SLAS token. For a full list of permissions, see the Authorization Scopes Catalog.Use Cases
Retrieve Payment Configuration
Retrieve payment configuration settings for Stripe, PayPal, and Adyen based on the payment methods enabled in the merchant's payment zone site. This includes API keys, vendor details, and live/test mode status. Specify a zone via
zoneIdor usecurrencyandcountryCodefor automatic resolution.*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: