Managing Transactions (Accelerate & Cancel)

On-chain congestion can sometimes cause your transactions to be "stuck" in the mempool if the fee was too low. Planbok provides two management functions—Accelerate and Cancel—to help you resolve these issues using Replace-By-Fee (RBF).

1. Accelerating a Transaction

Use this endpoint to resubmit a pending transaction with a higher fee to prioritize it for miners.

Endpoint: POST /v2/organization/transactions/{id}/accelerate
Headers:

• PLANBOK-X-API-KEY: <your_api_key>

Request Body:

Code
{
  "idempotencyKey": "<unique_uuid_v4>",
  "encryptedOrganizationSecret": "BASE64_CIPHERTEXT_HERE"
}

• How it Works: Planbok reconstructs the transaction with the SAME nonce but a higher gas/miner fee.
• Trustless MPC: Requires your organization secret to re-sign the new version of the transaction.

2. Canceling a Transaction

Use this endpoint to replace a pending transaction with a self-transfer (sending 0 assets to your own address) using a higher fee.

Endpoint: POST /v2/organization/transactions/{id}/cancel

Request Body:

Code
{
  "idempotencyKey": "<unique_uuid_v4>",
  "encryptedOrganizationSecret": "BASE64_CIPHERTEXT_HERE"
}

• Mechanism: This "overwrites" the previous transaction's nonce on-chain, effectively preventing the original transfer from executing.

3. Monitoring Status

After calling accelerate or cancel, you will receive a new transactionHash. You can monitor the progress of the challenge/transaction via:

Endpoint: GET /v2/transactions/{id}

• Status: pending or broadcast: The new version is waiting to be mined.
• Status: confirmed: The replacement has been successful and confirmed on-chain.
• Status: cancelled: The original transaction was replaced by a more recent version (the accelerated/canceled one).

Next Steps

To monitor your organization's assets across all wallets, see the Viewing Assets & Activity guide.