Terminologies: PaymentModelType library
Related schema specification: PaymentModelType
allowance-overagePaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/allowance-overagePaymentModel
- @type:
- definition:
Payment includes an allowance of billable units (entitlement, consumption, event, monetary value, outcome, or capacity units), with charges for excess units.
- name:
allowance-overage payment model
consumption-basedPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/consumption-basedPaymentModel
- @type:
- definition:
Payment is based on measured consumption units (e.g., data volume, compute time, storage space, network bandwidth).
- name:
consumption-based payment model
fixed-recurringPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/fixed-recurringPaymentModel
- @type:
- definition:
Time-recurring payment grants shared access, independent of billable units (entitlement, consumption, event, monetary value, outcome, or capacity units).
- name:
fixed-recurring payment model
performance-basedPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/performance-basedPaymentModel
- @type:
- definition:
Payment is triggered by achievement of defined outcome units (e.g., qualified leads, completed projects, conversions, performance targets).
- name:
performance-based payment model
retainerPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/retainerPaymentModel
- @type:
- definition:
Time-recurring payment reserves dedicated capacity units (e.g., staff hours, server instances, support slots).
- name:
retainer payment model
revenue-splitPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/revenue-splitPaymentModel
- @type:
- definition:
Payment is determined by dividing aggregated monetary value among participating parties according to predefined shares.
- name:
revenue-split payment model
single-paymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/single-paymentModel
- @type:
- definition:
Payment is made once for access, independent of any billable units (entitlement, consumption, event, monetary value, outcome, or capacity units).
- name:
single-payment model
step-pricingPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/step-pricingPaymentModel
- @type:
- definition:
Payment is determined by predefined thresholds of billable units (entitlement, consumption, event, monetary value, outcome, or capacity units).
- name:
step-pricing payment model
take-ratePaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/take-ratePaymentModel
- @type:
- definition:
Payment is calculated as a fixed percentage of the monetary value of each user transaction, so the user pays more when transaction amounts increase and less when they decrease.
- name:
take-rate payment model
transaction-basedPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/transaction-basedPaymentModel
- @type:
- definition:
Payment is based on counted event units (e.g., processing operations, message deliveries, document generations).
- name:
transaction-based payment model
unit-basedPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/unit-basedPaymentModel
- @type:
- definition:
Payment is based on allocated entitlement units (e.g., users, licenses, devices, seats).
- name:
unit-based payment model
zero-costPaymentModel
metadata sheet
- @context:
@vocab: <https://openminds.om-i.org/props/>
- @id:
https://openminds.om-i.org/instances/paymentModelType/zero-costPaymentModel
- @type:
- definition:
No payment is required for any billable units (entitlement, consumption, event, monetary value, outcome, or capacity units).
- name:
zero-cost payment model