What Happens After You Send a Pactvera

What happens next depends on whether you sent a Pactvera Agreement or a Pactvera Transaction.

A Pactvera Agreement generally involves documents, forms, signatures, reviews, and approvals.

A Pactvera Transaction may also include payments, items of value, inspections, release conditions, payout acceptance, or other transaction actions.

1. Recipients Receive a Notification

After you select Send:

Participants receive an email notification.
The email includes a link to open the Pactvera.
Participants can access their assigned actions on the web or in the ChainIT ID App.

Participants who do not already have a ChainIT ID may be prompted to create one before completing protected actions.

2. Each Party Receives Its Required Actions

The actions assigned to a party depend on how the Pactvera was configured.

Agreement actions

Agreement actions may include:

Signing a document
Viewing or reviewing a document
Completing a form
Providing an approval or acknowledgment
Receiving a copy after completion

Transaction actions

A Pactvera Transaction may also require participants to:

Provide or fund an item of value
Make a payment
Confirm receipt of an external payment
Complete an inspection
Confirm delivery or acceptance
Authorize release
Review and accept payout details
Complete another transaction-specific obligation

Only required actions block completion. A participant who is designated only to receive a copy does not need to act before the Pactvera can be completed.

3. Organizations Assign Actions to Authorized Users

When an organization is a party, the organization receives the Pactvera and assigns its actions to the appropriate authorized users.

Different actions may require different authority. For example:

A Pactvera Signer may complete a document-signing action.
A TCA Releaser may authorize the release of an item or funds.
Another authorized user may complete an inspection, payment, or confirmation task.

Access to the organization or Pactvera does not automatically authorize a user to complete every action. The user must have the authority required for the assigned task.

Click here to learn more about organizational authority in ChainIT.

Individual parties complete their own assigned actions.

4. Participants Complete Their Actions

Each participant generally:

Opens the Pactvera from the notification or My Tasks.
Reviews the request and any applicable disclosures.
Completes the assigned action.
Authenticates the action when prompted.
Submits the completed task.

Actions may be completed:

In a defined order when completion sequencing is enabled, or
Independently when the actions do not depend on one another

Completing a document does not necessarily complete the entire Pactvera. In a Pactvera Transaction, additional payment, funding, inspection, release, or payout actions may remain.

See Understanding Parties and Actions in a Pactvera for more information about parties, assignments, and required actions.

5. Transaction Obligations and Conditions Are Completed

For a Pactvera Transaction, documents and forms may be only part of the execution process.

The transaction may also require:

The item of value to be committed or funded
A payment to be made
An external payment to be confirmed
Delivery or inspection evidence to be submitted
Required documents and forms to be completed
Other transaction-specific conditions to be satisfied

Pactvera treats these as separate parts of the transaction:

Funding commits the item of value to the transaction.
Obligation fulfillment records that a required action, such as payment, has been completed.
Release authorizes the committed value to move.
Transfer or disbursement completes the movement of value to the recipient.

A funded item and a completed payment obligation are distinct states. A transaction may require both before release is available.

6. Required Conditions Are Evaluated

Before value can be released, the transaction checks whether its required conditions have been satisfied.

Conditions may include:

Document execution
Form submission
Funding status
Payment or payment-confirmation status
Inspection or delivery confirmation
Approvals or acknowledgments
Other requirements defined in the transaction

The release action becomes available only after the applicable requirements have been met.

This prevents an item, entitlement, or payment from being released simply because one participant decides to proceed before the agreed conditions are complete.

7. An Authorized User Releases the Value

Once the required conditions are satisfied, the assigned user with release authority can complete the release action.

The item is transferred to the designated recipient according to the transaction configuration.

8. Progress Updates as Actions Are Completed

As participants complete their actions:

The Pactvera status updates.
The sender can track progress from the Sent area.
Participants can view their outstanding tasks.
Completed actions become part of the execution record.
Transaction funding, conditions, release, and payout states update as applicable.

The Pactvera remains active while any required action or transaction stage is outstanding.

9. When the Pactvera Is Complete

A Pactvera is complete when all actions and completion requirements defined for it have been satisfied.

For a Pactvera Agreement

This may include:

Required documents being signed
Required documents being viewed
Required forms being submitted
Required approvals or acknowledgments being completed

For a Pactvera Transaction

Completion may also require:

The item of value to be funded
Payment obligations to be completed or confirmed
Required inspections or delivery actions to be completed
Release to be authorized
Payout acceptance to be completed
The final transfer or disbursement to be recorded

Signing all documents does not complete a transaction when other required transaction actions remain.

Once all completion requirements are met:

The Pactvera is finalized.
Its final execution record is created.
Participants and copy recipients receive access according to their permissions.

10. What the Final Record Includes

The final Pactvera record may include:

Completed documents
Submitted forms
Signatures, approvals, and acknowledgments
Participant and organizational authority information
Action timestamps and execution details
Funding records
Embedded or externally confirmed payment records
Inspection, delivery, or acceptance confirmations
Condition evaluations
Release records
Payout acceptance and disbursement records
Final value-transfer records

The record provides a connected history of:

Who completed each action
What was completed
When it occurred
Where it occurred, when captured
Under what authority an organizational user acted
Which conditions were satisfied
When value was funded, released, transferred, or disbursed

The completed agreement is sealed as its final Pactvera record, called the Valitorum. It preserves the agreement and its execution history together as a cryptographically anchored, tamper-evident record.

11. If Something Is Not Completed

When a participant does not complete a required action:

The Pactvera remains in progress.
Dependent actions may remain unavailable.
Release or finalization may be blocked.
Other independent actions may still be completed.

You may need to:

Follow up with the participant
Ask the receiving organization to assign an outstanding action
Confirm that the assignee has the required authority
Review the transaction status to identify an incomplete condition
Correct and resend the Pactvera if it was configured incorrectly

A Pactvera cannot be marked complete merely to bypass an unfinished required action or transaction condition.