Returns detailed bookings made on the OTA. See the Booking Format section of the documentation for the full booking format specification.

Credit/debit card data

If your GetBookingId responses can include guest credit/debit card data
(the Payments object), your channel must be enabled for secure card
handling. A PCI Attestation of Compliance (AoC) document is required before
card data can be enabled for a channel.

Retrieval of card data is handled over a secure path configured on the
Cloudbeds side; your GetBookingId implementation returns the Payments
object as documented in the booking format, with no special handling on your
end.

Within the Payments object, CardNumber and SeriesCode must be encoded
as JSON strings (quoted values, e.g. "SeriesCode": "143"), never as bare
JSON numbers. Card data is tokenized in place with non-numeric tokens;
unquoted numeric values cannot be tokenized.

A booking whose GetBookingId response contains card data is silently
dropped and not imported (no error can be returned on GetBookingId)
unless your channel has been enabled for card handling.