Configurations return merchant-level settings.

These are settings that other endpoints depend on, rather than records a merchant creates or edits directly.
Because these values shape what other endpoints accept, checking this configuration first can prevent avoidable errors.
For example, such as attempting a tip adjustment when `isTipsEnabled` is `false`.

Two endpoints make up this group.
Both are read-only; there is no way to create, update, or delete a configuration through the API itself.

* GET /pay-api/v1/configurations/contact-infos.
The contact-infos endpoint returns the merchant's address, phone number, and card details, information that can be reused elsewhere, such as when creating an invoice.
* GET /pay-api/v1/configurations/payments.
The payments endpoint returns the settings that govern how transactions are processed for the merchant account.
This includes whether tipping is enabled, the available currencies, card types, and transaction types, and the list of configured payment processors, each with its own settlement batch time slots.
It also reports defaults such as the surcharge rate, cash discount rate, and dual pricing rate, along with AVS options and the maximum allowed transaction amount.