Configuration

Caller-scoped configuration served directly by payments-backend. Both are resolved from the authenticated account/entity — there are no account ids in these paths (the admin variants, which take an explicit account id, live under the Admin API section).

What's here

• Payment Config — get and update the calling account's payment configuration (auto-convert, default payout currency, supported deposit currencies).
• Entity Config — read the calling entity's configuration (enabled products, business home URL, personal-enabled and legacy flags).

Requires a user JWT (role management:user); updating payment config requires the X-USER-UNIQUE-ID header.