Who is responsible for what
ChatterPay B2B is infrastructure, not a wallet with its own users. The Partner keeps the relationship with the end user; the platform provides the technical capability. This table states where the line falls.
| Area | Partner | ChatterPay B2B |
|---|---|---|
| Contractual relationship with the user | Responsible | Provides the technical capabilities |
| Authentication of the end user | Responsible, in the agreed app or channel | Consumes the claims and evidence it needs |
| KYC, AML and regulatory risk | Responsible by default | Applies the agreed technical controls and policies |
| Infrastructure of the real deployment | Controls the project, IAM, network and operation | Delivers artefacts and architecture |
| Master key and signing of the real deployment | Controls the vault and the signer | Builds the digest, verifies the signature, coordinates the lifecycle |
| Coordinated execution | Authorizes, sets policy | Builds, submits, observes and reconciles |
| Ledger | Consumes results | Keeps the platform's operational ledger |
| Webhooks | Receives, verifies, projects | Emits, signs and retries |
| Blockchain and providers | Defines the approved combination | Adapter, validation, observation and reconciliation |
| Releases | Approves and promotes | Publishes versioned artefacts |
What this means in practice
The Partner is the one with the customers. Identity, onboarding and regulatory obligations stay where the commercial relationship is. The platform never becomes the counterparty to the end user.
The Partner holds the keys. In a real deployment the vault and the signer are the Partner's. ChatterPay builds the digest to be signed and verifies the resulting signature, but cannot produce one on its own.
The platform owns the mechanics. Building the transaction, submitting it, watching the chain, reconciling what settled and keeping the ledger are ours, because that is the part that has to behave identically for every Partner.
Releases are the Partner's decision. We publish versioned artefacts. Nothing reaches a Partner's production because we decided it was ready.