why2 reasons
mandatedestination_not_allowed
op 0 pays GBXSOSF3WMENHH64Z5K52HG2HUDERNKWJ5ZRZDIHVWWFLFGMDH6Y6C5U, which is not in the allowlist
counterpartycounterparty_denied
GBXSOSF3WMENHH64Z5K52HG2HUDERNKWJ5ZRZDIHVWWFLFGMDH6Y6C5U 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
- 28fb2cd3cc877df682c0e58ea73bc06a3a47e29e337f5fa60fd198a850603ca0
- request
- bfd933252b0f51b1645e9fc78a14e2f51fbfd4ac038f2ddeeaa7f5c10ed28378
- transaction
- 388778af8d85de1c9e0c3e40e31e791e26161e815cf8e8e72cd9bba9f41e7374computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65319
the chainentry 65319
- sealed to the entry before
- af44184ba472c0847b6e43e78b22dab1805420ca27dc86e9fee20a98cdcec6d4
- this leaf
- 259ee3a36ae30d4dde1ce8444524d554901c7aad1a51cae55f216a40d871cf9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v9lcbadNw7+QD7wg6BWwdY//nzoPokxMpJ5ODK/12jsWBRrw45rXc9z/lGxPfSIlALfk00Dc9vBKWBSyf77qDw==