After a transaction is initiated it moves into an approval workflow. Approvers review the details and either approve or reject it. Once the required approval threshold is met, an Issuer submits it to the blockchain for final signing.
Roles in the Approval Flow
| Role | Responsibility |
|---|
| Approver | Reviews transaction details and approves or rejects the request |
| Issuer | Submits an approved transaction to the blockchain for signing |
Transaction States
| Status | Meaning |
|---|
| Pending Review | Awaiting the required number of approvals |
| Approved | Approval threshold met; ready to be issued |
| Rejected | Rejected by an approver or issuer — will not proceed |
| Signing In Progress | Submitted for MPC signing |
| Issued | Signed and broadcast to the blockchain |
| Errored | Signing attempt failed; can be re-submitted or rejected |
| Scheduled | Awaiting a future execution date |
| Expired | Staking transaction whose launch window has passed |
Reviewing a Transaction
Pending transactions appear in Requests → Transactions. Click any row to open the transaction detail page.
Review the following before taking action:
- Transfer details — source vault, destination address, network, token, and amount
- Estimated fee — network fee in native token and USD equivalent
- Risk assessment — automated security analysis result (Low, Warning, or High) with flagged details
- Initiator — who created the transaction and when
- Approvals — current approvals vs. required threshold (e.g., “1 / 2”)
Approving a Transaction
If you have the Approver role and the transaction is in Pending Review, the Approve button will be available.
If the risk assessment returns a Warning level, you will be prompted to explicitly acknowledge the flagged details before your approval is accepted. Review the risk information carefully before proceeding.
Rejecting a Transaction
Approvers and Issuers can reject a transaction at any point before it is issued. Click Reject on the transaction detail page.
Rejections are final. A rejected transaction cannot be restarted — the initiator must create a new transaction.
Submitting (Issuing) a Transaction
Once the approval threshold is met, the transaction moves to Approved status. Users with the Issuer role will see the Submit button on the transaction detail page.
Clicking Submit sends the transaction to the Fortary MPC signing service. The status updates to Signing In Progress while the signature is being generated. When complete, the status changes to Issued and the transaction is live on the blockchain.
Mobile Signer Vaults
For vaults using the Fortary Mobile App for signing, the mobile device must be online when the Issuer clicks Submit. There is a 5-minute window for the mobile signing app to receive and sign the transaction. If the window expires, the issuance request expires and must be re-submitted.
See Setting Up the Mobile Signing App for configuration details.
Cross-Chain Transfers (Avalanche)
Fortary supports moving certain assets between certain chains in a transfer. More assets and chains will be support automatic cross-chain transfers in the future
Current cross-chain transfers on Avalanche (such as C-Chain to P-Chain) require two separate transactions: an export and a follow-up import. After approving and issuing the export transaction, a second transaction will automatically appear in Pending Review for the import step.
Cross-chain import transactions cannot be rejected. They complete a transfer already in progress on-chain. The import must be approved and issued to recover the assets.
