why2 reasons
mandatedestination_not_allowed
op 0 pays GB5UC22SRVFJIKZNXPYFCSCYPWA63QCVUGZHHEHMLW5WQIA22TRBAA5D, which is not in the allowlist
counterpartycounterparty_denied
GB5UC22SRVFJIKZNXPYFCSCYPWA63QCVUGZHHEHMLW5WQIA22TRBAA5D is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- 07aee5a7f4523135270ad9816b57411c90381d14bcfaf933c6ab668b4943cd9d
- request
- 53e3c7693fdff4fb2ef161a52b37c5d0d1ad04548b182f199921b44be803104f
- transaction
- f9e0f32c7043552ace5e7d19c33ce9a928dd70fd19b1c72ca7df0d86b48b9d9ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70280
the chainentry 70280
- sealed to the entry before
- 4e8fa7cf3e45840ea820961adb618ed36903c5083af29d531b4620a780c5d8be
- this leaf
- 7815097a26cd2a28b8774b42e80226a2a7b85385fd32466326f0eae14d8b903d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gFTqoFtu4zx+FTAC+v/ibg7grW4GsUNyUk042tjOlgzyWGzEk8k1r8Zd2T1kHpv6RALuZm39TDquMC3BQbdoDg==