What can and cannot be reversed
The point of no return for a payment, and what your options are on either side of it.
Version 1.0 · Last updated
When you would read this
Before you approve anything large, and immediately if you think a payment has gone wrong.
The point of no return
A payment can be stopped at any time until the last required signature is given. After that it is broadcast to the network, and it cannot be recalled by you, by your counterparty, or by Stablerail.
There is no pending window in which we can pull it back. There is no reversal, no chargeback and no dispute process on a blockchain payment.
What you can reverse
A request that has not been fully signed. Cancel it from the signing queue. No money has moved.
A request that is still being screened. Cancel it. The compliance check stops and the request is marked cancelled.
A blocked payment. It cannot be sent at all. Reject and archive it.
A draft or unsent invoice. Edit or cancel it.
An unaccepted invitation. Revoke it.
A queued governance change, such as a policy update or quorum change. If it has not collected its signatures, it has not taken effect.
What you cannot reverse
A broadcast payment. Once signed and sent, the funds are gone from your wallet.
A payment to the wrong address. If the address was valid, the funds are at that address. Whoever controls it decides whether to return them. Your only route is asking them.
A payment on the wrong network. Stablerail does not currently check that a recipient address belongs to the network you selected. If you choose the wrong one, the payment is signed and broadcast normally and the funds cannot be recovered by Stablerail or anyone else. Contact your account manager, but treat this as unrecoverable.
A closed card. Closing is permanent. Freeze instead if you might want it back.
An executed fiat transfer. Bank transfers may sometimes be returned by the receiving bank, but that is the bank's decision and not something Stablerail controls. See "Send funds from your fiat account".
How to protect yourself
- Pay from saved counterparty records rather than pasting addresses.
- Never copy an address out of your transaction history. That is exactly what address-poisoning attacks rely on.
- On a first payment to a new address, send a small amount and confirm receipt before sending the rest.
- Check the network on the review screen every time.
- Keep a quorum above one for meaningful amounts. A second reader catches what the first one misses.
