# Changelog: 1.23.0

The bank details a guest is told to transfer money to must be right before a
site goes live. This release makes the account holder of a `bank_transfer`
payment option the PMS payment settings' holder and nothing else, and exposes
the same details read-only so they can be verified without creating a booking.

## Added

- `BookingService.getBankTransferDetails()`: the bank account the booking
  output's `bank_transfer` payment options will show, as
  `ReadonlyArray<BookingBankTransferDetails>` (`holder?`, `iban`,
  `swiftOrBic?`, `institution?`) with at most one entry, read from the PMS's
  primary document settings. It runs the same v10 document-settings query
  the `book` flow runs before the booking mutation and maps it with the same
  parser, so the two cannot disagree. Creates no booking, reservation or other
  PMS write. Empty when the account offers no bank transfer. Optional on the
  service shape, as the 1.22.0 additions were, so custom implementations of
  `BookingService` keep compiling; the v10 live layer provides it.
- `BookingBankTransferDetails` and `BookingBankTransferDetailsSchema`.

## Changed

- `holder` on the `bank_transfer` payment option is optional. When the PMS
  payment settings carry no holder, the option has no `holder` instead of an
  empty string. It is never substituted with another name.

## Unchanged

- Every other field of the booking output and of the other payment option
  variants.