Escrow release via Rules

Hi Aporie,

I need again your support with the release of the version 1.2 of the module, as this last version seems to have changed the way Escrow payments are released, and this is blocking the way my website works. Reading the release notes of v1.2, I guess this is coming from the following new feature:

Implementation of transaction hash so user don't see the transaction ID.

Explanations of my issue:
From the other issues I have posted you know that my website requires to have the commerce funds transactions (Escrows) automated. This automation was done using Rules, thanks to the very great support you did to integrate this module into Rules and the clear tutorial your have also provided as documentation.
The workflow on my website until v1.1 of commerce funds is as follows:

Step 1:
User A posts an ad and offers a single task job to the other users against a given amount of money (decided by User A)

Step 2:
Other users interested to perform this job are postulating to this ad

Step 3:
User A selects one of the postulants (let’s say User B) to perform the job. At that step, the website withdraw from User A account the amount offered for the job (+ fees). This is done automatically using Rules with a pending Escrow triggered when User A validates a postulant selection form. All this is done in accordance with your documentation, with Rules actions Create new transaction (type Escrow) and Perform transaction.
So that User A pays at the start for the service is asks for, but User B doesn’t receive the money yet.
At that step also, my system records the transaction ID of the created Escrow and copy it in a field linked to the published job node for later use.

Step 4:
User B performs the single task job offered by User A

Step 5:
User A fills another form on the website to confirm that the job has been performed by User B. When doing so, the pending Escrow is released/completed and User B gets the money from User A on his account (and fees are paid to the site admin).
This is also done automatically using Rules, with Rules action Page redirect to URL /user/funds/escrow/release/ transaction_id?action=release-escrow, where transaction_id is the transaction ID recorded in the database at step 3. (If done manually, there is a risk that User A confirms the job has been done but doesn’t trigger the payment release to User B, that’s why it has to be automated).

Now since version 1.2, my step 5 is not working anymore, as it seems that the URL /user/funds/escrow/release/ transaction_id?action=release-escrow is no more existing, in order to hide the transaction ID to the user.

At the start I was indeed a bit annoyed to have the transaction ID visible in the URL as somehow it shows the site mechanism to the user. Anyway because the module only allows each user to perform his own issuer transactions and prevents users to act on the transactions of other users, there was for me no security breech. In the worst case if the user is playing with the URL, the only consequence could be that he releases a payment withdrawing money from his own account, which is in the interest of no hacker.

In the end, I think I understand the security improvement which has been done, however I couldn’t find a solution with this new way of handling transaction ID to have the Escrow completed using Rules, allowing User B to get the money at step 5 from the transaction whose ID has been recorded at step 3.

Is there any solution for this issue?
For instance adding a new Complete Escrow action in Rules with the transaction ID as parameter?
Or a new URL to be redirected to, using the hashed transaction ID?

At the moment, I need to reverse to v1.1 and I cannot upgrade to 1.2.

Thanks!