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

Settle commercial identity nuances with consolidated enums and linking rules

Browse source 
Add commercial-identity-nuance-settlement.md resolving control_basis,
binding_trigger, cross-registry Synonymity strengths, OPI branch modeling,
escrow commitment type, reputation portability, payment edge cases, CRM renewal
rules, Person Account adapters, and eIDAS wallet scope. Update canon, OpenQuestions,
and all commercial-identity source notes.
This commit is contained in:
tegwick 2026-06-21 23:21:21 +02:00
parent 6ea582cd9e
commit 08361f6fb7
18 changed files with 403 additions and 64 deletions
Download patch file Download diff file Expand all files Collapse all files

10
research/commercial-identity/payment-credential-pci-boundary.md
View file

@ -153,9 +153,13 @@ Evidence Source → webhooks, mandate PDF, SCA audit
## Open Questions
- Network tokens (Visa VTS) — same Payment Instrument Reference pattern?
- Shared payment methods across Stripe org customers — scope on reference.
- Wallet balances (Stripe Customer balance) — Commercial Record attribute vs. commitment.
*(none — settled in `commercial-identity-nuance-settlement.md`)*
## Settled
- Network tokens → Payment Instrument Reference `instrument_type: network_token`.
- Shared methods → multi Commercial Record link within payment org Scope.
- Wallet balance → Commercial Record `provider_ledger_balance` attribute.
## References