Payment — Core concepts
| Concept | Meaning |
|---|---|
| PaymentOption | Business/customer-facing method: PayLater, PayNow, Direct Debit, Deposit, etc. |
| Payment method availability | Rules deciding which methods are available by BU, site, category, provider, and toggle. |
| PayLater | Continue booking/invoicing while collection happens later. |
| PayNow | Immediate card checkout through a provider. |
| Windcave | Card/checkout provider using redirect/result/webhook flow. |
| Direct Debit | Automatic collection using customer token and debit batch. |
| Kiwi Direct Debit | Provider-specific DD customer create/sync behavior. |
| Deposit | Partial upfront payment for booking; not full invoice settlement. |
| DirectPaymentBatch | Provider transaction group for direct payments or deposit payments. |
| AccountPaymentCustomer | Payment customer profile scoped by account, BU, and provider. |
Payment option vs provider
PaymentOption is the business method users select. Provider is the external system that processes it. PayNow can use Windcave; Direct Debit can use Kiwi.
Deposit is not full payment
Deposit can allow booking confirmation after a partial payment, while Finance may still generate the full invoice. Remaining settlement belongs to later payment/finance workflow.
Ownership summary
| Owner | Owns |
|---|---|
| Payment | Provider transaction, customer token, batch lifecycle, checkout result. |
| Finance | Invoice/billing lifecycle and financial documents. |
| BookingOrder | Booking lock/deposit snapshot for confirmation. |
| BusinessUnit | Method/provider settings and availability scope. |