Editing and Declining Transactions

Supported Providers

• Decline Available: ClearJunction, Clearbank, Railsbank, CurrencyCloud, and Fireblocks.

• Decline Not Available: Bitgo, Litas_sepa (Centrolink) (subject to change).

Ensure Access Rights

• Super Admin Role: Go to Administration -> Administrators and verify you have the "super admin" role.

• Without Super Admin Role: Go to Administration -> Access roles -> Transactions and ensure the following permissions are enabled: List, Create, Edit, Show, Export, and Decline.

Declining a transaction

Initiate the Decline Process

1. Navigate to Banking -> Transactions.

2. Click Edit in a transaction’s actions.

3. Select Decline under the Actions menu.

4. The decline option is only available for transactions with a Completed status.

Provide a Decline Reason

1. Enter a reason in the Decline reason field. The step is mandatory, and the text must fit the range of 3 to 228 characters.

2. Click Decline to complete the process.

Confirmation

A confirmation message will appear, defining that the transaction has been declined.

Declining Specific Transactions and Fees

You can decline only parent transactions or individual fees.

• Example: If a debit transaction of 100 EUR is created, automatically generating two fee transactions and one credit transaction of 100 EUR, only the debit 100 EUR and its associated debit fee can be declined.

• Declining the Debit Transaction: If the 100 EUR debit is declined, all associated transactions will be declined.

• Declining the Fee: If the fee is declined, all transactions related to the fee, including credit fee transactions and interledger transactions, will be declined.

If one or more transactions in the "chain" are pending, the decline will be prohibited. The user must wait until all transactions are completed and then manually attempt to decline them again.