This request requires a valid access token. See Authentication to obtain one with
POST /v1/auth/token before you continue.Branding profiles
Branding profiles — the colors, button styles, and typography for hosted checkout — are set up for you by RadiumOne support, not through this API. Contact support to create or change a profile, then reference it from a checkout session (see Brand the payment page).GET /v1/merchant/config and GET /v1/merchant/checkout below still return your resolved branding profile.
Merchant configuration
GET /v1/merchant/config returns your account-level hosted-checkout configuration: allowed redirect domains, your default branding profile, and whether a redirect secret is currently set.
Merchant checkout settings
GET /v1/merchant/checkout returns the settings hosted checkout’s front end resolves for your account — the same branding and configuration, in the shape the checkout page itself consumes. Its resolved branding profile’s button_text is null when blank, never an empty string.
Authentication and scopes
These endpoints use the same merchant bearer token as the rest of the Payments API. Reads (GET) require the payment-gateway:merchant-config-read scope; rotating or disabling the redirect secret requires payment-gateway:merchant-secret-rotate.
Next steps
Customize checkout
Reference a branding profile from a checkout session.
Rotate or delete your redirect secret
The other merchant-account setting managed through this API.