Read Check payment

GET

/v1/object-types/hospitality.check_payment/objects/{id}

const url = 'https://api.aerandil.com/v1/object-types/hospitality.check_payment/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://api.aerandil.com/v1/object-types/hospitality.check_payment/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
  --header 'Authorization: Bearer <token>'

Read an existing instance.

One tender taken against a guest check (check_payment_on_check) — the kernel is the system of record for a check’s payments. amount is what it applied to the check, tip rides beside it and stays out of what was paid; cash may be tendered above the balance and gives change_given. A card payment carries the terminal’s references (psp_reference, terminal_transaction_id, poiid), never card data. A room charge or charge-to-key posts to its folio (check_payment_to_folio) one charge per revenue category and the tip as a gratuity charge (check_payment_posted_charge). allocation records the payment’s share of each revenue category and its VAT, so a check paid in parts sums exactly. Written only by add_check_payment / settle_check.

Authorizations

aerandil_oauth
objects:read
aerandil_oauth
objects:hospitality.check_payment:read

Parameters

Path Parameters

required

string format: uuid

Object id (UUID v7, server-generated at create time).

Query Parameters

branch

string format: uuid

Read through an open branch’s copy-on-first-write overlay view instead of the canonical (main) plane. Does not compose with as_of (422). The branch must exist under the caller’s tenant.

Responses

200

Object found.

application/json

object

created_at

required

string format: date-time

required

string format: uuid

object_type

required

Allowed value: hospitality.check_payment

properties

required

object

allocation

required

Check payment allocation

Per revenue category, what of amount paid it and the tax inside that share, per rule — apportioned by largest remainder over what the earlier payments left, so a check’s payments sum exactly to its categories and its VAT. A room charge posts these shares to the folio.

Array<object>

object

amount

required

object

amount

required

string format: decimal

currency

required

string format: iso-4217

revenue_category

required

string

Allowed values: food non_alcoholic_beverage alcoholic_beverage other

tax

required

object

amount

required

string format: decimal

currency

required

string format: iso-4217

tax_lines

required

Array<object>

object

amount

required

object

amount

required

string format: decimal

currency

required

string format: iso-4217

code

required

string

inclusive

required

boolean

jurisdiction

required

string

rate

required

string format: decimal

allowance_applied

Check payment allowance applied

What of the payment the stay’s package allowance covered — the food and soft-drink share, capped at what the day’s allowance had left, never the tip. The folio carries that part as the package’s balance-neutral consumption line and only the rest as charges the guest owes; the consumption row names this payment (consumption_for_check_payment). Absent when nothing was covered.

object

amount

required

string format: decimal

currency

required

string format: iso-4217

amount

required

Check payment amount

Applied to the check (tip excluded)

object

amount

required

string format: decimal

currency

required

string format: iso-4217

authorised_by

The manager whose say-so overrode the stay's posting rules — the staff member signed in when the payment was taken

string format: uuid

change_given

Check payment change given

Change handed back (cash only)

object

amount

required

string format: decimal

currency

required

string format: iso-4217

external_ref

Source-system key for replayed / connector-landed payments

string

guest_id

The guest who signed

The guest the server confirmed for a room charge — the reservation’s guest (a sharer signs on their own booking). Carried onto the folio charges as signed_by.

string format: uuid

required

Payment id

string

override_kind

What a manager's override let through: the stay's no-post flag (no_post) or its credit (no_credit)

string

Allowed values: no_post no_credit

override_reason

Why the manager overrode the stay's posting rules

string

paid_at

required

When the payment was taken — business time

string format: date-time

poiid

The terminal (point of interaction) the card was taken on

string

psp_reference

The processor's reference for the card payment (Adyen pspReference) — an identifier, not a credential

string

recorded_by

required

Principal::stable_id() of the principal that took the payment

string

reservation_id

The reservation a room charge posted to

The booking whose bill a room charge or charge-to-key posted to — the folio belongs to it (a stay’s window or the booking’s own account). OHIP posts to a reservation, never to a room.

string format: uuid

staff_member_id

The staff member who took the payment, when the session is one

string format: uuid

tender

required

Tender

string

Allowed values: room_charge cash card comp external charge_to_key

tendered

Check payment tendered

Cash handed over (cash only)

object

amount

required

string format: decimal

currency

required

string format: iso-4217

terminal_transaction_id

The terminal's own transaction id for the card payment

string

tip

required

Check payment tip

The tip taken with the payment — a pass-through to the staff under the Employment (Allocation of Tips) Act 2023, never revenue and never in paid_total. Zero when none.

object

amount

required

string format: decimal

currency

required

string format: iso-4217

provenance

Per-property source attribution and pins. An entry under properties means the property’s current value came from that source (on the source’s own clock, source_updated_at); an entry under pins is a human override protecting the property from sourced writes.

object

pins

object

key

additional properties

object

pinned_at

string format: date-time

pinned_by

object

reason

required

string

properties

object

key

additional properties

object

external_id

string

recorded_at

required

string format: date-time

source

required

string

source_updated_at

string format: date-time

stream

string

scope

required

One of: discriminator: level

object

level

required

string

Allowed value: tenant

Allowed values: tenant

tenant_id

required

string format: uuid

updated_at

required

string format: date-time

version

required

integer

>= 1

Example

{
  "object_type": "hospitality.check_payment",
  "properties": {
    "allocation": [
      {
        "revenue_category": "food"
      }
    ],
    "override_kind": "no_post",
    "tender": "room_charge"
  },
  "scope": {
    "level": "tenant"
  }
}

Headers

ETag

string

/^"\d+"$/

Quoted strong validator (RFC 7232 §2.3) carrying the object’s monotonic version. Informational on the read path — object mutation goes through typed actions on /v1/actions/{action}/apply, not raw CRUD.

404

No object with that id (or soft-deleted).