why2 reasons
mandatedestination_not_allowed
op 0 pays GBIBEYK5QRG4HMXDP5QLLP5IQVOUHGW7MKTCJXAXNDY5NZPK2K2K3QC5, which is not in the allowlist
counterpartycounterparty_denied
GBIBEYK5QRG4HMXDP5QLLP5IQVOUHGW7MKTCJXAXNDY5NZPK2K2K3QC5 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
- 765a769cba6fb548c1f23b528957dbcce64926a17b457af1432139a39629af2c
- request
- 6b8874605e065c4fa4a5a62c816b107ac0986c5880e0693e6c9b49ca5a5be2db
- transaction
- 393d344d508cccdf321629f44ed436dd7a6abf27547f896ce609886b2c831357computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40359
the chainentry 40359
- sealed to the entry before
- f1effb2e4975f3f6a47ab2b418b49450d7d1e16576015a0cae36295256c944f4
- this leaf
- 8aef7ebfc5757a68e985ec3d75f01891b38d52b66252c7c9ca8d48fd27bf2593
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z+35F8VU1EQyN3z+YzoAoFvPkj9C527kx/r723ceUO2Hja2YGI91VY9t4OJdv2D9URIINTWGTB3HoEDEQCkaCA==