People and roles
A person may hold one role or several, but SecurePay never assumes two roles are the same thing.
The person or organization who prepared and proposed this agreement version.
It does not mean they fund the agreement, perform the work or approve a release.
Common actions
Acceptance. The creator still accepts their own responsibilities like any other participant.
The participant who connects money to the agreement.
It does not mean they decide alone that a condition is satisfied.
Common actions
Acceptance. Acceptance of the version is required before funding is requested.
The participant who receives an eligible amount when the conditions are satisfied.
It does not mean money is available on request.
Common actions
Acceptance. Yes. A recipient must accept before an amount becomes eligible for them.
The participant who carries out a responsibility.
Performing work does not automatically confirm the condition attached to it.
Common actions
Acceptance. Yes, for the responsibility they are named in.
The participant who supplies a record supporting what happened.
Providing evidence is not confirming a condition.
Common actions
Acceptance. Acceptance of the evidence responsibility is required where it is named.
The identified participant permitted to record a response about a specific condition.
It does not mean they own the money or can move it directly.
Common actions
Acceptance. Yes. The confirmer must accept the condition they are responsible for.
A person with recorded authority who accepts a specific proposal, stage or decision.
It does not mean they performed or witnessed the work.
Common actions
Acceptance. Yes, and their authority must be recorded before it applies.
A named participant responsible for a group purpose and its recorded governance.
An organizer does not personally own contributed money.
Common actions
Acceptance. Yes. An organizer must join and accept the responsibility.
An organizer role focused on the money position and its records.
It does not create authority to release money alone.
Common actions
Acceptance. Yes, and the governance rule still decides what approval is required.
A person contributing towards a group purpose.
Contributing does not grant organizer authority over the purpose.
Common actions
Acceptance. A contributor accepts the published purpose and governance before contributing.
Someone permitted to raise or take part in an Agreement Review.
Raising a question does not decide the outcome.
Common actions
Acceptance. Not separately, but only permitted participants may take part.
A person acting for a business or organization KSNumber under recorded authority.
It does not merge their personal KSNumber with the organization's.
Common actions
Acceptance. Yes. Authority must be recorded and accepted before it can be used.
The party responsible for an application that uses SecurePay as its agreement engine.
It does not make the application an agreement participant.
Common actions
Acceptance. Yes, through the developer terms and production access process.
About the examples on this page
Every example, record and status here is demonstration content and is labelled mock. Sandbox records behave realistically but move no money. Live records come from real activity. These pages are not live customer cases.
