why2 reasons
mandatedestination_not_allowed
op 0 pays GALURHTBTNFL5UJYHNFY5Y2DRNTL3QUSVIYWUA3GUOA5GMQKZ3EOY5HZ, which is not in the allowlist
counterpartycounterparty_denied
GALURHTBTNFL5UJYHNFY5Y2DRNTL3QUSVIYWUA3GUOA5GMQKZ3EOY5HZ 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
- ad04d62ca1ef9a6aa66674718606a96e0d33180c68d58d91900f4999ccaf7312
- request
- 310a6e56545034b31305fa94a2b80fcc701d0c29cf7aac47b33b2ef7c97c7fe0
- transaction
- 11ef6b06aef76d8b37b7578f6ec31782cdc609a35619e6f4b7d241233a274eedcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27403
the chainentry 27403
- sealed to the entry before
- ac94935aced529cb6e710861461518cfd0b74802dd76cc911662e53fa12baf21
- this leaf
- 3e21e85a30189d4f80ee9c826d01bd34114948205cd460af12879c853fb9e652
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yDArEpHIql16KIa4LQZD0t8XerDZiccUmEb3PzUPtEY2KhW9yCFZ9Nby2kRIIL/85JO50Mn5bvR/N5uUrmC2DA==