Agree on responsibility before activation.
Shape the working relationship: agree on responsibilities, commercial terms and operating decisions for the partnership you want to build.
A discussion draft your teams can complete.
Use this term sheet to prepare the commercial, privacy and service schedules for the selected relationship. Every entry below is open for agreement. The completed proposal becomes an input to each party’s authorized legal and operational review; this public draft has no signatures or binding terms.
| Schedule | Complete together |
|---|---|
| Parties and purpose | [Legal entities and authorized representatives]; [chosen business case]; [customer group]; [approved workflow and exclusions]; [term and renewal decision]. |
| Commercial proposal | [Deliverables and each party’s owner]; [implementation effort and cost owner]; [pricing unit, currency and invoicing]; [third-party fees and taxes]; [acceptance method]; [change approval]. |
| Data and privacy proposal | [Roles and purposes]; [data categories and permitted users]; [processing/subprocessor locations and approval]; [retention and backup expiry]; [rights-request ownership]; [incident notice procedure]; [export, return and deletion evidence]. |
| Service proposal | [Support hours, channels and named escalation owners]; [severity definitions]; [response and restoration targets to agree]; [measurement source and exclusions]; [maintenance and incident communications]; [tested recovery procedure]. |
| Financial schedule, if applicable | [Authorized provider/program and environment]; [assets and limits]; [execution, custody and settlement owner]; [customer eligibility and disclosures]; [refund/dispute authority]; [provider approval references]. Exclude this scope for non-financial relationships. |
| Legal review and exit | [Confidentiality, intellectual property, liability and dispute terms for counsel review]; [termination and exit assistance]; [revocation and data disposition]; [open items and decision owners]; [controlled original executed document reference after signing]. |
Write the relationship charter.
Identify contracting entities, use case, eligible audience, countries, assets, environments, interface set, volumes and excluded activities. Define whether the relationship is software supply, distribution, data exchange or a regulated financial program. The label “partner” establishes none of these automatically.
- Agree pricing, billing basis, provider fees, taxes, settlement deductions and who bears unresolved differences.
- Review customer disclosures, branding, marketing claims and authorization to represent either party.
- Define confidentiality, data terms, liability, disputes, change approval, termination and exit assistance with the responsible teams.
Proposed responsibility map
This map is a discussion framework, not an executed RACI or agreement. Replace each role with a named owner in the selected relationship. For non-financial integrations, mark financial roles not applicable and exclude their permissions.
| Work | Peyeli review role | Counterparty review role |
|---|---|---|
| Product and application records | Software design and scoped record behavior. | Use case, authorized users and integration mapping. |
| Financial execution / custody | Approved adapter and evidence handling within agreed scope. | Authorized provider/program owner under the agreement. |
| Compliance and customer eligibility | Required software gates and agreed disclosures. | Named legal/compliance authority; no delegation assumed. |
| Incident and settlement operations | Application investigation and exception records. | Provider/source evidence, contacts and authorized resolution. |
| Data, audit and exit | Scoped access/export and agreed technical controls. | Data rights, review, retention requirements and offboarding. |
Commercial agreement is not technical acceptance.
Keep separate approval records for commercial terms, security/privacy, interface acceptance, operational readiness and any financial program. No public fee schedule, liability limit, exclusivity term, live corridor, customer eligibility or service commitment is created by this documentation. These must be explicitly agreed for the selected relationship.
Prepare the shared proposal.
Commercial, data, service and exit schedules to complete and review.