coulomb/commerce-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Resolve payment credential and CRM pipeline commitment boundaries

Browse source 
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:
tegwick 2026-06-21 23:11:00 +02:00
parent bd272151af
commit 6ea582cd9e
11 changed files with 435 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

6
DownstreamRecommendations.md
View file

@ -131,4 +131,8 @@ later explicit package is extracted.
- Map PAYDEX, SLA metrics, and credit bureau data to Performance Evidence (observed tier).
- Map bonds, escrow, and signed SLAs to Commercial Commitment (committed tier).
- Map arbitration awards and court judgments to Adjudication Outcome (adjudicated tier).
- Trust Relationship projections must cite assurance_basis tier; weight opinion weak by default.
- Trust Relationship projections must cite assurance_basis tier; weight opinion weak by default.
- Never store PAN/CVV in identity-layer stores; use Payment Instrument Reference only.
- Map SetupIntent/mandate success to Payment Mandate Commercial Commitment.
- Map CRM Opportunity to Pipeline Pursuit; promote to Commercial Commitment only on binding_trigger.
- Do not treat Salesforce Forecast "Commit" as Commercial Commitment active state.