implicit.ink
read this in

properties

concern · the second axis

Payment

The storefront concern of which payment-method TYPES an offer accepts at the point of settlement — cash, a payment card, a mobile-money channel, a bank transfer, cash on delivery, a digital wallet, or pay-by-invoice. Orthogonal to `pricing` (the magnitude and composition of the ask) and to `subscription` (the SCHEDULE of paying over time): this concern is the CHANNEL of settlement. Region-neutral: the grammar governs the method TYPE; the specific brand (M-Pesa, Visa, PayPal) is an instance value the seller states, never Pool grammar. A fee charged for paying a particular way is NOT a separate host here — it is a `price_component` line of type=surcharge (pricing concern) qualified by the payment method it applies to. The realised transaction — which brand the buyer used, the amount settled, a percentage-of-order surcharge a checkout computes — is downstream catalogue/offer data (L1).

the questions here

1 question in all: 1 answered from a set list (accepted payment method).

The storefront concern of which payment-method TYPES an offer accepts at the point of settlement — cash, a payment card, a mobile-money channel, a bank transfer, cash on delivery, a digital wallet, or pay-by-invoice. Orthogonal to `pricing` (the magnitude and composition of the ask) and to `subscription` (the SCHEDULE of paying over time): this concern is the CHANNEL of settlement. Region-neutral: the grammar governs the method TYPE; the specific brand (M-Pesa, Visa, PayPal) is an instance value the seller states, never Pool grammar. A fee charged for paying a particular way is NOT a separate host here — it is a `price_component` line of type=surcharge (pricing concern) qualified by the payment method it applies to. The realised transaction — which brand the buyer used, the amount settled, a percentage-of-order surcharge a checkout computes — is downstream catalogue/offer data (L1).

questions in payment1 property
accepted payment method token