Payment — Data & read/write tables

Database view and external concepts that Payment reads/writes. Conventions: 📖 READ, ✏️ WRITE (insert/update).

Data read/write

Area	Data
Payment customer	AccountPaymentCustomer, provider token, BU scope, active status.
Direct payment	DirectPaymentBatch, DirectPayment, batch type, provider reference.
Method settings	Payment gateway settings, master toggle, method availability, category option.
Deposit	Booking order deposit flags/snapshot, checkout lock, paid/result state.
Checkout result	Success/failure message, method resolution, redirect/result payload.
Zero-amount checkout	No provider touched; resolve intent from payment settings + DD state + booking eligibility 📖 READ.
PayLater display name	BusinessUnitPaymentSetting.PayLaterDisplayName ✏️ WRITE (admin); 📖 READ via BookingForCheckoutModel for checkout.
PayLater eligibility	ProgramCategory.PayLaterAllowedTypeId, ProgramCategory.SubsidyEnabled 📖 READ — category scope + subsidy gate.
Billing payment option	Billing.PaymentOptionId ✏️ WRITE only for non-immediate (DD=4, Other=1); not written for Pay Now/Pay Deposit.
Success message settings	PayNowSuccessMessage, PayNowDepositSuccessMessage, DirectDebitSuccessMessage, PayLaterMessage ✏️ WRITE; 📖 READ at resolve time.
Windcave mode	BU payment setting mode XML/REST ✏️ WRITE; 📖 READ for every checkout/callback.

External providers

Provider	Role
Windcave	Card/PayNow checkout, result URL, notification/webhook.
Kiwi	Direct Debit customer create and debit/provider sync.
Accounting provider	Payment can affect finance/accounting sync but does not own accounting mapping.

Data from other domains

Domain	Why Payment reads it
Finance	Invoice/billing/payment option and reconciliation state.
Booking	Order ids, lock state, deposit eligibility, confirm after deposit.
Subscription	Billing schedule/payment selection during enrollment.
Master Data	Account, BU, site/category scope and provider config.

Related

• Architecture & data — provider, batch, token.
• Finance — documents & paid status.