Resolve payment credential and CRM pipeline commitment boundaries

Add research on PCI/tokenized payment references vs login Credentials (Payment
Instrument Reference, Payment Mandate) and CRM Opportunity promotion thresholds
(Pipeline Pursuit, binding_trigger). Resolve OpenQuestions for both topics.
Update glossary, conceptual model, terminology, and downstream recommendations.
This commit is contained in:
2026-06-21 23:11:00 +02:00
parent bd272151af
commit 6ea582cd9e
11 changed files with 435 additions and 19 deletions

View File

@@ -104,6 +104,11 @@ Evidence or secret material used to prove control, entitlement, or a claim.
Examples: password, passkey, certificate, hardware token, verifiable
credential, recovery code, signed assertion.
Excludes: payment card PAN, CVV, track data, and other PCI cardholder data —
those stay in payment-provider or PCI-scoped downstream vaults. Excludes
tokenized payment method references (`pm_xxx`); use **Payment Instrument
Reference** and **Payment Mandate** instead.
## Claim
A statement made by an issuer or source about an actor, account, identifier,
@@ -239,12 +244,55 @@ An evidenced obligation that binds commercial parties and raises the cost of
identity fluidity for counterparties.
Examples: signed contract, active subscription, payment mandate, regulated
onboarding acceptance, qualified electronic seal on an agreement.
onboarding acceptance, qualified electronic seal on an agreement, executed
purchase order.
Commercial Commitment carries lifecycle state (proposed, active, breached,
fulfilled, expired, revoked) and may attach to Commercial Relationship,
Commercial Record, or Legal Entity/Organization actors.
Recommended `commitment_type`: `contract` | `subscription` | `payment_mandate` |
`regulatory_onboarding` | `purchase_order` | other.
Does not include CRM pipeline stages by default — see **Pipeline Pursuit**.
Salesforce Forecast "Commit" category is sales confidence, not this concept.
## Payment Instrument Reference
A **Scoped Identifier** for a tokenized payment instrument in a payment-provider
scope — not PAN, not a login **Credential**.
Examples: Stripe `pm_xxx`, SEPA mandate reference, network token ID, display
last4 + fingerprint.
Links to **Commercial Record**. Carries `provider_scope`, `instrument_type`,
`reusable`, and `lifecycle_state` (attached, detached, revoked). CHD stays
downstream; canon holds references only.
## Payment Mandate
A **Commercial Commitment** (`commitment_type: payment_mandate`) authorizing
future charges against a **Payment Instrument Reference**.
Created when customer consent is evidenced (SetupIntent success, signed debit
mandate, card-on-file with off-session authorization). Distinct from
**subscription** commitment but often co-created at checkout. Assurance tier:
committed.
## Pipeline Pursuit
A Record layer artifact for an in-flight sales or procurement deal before a
binding **Commercial Commitment** exists.
Examples: Salesforce Opportunity, HubSpot deal, renewal pursuit on existing
account.
Carries `stage`, `forecast_category`, expected amount/date, and `lifecycle_state`
(open, won, lost). Stage changes are **Evidence Source** (internal telemetry);
they do not alone create Commercial Commitment. Promote to commitment only when
a `binding_trigger` is satisfied (signed quote/LOI → `proposed`; executed
contract/PO/subscription → `active`).
## Commercial Record
A record in a billing, CRM, or commerce system that tracks payment methods,