why2 reasons
mandatedestination_not_allowed
op 0 pays GBPHDPGJVMAE4ENFONBX7FOIDM52HVE7KZGPIUTQAZUW7CTHZKPGDEK6, which is not in the allowlist
counterpartycounterparty_denied
GBPHDPGJVMAE4ENFONBX7FOIDM52HVE7KZGPIUTQAZUW7CTHZKPGDEK6 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
- fe2bb9d850e0ca2a755a9620b04969964154546b1d5ee9b053c3459fe3f72990
- request
- 4b766930e5c54b85615d672f626926e22a3e161822f354bc58111901293e558f
- transaction
- 8c8769821eb22c84633de30bbd464c4761b3d33aaefc8bff78bba9c3f3cead10computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56388
the chainentry 56388
- sealed to the entry before
- c6245ff7afd385d90b335819efe9fbacdffb7aa01c4e4ea2007fa3530a877c3e
- this leaf
- cd43d8175c6f8d1580a67a502e77bc090c794daa368774d2d743dbe27a9e4190
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9mCxZSv3uFLu7d+rWuEnR0pHtPYCEIkBfcHNtUeCXuStILtHde7cmkARhj6WpiilDW0zsvwJssm2PpoRcG0mBA==