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

@@ -91,6 +91,8 @@ Commercial Commitment + Evidence, not declared ad hoc.
subtypes with authority class, ICD scheme, and renewal lifecycle.
- **Counterparty Assurance Gradient** — opinion → observed → committed →
adjudicated; Reputation Signal, Performance Evidence, Adjudication Outcome.
- **Payment Instrument Reference** + **Payment Mandate** — PCI boundary; not Credential.
- **Pipeline Pursuit** — CRM Opportunity before Commercial Commitment promotion.
### Unchanged roots
@@ -103,7 +105,9 @@ Commercial Commitment + Evidence, not declared ad hoc.
Model as lifecycle events, not silent merges:
- Lead → Account (CRM conversion): weak → medium evidence.
- Trial → paid subscription: attach Commercial Commitment + payment Credential.
- Opportunity opened: Pipeline Pursuit — not Commercial Commitment until binding trigger.
- Trial → paid subscription: Commercial Commitment (subscription) + Payment Mandate
+ Payment Instrument Reference.
- Org onboarding → KYC complete: raise Assurance Level, add BO relationships.
- Pseudonym → verified legal person: Synonymity Assertion with strength upgrade and scope change.
@@ -117,7 +121,8 @@ Model as lifecycle events, not silent merges:
## Research Gaps
- Payment Credential vs. authentication Credential boundary in PCI contexts.
- Standard `binding_trigger` enum across CRM adapters.
- Network token (Visa VTS) mapping to Payment Instrument Reference.
- Smart contracts and automated Commercial Commitment lifecycle.
- Synonymity strength bands for LEI ↔ DUNS ↔ company reg crosswalks.
- Cross-platform reputation portability (Synonymity between Reputation Signals).
@@ -136,6 +141,8 @@ Model as lifecycle events, not silent merges:
- `beneficial-ownership-kyc-boi.md`
- `registry-identifier-subtypes.md`
- `reputation-assurance-gradient.md`
- `payment-credential-pci-boundary.md`
- `crm-pipeline-commitment-threshold.md`
- `../commercial-subscription/b2b-saas-subscriber-tenancy.md`
- `../commercial-subscription/stripe-customer-billing.md`